The Weekly Team Meeting that replaces fifteen confused conversations

Ninety minutes. Seven fixed segments. Same day every week, same time, same agenda. The meeting is the rhythm that lets a UK service team self-coordinate without every question landing on the owner's desk. Here is how the BOS UP Meetings competency actually runs.

Where to start

By Roy CastlemanPublished 19 April 2026

The Weekly Team Meeting (L10-Style)

The BOS UP Meetings competency applied to UK owner-managed service businesses. A ninety-minute Weekly Team Meeting held same day, same time, with a fixed agenda of seven segments: Segue (5 min), Data (5 min), Rocks (5 min), Headlines (5 min), To-Dos (5 min), Issues (60 min), Conclude (5 min). Issues are resolved using the Raise-Discuss-Resolve framework. One structured meeting replaces fifteen scattered ad-hoc conversations. Roy Castleman teaches this as the single highest-leverage change a small service business can make.

One structured meeting, fifteen fewer confused conversations

A UK service business without a weekly meeting rhythm runs on corridor conversations, Slack threads, and the owner's availability. Fifteen separate questions arrive across the week. The owner answers them in fifteen separate moments, usually while doing something else. The context switching is exhausting and the answers are inconsistent, because the owner's mental state changes across the week and the fifteenth answer is not as clean as the first.

The Weekly Team Meeting is the structural fix. Ninety minutes, same day every week, same time, same agenda. All of the week's small coordination work happens inside that one window. The team arrives prepared, which is the precondition that makes the meeting useful. The owner arrives regulated, because the rhythm means they know exactly what to prepare. Issues surface in the five-minute Data and Rocks segments, and resolve inside the sixty-minute Issues segment. What would have been fifteen distracted conversations becomes one focused session.

This is the single highest-leverage change a small service business can make. If you do nothing else with BOS UP, run your Weekly Team Meetings the BOS UP way.

The seven-segment agenda

The agenda is fixed. The timings are fixed. The order is fixed. The discipline is in the repetition, which is why the same seven segments run every single week.

Segment	Time	Purpose
Segue	5 min	Personal best plus professional best. Transitions everyone from "in" the business to "on" the business.
Data	5 min	Quick scorecard review. Any KPI off target becomes an issue.
Rocks	5 min	Status on each quarterly Rock: on-track, off-track, complete. Any roadblock becomes an issue.
Headlines	5 min	FYI announcements. Team news, client updates, anything the room needs to know.
To-Dos	5 min	Review completion of last week's To-Dos. Anything still open becomes an issue.
Issues	60 min	The bulk of the meeting. Raise, Discuss, Resolve every issue surfaced above.
Conclude	5 min	Recap To-Dos, cascading messages to anyone not present, rate the meeting one to ten.

Five of the seven segments are deliberately short. They exist to surface issues, not to resolve them. The sixty-minute Issues segment is where the work happens. If the Issues segment is not running the full sixty minutes, the first five segments are not surfacing enough.

The RDR framework: Raise, Discuss, Resolve

The sixty-minute Issues segment has a structure of its own, because sixty unstructured minutes turns into a vent session. RDR prevents that.

Raise an issue in a single structured line using five prompts: Who raises it, Who it concerns, One sentence describing it, What is needed, Why it matters. The structure takes thirty seconds and it removes the preamble that otherwise eats the segment.

Discuss with the facilitator keeping the conversation concise and making sure the people it concerns are heard. Feed Forward (future-focused suggestions) rather than dwelling on the past. Work in progress is acceptable: not everything resolves in one week.

Resolve along one of three paths. Create a To-Do for action in the next week. Keep the issue on the WTM list for next meeting. Move it to the long-term issues list for a quarterly planning conversation. Every issue gets one of these three outcomes, which is what stops the same issue appearing week after week without movement.

The five non-negotiable rules

If the meeting drifts on any of these five, the rhythm breaks. The fifteen corridor conversations start returning across the week, and the owner becomes the bottleneck again.

Same Day every week. Tuesday morning works well for most UK service businesses. Pick one and hold it.
Same Time every week. Start time does not shift by availability. The meeting is the anchor.
Same Agenda every week. Seven segments, fixed order, fixed timings. Drift breaks the discipline.
Starts on Time. Everyone is present and ready at the start. Late is not a problem to manage; it is a signal the rhythm is slipping.
Ends on Time. Ninety minutes, not ninety-five. The Conclude segment runs whether or not the Issues segment got through everything.

