A pull plan is only as good as the weeks after it. A short, steady weekly meeting keeps it true.

Every week (30 minutes)

  1. Look back. For each note due last week: done or not? Tick off what's done. For what isn't, ask why: with the Pull Plan Coach on, pick the reason under its check-in, in one click.
  2. Look ahead three to six weeks. What's coming, and what's in its way? Clear the RAIDD items that block next weeks' work, or give them an owner and a date.
  3. Commit to next week. Each person promises only what they can actually do: the work is ready, the information is in, the people are free.
  4. Update the Timeline so it shows the plan as it really is now.

Learn from the misses

  • Track how many of last week's promises were kept. The number matters less than the trend, and the reasons behind each miss: the coach's Why promises slip chart adds them up.
  • Misses usually repeat: waiting on information, a decision, another discipline, or too much work at once. Fix the cause, not the person.
  • If the milestone is at risk, don't quietly slide it. Pull the remaining work again with the team.

Where this lives in 7SecondOS

  • Each person's notes appear in their Notebook → Project Tasks, grouped by when they're due, where they can tick them off.
  • @mention someone in a comment when you're waiting on them. See Comments and @mentions.
  • A Portfolio's Team load shows who is overloaded across projects before they miss a promise. See Portfolios and Team load.
  • Ask Project Intelligence "What's due next week, and what's blocking it?" before the meeting.
  • Switch on the Pull Plan Coach on the project's Overview: every week it posts the promises kept and missed, what's due, and what's blocking it, so the meeting starts from the facts. See The Pull Plan Coach.