MetodicMETODIC | learn
Build a Session
Session Flow

Lencioni's Weekly Tactical Meeting

The weekly tactical meeting is one of the four meeting types in Patrick Lencioni's Death by Meeting: a 45-90 minute team meeting about this week's work that has no agenda set in advance. A quick round of priorities and a short look at key metrics come first, and the team then builds its agenda from what those showed.

4 phasesSession Flow
When to Use This Framework

When your sessions feel disjointed or participants lose focus

Your meetings or sessions need better pacing, clearer transitions, or more engaging sequences to keep participants engaged.

Weekly team or leadership meetings of 45-90 minutes that should solve this week's issues instead of only sharing updates.

The 4 Steps
Follow this sequence to apply Lencioni's Weekly Tactical Meeting
1

Lightning Round

Each person takes about one minute to name their two or three priorities for the week. No discussion yet: the round shows the whole team what everyone is working on.

2

Progress Review

The team runs through a handful of key metrics or goals in a few minutes, to see what is on track and what is not.

3

Real-Time Agenda

Only now is the agenda set, from what the lightning round and the progress review showed. The team resolves the tactical issues that block this week's work; strategic topics are parked for a separate, longer meeting.

4

Close & Cascading Communication

The team states what it decided and agrees what each person passes on to their own people, so everyone leaves with the same message.

What You'll Achieve

Creates natural rhythm and momentum that keeps energy high throughout.

Use it as the running order of a weekly team or leadership meeting: a lightning-round block, a short progress block, one or two blocks for the issues the team picks on the spot, and a close that agrees the message to pass on. Keep strategy topics for their own session.

Practical Tips
How to get the most out of this framework
  • 1
    Vary the pace between high and low energy activities
  • 2
    Use clear transitions between sections
  • 3
    Build complexity gradually throughout
  • 4
    End with actionable takeaways
Best For
  • Weekly leadership team meetings
  • Operational team meetings
  • Teams whose meetings are all status updates
Key Principles
  • No pre-set agenda: build it after the lightning round
  • Short, strict status rounds
  • Tactical only: strategic topics get their own meeting
  • Resolve issues, don't just report
  • Leave with one shared message
Watch Out For
  • Strategic topics creep in easily; park them for a monthly strategic meeting
  • The close draws on Lencioni's cascading-communication discipline from his later work, not on Death by Meeting itself
  • Time limits and the number of metrics come from summaries of the book; adjust them to the team
  • Part of a rhythm with daily check-ins, monthly strategic and quarterly off-site meetings
Related Frameworks
Other Session Flow frameworks you might find useful
Derby & Larsen's Five Stages of a RetrospectiveA five-stage arc for team retrospectives from Esther Derby and Diana Larsen's book Agile Retrospectives. It works as a container: any retro activity, such as a timeline or a sailboat, slots into one of the stages, so the meeting moves from data to insight to commitment instead of stopping at venting.
Daily Scrum (Scrum Guide)The Daily Scrum is the Scrum Guide's 15-minute daily event in which the Developers inspect progress toward the Sprint Goal and adapt their plan. The 2020 Guide no longer prescribes questions; the team picks any structure as long as it focuses on the goal and ends in a plan for the day.
EOS Level 10 MeetingThe weekly leadership meeting of the Entrepreneurial Operating System, with a fixed 90-minute agenda. Short reporting segments surface problems quickly so most of the time goes to solving the top issues through Identify-Discuss-Solve.