Service / Operating cadence
The same meeting again. Still no decision.
Decide what needs a meeting, what can happen in writing, and how people keep track of what they agreed to do.
Discuss this workBest fit
Who it is for
Founder-led teams with more work crossing between people. Leaders need to make decisions and catch problems without calling a meeting for every question.
The aim
Meetings that produce decisions, with owners and next steps people can find.
Common problems
Does any of this sound familiar?
- The same priorities are discussed in several meetings but still do not become coordinated work.
- Important decisions arrive late because the right people were never in the same conversation at the right time.
- Weekly updates describe activity, while unresolved commitments and risks remain hard to see.
- The founder keeps explaining the same background because it is not recorded anywhere useful.
Method
Build around the work people actually need to do.
Review recurring meetings: who attends, what they need beforehand, and what gets decided. Find the gaps and repetition.
Agree which meetings to keep, how people prepare, and where decisions and follow-ups are recorded.
Try the schedule on current work. Adjust what breaks when people are busy or priorities change.
What the work can include
Documents and tools the team can use.
These are examples. The scope determines what we agree to deliver.
- A clear view of the current meeting and decision rhythm
- A purpose and working rules for each recurring meeting
- Simple agenda, preparation, and follow-through templates
- A record of decisions and commitments the team can keep up to date
- Short instructions for the people running the meetings
How the work moves
Start small, then adjust.
The steps below are a guide. Timing depends on the scope, who is available, and what we find.
- 01
See the current rhythm
Understand where work is reviewed, where decisions stall, and which conversations already earn their place.
- 02
Agree what needs a meeting
Agree who attends, what they prepare, and what each meeting needs to decide.
- 03
Run, learn, and adjust
Try it with current priorities. Adjust it to the time and attention people actually have.
Operating-system map
How priorities become finished work.
Priorities guide decisions. Reviews show what is moving and what is stuck. What you learn changes the next plan.
What to look for
What a useful change could look like.
- A leadership forum ends with named decisions, owners, and next review points rather than a general recap.
- A priority review distinguishes blocked work, decisions needed, and work that can proceed without leadership attention.
- Team members can tell which questions belong in which forum and which can be resolved without convening a meeting.
- The recurring calendar reflects the work that needs coordination, not a legacy collection of status meetings.
Boundaries
What this work does not replace.
- It does not replace leadership judgement, difficult people conversations, or decisions that only the team can make.
- It is not a promise that every meeting becomes short or that all uncertainty disappears.
- It does not require a wholesale organisational redesign; the work stays focused on the rhythm that is useful now.
Questions
FAQs
Do we need to replace every meeting?
No. The starting point is to understand the work each meeting supports. Some forums may stay intact, some may need a clearer purpose, and some may no longer be needed.
Can this work if our team is distributed?
Yes. Preparation and updates can happen in writing. Use time together for the decisions and conversations that need it.
What if the immediate problem is one high-stakes initiative?
Start there. Agree how to review progress and make decisions, then see which parts are useful for the next project.
Start with the problem