Your direct report questions every decision. They need more time than others to commit. They push back on initiatives that others accept without hesitation.
This isn't resistance. It's Reasoning. And once you understand how to manage it, you'll have one of your most valuable team members.
I worked with a department head at a manufacturing firm in Johor who was ready to put his senior engineer on a performance improvement plan. "He challenges everything I say," the manager told me. "It feels like he doesn't respect my authority." When we dug deeper, we discovered the engineer had flagged three process risks in the previous quarter alone -- every one of them legitimate. The manager wasn't dealing with insubordination. He was dealing with a Reasoning-dominant team member whose contributions were being misread as conflict.
Sound familiar? Here's what I've learned about getting the best from these people.
What Your Reasoning Reports Actually Need
Transparency in decision-making. They need to understand the why, not just the what. When decisions seem arbitrary, they disengage. I've seen this happen repeatedly -- a leader announces a direction without sharing the logic, and the Reasoning person mentally checks out.
Time to process. Don't spring complex decisions on them in meetings. Share information in advance. This one small adjustment changes everything.
Respect for their analysis. Their questions aren't attacks -- they're contributions. Value the rigor.
Data access. Let them examine evidence themselves rather than relying on summaries. They trust what they can verify.
Intellectual challenge. Routine work without complexity bores them. Keep their minds engaged, or you'll lose them to someone who will.
How to Run 1:1s That Actually Work
With Reasoning reports, consider:
- Share topics in advance so they can prepare thoughts
- Go deeper on fewer topics rather than surface-level on many
- Ask for their analysis on problems you're facing -- they love this
- Explain your reasoning when discussing decisions
- Allow silence for processing -- it's not disengagement
Here's something I tell every manager I coach: if your 1:1 with a Reasoning report feels like a rapid-fire status update, you're doing it wrong. These conversations should feel more like a strategy discussion between peers. Give them a problem to chew on before the meeting, and watch the quality of the conversation transform.
Giving Feedback That Actually Lands
Reasoning types respond best to feedback that:
- Is evidence-based. Specific examples, not vague impressions
- Includes rationale. Why does this matter? What's the impact?
- Is logically consistent. Don't contradict yourself across situations
- Invites dialogue. Let them ask clarifying questions
Avoid emotional appeals, vague criticism, or feedback that seems arbitrary. I once observed a manager tell a Reasoning team member, "You just need to be more of a team player." The employee's response? "Can you give me a specific example of when I wasn't?" That's not pushback -- that's a Reasoning person asking for the data they need to actually improve. If you can't provide it, the feedback falls flat.
Development and Growth
Help your Reasoning reports grow by:
- Assigning complex problems that require deep analysis
- Including them in strategy work where their thinking adds value
- Teaching them to communicate conclusions without exhaustive detail
- Encouraging timely decisions even with imperfect information
That last point is important. One of the biggest growth edges for Reasoning types is learning to act with 80% certainty rather than waiting for 100%. Your job as their manager is to create a safe environment where imperfect decisions aren't punished -- because that's the only way they'll learn to move faster.
The Mistakes I See Managers Make
Rushing their process. Forcing instant decisions degrades their contribution quality. But how many managers actually give people the space to think?
Dismissing their concerns. Their caution often identifies real risks. I've seen teams regret ignoring their Reasoning member's warnings more times than I can count.
Treating questions as resistance. They're trying to understand, not obstruct. Once you internalize this distinction, your whole relationship shifts.
Over-simplifying communication. They want the full picture, not just headlines. Give them the details, and they'll reward you with better analysis.
When You Get This Right, Everything Changes
Well-managed Reasoning reports become your trusted advisors. They catch problems before they escalate. They improve decision quality across the team. They provide the analytical depth that prevents costly mistakes.
The manager in Johor I mentioned earlier? He shifted his approach -- started sharing context before decisions, gave his engineer advance notice on agenda items, and explicitly asked for risk assessments. Within two months, he told me that engineer had become the person he relied on most. Same person, same style. Different management approach, completely different outcome.
The investment in managing their way yields a team member who makes everything they touch more rigorous and defensible. And honestly? That's the kind of person every leader needs on their team.
