Two-pagers

Before Half Strategy sets the next 6 months of Big Rocks, every team writes a two-pager: the last 6 months and the next 6, in two pages, no more. Leadership gathers every team’s two-pager and reads all of them before planning starts. The two-pager isn’t a status report you file and forget; it’s the raw material planning is built from.

What it is, and why#

A two-pager is short by design. Two pages forces a team’s leads to decide what actually matters instead of listing everything that happened. That constraint is the point: writing a real two-pager is hard precisely because it means cutting the material that feels important but isn’t load-bearing.

Three things make this worth doing every 6 months, not just once:

It’s a forcing function to write goals down. A team that has to state, in writing, what it accomplished and what it’s betting on next finds out fast whether its goals are actually clear, or whether they were always a little vague and nobody had noticed.
It’s a reference for new hires. A stack of two-pagers is the fastest way for someone joining a team to understand what that team has actually been doing and where it’s headed, far faster than reconstructing it from Slack history or a deck nobody kept updated.
It plugs the leader into every team, on a fixed cadence. Reading every team’s two-pager twice a year is how a leader who can’t sit in every team’s daily work still gets a grounded, current read on all of them, not a filtered summary, but the team’s own account in the team’s own words.

The required sections#

Every two-pager covers five things. The first three are the ones teams skip if you let them; they’re also the ones that make the two-pager useful instead of decorative.

Section	What it draws out
3 things we want to be sure [leader] knows	A real TLDR: the handful of facts or judgment calls that would change how leadership reads the rest of the doc if missed. Naming a reader forces honesty in a way “summary” doesn’t; “summary” invites a recap, “things we want you to know” invites the truth.
3 things that would help us move faster	Strategic clarifications and asks of other teams: a decision you’re waiting on, a dependency that’s unclear, a direction you need confirmed. Resource asks (“give us another engineer”) are frowned on here; this section is for clarity, not headcount.
The {graph, chart, picture} we’re obsessed with	Whatever the team actually watches day to day. This section reveals more than any prose in the doc: a team obsessed with a funnel chart is telling you something different than a team obsessed with a support-ticket trend line, and it’s rarely what the rest of the two-pager would suggest on its own.
What we accomplished (last 6 months)	The real record: not everything shipped, the things that mattered.
Key bets (next 6 months)	Where the team believes it should place its capacity next, ahead of Strategic Planning turning those beliefs into Big Rocks.

How reviews run#

Two-pagers get published a few days ahead of the review, not read cold in the room. Leadership pre-reads every one before the session.

The review itself is short: 10–15 minutes per team. It is not a presentation; nobody walks through slides or reads the doc out loud. It’s a focused conversation built on questions: what’s behind the obsession chart, what’s really being asked for in the “move faster” section, what’s uncertain about a key bet. The two-pager did the work of laying out the facts; the review spends its time on judgment, not restating what’s already on the page.

Every team’s two-pager, read together, is what seeds Half Strategy’s Big Rocks: leadership goes into planning already knowing what every team accomplished, what it’s watching, and where it wants to bet next, instead of discovering it live in the planning session.

Systeric’s two-pager and the review cadence around it are adapted from Shishir Mehrotra’s account of how YouTube scaled: see “Rituals for Hypergrowth: An Inside Look at How YouTube Scaled.”

Template#

# [Team]: Two-Pager, [Period]

Leads: [PM name] · [Eng name] · [Design name]
Team: [X] PM · [X] Eng · [X] Design · [X] open headcount

## 3 things we want to be sure [leader] knows
1.
2.
3.

## 3 things that would help us move faster
1.
2.
3.

## The {graph, chart, picture} we're obsessed with
[Embed or describe it, and why it's the one the team watches.]

## What we accomplished (last 6 months)
-
-
-

## Key bets (next 6 months)
-
-
-

A filled example#

The online store’s checkout team, writing ahead of H2 planning:

# Checkout: Two-Pager, H1 2026

Leads: Priya (PM) · Dan (Eng) · Mira (Design)
Team: 1 PM · 3 Eng · 1 Design · 1 open eng

## 3 things we want to be sure [leader] knows
1. Orders/week have been flat at ~1,900 for two halves, and it is not a traffic problem: sessions are up 8%. We are losing the carts we already have.
2. The biggest leak is checkout: 1 in 5 shoppers who reach it abandon rather than re-type an address. Completion sits at 80%.
3. Our saved-address A/B lifted completion 3 points before a bug pulled it. The signal is real; we want to ship it for good.

## 3 things that would help us move faster
1. A decision on whether card vaulting is ours or the payments team's; it is the other half of the checkout leak.
2. Security-review capacity reserved up front; last half the payment-vault review stalled us for a block.
3. Confirmation that checkout completion is our owned input, so we stop being measured on total orders we do not solely control.

## The {graph, chart, picture} we're obsessed with
The checkout funnel drop-off: carts -> checkout started -> completed. The 20% we lose at the final step is the number on every wall in the team room.

## What we accomplished (last 6 months)
- Cut product-page load 4.2s -> 3.5s (first pass; more to come).
- Shipped guest checkout, which lifted first-time completion 4 points.
- Killed the loyalty-points pilot after it moved nothing in 8 weeks.

## Key bets (next 6 months)
- Saved address & payment: completion 80% -> 88% (~+190 orders/wk). Highest conviction.
- Faster product pages: 3.5s -> 1.5s (~+160 orders/wk).
- Explore one-tap buy from the product page (the 10x version) if the first two land early.

Notice it carries the same numbers the diagnosis and half strategy later use: the same north star (~1,900 orders/wk), the same leaks, and bets that are candidates for Big Rocks, not decisions. That is the point of the intake: leadership walks into planning already holding the team’s evidence and conviction, instead of discovering it live.