Build a Delivery Playbook So Quality Doesn't Depend on You

Extracts what you actually do on an engagement into a playbook someone else can follow, including the judgement calls that usually stay in your head. Use it before hiring, and before you become the bottleneck you already are.

0 likes 0 dislikes
Sign in to rate this prompt

Prompt

    You are helping a services-firm founder document how delivery actually
works.

The engagement type to document: {{ENGAGEMENT_TYPE}}
How I currently run it, in as much detail as I can give: {{HOW_I_RUN_IT}}
The points where I make a judgement call rather than follow a step:
{{JUDGEMENT_POINTS}}
What has gone wrong on past engagements of this type: {{PAST_FAILURES}}
Who will use this playbook and their experience level: {{WHO_WILL_USE_IT}}
Tools, templates and assets that already exist: {{EXISTING_ASSETS}}

Work only from the numbers and facts I supply. Do not invent
utilization rates, benchmarks, salary figures, industry averages or market data.
Where a calculation needs an input I have not given you, write [NEED: ...] rather
than assuming a value.

The hard part is not the steps - it is the judgement. Most playbooks document
the procedure and omit the reasoning, which is why the person following it
produces something that is technically compliant and wrong. Interrogate my
judgement points specifically: for each, what am I actually weighing, what
signals am I reading, and what would I do differently in the two or three
common variations?

Produce:
1. **Phases**, with entry and exit criteria for each - what must be true to
   start, and what must exist to be finished.
2. **Steps within each phase**, with who does them and roughly how long.
3. **Decision points**, written as the question being answered, the signals to
   read, and the options - not as a single prescribed answer.
4. **Artifacts and templates** produced at each stage, and which already exist
   versus which need creating.
5. **Quality gates**: what gets checked, by whom, before it reaches the client.
6. **Known failure modes** from my history, each with the early warning sign and
   the response.
7. **What still requires me**, named explicitly, with a note on whether each is
   genuinely irreducible or just undocumented. Most founders find that list is
   shorter than they assumed.

Flag anything I described too vaguely to be followed by someone who has not
watched me do it.

Like this prompt?

Create an account to copy this prompt, create your own, and find the best prompts to scale your business.