10/10/10 One-on-One Model: Employee Time, Manager Time, Then Growth
The 10/10/10 One-on-One Model splits a 30-minute manager and team member meeting into three equal jobs: ten minutes for the report's agenda, ten for the manager's agenda, and ten for future work (skills, career, or growth). It is a meeting container. It does not write the feedback.
Framework Card
- Name:
- 10/10/10 One-on-One Model
- Goal:
- Split a 30-minute manager and team member meeting into equal time for the report's agenda, the manager's agenda, and future work.
- Flow:
- Team member topics (10 minutes) → Manager topics (10 minutes) → Future planning (10 minutes)
- Best For:
- Recurring 1:1s that have become status reports; Weekly or biweekly performance talk instead of waiting for an annual review; Onboarding 1:1s that need a predictable agenda
Why it matters
A weekly 1:1 is one of the few slots where a manager and a report can talk without a project crowd. It often does not get used that way.
The calendar says "1:1." The conversation becomes a status report: tickets, dates, blockers the standup already covered. Or the manager talks for 25 minutes and asks "anything else?" with four minutes left. Employee concerns stay unsaid. Growth waits for the annual review.
10/10/10 is a way to assign the 30 minutes so those three jobs cannot all lose to status. It is not a promise that the conversation will be honest. It is a habit of protecting airtime.
What it is
The 10/10/10 One-on-One Model is a timebox for a direct-report 1:1 of about 30 minutes. The first block belongs to the team member. The second belongs to the manager (feedback, expectations, what the manager needs on the table). The third is future planning: not this week's tickets, but skills, career, or a growth bet that would otherwise slip.
The numbers 10, 10, and 10 are a teaching split for a 30-minute slot. A 45-minute 1:1 can keep the same three jobs with longer blocks. A 15-minute slot can keep the three jobs only in thin form; many teams use a different format for that length.
This is not Suzy Welch's 10-10-10, which asks how a decision looks in ten minutes, ten months, and ten years. Same digits. Different method.
How it works
A useful 10/10/10 pass is three jobs on a clock, not a poster that says "be structured."
1. Team member topics (first 10 minutes)
Ask what is on their mind. Listen. Do not spend this block on your list. Status can appear if they bring it. If they only report tickets, you can ask a prompt ("Where are you stuck?" "What is not in the standup?") without taking the block back.
2. Manager topics (second 10 minutes)
This is your agenda: one or two points, not a dump. Feedback belongs here if it is yours to give. Specifics beat a tour of every project. If a topic needs a working session, name a follow-up instead of stealing the third block.
3. Future planning (last 10 minutes)
Talk about skills, career, or a near-term growth move. This block is the one teams drop when the first two run long. If you skip it three weeks in a row, you have a two-block 1:1, not 10/10/10.
The ten-minute marks are a discipline, not a gavel. If a topic is live, finish the thought and park the rest, or schedule a dedicated session. The test is whether all three jobs appeared, not whether the timer hit zero on the second.
How it compares
When another lens fits better, or when you need a complementary view, these frameworks do different jobs. They are not interchangeable labels for the same question.
| Framework | What it helps you see | How it differs from 10/10/10 |
|---|---|---|
| GROW Model | A coaching path: Goal, Reality, Options, Will | Sequence for a goal conversation. 10/10/10 is the 1:1 clock. |
| SBI Model | One piece of feedback as Situation, Behavior, Impact | Content of a feedback turn. It can live in the manager block. |
| Radical Candor | Care personally and challenge directly | Feedback stance, not a timebox |
| ORID Focused Conversation | Facts, reactions, meaning, then a decision | Facilitated thinking sequence, not a 1:1 agenda |
| Daily standup | Team status in a short group slot | Group coordination, not a manager-report 1:1 |
| Skip-level 1:1 | Conversation across a reporting skip | Different relationship |
| Suzy Welch 10-10-10 | How a choice looks in ten minutes, ten months, ten years | Decision horizons. Same digits, different job. |
The 10/10/10 model is the lens for splitting a 30-minute direct-report 1:1 into employee, manager, and future blocks. Other methods help when the question is coaching, feedback wording, or a different meeting type.
When to Use This Framework
- Onboarding 1:1s. A new hire needs a predictable agenda: their questions first, then expectations, then how the role can grow.
- Project-heavy seasons. The work is loud. The 1:1 still needs a block that is not the project sync.
- Continuous performance talk. The manager wants timely feedback in the middle block instead of storing everything for an annual review.
Example
A concrete example makes the structure easier to reuse when you are under uncertainty.
Example: Quiet report, loud project
A manager of a six-person QA team runs 30-minute weekly 1:1s. Lately they are ticket reviews. One report has gone quiet.
First 10 minutes (their agenda). They say manual regression is eating evenings. The manager notes it and does not jump to a solution lecture.
Second 10 minutes (manager agenda). Last sprint, a release note went out late. The manager names the date and the impact on support, and asks what got in the way. They do not use the whole block to relitigate the sprint.
Last 10 minutes (future). They agree to try a small automation spike on the two highest-volume checks, and to talk in two weeks about whether the report wants more test-architecture work.
Implication: The meeting covered a blocker, one piece of performance, and a growth move. It did not replace SBI as a feedback script, and it did not replace a project standup. Dropping the third block to "solve testing" in the room would have been a different meeting.
Takeaway
What 10/10/10 can help with
- Giving a 30-minute 1:1 three jobs so status cannot take all of them
- Protecting employee airtime before the manager's list
- Making growth a recurring block instead of leftover time
- Giving onboarding 1:1s a shape both people can prepare for
What 10/10/10 cannot replace
- Feedback craft. SBI structures one piece of feedback. Radical Candor is a stance (care and challenge). Neither is an agenda.
- Coaching toward a goal. GROW is a coaching path. You can run GROW inside a block. The clock is still 10/10/10.
- A daily standup or project sync. Those meetings exist to share status with a group. Using 10/10/10 there misuses the container.
- A skip-level 1:1. Different reporting line, different purpose.
- Suzy Welch 10-10-10. That method is decision time horizons, not a meeting split.
- A performance system. Weekly middle-block feedback does not replace documentation, calibration, or formal review where those are required.
Honest scope: 10/10/10 structures time in a direct-report 1:1. It does not guarantee candor, and it should not be sold as a perfect meeting.
Frequently asked questions
No. Welch's method looks at a decision across three time horizons. This page is a three-block agenda for a manager and direct report 1:1.
Finish the live point, then park the rest or book a working session. The method fails when one job (usually status or the manager's list) takes every week.
The teaching split assumes about 30 minutes. You can keep the three jobs in thinner form. Many teams use a different format when the slot cannot hold a real growth close.
No. SBI is how you say one piece of feedback. GROW is how you coach toward a goal. They can sit inside a block. They do not assign the 30 minutes.
Yes. The split does not require a room. Shared notes per block help when cues are thinner.