How-to: Make Your 1:1 Employee-Owned
Most 1:1s quietly become status meetings the manager could have read in a doc. Employee-owned 1:1s flip the default: the report sets the agenda, brings the problems that need judgment, and uses the manager as a multiplier. Status still happens, but it is pre-read or last, not the whole hour.
Time box: 10 minutes for the employee to update the agenda before the meeting, and 25–50 minutes for the 1:1 itself depending on cadence. Protect a standing slot; canceling every week teaches that people are optional.
For ICs, start in the Individual Contributor hub. Managers should coach the habit from the New Manager hub. New joiners can adopt this by week two; see New hire.
When to use / when not
Use when:
– You have a recurring 1:1 and want higher signal
– Growth, blockers, career, and feedback need airtime
– Status is already available in tickets, dashboards, or async updates
Do not use when:
– There is an active crisis that needs a dedicated ops standup
– The meeting is a formal performance or PIP conversation with a required structure (separate process; see how HR works)
– Psychological safety is so low that “you own the agenda” would be a trap; rebuild trust first with lighter prompts
Employee-owned does not mean manager-absent. Managers still bring feedback, context, and decisions.
Prep
Employee (before each 1:1):
- Update a shared doc with ranked topics
- Mark each item: decide / advise / inform / vent-with-ask
- Link artifacts; do not paste walls of text
- Include one career or development micro-topic every few sessions
Manager:
- Read the agenda before joining
- Bring one piece of specific feedback or context from up-level
- Hold time for their items before yours
If priorities span functions, note partners using how departments work together.
Steps
- Create a standing shared doc (one per report) with sections: agenda, decisions log, parking lot, career.
- Employee posts agenda at least a few hours ahead (norm: night before or morning of).
- Manager skims and adds 1–2 items at the bottom, not the top, unless urgent.
- Open live by confirming the order (1 min). Time-box long topics.
- Work top priority first. Drive to a decision, experiment, or clear next step.
- Manager adds feedback and org context in a reserved window.
- Close with notes: decisions, owners, dates.
- Async between meetings: update the doc so the next 1:1 starts smarter.
Script (what to say / send)
Employee agenda template:
1) Decision needed: [topic]; options A/B; my recommendation
2) Blocker: [X]; asks of you
3) Feedback request: how I handled [situation]
4) Career/development (biweekly): [skill or path]
5) Quick FYIs (read ahead): links
Employee invite note:
I’ll keep our 1:1 agenda updated here: [link]. I’ll prioritize decisions and blockers. Please add anything from your side below my list.
Manager opening:
“Your agenda leads. I’ll save ten minutes at the end for feedback and anything from leadership. What’s first?”
When it drifts to pure status:
“Let’s move status to the doc. What judgment do you need from me on the risks?”
When the employee brings an empty agenda:
“No topics is a topic. Are we clear on priorities, or are you stuck and need help naming the problem? Let’s use fifteen minutes to diagnose.”
Career micro-prompt (manager):
“What skill do you want more reps on this month, and what project gives you those reps?”
Output artifact
Living 1:1 doc:
| Section | Purpose |
|---|---|
| Upcoming agenda | Ranked, owned by employee |
| Decision log | Date / decision / owner |
| Feedback notes | Specific, dated |
| Career thread | Ongoing goals |
| Parking lot | Not now |
Optional: link a monthly priority list so every 1:1 ties to real outcomes, not vibes. For budget or headcount asks that appear, prep with finance for non-finance managers before using the 1:1 to escalate.
Watch-outs
- Manager hijack. If your items always go first, it is not employee-owned.
- Therapy without action. Venting is allowed briefly; end with an ask.
- No documentation. Recurring arguments mean nothing was written down.
- Skipping 1:1s for “we talk all day.” Ad hoc chat is not a substitute for dedicated development space.
- Weaponized agendas. Do not surprise someone with a formal performance process inside a casual 1:1 without following policy.
- Status theater. If both of you read the same dashboard aloud, shorten the meeting.
- Ignoring cross-team reality. Sales deadlines and shared roadmaps shape good agendas; learn the shape via how sales works when relevant.