Evidence-based selected work and illustrative project methods. Designed for prospective consulting buyers; academic and research collaborators; scoped around source evidence and specific commercial or operational decisions.
Selected Work & Case Studies is assessed through a defined research question rather than a generic claim of expertise. The proposed scope is evidence-based selected work and illustrative project methods. Work starts with the decision to be supported, the accountable decision-maker and the records available for review. The project brief identifies assumptions, evidence quality, access limits, relevant time horizons and matters requiring independent specialist validation.
A selected-work entry should start with the decision problem, work undertaken, source period and type of output. Separate the consulting process from client results. Anonymized examples must still avoid reidentification through details of industry, geography or unusual facts.
Record the actual contributor role, artifacts demonstrating the work, review status, consent to publish and whether statements can be corroborated. Training exercises, hypothetical methods, historical articles and live-client assignments should never appear in the same category without clear labeling.
Use a consistent six-part case outline: initial question; permitted source corpus; analytical method; deliverable and decision handoff; boundaries and unresolved assumptions; publication permission. No confidential case or quantified impact is asserted on this page without permission and original evidence.
The following are illustrative research formats, not assertions that a particular engagement or deliverable has already been completed.
The permissioned case-study register describes which evidence must be collected, its origin and review status, applicable commercial assumptions and the open decisions. It is intended to be reviewed with the project sponsor, not accepted as a certification, legal ruling or claim of future performance. Final scope depends on available records and agreed confidentiality arrangements.
The project-method summary describes which evidence must be collected, its origin and review status, applicable commercial assumptions and the open decisions. It is intended to be reviewed with the project sponsor, not accepted as a certification, legal ruling or claim of future performance. Final scope depends on available records and agreed confidentiality arrangements.
The role-and-evidence matrix describes which evidence must be collected, its origin and review status, applicable commercial assumptions and the open decisions. It is intended to be reviewed with the project sponsor, not accepted as a certification, legal ruling or claim of future performance. Final scope depends on available records and agreed confidentiality arrangements.
Identify the precise business or technical decision, relevant evidence owner, published standard or source version and unresolved assumptions. Compare alternative interpretations, document the limitations of available data and specify what must be reviewed before a claim can be relied upon.
Identify the precise business or technical decision, relevant evidence owner, published standard or source version and unresolved assumptions. Compare alternative interpretations, document the limitations of available data and specify what must be reviewed before a claim can be relied upon.
Identify the precise business or technical decision, relevant evidence owner, published standard or source version and unresolved assumptions. Compare alternative interpretations, document the limitations of available data and specify what must be reviewed before a claim can be relied upon.
Describe the problem, intended use, decision owner and territorial scope; agree which facts would change the decision.
Map public standards, original contracts, product specifications, data, stakeholder interviews and available records. Timestamp versions and permissions.
Test alternatives against explicit criteria such as cost, novelty, operational impact, implementation dependencies and review effort.
Produce a source-linked memorandum or matrix with assumptions, limitations, specialist referral points and practical follow-up decisions.
Professional profile content should not overstate outcomes, the scope of past engagements, universal jurisdictional authority or publication permissions. An evidence ledger identifies which claims can be backed by primary records and which should stay out of public copy until reviewed. This page explains a working model and not a collection of invented client case studies, awards or testimonials.
Avoid named clients, outcomes, roles or confidential cases unless independently supported and permitted.
External links are starting points for dated primary-source review, not substitutes for issue-specific verification.
Define the immediate decision, the relevant sources and stakeholders, the applicable time frame and the proposed evidence record. An initial scope may include source verification, confidentiality, attributable deliverables.
No. Avoid named clients, outcomes, roles or confidential cases unless independently supported and permitted. Professional opinions, certifications and specialist assessments require separately qualified parties and supporting facts.
Share the specific question, intended decision, technology or commercial context, relevant geography and expected output. Avoid sending confidential material before an appropriate process is agreed.