Advisory Sprint
Fixed-fee, written-briefing output. Best for vendor selection decisions, second opinions on a program, or restructuring advice.
Services
Four services. Each named for the work, not the sales pitch.
Most engagements combine two. All are delivered personally. Below is what each one actually is, when you'd engage me, and what "done" looks like.
What this is
I step into programs as the accountable delivery lead. That means running the plan, chairing the steering committee, writing the status report, and making the judgement calls between the two.
I work in Agile, Scrum, SAFe or traditional waterfall — the method follows the environment, not the other way around. PMO teams, delivery partners and vendors report into me.
What you get
- A re-baselined plan with trade-offs named and approved
- A governance model collapsed to the minimum effective number of forums
- Weekly written status — specific, honest, and readable in three minutes
- Risk, issue, dependency and assumption registers that reflect reality
- A delivery cadence your team can operate after I leave
When to engage me
- The program is red or amber and the reporting says green
- A senior PM has left and the program is drifting
- You're launching a regulatory or board-reported uplift program
- You need an independent voice on a program you already own
Typical engagement
Three to twelve months. On-site where required, hybrid otherwise. Fixed fee for discovery; time and materials or milestone-based for delivery. Day rate on request.
What this is
Process mapping, service blueprinting, requirements elicitation, user research, and the unglamorous work of writing it all down in a form engineering, design, risk and executive can sign off on.
I combine classic BA craft (BABOK, IIBA) with service design methods (journey mapping, service blueprints, stakeholder mapping). The output is always a written artefact — not a workshop that left the room.
What you get
- Current-state and target-state process maps
- A service blueprint covering front-stage, back-stage and supporting systems
- Prioritised requirements or user stories, traced to business outcomes
- A stakeholder map with positions, interests, and escalation paths
- A written decision log for every scope call made along the way
When to engage me
- A program is about to start and nobody can describe what's actually being built
- A service is operationally painful and you need the shape of the problem named
- A vendor RFP needs a requirements foundation that won't collapse on contact
- You're inheriting a regulatory obligation and need to scope the response
Typical engagement
Four to sixteen weeks. Fixed fee or time and materials depending on scope clarity. Output is a written deliverable you own.
What this is
Short, focused engagements where a senior leader needs an independent view: on a vendor selection, a restructure, a program their team can't critique objectively, or a technology direction the board is about to commit to.
The output is a written briefing paper — options, trade-offs, recommendation, and the reasoning. No decks that need interpretation. No findings that require a follow-on engagement to action.
What you get
- A written briefing, typically 10–20 pages, signed by me
- A clear recommendation with the cost of each alternative named
- An executive summary suitable for board or committee tabling
- A 90-minute debrief session and follow-up Q&A
When to engage me
- You're about to sign a major vendor contract and want independent validation
- An internal program needs a second opinion before the next stage gate
- You're restructuring an IT function and want a sounding board outside the org
- A board member has asked a question you don't have a defensible answer to
Typical engagement
Two to four-week advisory sprints. Fixed fee. Confidential by default, contracts available under NDA.
What this is
A structured review of a program's plan, governance, risks, dependencies, financials and team — delivered as a written report with findings, root causes and recommendations.
Not a "gateway review" template with boxes to tick. An actual diagnostic, conducted by a practitioner who has run programs like yours.
What you get
- An independent assurance report with a traffic-light summary and narrative findings
- Root-cause analysis on each material finding — not just symptoms
- Prioritised, actionable recommendations with suggested owners
- A verbal walk-through with sponsor and program leadership
When to engage me
- A program is reporting green and you suspect it isn't
- A stage gate is coming up and leadership wants an independent view
- A new sponsor has inherited a program mid-flight
- An internal audit or risk function has flagged concerns
Typical engagement
Three to six weeks, fixed fee. Conducted discreetly when required.
Engagement models
Commercial structures that match the work.
I don't pitch a single retainer shape to everyone. Pick the one that suits the engagement — I'll tell you honestly if it's wrong for what you're asking for.
Project Delivery
Full-time or majority-time program delivery leadership. Time and materials or milestone-based. Most common engagement shape.
Retainer Advisory
Ongoing trusted advisor to a CIO, COO, or program sponsor. Fixed monthly fee, agreed cap on hours. Quarterly reviews.
Workshops & Discovery
Single-day or multi-day facilitation — stakeholder alignment workshops, program discovery, leadership offsites.
Not sure which service fits?
That's a good reason to book a discovery call. I'll tell you honestly what shape of engagement would actually help — or whether you need one at all.