ED3 in Practice · P1 · P3 · P6

The ED3 1-1 Template

Status updates are written before you sit down. Live time is for blockers, decisions, and the conversations that actually need a room.

The typical 1-1 goes like this: "So, how's everything going?" Fifteen minutes of status recitation. A few surface-level questions. Time runs out. The hard conversation — the blocker, the decision, the thing that actually needed two humans in a room — gets pushed to next week. Repeat indefinitely.

The ED3 1-1 template fixes this by splitting the meeting into two parts: a written pre-read that handles status, and live time that handles only what writing can't — decisions, unblocking, and the conversations that require trust and nuance.

"If your manager learns what you've been working on during the 1-1, you've already wasted the first fifteen minutes."


Why it works

The template operationalizes three principles. It ensures every 1-1 exists for a defined purpose beyond "checking in" (P1). It treats delay and ambiguity as decisions that must be named explicitly — if something is stuck, say so, with a date (P3). And it moves status updates into writing where they belong, freeing live time for what actually needs a room (P6).

The result is 1-1s that are shorter, more useful, and — counterintuitively — more human. When you're not burning time on "what did you do this week," you can actually talk about the things that matter: career growth, hard problems, the conversation someone's been avoiding.


The pre-read (written by the report, 24 hours before)

The report fills this in and shares it before the meeting. The manager reads it async. None of this gets recited aloud.

Progress What shipped, moved forward, or got done since last time? Keep it to 3-5 items. This is the part that used to consume half the meeting — now it's two minutes of reading.
"- Shipped the new onboarding flow to staging. QA in progress.
- Finalized vendor selection brief (recommending Option A — see doc).
- Closed 3 of 5 items from last sprint. Remaining 2 carry over."
Blockers What's stuck, and what do you need to get it unstuck? Be specific: name the decision, the person, or the resource you're waiting on.
"- Waiting on legal review for the data processing agreement. Requested March 12, no response. Need escalation path.
- Design resources are overcommitted — can't start the dashboard redesign until April unless we reprioritize."
Decisions needed What do you need your manager to decide, approve, or weigh in on? Frame each one as a decision, not a discussion topic. Include your recommendation.
"- Should we delay the dashboard redesign to Q3, or cut scope on the onboarding project to free up design? I recommend delaying the dashboard.
- I'd like to skip the team offsite planning committee. It's 3 hours/week and not aligned with my goals. Your call."
Topics for live discussion Anything that genuinely benefits from a real-time conversation — career development, sensitive feedback, complex tradeoffs, things that need tone and trust.
"- Want to talk through my promotion case. I have a draft self-assessment.
- Feeling friction with the platform team on API ownership. Not sure if it's a process problem or a people problem."

The live meeting

The manager has already read the pre-read. The meeting starts at the blockers, not at "so what are you working on?"

01

Blockers first (5 min)

Start with what's stuck. The manager's job here is to unblock: escalate, approve, connect, or decide. If a blocker needs more than 5 minutes, it probably needs its own Decision Brief.

02

Decisions (5 min)

The report brought recommendations. The manager decides or delegates. No open-ended "what do you think we should do?" — the thinking was done in writing.

03

Live topics (15 min)

The conversations that actually need two humans. Career, feedback, strategy, the thing someone's been avoiding. This is where 1-1s create real value — and it only gets this time because you reclaimed it from status updates.

04

Capture & close (5 min)

What was decided? Who owns what? When? Write it down on the spot — not in a follow-up email three hours later. The pre-read becomes the decision record when you annotate it with outcomes.


Before & after

Typical 1-1 (30 min)

0:00 "So, how's it going?"
0:05 Report recites project status
0:18 Manager asks follow-up questions about status
0:25 "Oh, one more thing..." (the real issue surfaces)
0:30 "Let's pick this up next week"

ED3 1-1 (30 min)

0:00 "I read the pre-read. Let's start with the legal blocker."
0:05 Two decisions made (dashboard timing, offsite committee)
0:10 Promotion case discussion — real conversation, full attention
0:25 Platform team friction — manager offers to have a direct conversation
0:28 Decisions captured, next steps owned. Done.

Getting started

You don't need organizational buy-in to start. One manager and one report can adopt this template tomorrow. Here's how to introduce it without it feeling like overhead:

Start with one report. Try it for two weeks. When the 1-1s get noticeably better, the format spreads on its own.

Keep the pre-read short. Five to ten minutes to write, two minutes to read. If it's longer, the report is over-documenting — coach them to be terse.

The manager reads before the meeting. Non-negotiable. If the manager hasn't read it, the report has no reason to write it. Model the behavior.

Don't fill awkward silence with status. If blockers and decisions are handled in ten minutes, you have twenty minutes for the conversations you've been deferring. Use them.

Download the template

A clean, tool-agnostic version you can adapt to Google Docs, Notion, Confluence, or wherever your team works.

Download (.md) →