This page has one job: show you the whole method on a single page before you meet any of it in detail. It is the map — the four steps every initiative runs and how the pieces fit. (The next part, the weekly rhythm, zooms all the way into a single week; this one stays at altitude.)

Scaleflow is a small number of moving parts that fit together in one repeating shape. Building software is not a linear path, and uncertaintyUncertaintyWhat the team does not yet know — sized and tracked deliberately rather than hidden inside estimates. is a certainty — so the shape is not a plan that survives contact with the work. It is a rhythm for learning faster than the plan goes stale. Learn the shape first; every later part is a zoom into one piece of it.

The canonical workflow

The method is a four-step workflow that you run, then run again.

  1. Write an Initiative DocumentInitiative DocumentThe PR/FAQ-shaped document where an initiative's context lives — customer, solution, plan, business case, and success metrics.. Name the customer, the problem, the solution, the timeline, the team, the business case, and the success metrics. This is the north star for the whole effort — the thing a new joiner reads to get up to speed.
  2. Plan it with the team into an Approach. Translate the document into a multi-week Approach: a narrative roadmap with one demo per week, planned backwards from the end.
  3. Recruit a Product BoardProduct BoardTwo or more stakeholders who see the team's weekly demo and coach it — the human in the loop, with no single lead.. Two or more advisors who will see the team’s weekly work and give feedback — between them a specialist, a critic, a decision enabler, and a customer connection.
  4. Run a weekly team rhythm. Week Planning opens the week, a Daily Check-inDaily Check-inA 15-minute daily ritual where the team surfaces reality and unknowns rather than reporting status. plus optional Collab time carries it, an optional Dry Run sharpens it, and a Board Meeting closes it with a real demo.

That cycle repeats. It is the same loop whether you are at week one of a proof of concept or week forty of a settled product.

The four steps also map cleanly onto how an effort matures. The first two — write the document, plan the ApproachThe ApproachThe multi-week narrative roadmap — titled weekly outcomes ("The one where…"), each with a demo, planned backwards from success. — are inception: mostly thinking, mostly the Initiative AuthorInitiative AuthorThe person accountable for an initiative's context — they write and keep the Initiative Document honest.. The last two — recruit the board, run the rhythm — are where the full Team comes in and weekly delivery begins. You do not finish step one before starting step two; the document and the Approach grow up together, and both keep changing as the rhythm teaches the team things it did not know at the start.

How artifacts, roles & rituals fit

Three kinds of thing do three different jobs, and they only work together.

  • Artifacts hold context. The Initiative Document, The Approach, the Daily Check-in, and the Uncertainty ListUncertainty ListThe team's living list of open unknowns — sized 1/3/5, phrased as questions, reviewed daily and in planning, chipped away each week. carry the shared picture of what we are doing and why.
  • Roles hold accountability. The Initiative Author, the Initiative OwnerInitiative OwnerThe role accountable for keeping an initiative on track — owns the Initiative Document, the Approach, the team, and the board., the Team, and the Product Board carry the responsibilities — these are responsibilities, not job titles.
  • Rituals hold the rhythm. Week Planning, the Daily Check-in, the Board Meeting and the rest set the pace.

Each ritual reads from and writes to an artifact. Week Planning updates The Approach; the Daily Check-in feeds the Uncertainty List and produces Lessons Learned; the Board Meeting holds the team accountable to the demo The Approach promised. That coupling is what keeps the documents alive instead of stale — and it is what stops work degenerating into a Banana, a task with no visible link to a real outcome.

The point of separating the three is that no single artifact, role, or meeting carries the whole method. Context without accountability drifts; accountability without rhythm burns out; rhythm without context is just busywork. Scaleflow works because the three reinforce each other every single week.

A mental model

An initiative is a multi-week story. Each week is a chapter titled “The one where we…” — the one where we validated with ten users, the one where we shipped v1. Read the chapter titles end to end and they should make a coherent story. Each day, every person commits to one thing they will figure out: a single Things to Figure OutThings to Figure OutEach person's one thing to figure out today, framed as a Why/How/What/When question that resolves into a Lesson Learned. (TFO) question that resolves into a lesson by the next Check-in.

The three scales nest:

  • The initiative is the whole story — a customer, a problem, a solution, a destination, captured in the Initiative Document.
  • The week is one chapter — a single titled outcome the Team can demo, captured in The Approach.
  • The day is one sentence — one question per person, captured in the Daily Check-in as a TFO.

This is why the plan is built backwards. You start from the final chapter — success, lifted straight from the Initiative Document — title it, then work back week by week until you reach today. A story planned forwards tends to wander; a story planned backwards stays pointed at the ending.

Initiatives layer over each other

One more thing the map has to show: a team rarely runs just one initiative. Several run at once, started and finished at different times — one in inception, one mid-delivery, one winding down — and the Team holds them all in a single week rather than keeping a separate calendar per effort. That is why the weekly rhythm blends initiatives into one week, and why the Team’s composition shifts as initiatives move through their phases. The mechanics of that blended week are the next part’s job; here it is enough to know the shape repeats per team, not per initiative.

A reader’s map

From here the parts zoom in, each into one piece of this shape: The Big Picture finishes with the roles and the weekly rhythm; then the artifacts that carry context, the rituals that set the pace, how it all stretches across quarters and years, and the tactics for the problems you hit along the way.