What a capacity-aware 1:1 actually is
A capacity-aware 1:1 is a one-on-one where both people walk in already looking at the same picture of the work — who's stretched, who has room, and how that's changed since the last conversation — so the half hour goes to the conversation instead of the reconstruction. Neither person spends the first ten minutes figuring out what happened this month; the data is already on the table, and it's the same data on both sides.
That last part is the whole point. Most "data-informed" 1:1s are informed for one person. The manager pulls a report, forms an opinion, and walks in with a conclusion already reached. That's not a capacity-aware 1:1 — it's a review wearing a 1:1's clothes. A capacity-aware 1:1 starts from a picture both people can see before the meeting starts, so the conversation is something that happens with the team member, not about them.
Why capacity-blind 1:1s fail
Take away the shared picture and a 1:1 defaults to one of two failure modes.
The first is status theater. The manager asks "how's it going," the team member says "good, busy," and thirty minutes get spent narrating a task list neither person needed narrated — because neither one has anything more specific to react to. Nobody's lying; there's just nothing else on the table.
The second is worse: someone is quietly drowning and the 1:1 never surfaces it. A team member who's over capacity for two months running rarely announces it in those words — they say "busy" too, right up until they burn out or quietly start looking elsewhere. Without a shared number to anchor the conversation, "busy" and "overloaded" sound identical from across the table, and the manager finds out only when it's already a resignation letter or a missed deadline.
Both failure modes trace back to the same root cause: the manager and the team member are not looking at the same thing. Fix that, and the 1:1 has somewhere to start.
There's a third, quieter failure mode worth naming: the growth conversation that arrives out of nowhere. A team member gets passed over for a promotion, or worse, gets one they weren't expecting, and either way the decision feels like it landed from outside — because the evidence behind it lived in a manager's head, not somewhere both people had been watching together. Capacity-blind 1:1s don't just miss the overload cases; they turn growth into a surprise instead of a conversation that's been building for months.
The method: shared picture, question-shaped prep, growth timeline
1. Start from a shared capacity picture
Before anything else, both people need to see the same numbers — capacity vs. target, and how that's moved month over month. Not a manager-only dashboard, not a report that gets summarized secondhand. The same screen, in front of both people, at the same time. This is the "data symmetry" idea stated plainly: if only one person in the room can see the data, it isn't a conversation, it's a review.
2. Prep in questions, not judgments
The picture doesn't tell the manager what's true — it tells the manager what to ask. A number that's climbed for two months isn't a verdict ("you're overloaded"); it's a question ("your workload shifted a lot since last month — what changed?"). The distinction matters more than it looks. A verdict puts the team member on the defensive before the conversation starts. A question invites them to bring context the number can't carry on its own — a client that spiked, a teammate out sick, a project that turned out bigger than scoped. Capacity-aware prep generates open questions, never closed conclusions.
3. Track growth as a timeline, not a single review
The same shared picture that flags an overloaded month is what shows sustained strength over several. A team member who's been operating comfortably above their current level for a while isn't a surprise at review time — it's a trend the manager and the team member have already been watching together, meeting after meeting. Growth conversations stop being an annual event decided behind closed doors and become a running thread with evidence both people have seen accumulate.
Cadence and team size
The method above doesn't specify a fixed rhythm, because the right cadence depends on how fast the picture actually changes. A five-person team where client assignments shift week to week needs a weekly touchpoint — a month between conversations is long enough for someone to go from comfortable to over capacity and back without either person ever discussing it. A steadier team of twelve, where assignments hold for months at a stretch, can run every two weeks or even monthly without losing anything, because the picture itself isn't moving that fast.
The mistake to avoid is picking a cadence once and never revisiting it. A team that just took on three new clients needs tighter check-ins than the same team did a quarter ago; a team coming off a slow season can stretch back out. The shared picture is what tells you which situation you're in — treat cadence as something the data informs, not a calendar default nobody questions.
Example talking points
These come from a phrasing bank built around one rule: every prompt is a question, never a verdict. A manager reviewing the shared picture before a 1:1 might walk in with prompts shaped like these:
- "You're running well past your target this month — how does that feel? Is it sustainable?"
- "You're sitting well under your target lately — is that by choice, or is there work you'd like to pick up?"
- "You've been carrying more than your current level for a while now — want to talk about what the next one looks like?"
- "Your workload shifted a lot since last month — what changed?"
- "You're almost at the goal we set together — what's the last step?"
- "Anything on your plate that isn't showing up in the numbers?"
That last one is worth calling out on its own: it's the standing closer, asked every time, regardless of what the numbers show. The picture is real, but it's not the whole picture — the always-on question exists precisely because some things never show up in a chart.
How this differs from a performance review
A performance review looks backward and produces a verdict — a rating, a ranking, something that gets filed. A capacity-aware 1:1 looks at the present and produces a question. Nothing discussed in the 1:1 workspace feeds a rating or a review export, and it never will — that's not a current limitation, it's a line we won't cross. The moment a capacity conversation starts feeding a performance score, it stops being a conversation between two people and starts being surveillance with extra steps. Growth still gets discussed — the timeline in step 3 makes sure of that — but it's discussed as a conversation about direction, not a judgment about performance.
How this differs from activity-inferred prep
Some newer 1:1 tools now pull in signals from Slack, Jira, or your calendar to guess at what someone's been doing, then hand the manager a summary before the meeting. It looks similar from a distance — data-informed prep — but the mechanism is the opposite of what's described above.
Everyone else either ignores workload, or infers it by watching your work tools and reporting up to the boss. Capysaurus puts the same explicit capacity picture in front of the worker and the manager.
The difference is not a feature checklist, it's structural. Inferred prep is built by watching tools the team member didn't choose to hand over, and the summary goes to the manager first — the team member finds out what was inferred about them only if the manager mentions it. Explicit prep starts from numbers the team agreed on together (effort scores, capacity targets), and both people see the identical picture before either one walks into the room. One is a report about you, sent somewhere you're not in the room for. The other is a page you're both looking at, at the same time.
Frequently asked questions
Is a capacity-aware 1:1 the same thing as a status check-in? No. A status check-in asks what someone did; a capacity-aware 1:1 starts from what the shared picture already shows and spends the time on what the number doesn't explain — why it moved, what's coming, what needs to change.
Do I need special software to run one? You need a shared, visible number both people can point to — a whiteboard would technically work. In practice, software that keeps the capacity picture current and generates question-shaped prep from it (rather than a manager reconstructing it from memory before every meeting) is what makes the practice sustainable week after week.
What if the team member disagrees with the number? That disagreement is the conversation, and it's a feature, not a bug. A shared number that's wrong is easy to correct out loud, in the room, because both people can see exactly what it says. A manager's private impression that's wrong rarely gets corrected at all.
Does this replace performance reviews entirely? No — it deliberately stays separate from them. See "How this differs from a performance review" above; that separation is a hard line, not a phase-one limitation.
How often should a capacity-aware 1:1 happen? Cadence should match team size and how fast workload shifts — weekly for smaller, faster-moving teams; every two weeks or monthly for steadier ones. What matters more than frequency is that the picture stays current between meetings, so nothing is stale when the conversation starts.
What happens to the data between 1:1s? It stays visible to both people continuously, not just during the meeting. A team member who wants to check their own capacity picture at 9pm on a Tuesday can — the same screen the manager sees, on their own time, without asking permission.
Getting started this week
None of this requires overhauling how your team works before the next 1:1 on your calendar. Start with the one piece that unlocks everything else: get capacity vs. target visible to both people, even in a rough form. A shared spreadsheet both people can open is a real starting point — the goal isn't a polished dashboard on day one, it's closing the gap between what the manager sees and what the team member sees.
From there, bring one question-shaped prompt into your next 1:1 instead of a full list — the always-on closer is the easiest place to start, because it costs nothing to ask and it's never the wrong question to ask. Notice what comes back. Most managers find the answer surfaces something the shared numbers alone wouldn't have shown, and that's usually the moment the rest of the method stops feeling theoretical.
Growth is the piece to add last, not first. It only works once there's a few months of shared history to point to — trying to have a capacity-aware growth conversation before the picture has any track record just recreates the surprise problem from a different angle. Get the weekly or biweekly rhythm working first; the timeline builds itself from there.
Where to go next
If the idea of a manager-only view of your data makes you uneasy, that reaction is correct — read /trust for the specific commitments behind data symmetry, including what we will never build. And if you want to see how other managers are actually running 1:1s and talking about workload right now, keep an eye out for The State of Team Capacity 2026 — our original survey of managers running 3–15 person teams, publishing soon.
