Gantrywell Leadership Team Update, Week 21

Leadership team update deck: eight slides every week

A weekly leadership team update has to show, in under half an hour, whether the numbers moved, whether last week's decisions actually happened, and what each executive needs from the others before next Monday. Gantrywell, an invented managed detection company, runs the same eight slides every week, starting from six fixed numbers and ending on three asks with names and dates.

Every slide, in order

The whole deck as it renders, one slide after another. Read it the way the audience would.

GANTRYWELL · LEADERSHIP WEEKLY

Week 21, 24 May 2027

Eight slides, thirty minutes, decisions first

Chief of staff

Numbers to Friday 21 May, risks and asks from each executive

Quarter

Q2, week 8 of 13

Slide 1 · cover · Names the week so every weekly deck files in order and the team knows which numbers are current.

The six numbers

Same six every week, to Friday close. ARR and pipeline in US dollars.

$11.2M

ARR

Up $140K this week from two new customers, no churn.

$0.9M

Q2 net new ARR

Against a $1.2M quarter plan, with five weeks left.

$4.6M

Weighted pipeline

Up $0.3M on last week. Nine deals at contract stage.

37

Incidents contained

Across all customers this week, none spread past one host.

4.0 min

Median response

From alert to an analyst acting. Target is under five.

1

Priority one incident

Ransomware attempt at a logistics customer, contained in 22 minutes.

02

Slide 2 · metrics · Pipeline, ARR and incidents in six numbers, the same six every week.

Last week, decided

Eight decisions from 17 May. Five done, two in progress, one blocked.

Six percent renewal price rise

Done. Applies to renewals from 1 July.

Open two analyst roles

Done. Both adverts live since 19 May.

Partner launch moved to Q3

Done. Partners told on 18 May.

SOC 2 auditor chosen

Done. Engagement letter signed 20 May.

Advisory board date

Done. 24 June, eight customers confirmed.

Reserved cloud capacity

In progress. Decision on 31 May with CTO numbers.

On call allowance

In progress. In payroll from 1 June.

Drop Windows Server 2012 agent

Blocked. Three customers still run it.

03

Slide 3 · checklist · Last week decisions with their status, so nothing agreed in this room quietly stalls.

RISKS

Five risks this week

Risk
Owner
Trend
Next step
Q2 net new ARR $0.3M short
CRO
Worse
Pull two contract stage deals into June
Two analysts resigned in May
COO
Same
Retention review on 26 May
Cloud cost up 18% on Q1
CTO
Worse
Reserved capacity decision on 31 May
July renewal, 8% of ARR
CEO
Better
Executive call booked for 3 June
SOC 2 evidence gaps
Head of security
Better
Three of eleven gaps still open
Trend is against last week. A risk that is worse two weeks running goes to the board update.

04

Slide 4 · metrics · The live risk register in five lines, each with an owner, a trend and the next step.

The next fortnight

Seven dates between this meeting and the one after next.

1

Wed 26 May

Analyst retention review with the COO and people lead.

2

Fri 28 May

Two contract stage deals due to sign, $310K ARR together.

3

Mon 31 May

Leadership weekly. Reserved cloud capacity decision.

4

Tue 1 Jun

On call allowance paid for the first time.

5

Thu 3 Jun

CEO call with the July renewal customer.

6

Fri 4 Jun

SOC 2 fieldwork starts with the auditor.

7

Mon 7 Jun

Leadership weekly, Q2 forecast refreshed.

05

Slide 5 · timeline · The next fortnight in seven dates, so everyone sees the collisions before they happen.

The week in six lines

Win: regional hospital group

$84K ARR, signed after a two week trial that caught a live phishing campaign.

Loss: freight forwarder

Chose to build in house. Price was not the reason, data residency was.

Priority one incident

Logistics customer, contained in 22 minutes, report sent within 24 hours.

Release: faster triage

Alert grouping shipped Thursday. Duplicate alerts down a third in two days.

Joined: head of security

Started Monday and now owns the SOC 2 risk.

Leaving: two analysts

Both to larger teams for pay. Exit interviews feed the review on 26 May.

06

Slide 6 · pillars · The week news in six short cards, good and bad, so the team hears it here first.

THIS WEEK

The quarter turns on two deals closing by Friday and keeping the analysts we have. Everything else can wait a week.

CEO, leadership weekly, 24 May 2027

07

Slide 7 · takeaway · The one thing the team should take away from this week.

Three asks before next Monday

Each ask has an owner and a date. Answers go in the leadership channel, not in a meeting.

CRO to CEO

Join both contract stage calls on Thursday 27 May

COO to CFO

Approve a $45K analyst retention budget by Wednesday

