What a 12-week build actually cuts

Every fixed timeline is a series of trade-offs. Here are the ones teams regret.

12 week build
FIG. 00 — 12 week build

Twelve weeks is a budget, and it gets spent whether or not you decide how when you build.

The happy ending of that conversation happens in week 1, deliberately, with key stakeholders present. The tragic ending happens in week 9, over email, while your team waits.

The 3 questions that make the cuts obvious

  1. Which single user journey has to work on launch day? Name one. An example of a user journey: sign-ups.
  2. What breaks the business if it’s wrong? Money, permissions, regulated processes.
  3. What are we willing to do manually for 3 months? Onboarding, invoicing, support and provisioning could all be examples.

Most of what founders ask us to automate in week 2 turns out to happen 4 times a month and take 11 minutes.

Good brisket needs fat. Bad brisket has too much of it. Same goes for digital solutions. Book a free discovery call, and we’ll help you figure out which is which before you build.

Studio137

Continue reading

The Signal Desk Briefing

Stay close to the signal.

A concise monthly briefing on technology, design and the business systems connecting them. Delivered straight to your inbox.

One useful briefing each month. No noise.