A good manager keeps the team running. A great manager keeps the team compounding. The gap between the two is not a personality difference, and it is not a longer trait list. It shows up in seven specific moments every manager already has on their calendar this week.
This post is the diagnostic. If you want the deeper how-to, read the flagship guide on how to effectively manage your team after you have figured out where you stand.
Why the trait lists fail
Most “great manager” articles give you ten adjectives: inspiring, strategic, empathetic, calm under pressure.
The problem with adjective lists is that you cannot see them. You cannot watch yourself “be strategic” on a Tuesday afternoon. You cannot grade your own empathy in a 1:1.
What you can see is behavior. Specifically, what you do in seven recurring moments: 1:1s, escalations, hiring loops, postmortems, feedback conversations, your own week, and conflict. Those seven moments are where good and great diverge in a way the team actually notices.
Here are the shifts.
Shift 1. In 1:1s
Definition: What you choose to ask in the 30 minutes you have one-on-one with each direct report every week.
Good managers ask for status. “What’s on your plate? What shipped? What’s blocked?” Useful, but the team can already see this in the project tool.
Great managers ask “what’s hard right now?” and then stay quiet. They listen for what is not said. A pause before “fine,” a redirect when the topic of a peer comes up, a shrug at a project the person used to care about.
The moment: Minute 4 of any 1:1. The status report has wound down and there is a small silence.
Upgrade move: Replace your first three status questions with one question: “What is the hardest part of your week right now?” Then count to seven before you speak again.
Shift 2. In escalations
Definition: What you do when a problem gets surfaced to you that the team could not solve on its own.
Good managers escalate cleanly. They take the issue up, frame it well, and bring an answer back. The work moves.
Great managers do all of that AND lower the temperature in the room first. Before they go up, they say something like “this is solvable, let’s slow down for ten minutes and figure out what we actually know.” A panicked team makes worse decisions. That is true even with a great manager fighting for them upstairs.
The moment: The Slack ping that starts with “we have a problem.”
Upgrade move: Before you respond to an escalation, name the temperature out loud. “Okay, this feels like a 7 out of 10 in the room. Let’s bring it down to a 4 before we decide anything.” Then ask what is actually known versus assumed.
Shift 3. In hiring loops
Definition: What you do in the first 48 hours of an open headcount.
Good managers fill seats. They write the JD, run the interviews, and make a call. The role gets filled, usually within a reasonable bar.
Great managers calibrate the bar before a single resume gets read. They sit down with the team, write the rubric, and align the panel on what “yes” actually means for this specific role on this specific team at this specific stage. Daniel, an engineering lead at a mid-stage SaaS company, blocks two hours with his panel before the JD goes live. Six months later his team has the lowest regret rate in the org.
The moment: The day the headcount approval lands in your inbox.
Upgrade move: Before you open the JD doc, run a 60-minute calibration session with your panel. Three required outputs: the rubric, the disqualifiers, and one calibration candidate everyone has interviewed before so the panel scoring is anchored.
Shift 4. In postmortems
Definition: What you look for after something has gone wrong.
Good managers find the bug. The deploy that broke production, the spec that was wrong, the person who missed the handoff. They fix it, and they ship a learning.
Great managers find the system that made the bug invisible. Why did three people see the warning sign and none of them flag it? What was the incentive structure that made silence the safe choice? Sarah, a product manager who runs postmortems at a fintech, has a rule. The first 20 minutes are about the bug. The remaining 40 are about why the bug was allowed to live for as long as it did.
The moment: The first 30 seconds of any retrospective.
Upgrade move: Open every postmortem with two questions on the whiteboard. “What broke?” and “What made it hard for us to see it earlier?” Spend equal time on both.
Shift 5. In feedback
Definition: What you do in the moment when someone has done something that needs correcting.
Good managers say what’s wrong. They are direct, they cite the example, and they move on. The person hears the message.
Great managers leave the person more capable than they walked in. Same directness, same example, but they add the part most managers skip: what to do differently next time, and an offer to practice once before the real moment shows up. The standard does not move. The skill ceiling does.
The moment: Any time you find yourself rehearsing a hard sentence in the shower.
Upgrade move: Before any feedback conversation, write down three things on a sticky. The behavior, the impact, and the alternative move. If you cannot fill in the third box, your feedback is a complaint, not coaching.
Shift 6. In your own week
Definition: How your calendar actually looks on a Friday afternoon when you scroll back through the last five days.
Good managers stay on top of the work. Every meeting got attended, every review got done, every Slack got answered. The team is unblocked. The manager is exhausted.
Great managers protect 25% of their week for the work nobody else can do. Hiring decisions, performance calibration, the strategy doc that is two months overdue, the conversation with the peer team that nobody else has the relationship to have. They guard this block the way they would guard a customer meeting.
The moment: Whenever a meeting request lands in a previously empty 90-minute block.
Upgrade move: Block 10 hours a week as “manager work” before you do anything else on Monday. Treat them as immovable. If something has to break that block, something else on your calendar has to come off first.
Shift 7. In conflict
Definition: What you do when two people on your team disagree in front of you.
Good managers resolve the disagreement. They listen to both sides, find the merit in each, and call the decision. Things move forward. People feel heard.
Great managers extract the disagreement’s actual signal before they decide. Two strong engineers fighting about an architecture choice are usually fighting about something underneath, like risk tolerance, ownership, or a past decision that never got revisited. The decision the manager makes is the same on the surface. The conversation that gets there is different, and the team learns to argue better next time.
The moment: The third sentence of any disagreement that has gotten louder than it should be.
Upgrade move: Before you call the decision, ask “what are we actually disagreeing about underneath this?” Wait for an answer. Most of the time the surface fight is a proxy for a deeper unresolved question, and the deeper question is the one worth deciding.
The diagnostic
Score yourself honestly on each shift, using the last 30 days as evidence. Use what your team would say, not what you would say.
| Shift | 1 (good) | 2 (mixed) | 3 (great) |
|---|---|---|---|
| 1:1s | I ask for status | I ask one open question, then push back to status | I ask what is hard, and the silence is the work |
| Escalations | I escalate quickly | I escalate and try to keep the room calm | I lower the temperature before I take it up |
| Hiring | I fill the seat | I write a rubric most of the time | I calibrate the panel before the JD goes live |
| Postmortems | I find the bug | I find the bug and one process gap | I find the system that made the bug invisible |
| Feedback | I say what is wrong | I say what is wrong and what to do | I leave the person more capable than they came in |
| Calendar | I stay on top of the work | I block focus time sometimes | I protect 25% for work only I can do |
| Conflict | I resolve the disagreement | I listen to both sides, then decide | I find the disagreement underneath the disagreement |
Add up your score. 7 to 12 means you are running the operating cadence well and the next quarter is about deepening one shift at a time. 13 to 17 means you are mid-transition. 18 to 21 means you are running compound behavior, and the work is to spread it to the next layer of leaders.
Pick your lowest score. That is the shift to work on this quarter. Not all seven. One.
The 12-week reality check
The honest reframe of this post is that none of these shifts are personality. They are practices. Across 3,000+ managers in 40+ organizations, Risely has seen consistent 26% improvement on targeted manager skills in 12 weeks. The condition: the practice has to be specific, measured weekly, and reinforced inside the actual moments above. 73% of managers in the program engage with daily nudges, because the nudge lands inside the actual 1:1, escalation, or postmortem they were already going to run.
The shift from good to great is not adding traits. It is upgrading what you already do.
Closing CTA
Pick the lowest-scoring shift on the diagnostic. Run the upgrade move for it for the next two weeks. Then come back and rate yourself again.
If you want the deeper structural read on how all seven of these fit into a manager’s full operating system, the flagship guide is the next step. Read how to effectively manage your team.
Frequently Asked Questions
What is the actual difference between a good manager and a great manager? A good manager runs the operating cadence reliably. A great manager runs the same cadence but uses each weekly moment (1:1s, escalations, hiring, postmortems, feedback, conflict) to compound their team’s capability over time. The difference is not personality, it is what they do inside the moments they already have on their calendar.
Can a good manager become a great manager? Yes, and almost always within the same role. Risely’s coaching data shows 26% measurable skill improvement in 12 weeks across 3,000+ managers. The shift is not about becoming a different person. It is about changing what you do in 1:1s, escalations, and postmortems you are already running.
How do I know which behavior shift to work on first? Use the diagnostic above. Rate yourself 1 to 3 on each of the 7 shifts. Your lowest score is your first target. Most managers score lowest on the calendar shift (protecting 25% for work nobody else can do) and the postmortem shift (finding the system, not the bug).
Is this list research-backed or opinion? Both. The 7 shifts come from observed behavior across 5,000+ coaching conversations with managers in 40+ organizations. Each shift maps to a moment that already exists on a manager’s calendar, so the diagnostic is observable, not abstract.