Don’t start the next step until you’re ready

Starting too early is one of the most expensive mistakes

Launching before enough people have tested, building before the design is approved, ordering parts before the budget is confirmed: most project problems come from moving on before something was actually ready. Deadlines don’t catch this. Checkpoints do.

How it works in Flowboard

1. 1

   Place a gate

   Add a gate from the Checkpoint menu between the steps it should hold back, and write what it’s waiting for, over several lines if needed.

2. 2

   Choose its condition

   A gate can wait for a step to be complete, a date to be reached, all materials to be purchased, a metric to reach a number, or for you to mark it yourself.

3. 3

   Plan both outcomes

   Connect what happens when the gate passes (Yes path) and, if you like, a fallback for when it fails (No path).

4. 4

   Let the board keep watch

   Held-back steps show what they’re waiting on, and starting one early asks you to confirm.

When to use it

• A launch depends on a number, like beta users or pre-orders
• Work can’t start until something is approved or delivered
• You want a plan B written into the plan
• Marking the big moments between phases (milestones with dates)

Common questions

What’s the difference between a gate and a milestone?

A milestone marks a big moment with a date. A gate is a milestone with a condition: the steps after it wait until that condition is met.

Can a gate depend on a number?

Yes. Track a metric (sales, sign-ups, hours, money or a percentage) and set the gate to open when it reaches your target.

Related