It’s the weeks your work spends waiting in the seams between disciplines, where nothing is logged. In two weeks, I’ll tell you how many weeks you’re losing and what it costs at your burn rate.
Crunch is not a fix. It’s what a studio does when it finds out too late.
RAFT is the method. The Flow Diagnostic is the measurement that tells you whether you need it. You can buy the number without ever adopting the method.
Step 1: Connect the Work
Identify what you’re delivering together, what each team contributes, and when each team should begin relative to the others. One deliverable, multiple teams, complete visibility.
Step 2: Progress Triggers Action
Step 3: Work When Ready
Teams work simultaneously on the same outcome, pulling work when they’re ready. No waiting for handoffs, just visible progress, unified momentum, and naturally faster delivery.
Multiple disciplines working the same content against a fixed ship date. Most useful when someone senior already suspects the schedule is leaking and cannot prove where.
Single-discipline teams under twenty people, because there are no seams to measure. Outsourcing shops, because waiting is billable.
Start with the Flow Diagnostic: in two weeks you’ll know where the waiting is and have a 90-day plan your team can run on its own. Want the worst seams closed with Jon in the room? That’s the Flow Sprint. Unsure where you fit? Book a call.
Read-only access to the tracker you already use. At the end you know what percentage of your calendar is spent waiting between teams, what it costs at your burn rate, and which three seams are worst.
Once you know where the schedule goes, this is the engagement that closes the worst seams.
A short course in flow-based delivery for the rest of the team. A course, not a certification.
Ask any questions. jon@raft.works
No. The diagnostic reads what is already in your tools and reports what is true regardless of how you run. RAFT is a technique you can layer on afterward if the findings suggest it, and plenty of studios never do.
No. If you never use RAFT, the number is still the number.
Read-only access to your tracker. Nothing else. No build access, no repo access, no telemetry, and no changes to how your teams work.
Software does the measurement. The analysis and the readout are mine. I am not going to hand you a model’s opinion about your studio.
No. Everything runs from a read-only export and a video call. If you want the readout delivered in person, I will fly to you.
Usually it’s the opposite. While cuts are still happening, I’d wait. Findings get read as ammunition, and nothing gets fixed. But six to twelve months out is often the best moment to do this: the seams a reorg opened up are still visible, the team can feel them daily, and leadership has the mandate to close them. If you’re not sure where you sit, the 30-minute call is the cheapest way to find out.
