You give a report a quick verbal brief and expect them to run with it. Instead they come back with a list of clarifying questions, then ask for a day to think it over. To you it reads as hesitation. To them, your brief was so thin it would have been irresponsible to start without checking. Neither of you is wrong. You just work differently, and nobody has said so out loud yet.
This is one of the most common sources of manager-report friction, and one of the most misdiagnosed. It gets labeled as a personality clash, an attitude problem, or a coaching opportunity, when it’s usually something narrower and more fixable: a mismatch in work style, specifically in pace or focus. Once you can see the mismatch clearly, most of the friction becomes something you can design around instead of something you just tolerate.
Key Takeaways
- A report who works nothing like you is usually a pace or focus mismatch.
- Diagnose which axis the mismatch is on before you adjust anything: are you moving at different speeds, or paying attention to different things?
- Adjust the mechanics, how you delegate, how you give feedback, how you read their behavior in a meeting, rather than trying to change how they work.
- Name the mismatch out loud and agree on one concrete accommodation. That single conversation does more than months of quiet frustration.
- If the outputs are genuinely not landing, it’s a performance conversation, and calling it a style difference helps no one.
Before you change how you manage someone, get specific about what’s actually different. Two questions cover most of it.
Are you moving at different speeds? If you decide fast and they want to deliberate, or you like to sit with something and they push to act, that’s a pace mismatch. It shows up around deadlines, in how much certainty each of you needs before committing, and in how one of you feels when a plan changes.
Are you paying attention to different things? If your first instinct is the task, the logic, the quality of the output, and theirs is the people, the morale, how a decision is going to land, that’s a focus mismatch. It shows up in what each of you thinks a good update includes, and in which parts of a problem you each consider urgent.
You can be mismatched on one axis and perfectly aligned on the other. A fast manager and a fast report who differ only on focus have a very different problem from a manager and report who move at completely different speeds. Naming the specific axis stops you from applying a generic fix to a specific mismatch.
The handoff is where a pace or focus mismatch does the most quiet damage.
If you move faster than your report, your instinct is to brief lightly and trust them to fill the gaps. A steadier report often reads a light brief as a lack of clarity about what you actually want, and stalls rather than guess wrong. The fix isn’t to slow down permanently but to front-load one extra layer of context on the handoff: what the output needs to do, what a good version looks like, and what is genuinely open for them to decide. That costs you five minutes and removes the round of clarifying questions that was costing you more.
If your report is more people-focused than you are, a task-and-deadline brief lands as cold and slightly baffling. Add the one sentence you would normally skip: who this is for, why it matters to them, what changes for them once it’s done. For this person, that framing isn’t a nicety but the information they need to prioritize well.
Feedback is where style mismatches turn into hurt feelings if you’re not deliberate.
A direct, fast manager giving feedback to a steadier report can easily deliver it at a pace that feels like an ambush, three points in quick succession with no room to absorb any of them. The same content, given one point at a time with a pause after each, lands as useful instead of overwhelming. You keep the message intact and change only its shape, so the other person can actually take it in. The mechanics of delivering feedback without breaking trust matter especially when the two of you process information at different speeds.
Going the other way, if you are the steadier one managing a fast-moving report, your careful, caveated feedback can read as vague or non-committal to them. They want to know the one thing to change. Lead with it, then add the nuance.
A lot of manager-report friction is just misread signals.
A steady, thoughtful report who goes quiet in a fast-moving meeting is often still processing, and their silence gets logged as agreement or disengagement when it is neither. If that’s your report, build them an explicit on-ramp: “I’d like your read on this, take until tomorrow if you need it.” When a people-focused report opens a one-on-one with a few minutes on how the team is doing, that check-in is how they do the job well, and it usually surfaces something you would not have heard otherwise.
The pattern here is the same each time. The behavior that reads as a problem through your work style is often the exact thing that makes the person good at their job through theirs.
None of this works as a private adjustment you make in your own head. The single most useful move is to name the mismatch directly with the person.
Describe your own tendency first, then what you have noticed about theirs, then propose one concrete change. “I tend to decide fast and keep moving. You seem to want more time to think a decision through, and I think that’s why my updates land as rushed for you. Can we agree on a checkpoint before I treat something as final?” That framing puts the mismatch between the two of you, rather than inside them, and it turns a vague sense of friction into a specific working agreement.
If you manage more than one or two people, it’s worth doing this as a team exercise rather than one relationship at a time. Having everyone place themselves on the same two axes, pace and focus, gives the whole team a shared way to talk about the friction. Lynxify.me built a Work Style Quiz for this: about 8 to 10 minutes per person, and everyone comes out with a placement on both axes and the trade-offs that come with it. The value isn’t the labels themselves but the fact that the team suddenly has language for something they were all feeling and nobody was naming.
Be straight with yourself about the line here, because it’s easy to hide behind “we just have different styles.”
A work style mismatch produces friction around timing, tone, and process while the actual work still lands. If deadlines are slipping, quality is dropping, or the person isn’t doing what they committed to, that’s not a style difference, and managing around it as though it were does the person a disservice. They deserve the direct performance conversation instead of a permanent set of accommodations for a problem that was never about work style.
The manager’s job with a genuine style mismatch isn’t to convert the person to your way of working but to build enough shared vocabulary and specific accommodations that the difference stops costing both of you energy. Done well, a report who works nothing like you ends up being one of the more useful people on the team, precisely because they catch and care about the things you don’t.
Dmytro Shtapauk
Practical tips and experience from top-notch experts