The rating question at the end is the sixth informal rule. One to ten, every person, every week. Anything below eight gets a thirty-second comment on what would have improved it. The rating compounds quality across quarters.

The short version

Ninety minutes, same day, same time, same agenda. Seven segments: Segue, Data, Rocks, Headlines, To-Dos, Issues, Conclude. Sixty minutes on Issues via Raise-Discuss-Resolve. Rate the meeting one to ten at the end. Never miss a week. Over six to eight weeks, the rhythm becomes the backbone of the business, and the fifteen ad-hoc conversations that used to land on the owner's desk stop happening.

If you do nothing else with BOS UP, run your Weekly Team Meetings the BOS UP way. This is the single highest-leverage change.

Read the accountability chart Read the nine competencies

Keep reading

BOS UP Pillar · Live

The Nine Core Competencies

Where Meetings sits inside the full BOS UP system.

BOS UP Pillar · Live

The Accountability Chart

The sibling competency. The chart the meeting enforces.

BOS UP Pillar · Live

Feelings Lie, Dashboards Don't

The scorecard that lives inside the five-minute Data segment.

BOS UP Pillar · Live

The BOS UP Pillar

The pillar hub.

BOS UP Pillar · Live

Do The Job Before You Delegate

The Process-competency cousin. What the Issues segment resolves against.

Methodology · Live

Where to start

The Sequence Rule. Why the meeting rhythm lands properly only once the operator has reclaimed time.

Weekly meetings, answered

What is an L10 or Weekly Team Meeting?+

A ninety-minute meeting held at the same day and time every week, with a fixed seven-segment agenda. The BOS UP version runs Segue (5 min), Data (5 min), Rocks (5 min), Headlines (5 min), To-Dos (5 min), Issues (60 min), Conclude (5 min). The rhythm replaces fifteen scattered ad-hoc conversations that would otherwise land on the owner's desk across the week. L10 is the Entrepreneurial Operating System name for the same shape of meeting. Most UK service businesses find the structure more useful than the name.

Why ninety minutes?+

Long enough to handle real issues, short enough to stay focused. Thirty-minute meetings produce surface-level conversations. Three-hour meetings produce fatigue and drift. Ninety minutes is the format that lets sixty minutes land on Issues (which is the work the meeting is actually for) while keeping the other six segments tight. Service businesses that try to compress the meeting into sixty minutes usually lose the Issues segment, which is the only segment that resolves anything.

What is the RDR framework?+

Raise, Discuss, Resolve. The process for handling issues inside the Issues segment. Raise an issue using five prompts: Who raises it, Who it concerns, One sentence describing it, What is needed, Why it is relevant. Discuss with the facilitator making sure everyone is heard, concisely. Resolve along one of three paths: create a To-Do, keep it on the Weekly Team Meeting issues list, or move it to the long-term issues list. The RDR framework is what stops the Issues segment from turning into an unstructured sixty-minute vent.

Why rate the meeting one to ten?+

The last thirty seconds of the meeting. Everyone rates it one to ten based on how useful it was. Anything below eight gets a brief comment on what would have made it better. The rating is not performative. It produces a feedback loop that compounds over quarters. Meetings that routinely rate at nine are usually well-prepared, tightly run, and resolving real issues. Meetings that routinely rate at six are usually not preparing or not defending the agenda. The rating makes the quality visible, which is the precondition for improving it.

Do I really need to hold it every single week?+

Yes. The five WTM rules are non-negotiable for the rhythm to work. Same Day every week. Same Time every week. Same Agenda every week. Starts on Time. Ends on Time. Missing weeks once a quarter is usually the point at which the rhythm breaks and the fifteen ad-hoc conversations start returning. The meeting is the rhythm. The rhythm is what lets the team self-coordinate without the owner handling every thread.

What if my team is only three people?+

The format still works, and the meeting may run shorter (sixty minutes is often enough for three people). The principle is the same. One structured conversation replaces the five scattered ones that otherwise happen in corridors and Slack threads. A three-person team running a proper Weekly Team Meeting usually sees the biggest relative benefit, because the owner's time is the scarcest resource in the room and the meeting is the mechanism that protects it.

Where does this sit inside BOS UP?+

Meetings is one of the nine core competencies, and the Weekly Team Meeting is the primary rhythm inside it. Meetings typically installs alongside Structure (the accountability chart) in the first quarter of a BOS UP engagement, because those two competencies together produce the fastest operator relief. The meeting enforces the chart. The chart enables the meeting. Quarterly Planning (one day every ninety days) and Annual Planning (two days every year) are the sibling rhythms inside the competency.