CTO to finance

Twelve month cloud forecast by Friday 28 May

08

Slide 8 · closing · Closes with the asks, each to a named person with a date.

The structure

What each slide is doing, so you can reuse the order even with different content.

Slide 1cover
Names the week so every weekly deck files in order and the team knows which numbers are current.
Slide 2metrics
Pipeline, ARR and incidents in six numbers, the same six every week.
Slide 3checklist
Last week decisions with their status, so nothing agreed in this room quietly stalls.
Slide 4metrics
The live risk register in five lines, each with an owner, a trend and the next step.
Slide 5timeline
The next fortnight in seven dates, so everyone sees the collisions before they happen.
Slide 6pillars
The week news in six short cards, good and bad, so the team hears it here first.
Slide 7takeaway
The one thing the team should take away from this week.
Slide 8closing
Closes with the asks, each to a named person with a date.

Slide by slide

Slide one names the week and the quarter position, week 8 of 13. Slide two shows the six numbers. Slide three checks last week's decisions. Slide four is the risk table. Slide five lays out seven dates across the next fortnight, including two contract stage deals worth $310K due on 28 May, enough to close the $0.3M gap. Slide six gives the week's news in six cards, from a hospital win to two analysts leaving. Slide seven states the one thing that matters this week. Slide eight lists three asks, each from one executive to another with a date.

How to adapt this deck

A product company should swap incidents and response time for active users and release count, keeping six numbers and never more. A leadership team that meets fortnightly should widen the timeline to four weeks and add a slide on decisions needed today, because fewer meetings means larger agendas. If the team keeps running over time, cut the news slide first: it is the part people can read on their own before the meeting.

What meeting and risk guidance says

The Table Group, which developed the weekly tactical meeting, describes a lightning round in which each leader states the three most important things they will do that week, with questions held for the agenda rather than discussed on the spot. The Institute of Risk Management's short guide to RAID logs recommends recording risks, assumptions, issues and dependencies in one place and updating them as decisions are made. This deck combines both: priorities and asks, plus a risk table reviewed every week.

What makes this deck work

The same six numbers every week

Slide two always shows ARR, Q2 net new ARR, weighted pipeline, incidents contained, median response and priority one incidents. This week ARR is $11.2M and Q2 net new ARR $0.9M against $1.2M. Because the six never change, a change in any one of them is noticed at once.

Last week's decisions are checked

Slide three lists the eight decisions from 17 May with five done, two in progress and one blocked by three customers still on an old server. Reviewing decisions before making new ones is what stops a weekly meeting becoming a place where things are agreed and then forgotten.

Risks carry a trend

The table on slide four gives each of five risks an owner, a next step and a trend against last week. The $0.3M ARR gap and cloud cost are worse, the July renewal and SOC 2 gaps better. The rule in the caption sends anything worse two weeks running to the board.

Questions people ask

What should a weekly leadership team update include?

A fixed set of numbers, the status of last week's decisions, the current risks, the next two weeks of key dates, short news, and asks between leaders. Keep it to eight slides or fewer so the meeting spends its time deciding, not presenting. Detail goes in the pre-read.

How many metrics should a leadership weekly show?

Five to eight, always the same ones, in the same order. Changing the set each week makes trends impossible to see. Pick numbers that can move within a week, such as pipeline and incidents, and leave slower measures like retention to the monthly review.

Who prepares the leadership team update each week?

Usually a chief of staff or an executive assistant collects the numbers and status lines, and each executive owns their own risks and asks. Set a deadline, such as Friday close for numbers and Sunday evening for risks, so the deck is final before the meeting starts.

How do I track decisions from one leadership meeting to the next?

Open each meeting with last week's decisions and a status for each: done, in progress or blocked, with one line of detail. A decision blocked for two weeks running should become an agenda item. This takes a few minutes and is the main reason weekly meetings stay useful.

What makes a good ask in a leadership update?

It names who is asking, who is being asked, what exactly is needed and by when, like the COO asking the CFO to approve a $45K retention budget by Wednesday. Asks without a person and a date tend to be repeated week after week without anything happening.

Can every slide in the deck use a dark background?

Yes. Each slide has a colour mode button that cycles through four modes, spectrum, matching, outline and dark, and this deck sets every slide to dark. The mode is stored per slide, so a single slide can be switched back to a light mode when it reads better.

Build your own in about a minute

The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.

Make one like this

Other presentation examples

Want the steps in the builder? Read Edit your deck with the AI assistant, then Export a presentation to PowerPoint or PDF. For everything this generator can do, see the presentation maker.

Sources

Written and checked by the OneCraft team. Last checked .