Everything you need to get stuck work shipped.
Every diagram and worksheet from the book, interactive. Plus plain-English AI tools for people who want progress without the tech theatre.
Every diagram. Every worksheet. Interactive.
The companion toolkit for Just F*cking Ship It. Five short sections: the method, the map, the diagrams, the worksheets, and the scripts for when the room fights back. Open what you need, fill it in, copy it out.
Five moves. One circuit.
The whole method on one card each: when to use the move, the question to ask, and the output it must produce. Current only flows when the loop is closed — a stuck project is an open circuit. (Tap the letters to close it.)
The Full Loop and the VOLTS Field Guide — Chapter 1 / Appendix A.
From stuck to shipped.
How work moves from stuck to shipped, in five stages. Open a stage for what to do and where the book takes it on.
Part IStuckThe work has motion, not traction
Chapters 1–4: the boring meeting that decides everything, the social physics of a room, why 'we’re aligned' is often theatre, and the decision that makes delivery possible.
Part IITractionRooms become usable again
Chapters 5–8: confidence as a trained skill, why some people love the stage, the stakeholder who wants to win, and the hidden cost of being nice.
Part IIIDeliveryDecisions turn into work that ships
Chapters 9–12: the one slide that saved the project, surviving being 'the new one', the supplier sales pitch, and the meeting after the meeting.
Part IVPressureThis is where projects get killed
Chapters 13–16: the spec that ate the project, when the plan meets reality, the bad news meeting, and the email that turns a project into a court case.
Part VShippedRepeatable without heroics
Chapters 17–19: deadlines, detours and the point of no return, the moment it ships, and a method you can teach.
The book’s diagrams, working.
Lifted straight from the chapters. Use them live in the room or as a two-minute rehearsal beforehand.
The Fork
Every stuck room must choose. — Chapter 4
‘We will narrow this to the core outcome, so that we can ship something that works in practice, prove it, and decide responsibly what earns its way into the next phase.’
‘We will stage delivery in tranches, so that each tranche earns the next with evidence instead of optimism.’
‘We will park this piece explicitly, so that the team stops paying an attention tax on work nobody has agreed to do.’
Then write the travel version in one breath: ‘We’re doing this so we can ship the core outcome, prove it works, and protect the value.’ Build the full sentence in worksheet B2 below.
The Confidence Loop
Confidence as a trained skill. — Chapter 5
‘Feels like confidence is low because last time didn’t work. What would make this safe enough to try properly?’
‘We’re circling. I think we’re avoiding the decision because nobody wants to own the risk. Let’s name the risk and design around it.’
‘I can see two camps forming. That’s normal. Can we agree what we’re optimising for before we pick a side?’
The Supplier Test
Five questions, in this order. — Chapter 11
‘What’s the one user journey you’d bet your reputation on in our context?’
‘Where does this go wrong?’
‘What would you need from us for this to work?’
‘What would you not recommend we do in phase one?’
‘What’s the smallest proof point we can run in two to four weeks that would make us confident to proceed?’
If the supplier answers well, brilliant. If they get slippery, you have just saved yourself six months of pain and an expensive lesson in optimism.
After the Meeting
The decision either travels or mutates. — Chapter 12
The First 72 Hours
72-hour triage cadence: from issue to learning. — Chapter 18
Keep rolling
Keep rolling. The issue is triaged, fixed and communicated. Users informed where needed, support briefed. Momentum holds — and the update to stakeholders is one clean line, not a play-by-play.
Pause
Pause. A pause is a decision, not a defeat — bounded, owned, with a re-start condition attached. ‘We pause X until Y is true, and we review on Z.’ That sentence keeps a pause from becoming a drift.
Rollback
Rollback. The grown-up option nobody wants to need. If you planned the rollback before launch, this is a controlled move. If you didn’t, it’s a scramble. Plan the first 72 hours. Define day-one success. Know your rollback before you need it.
That structure stops panic, and it stops performance. It turns uncertainty into a series of adult decisions.
The toolkit. Templates you can actually use.
Everything from Appendix B, plus the field templates from the chapters. Open one, fill it in, and the copy-ready version writes itself on the right. Drafts save in your browser — nothing leaves your machine.
Appendix B1One-Page VOLTS Session Sheet
Use when: you have got 45 to 90 minutes, a stuck decision, and a room full of smart people who are about to spend the next three weeks talking in circles.
VOLTS SESSION SHEET Turning discussion into decision, decision into proof, and proof into momentum. — DECISION SENTENCE — We are deciding: [decision] So that: [outcome] For: [who] Trade-off accepted: [trade-off] Owner: [owner] Date: [date] — CONDITIONS TO PROCEED — Fixed: [non-negotiables] Flexible: [can move] Assumptions to test: [assumptions] If ignored, this comes back as: [failure mode] — PROOF PLAN — Next step: [smallest real step] Owner: [one name] Deadline: [date] Proof artefact: [must be showable] Likely blocker: [blocker] Blocker owner: [who removes it] Checkpoint: [date/time] Checkpoint decision: Proceed / Adjust / Stop — CADENCE — Frequency: [rhythm] Next decision required: [decision] What counts as shipped here: [define done] — STORY THAT TRAVELS — Why this matters: [why] What happens next: [next] Rule: if you cannot fill this in by the end, you did not have a decision. You had a discussion. — From Just F*cking Ship It · voltsmethod.com/learn
Rule: if you cannot fill this in by the end, you did not have a decision. You had a discussion. Different product. Different biscuit tin.
Appendix B2Decision Sentence Template
Most projects do not die from bad ideas. They die from sentences nobody can repeat.
DECISION SENTENCE (Visualise & Align) We are deciding [choice] for [user/customer] to achieve [outcome] within [constraint] by [date], while accepting [trade-off]. Quick test: ask three people privately, 'What did we just decide?' Three different answers = you hosted a polite misunderstanding. — From Just F*cking Ship It · voltsmethod.com/learn
Quick test: ask three people privately, 'What did we just decide?' If you get three different answers, you did not Visualise & Align. You hosted a polite misunderstanding.
Appendix B3Conditions to Proceed Map
Use when: the room is emotionally weird, politically loaded, or hiding behind 'risk' as a stop sign.
CONDITIONS TO PROCEED MAP (Own the Obstacles) Fixed (non-negotiable): [fixed constraints] Flexible (can move): [flexible items] Assumptions (challenge politely): [assumptions] Trade-offs we are consciously accepting: We accept […] in exchange for […]. We accept […] to protect […]. Read-back line: ’So the real constraint is X, not "it’s hard". If we honour X properly, we can move. Agreed?' (You are not looking for enthusiasm. You are looking for nods that carry responsibility.) Output line: Conditions to Proceed — for this to move responsibly, the following must be true: [conditions] — From Just F*cking Ship It · voltsmethod.com/learn
Draw it on a whiteboard if you can. If you cannot, write it here and read it back out loud. Half the room only believes reality once it has been said in an adult voice.
Appendix B4Proof Plan Template
One move. One owner. One proof point. A deadline that is not 'ASAP', because that is just another way of saying 'never'.
PROOF PLAN (Launch & Learn) Next step (smallest real step): [step] Owner (one name): [owner] Deadline (date): [date] Proof point (must be showable): [type] Specific: [what will be shown] What will block this: [blocker] Who removes the blocker: [name] by [date] Checkpoint (date/time): [checkpoint] Decision we will make at checkpoint: [decision] Rule of thumb: if the proof point cannot be shown, it is not proof. It is vibes in a Word document. — From Just F*cking Ship It · voltsmethod.com/learn
Rule of thumb: if the proof point cannot be shown, it is not proof. It is vibes in a Word document.
Appendix B5Cadence Template
Pick one. Commit to it. Then protect it. Cadence works when it is predictable: same time, same people, decision-led.
CADENCE (Track & Tune) [option] Decision-led, not update-led. Pre-read is proof points, not status slides. Output: approvals, escalations, trade-offs confirmed. Same people: [who] Same time: [when] Next decision required: [decision] Cadence script: ’What shipped since last time?' ’What are we shipping next?' ’What decision do we need to protect momentum?' ’What have we learned that changes the plan?' — From Just F*cking Ship It · voltsmethod.com/learn
If someone answers 'what shipped since last time?' with 'we had loads of meetings', you are allowed to pause for a beat. Not rude. Just diagnostic.
Appendix B6Story That Travels Template
This is how you stop the decision being undone in side conversations. Two-line version for speed; four-line version when the room is slippery and you need boundaries and proof in writing.
STORY THAT TRAVELS (Story & Spark) — two-line version Why this matters: [why] What we’re doing next: [next] Rule: if you cannot explain it in two lines, you have not anchored reality yet. — From Just F*cking Ship It · voltsmethod.com/learn
Rule: if you cannot explain it in two lines, you have not anchored reality yet. You have written marketing.
Appendix B7Decision Log Template
The boring admin that saves you when someone says, three months later, 'I don’t remember agreeing that.' Keep it lightweight. Keep it truthful. Treat it like insurance.
DECISION LOG Date | Decision Sentence | Owner | Boundary (in/out) | Trade-off accepted | Proof point | Next review trigger | Link (email/artefact) [date] | [decision sentence] | [owner] | [boundary] | [trade-off] | [proof point] | [review trigger] | [link] — From Just F*cking Ship It · voltsmethod.com/learn
Fill one entry per decision and copy it into wherever your log lives. The header row is included so the first entry starts the log.
Appendix B9If You Only Do One Thing
Bring these three questions into your next stuck room. Then end the meeting with a Proof Plan: one move, one owner, one proof point, one checkpoint.
Nothing to fill in — this one is the whole point. Copy it and take it into the room.
IF YOU ONLY DO ONE THING Bring these three questions into your next stuck room: 1. 'What are we actually deciding today?' 2. 'When this ships, what does "good" look like in real life?' 3. 'What’s the real constraint here, not the assumed one?' Then end the meeting with a Proof Plan: one move, one owner, one proof point, one checkpoint. That is how projects stop being a fog machine and start being a delivery machine. — From Just F*cking Ship It · voltsmethod.com/learn
That is how projects stop being a fog machine and start being a delivery machine.
Chapter 6The Five-Beat Update
The update that keeps leadership backing the work. Five beats. Clear. Repeatable. Easy to follow even if someone is half-asleep on Teams.
THE FIVE-BEAT UPDATE (Story & Spark) 1. What’s good now: […] 2. What’s great next: […] 3. What’s risky: […] 4. How we’re solving it: […] 5. What we need from you: […] Then write the ask in one sentence. Make it a decision, not a favour. — From Just F*cking Ship It · voltsmethod.com/learn
Once you know the five beats, you stop improvising. You say what is true, what is next, what could bite, how you are handling it, and what you need.
Chapter 12The Decision Note
You write a note that can survive copy and paste. No essay. No preamble. No context section that breeds interpretation. Just something the organisation cannot accidentally improvise.
DECISION NOTE (Story & Spark) Decision: [decision] Why: [why] Not doing yet: [out of scope for now] Next proof + date: [proof + date] No essay. No preamble. Just something the organisation cannot accidentally improvise. — From Just F*cking Ship It · voltsmethod.com/learn
Send it to everyone who was in the room — and the stakeholders who weren’t. Because if the decision cannot travel, it does not exist.
Chapter 13The One-Page Decision Spec
Split everything into two buckets — must be true to proceed and discover through delivery — then replace the monster document with one page.
ONE-PAGE DECISION SPEC Decision statement: [statement] 3 constraints: [constraints] 3 key journeys: [journeys] Next proof + date: [proof + date] Must be true to proceed: […] Discover through delivery: […] Cut anything not directly tied to a key user journey, a control or constraint, or a proof point. — From Just F*cking Ship It · voltsmethod.com/learn
A 200-page spec does not prevent surprises. It just delays them until they are more expensive.
Chapter 15The Bad News Four
When you need to deliver bad news, do not hide it in slide 12. No warm-up. What’s true, plainly — then a bounded recommendation.
THE BAD NEWS FOUR (Chapter 15) • What’s going well: [something real] • What’s changed: [plain language, no blame] • What the impact is: [trade-offs, not excuses] • What we’re doing about it: [a bounded recommendation] • What I need from you is: [a decision, not a favour] — From Just F*cking Ship It · voltsmethod.com/learn
If you want the deck version, it is two slides: 'What’s true' and 'What we need'. Anything more is usually just your nerves trying to feel busy.
Chapter 16The Record Reset
For the email that is quietly rewriting history. Correct the record. Restate the boundary. Anchor the next proof point. Your job is not to win an email exchange — it is to stop the story being rewritten.
THE RECORD RESET (Visualise & Align + Launch & Learn) Correct the record. Restate the boundary. Anchor the next proof point. Decision: We have agreed to [decision] (boundary: [in or out]). Conditions: This is contingent on [conditions]. Assumptions: [assumptions]. Next proof point: We will review [what] on [date] and decide [decision]. Written to be read. Not aggressive. Precise. — From Just F*cking Ship It · voltsmethod.com/learn
The court-case test: decision, conditions, next proof — written to be read. Not glamorous. Some of the cheapest legal insurance you will ever buy in delivery.
When the room fights back.
The appendix nobody admits they need, and everyone uses. Find the pattern you are seeing, use the script once, then stop talking long enough for the room to respond — that pause is where the truth usually turns up.
C1‘We tried this before and it didn’t work.’Folklore and scar tissue
What’s happening: Scar tissue, reputational protection, or a polite way of saying, ‘I’m not getting blamed again.’
What to do: Do not argue. Convert folklore into evidence.
C2‘We just need alignment first.’Alignment theatre and 'safety' requests
What’s happening: They are asking for safety, not alignment.
What to do: Make alignment decision-shaped and reduce the threat.
C3‘It depends.’ (said with pride)Complexity as identity
What’s happening: Complexity as identity. Occasionally, yes, it genuinely depends.
What to do: Turn ‘it depends’ into a testable fork.
C4The risk person says no (and everyone panics)Risk panic
What’s happening: ‘No’ usually means ‘not enough information to say yes safely.’
What to do: Convert ‘no’ into conditions and a proof step.
C5‘We don’t have capacity.’Capacity as a weapon, or a fact
What’s happening: Either real, or a refusal disguised as a fact.
What to do: Trade capacity openly. Aim for steps that reduce future load.
C6The sponsor goes missing right when it gets hardSponsor disappearance
What’s happening: Optimism-phase sponsorship. Trade-off-phase disappearance.
What to do: Force a decision slot or accept the slip explicitly. No limbo.
C7The supplier tries to steer the decision (politely)Supplier steering
What’s happening: Their product wants to become your problem definition.
What to do: Re-anchor outcome and constraints before solutions.
C8The meeting after the meeting undoes everythingSide-room sabotage
What’s happening: The decision did not travel, or travelled badly.
What to do: Send a written record that is hard to reinterpret.
C9Everyone agrees in the room, then nothing happensVerbal agreement, no movement
What’s happening: Verbal agreement, no operational commitment.
What to do: Force ownership and proof.
C10The loud person dominates the roomOne voice running the room
What’s happening: Status protection, anxiety, or performance.
What to do: Change the room mechanics, not the argument.
C11The nice culture that kills decisionsNiceness turning into drift
What’s happening: Drift disguised as kindness.
What to do: Name the trade-off out loud and price the delay.
C12The project is green but everyone feels sickStatus theatre
What’s happening: Status theatre.
What to do: Ask for evidence, then reset to reality.
Build a better AI prompt in two minutes.
Not sure what to write? Perfect. Pick the closest business goal, add a few messy details, and this builder will turn it into a useful prompt for ChatGPT, Claude or your preferred AI tool.
Pick the goal. Add the mess. Generate the prompt.
Start broad, then narrow it down. You do not need the perfect answer — just enough context for AI to be useful instead of confidently vague.
Copy this into ChatGPT, Claude or your preferred AI tool.
Pick a goal, choose what sounds familiar, add any rough notes, then generate your prompt.
Give context
Bad: Write me a sales email.
Better: explain who you are selling to, what you offer, why they care and what action you want.
Give constraints
Tell AI your budget, team size, tools, deadline and what not to do. Otherwise it may recommend a spaceship when you asked for a bike.
Ask it to challenge you
Do not just ask AI to agree. Ask what could fail, what assumptions are weak and what you should test first.
Start here if AI has entered the chat and everyone is pretending to be calm.
You do not need to become technical overnight. You need enough clarity to make good decisions, avoid wasting money and stop letting shiny software drive the bus.
Pick the business headache. Run the tool. Leave with a clue.
The toolkit gets you moving. The book installs the method.
Just F*cking Ship It: The five-move method to get stuck work shipped — out 28 September 2026. Every tool on this page comes from its pages: the stories, the scripts, the scar tissue and the method that turns stuck rooms into shipped work.
