Evidence
Review stakeholders, decisions, governance cadence, delivery artifacts, risks, and dependencies.
- 01Interview notes
- 02Decision-rights evidence note
- 03Artifact review note
Read this before you open the calendar. The rules say what I refuse. The rhythm is what your team can hold me to, for client delivery, programme leadership, or training. Commercials live on the fees page.
Each rule protects the sponsor, the delivery team, and the handoff state.
A pilot is useful only when it proves a decision, risk, or operating condition.
I read decisions, governance records, delivery artifacts, risks, and dependencies before recommending a path.
Engagement shape, access, decision rights, and handoff conditions are confirmed before work starts.
If you need a specialist implementer, a hands-on builder, or a different geography, I will say so early.
A decision log, risk register, plan, steering note, or problem description is more useful than a pitch deck.
The output must be readable without me in the room: owners, risks, options, decisions, and handoff conditions.
If access, decision rights, or accountability are structurally missing, the mandate is not ready.
“Evidence first. Decision rights explicit. Handoff written.”
See the rhythm ↓The rhythm is the same for every mandate: gather evidence, map control, write the sponsor decision, then agree whether client delivery, programme leadership, or training should continue.
Every engagement starts by clarifying evidence, decision rights, delivery risks, partner alignment, and handoff conditions. Client delivery, programme leadership, and training are scoped separately when geography, contracting, sponsor access, and decision rights work.
Review stakeholders, decisions, governance cadence, delivery artifacts, risks, and dependencies.
Map ownership gaps, delivery risks, dependencies, escalation paths, and partner alignment.
Prepare bounded options, named owners, handoff criteria, and the sponsor decision note.
Continue only under an agreed client delivery, programme leadership, or training mandate.
Every artifact is a file your team can open, challenge, and carry into steering, procurement, SI governance, or handoff.
Findings, options, owners, risks, and recommended decision path.
Open risks, dependencies, owners, escalation path, and delivery impact.
Decision rights, accountable owners, unresolved gaps, and handoff conditions.
If yours is not here, raise it on the call. Scope is confirmed before work starts.
Bring the decision context, current artifacts, or a plain-language description of the problem. The call names whether client delivery, programme leadership, or training fits, and whether I am the right person.