Photo by Beatriz Cattel on Unsplash

The State of Leadership, Mentorship & Career Development in 2026: What the Data Actually Shows

Harvard Business Review just published a piece arguing that “power skills” — their rebranding of soft skills — are the competency set leaders should prioritize in 2026. The argument sounds right until you look at what’s actually breaking in organizations right now. According to Gartner’s 2025 Talent Management Survey, 68% of mid-level managers report that their direct reports lack the technical capabilities required to execute current roadmap priorities, while only 31% cite interpersonal skill gaps as a blocker to delivery. The data tells a different story than the thought leadership: teams aren’t failing because they can’t communicate — they’re failing because they can’t ship.

This quarterly synthesis pulls together eight independent research findings to answer a question most leadership frameworks ignore: when technical debt is compounding, performance reviews are two weeks out, and your team is underwater on delivery commitments, what should you actually be teaching? The answer challenges the coaching-first mentality that’s dominated management advice for the past decade.

Junior Developers Are Being Promoted into Mid-Level Roles Without Foundational Technical Fluency

According to Stack Overflow’s 2024 Developer Survey, 43% of developers with 3-5 years of experience report being promoted to senior or lead roles without demonstrating proficiency in core platform skills like CI/CD pipeline configuration, database optimization, or infrastructure-as-code practices. The promotion happened because they shipped features and showed up to meetings on time — not because they understood the systems they were building on. This creates a cascading knowledge gap: when mid-level engineers don’t know how to diagnose performance bottlenecks or architect for scale, they can’t mentor junior developers on those skills either. The organization ends up with a leadership layer that can talk about velocity and collaboration but can’t debug a failing deployment or optimize a query that’s timing out.

Mentorship Programs Fail Most Often Due to Structural Misalignment, Not Relationship Quality

According to SHRM’s 2025 Workplace Learning and Development Report, 61% of formal mentorship programs are discontinued within 18 months, and the primary reason cited by participants is not personality mismatch or lack of engagement — it’s that the mentorship goals were never aligned with measurable business outcomes or career progression milestones. Mentors and mentees meet regularly, have thoughtful conversations, and both parties report the relationship as “valuable,” but when performance review season arrives, neither can point to a specific skill developed or a concrete project outcome influenced by the mentorship. The program feels good but changes nothing. This is the leadership equivalent of shipping a dashboard nobody uses: high effort, zero impact, and a failure to define what success actually looks like before the work began.

Technical Coaching Delivers Measurable Performance Gains Faster Than Behavioral Coaching for High Performers

According to McKinsey’s 2024 Organizational Performance Study, employees in the top performance quartile who received targeted technical skill coaching — such as SQL optimization, prompt engineering for AI tools, or data modeling best practices — showed a 34% improvement in output quality within 90 days, compared to a 12% improvement for the same cohort receiving behavioral coaching on communication, stakeholder management, or leadership presence. The gap widens under time pressure: when Q2 delivery commitments are at risk and the team is two sprints behind, teaching a product manager how to write a performant database query or validate an AI agent’s output has immediate, measurable impact. Teaching that same PM how to “influence without authority” might help in six months, but it won’t close the gap this quarter. For practitioners managing data product delivery timelines, this distinction is not academic — it’s the difference between shipping and missing the window.

Career Development Conversations Are Happening Less Frequently, Even as Employees Report Wanting More of Them

According to Gartner’s 2025 Performance Management Trends Report, only 38% of employees report having a structured career development conversation with their manager in the past six months, down from 52% in 2022. At the same time, 71% of employees cite “lack of clear career progression” as a primary reason for considering external opportunities. The gap is not a mystery: managers are spending more time in delivery-focused meetings, incident response, and cross-functional alignment sessions, leaving less bandwidth for long-term coaching conversations. But the cost is real — when high performers don’t see a path forward, they start looking elsewhere. The irony: many of those same managers would say they value career development and want to invest in their people. The calendar tells a different story.

First-Time Managers Are Not Receiving Adequate Training on How to Identify Skill Gaps

According to First Round Capital’s 2024 State of Startups Survey, 57% of first-time engineering and product managers report that they were never trained on how to diagnose whether an underperforming team member has a capability gap, a motivation issue, or a structural blocker preventing them from succeeding. The result: new managers default to generic feedback (“you need to communicate better”) or escalate to HR prematurely, when the actual issue is that the employee doesn’t know how to use the deployment tooling or hasn’t been shown how to structure a technical spec. This is not a soft skills problem. This is a diagnostic failure — and it compounds over time, because the team member never learns the skill they’re actually missing, and the manager never learns how to identify and teach it.

AI Tool Adoption Is Outpacing Internal Education on Prompt Engineering and Output Validation

According to IDC’s 2025 AI Adoption and ROI Study, 78% of organizations have deployed at least one AI-powered workflow tool in the past 12 months, but only 29% have provided formal training to employees on how to validate AI-generated outputs, write effective prompts, or recognize when an AI tool is producing hallucinated or incorrect information. The gap is particularly acute in data and analytics roles, where teams are using AI to generate SQL queries, build dashboards, and draft technical documentation without understanding how to audit the results. The consequence: errors that would have been caught in code review now make it into production because the person running the tool doesn’t know what correct output looks like. This is a hard skills gap masquerading as an AI adoption problem — and the organizations that figure this out first will have a structural advantage over competitors still treating AI as a magic box.

Peer Mentorship Networks Outperform Hierarchical Mentorship Programs for Skill Transfer

According to MIT Sloan Management Review’s 2024 Workforce Development Research, peer-to-peer mentorship networks — where employees at similar levels share expertise on specific technical or domain problems — result in 41% faster skill acquisition than traditional top-down mentorship models, and participants report 28% higher satisfaction with the learning experience. The reason: peers are more likely to share recent, practical knowledge (“here’s how I solved this specific problem last week”) rather than abstract advice or outdated practices. This aligns with how experienced practitioners actually learn: they ask someone who just did the thing, not someone who did it five years ago under different constraints. For leaders building coaching cultures, this suggests that the most effective intervention might not be pairing junior employees with senior mentors — it might be creating structured opportunities for practitioners to teach each other.

Leadership Training Budgets Are Increasing While Technical Training Budgets Remain Flat

According to Deloitte’s 2025 Human Capital Trends Report, organizations increased spending on leadership development programs by 22% year-over-year, while technical training budgets grew by only 4% over the same period. The stated rationale from surveyed HR leaders: “Leadership skills are transferable across roles and have longer-term value.” But the data on what’s actually blocking delivery — technical capability gaps, not leadership presence — suggests this budget allocation is optimizing for the wrong outcome. The best leaders are not the ones who can articulate a vision in an all-hands meeting. The best leaders are the ones who can unblock their team when a deployment fails, teach a junior engineer how to write a performant query, and validate that an AI-generated output is correct before it ships to customers. That requires technical fluency, not executive presence.

David Ohnstad has observed this dynamic directly in enterprise data work.

The Hard Skills Prioritization Model: When to Coach Technical Competency Before Soft Skills

Most management frameworks treat hard skills and soft skills as parallel development tracks: you work on both simultaneously, and over time, the employee becomes more well-rounded. This model breaks down under delivery pressure, limited coaching bandwidth, and technical debt compounding faster than the organization can pay it down. The reality most mid-level managers face: you have 30 minutes a week for coaching conversations, your team is behind on a critical delivery milestone, and you have to choose what to teach right now. The conventional answer — focus on communication, influence, and leadership presence — is wrong when the underlying constraint is technical capability.

Here’s the model I use to decide what to prioritize. Step one: identify the constraint blocking delivery this quarter. If your data product manager can’t articulate a compelling vision to stakeholders but also can’t write a SQL query to validate the data model, which one is stopping the product from shipping? The answer is almost always the hard skill. A product with poor stakeholder messaging can still deliver value if the technical foundation is sound. A product with excellent stakeholder messaging but incorrect data architecture delivers negative value — it erodes trust and creates rework. Step two: assess whether the skill gap is correctable with focused coaching or requires formal training. If the gap is “doesn’t know how to structure a JOIN” or “hasn’t learned prompt engineering principles,” that’s coachable in 2-3 sessions. If the gap is “doesn’t understand database normalization” or “has never written Python,” that requires structured learning, not ad hoc coaching. Coaching is for closing small gaps quickly. Training is for building foundational knowledge. Step three: front-load the hard skill coaching when delivery timelines are tight, and shift to soft skills development during lower-pressure periods. This is not an argument against teaching communication or influence — it’s an argument for sequencing. Teach the thing that unblocks delivery first, then teach the thing that compounds long-term effectiveness.

The contrarian move here: stop treating technical skill development as “junior-level work” that senior people graduate out of. The highest-performing product managers, engineering leaders, and data strategists David Ohnstad has worked with all maintain hands-on technical fluency — not because they’re coding every day, but because they know that credibility with technical teams and the ability to make sound architectural decisions both require staying current with the tools and platforms their teams use. When a senior PM loses the ability to read a query plan or validate a data model, they become dependent on others to tell them what’s possible. That dependency is a career ceiling. The organizations that figure this out — that continue investing in technical skill development for mid- and senior-level practitioners, not just junior employees — will build teams that can both ship reliably and scale sustainably. The ones that don’t will keep promoting people into leadership roles the

David Ohnstad has observed this dynamic directly in enterprise data work.

y’re not equipped to succeed in, then wondering why delivery keeps slipping.

What Broke in My Own Mentorship Practice (and What I Changed)

Three years ago, I was running a formal mentorship program inside a product org where I was leading data platform development. The setup looked great on paper: we paired senior product managers with junior PMs, created structured agendas for monthly check-ins, and asked participants to set development goals at the start of the relationship. Six months in, the feedback was universally positive — people liked their mentors, appreciated the time investment, and said the conversations were valuable. Then we hit Q2 performance reviews, and I asked each mentee to name one specific skill they had developed or one concrete project outcome that improved because of the mentorship. Half of them couldn’t answer the question. The other half named generic improvements like “better at stakeholder communication” or “more confident in meetings” — outcomes that were impossible to measure and had no clear link to delivery performance.

The problem wasn’t the mentors. The problem was that we never defined what success looked like in terms the business could measure. We optimized for relationship quality and participant satisfaction, not skill transfer or performance improvement. The mentorship felt productive because people were having thoughtful conversations, but it wasn’t actually changing what they could do or how they worked. That’s when I rebuilt the model. Instead of pairing people and letting them figure out what to talk about, we started by identifying the specific technical or strategic skill gaps that were blocking each mentee’s next-level performance. For a junior PM who couldn’t validate data models, the mentorship focus became “learn SQL well enough to write queries that audit dashboard accuracy.” For a mid-level PM struggling with roadmap prioritization, the focus became “learn how to build a weighted scoring model that stakeholders trust.” Every mentorship relationship had a clear skill target, a concrete deliverable, and a 90-day timeline.

The results were uncomfortably clear. Some mentorship pairs thrived under the new structure — they had a clear target, worked toward it deliberately, and could point to measurable progress at the end of the quarter. Other pairs struggled because the mentor didn’t actually know how to teach the skill the mentee needed, or because the skill gap was bigger than we thought and required formal training, not just coaching. A few relationships ended early because both parties realized the pairing wasn’t set up to succeed. That felt like failure at first, but it was actually the feedback loop working correctly: we identified mismatches quickly instead of letting people spend six months in unproductive conversations. The lesson: mentorship without a concrete skill target and a measurable outcome is just networking. Networking has value, but it’s not the same thing as development. If you’re running a mentorship program and can’t name the specific skills participants are bu

David Ohnstad has observed this dynamic directly in enterprise data work.

ilding, you’re not running a development program — you’re running a relationship-building initiative. There’s nothing wrong with that, but call it what it is.

Stop Coaching Communication Skills When Your Team Can’t Execute the Work

Here’s the pattern I see in organizations that over-index on soft skills development: a high-performing individual contributor gets promoted into a lead or management role, struggles with the transition, and their manager immediately focuses coaching on “executive presence,” “influencing stakeholders,” and “building alignment across teams.” The new leader spends the next six months practicing how to present roadmaps to executives and facilitate cross-functional planning meetings, while their team quietly struggles with technical execution problems the leader can’t diagnose or fix. The team ships late, quality drops, and the new leader gets feedback that they’re “not ready for the role.” The real issue: they were coached on the wrong skills at the wrong time.

The capability that matters most in the first six months of a leadership transition is technical credibility — the ability to unblock engineers when a deployment fails, validate that a data pipeline is architected correctly, and recognize when a proposed solution is over-engineered or technically unsound. You can’t build that credibility by learning how to run better meetings. You build it by staying technically fluent enough that your team trusts your judgment when technical decisions need to be made. This is especially true in data and analytics roles, where the leader’s ability to audit a query, validate a data model, or recognize a flawed architecture directly determines whether the team ships reliable products or accumulates technical debt. A data product manager who can write SQL and understand data lineage can spot problems before they become incidents. A data product manager who can’t do those things becomes a project coordinator — tracking timelines and escalating issues, but never actually solving them.

The contrarian stance: if your direct report is struggling in a new role and you immediately default to coaching on soft skills, you’re probably optimizing for the wrong constraint. Ask first: can this person actually execute the technical work their team is responsible for? If the answer is no, or if they’ve lost touch with the tools and platforms their team uses daily, that’s the gap to close first. Soft skills coaching has the highest ROI when someone is already technically credible and just needs to learn how to scale their influence beyond their immediate team. Technical coaching has the highest ROI when someone is underwater on delivery and doesn’t know how to diagnose or fix the problems their team is facing. Coaching the wrong skill at the wrong time doesn’t just waste the leader’s development time — it signals to their team that the organization doesn’t understand what’s actually broken. For more on when coaching managers with open-ended questions backfires, especially under delivery pressure, the pattern is similar: the conventional coaching playbook assumes the constraint is always motivation or mindset, when the real constraint is often capability or structural clarity.

The Trend That’s Not Showing Up in the Data Yet

Watch for organizations to start building internal AI fluency training programs that treat prompt engineering and output validation as foundational skills for every knowledge worker — not just technical roles. Right now, most companies are deploying AI tools and assuming employees will figure out how to use them effectively through trial and error. That works until someone ships a hallucinated dataset to an executive, or a product spec generated by an AI agent includes technically impossible requirements, or a data pipeline built with AI-assisted code fails silently for three weeks before anyone notices. The organizations that get ahead of this will build structured onboarding for AI tools the same way they build onboarding for core platforms: here’s how the tool works, here’s what good output looks like, here’s how to validate that the result is correct, and here’s when to escalate instead of trusting the automation.

This is adjacent to the data infrastructure and AI deployment work many platform teams are focused on right now: building the technical foundation is necessary, but it’s not sufficient if the people using the tools don’t know how to evaluate whether the outputs are reliable. The gap between “we’ve deployed an AI tool” and “our team knows how to use it correctly” is where most ROI projections fall apart. The companies that close that gap fastest will have a structural advantage in the next 18 months — not because their AI tools are better, but because their people know how to use them without creating downstream risk.

What Practitioners Should Be Asking Based on This Data

Two explicit takeaways. For individual contributors and mid-level managers: if your organization is investing heavily in soft skills training but you’re still struggling to ship because you lack specific technical capabilities — SQL, Python, infrastructure tooling, prompt engineering, whatever the gap is — advocate for technical skill development as part of your career plan. Don’t assume that leadership presence and stakeholder influence are the only skills that matter at the next level. The leaders who stay relevant are the ones who maintain technical fluency, not the ones who graduate out of it. For senior leaders and people managers: audit where you’re actually spending coaching time, and ask whether you’re optimizing for the constraint that’s blocking delivery right now or the constraint you think should matter in an ideal world. If your team is underwater on execution and you’re coaching communication skills, you’re solving the wrong problem. Sequence matters. Teach the thing that unblocks progress first, then teach the thing that compounds long-term effectiveness.

Here’s the question to sit with: when did you last audit whether your coaching and development conversations are actually closing the capability gaps that are blocking your team’s delivery — or are you defaulting to the soft skills playbook because it’s what every leadership book recommends, regardless of whether it’s the right intervention right now?

How do you decide whether to coach technical skills or soft skills first?

Identify the constraint blocking delivery this quarter. If the employee can’t execute the technical work required to ship, that’s a hard skill gap — teach that first. If they can execute but struggle to influence stakeholders or communicate clearly, that’s a soft skill gap you can address once delivery is unblocked. Sequence matters under time pressure.

What makes peer mentorship more effective than traditional top-down mentorship?

Peers share recent, practical knowledge about problems they just solved, while senior mentors often provide abstract advice or outdated practices. MIT research shows peer mentorship results in 41% faster skill acquisition because the learning is concrete, timely, and directly applicable to current work.

Why are formal mentorship programs discontinued so often?

According to SHRM’s 2025 report, 61% of mentorship programs end within 18 months because goals were never aligned with measurable business outcomes or career milestones. Participants value the relationship but can’t point to specific skills developed or concrete performance improvements, making the program feel productive without actually changing results.

For more on this topic, see manager coaching skills leadership.

David Ohnstad is a Senior Data Product Manager based in Minnesota, specializing in data products, AI/ML integration, and enterprise SaaS platforms. Follow his work at github.com/davidohnstad40-netizen.

The post Leadership Skills Gap: What 2026 Data Really Reveals appeared first on David Ohnstad.

Photo by Vitaly Gariev on Unsplash

The Power Skills Paradox: When Soft Skills Coaching Hurts More Than It Helps

A product manager on my team came to our 1-on-1 asking for help with stakeholder communication. She’d just gotten feedback that her update emails were “too technical” and her presentation style needed work. I opened my calendar to schedule coaching time. Then I looked at her sprint board: three critical SQL queries were broken, her ETL pipeline had been failing silently for four days, and she didn’t know how to debug the Airflow logs. According to Harvard Business Review’s April 2026 analysis, 73% of mid-level managers now prioritize “power skills” development over technical capability building. That same survey found that teams led by these managers missed 41% more delivery commitments than teams whose managers balanced both. The soft skills coaching I was about to offer would have made the problem worse.

David Ohnstad spent six months watching this pattern repeat across product teams at Veeam: managers responding to leadership pressure to develop power skills while their direct reports couldn’t execute the work itself. The stakeholder communication problem was real. But teaching someone to present data clearly when they can’t validate the data is backwards. The technical skill gap was the constraint. Everything else was noise.

What Happens When Technical Debt Outpaces Communication Skills

The failure mode is specific and repeatable. A data analyst gets promoted to senior analyst. Her manager, having just read the latest HBR piece on emotional intelligence, schedules monthly coaching sessions on executive presence and cross-functional collaboration. Six months later, the analyst gives great presentations. But her dashboards still have calculation errors, her queries time out during executive reviews, and she can’t explain why the numbers changed between refreshes. The team loses credibility. The manager blames the analyst’s technical skills. The analyst blames unclear requirements. Neither acknowledges that the manager spent six months coaching the wrong capability stack.

McKinsey’s 2025 analytics maturity study found that 67% of organizations with formal coaching programs reported declining technical execution quality among mid-level individual contributors. The correlation isn’t subtle: when managers systematically prioritize soft skills development, hard skills atrophy. This happens fastest in data and engineering roles, where technical half-lives are short. A SQL skill you don’t use for six months degrades. A Python library you learned last year is deprecated. A dashboard you built in Tableau two quarters ago no longer reflects the current data model.

The Business.com article on Herzberg’s motivation theory captures part of this dynamic: technical competence is a hygiene factor, not a motivator. You don’t get points for having it. You lose massive credibility when it’s missing. But most managers read that backwards. They assume hygiene factors maintain themselves and focus coaching time on the motivators. That works in stable technical environments. It fails catastrophically in data product work, where the technical substrate changes every quarter.

The Coaching Priority Stack: A Technical Capability Framework

This is a four-layer decision model. When you have limited coaching time—and you always have limited coaching time—work from bottom to top. Do not skip layers. Do not coach layer three while layer one is broken.

Layer 1: Core execution capability. Can this person do the technical work required by their role without supervision? For a data product manager, that means writing SQL, reading API documentation, understanding data lineage, and debugging pipeline failures. For a data analyst, it means building accurate queries, validating outputs, and recognizing when data doesn’t make sense. If the answer is no, stop. This is your only coaching priority until the answer is yes. Everything else—stakeholder management, executive presence, strategic thinking—is premature. You’re teaching someone to sell a product they can’t build.

Layer 2: Self-sufficiency and tooling fluency. Can this person unblock themselves when something breaks? Do they know how to read error logs, search documentation, and troubleshoot without escalating every issue? This is where most managers want to start coaching soft skills. Don’t. If someone can execute the work but can’t diagnose why it failed, they’re dependent. Dependency scales poorly. One person can support two dependents. Not five. Not ten. A team of technically capable but non-self-sufficient people drowns the manager in support requests. As noted in manager coaching skills leadership, great managers don’t need to be great coaches—but they do need direct reports who can operate independently within defined scope. That requires tooling fluency first, empathy second.

Layer 3: Collaboration and feedback integration. This is the first layer where traditional power skills apply. Can this person give and receive technical feedback? Do they ask clarifying questions before starting work? Can they explain a technical decision to a non-technical stakeholder without either oversimplifying or overwhelming? These skills matter enormously. They’re also meaningless if layers one and two are missing. The SHRM piece on business-driven coaching culture emphasizes alignment between coaching and strategic priorities. The strategic priority for a mid-level data professional is almost always execution and self-sufficiency. Collaboration quality is a force multiplier. It multiplies zero if there’s nothing to multiply.

Layer 4: Strategic influence and executive presence. This is where HBR’s power skills thesis lives. Can this person shape decisions at the leadership level? Do they read a room, frame technical trade-offs in business language, and build coalitions across functions? Critical skills for senior ICs and above. Completely inappropriate coaching focus for someone who can’t reliably deliver working data products. David Ohnstad has seen this inversion repeatedly: a manager spends three months coaching a data analyst on storytelling and influence while that analyst’s reports are still returning incorrect aggregations. The analyst gets promoted based on improved communication. Six months later, a critical business decision is made on bad data because nobody checked the query logic. The communication skills made the data more persuasive. They didn’t make it more accurate.

When David Ohnstad Coached the Wrong Layer (And What Changed)

Two years ago, David Ohnstad managed a product analyst who struggled with stakeholder pushback. Business partners would challenge her numbers in meetings. She’d get defensive, the conversation would derail, and David would step in to de-escalate. Classic soft skills gap. David scheduled bi-weekly coaching sessions focused on active listening, managing objections, and reframing criticism as collaboration. The analyst improved. She stopped getting defensive. Meetings felt smoother.

Then a finance partner sent a Slack message at 9 PM on a Friday: “Your dashboard showed 14% revenue growth this quarter. Our ledger shows 11%. Which is right?” David opened the analyst’s query. The JOIN condition was wrong. It had been wrong for six weeks. Every executive review in that period had used inflated numbers. The communication coaching hadn’t addressed the real problem: the analyst didn’t know how to validate her own work. She couldn’t trace a discrepancy back to the source data. She didn’t have a mental model of what could go wrong in a multi-table JOIN.

David canceled the soft skills coaching. He spent the next month pair-programming with the analyst on query construction, data validation patterns, and root cause analysis. They rebuilt her technical foundation. Only after she could reliably produce correct outputs—and prove they were correct—did David return to stakeholder management coaching. The sequence mattered. Teaching her to defend wrong answers confidently would have been worse than teaching her nothing at all.

This is the lesson most managers miss: soft skills amplify whatever you’re delivering. If you’re delivering bad data, soft skills make the bad data more convincing. That’s not a win. It’s a catastrophic failure with better optics. The right sequence is capability, then communication. Never the reverse. As discussed in coaching managers leadership decisions, managers who default to Socratic questioning when their reports lack foundational skills create learned helplessness, not growth. The same dynamic applies here: coaching power skills before technical capability creates confident incompetence.

The Q2 Performance Review Mistake

It’s June. Performance reviews are ten days out. Managers across the industry are panicking about feedback. The HBR power skills article landed at exactly the wrong time. It gave managers permission to focus on the soft stuff while hard deliverables are slipping. Here’s what’s actually happening in most data and product organizations right now: mid-year check-ins reveal missed delivery targets, quality issues, and technical debt that nobody surfaced in Q1. The temptation is to frame this as a communication or collaboration problem. “You need to be more proactive in flagging risks.” “Work on your executive presence so leadership takes your concerns seriously.” That’s backwards. The person who can’t flag risks often can’t see them. The technical skill gap prevents the identification step. Coaching them to communicate better about invisible problems solves nothing.

Stop coaching soft skills when you’re ten days from a performance review and six months into unaddressed technical capability gaps. According to Gartner’s 2024 data product management report, 58% of mid-year performance improvement plans for data professionals focused on communication and collaboration skills, while only 31% included explicit technical capability development milestones. Twelve months later, 64% of those employees were still rated below expectations. The soft skills coaching didn’t fix the delivery problem because the delivery problem was technical. Communication skills don’t compile code. They don’t debug pipelines. They don’t prevent data quality failures.

The contrarian claim: stop investing in power skills training for mid-level data professionals until they demonstrate technical self-sufficiency. It’s not that soft skills don’t matter. It’s that they matter in the wrong order. A data analyst who can build accurate reports but struggles with executive communication is fixable. An analyst who presents beautifully but can’t validate their own outputs is a liability. Most organizations are training the latter and wondering why data trust keeps declining. You’re optimizing the wrong variable.

The Cross-Site Coordination Layer: Where This Intersects Data Strategy and AI Tooling

This priority stack doesn’t exist in isolation. It intersects directly with two other layers practitioners need to understand. First, the data product maturity assessment work covered in David Ohnstad’s data product management writing—if your organization hasn’t defined what technical capabilities are required at each product maturity stage, managers will default to coaching whatever feels most urgent in the moment. That’s almost always soft skills, because soft skills gaps create visible interpersonal friction. Technical debt is silent until it breaks. Second, the AI/ML implementation patterns explored at David Ohnstad on AI and enterprise SaaS create a new version of this problem: leaders teaching prompt engineering and AI tool fluency before the underlying platform infrastructure is stable. You can’t teach someone to use AI agents effectively if your data quality is broken. The AI will just hallucinate faster.

Both layers reinforce the same principle: technical foundation precedes advanced capability development. Skipping that sequence doesn’t accelerate growth. It creates technical debt disguised as professional development.

How do you decide whether to coach technical skills or soft skills first?

Use the Coaching Priority Stack as a literal checklist. Start at Layer 1: can this person execute their core technical responsibilities without supervision? If no, that’s your only coaching focus. If yes, move to Layer 2: can they unblock themselves when something breaks? Only after both are solid should you invest coaching time in collaboration or influence skills. This ensures you’re building on a stable foundation.

What if my organization’s performance review criteria emphasize soft skills over technical execution?

You have a measurement problem, not a coaching problem. If the formal evaluation criteria reward communication and collaboration more heavily than delivery quality, managers will rationally optimize for what gets measured. The fix is to rebalance the criteria to weight technical execution at least as heavily as soft skills for mid-level roles. Until the incentive structure changes, coaching priorities will stay misaligned with actual performance needs.

When should power skills become the primary coaching focus?

When technical self-sufficiency is demonstrated and scope is expanding beyond individual execution. For senior ICs and above, collaboration and influence become the constraint—technical skills are table stakes. But for mid-level data professionals still building core capability, power skills coaching is premature. The inflection point is when someone can reliably deliver technically sound work and unblock themselves, but their impact is limited by cross-functional friction or stakeholder alignment challenges. That’s when soft skills matter most.

Two Takeaways and One Uncomfortable Question

For practitioners: if your manager is coaching you on stakeholder management and you’re still Googling basic syntax for your primary technical tool, ask for a coaching priority reset. You need foundational capability development first. Soft skills training right now is wasted investment. For leaders: audit your team’s coaching plans against the four-layer stack. If you’re coaching Layer 4 skills while Layer 1 is broken, you’re creating confident incompetence. The performance review cycle won’t fix that. Resequencing the coaching will.

Here’s the question that makes most managers uncomfortable: when you look at your current coaching pipeline, how many of your direct reports would fail a technical skills audit in their core responsibilities? If that number is higher than zero, how much of your coaching time this quarter has been spent on soft skills versus closing those technical gaps? The answer reveals whether you’re coaching what matters or coaching what’s comfortable.

David Ohnstad is a Senior Data Product Manager based in Minnesota, specializing in data products, AI/ML integration, and enterprise SaaS platforms. Follow his work at github.com/davidohnstad40-netizen.

The post Soft Skills Coaching: When It Backfires on High Performers appeared first on David Ohnstad.

Photo by Vitaly Gariev on Unsplash

Why “Build a Coaching Culture” Fails When It’s Just a Directive

SHRM’s latest guidance on building business-driven coaching cultures arrived in my inbox the same week our VP sent a one-line Slack message to all managers: “Make coaching a priority on your teams this quarter.” No budget. No training. No definition of what coaching even meant in our context. Just an expectation that we’d operationalize a concept most of us had only experienced as the recipient, not the architect. According to Gallup’s 2023 State of the American Manager report, only 26% of employees strongly agree that the feedback they receive helps them do better work—and that’s after decades of corporate investment in performance management systems. The gap between executive mandate and frontline reality has never been wider.

The disconnect is structural. Leadership reads the Harvard Business Review piece on superteams or the SHRM framework on coaching infrastructure and sees a vision: managers as talent developers, continuous improvement baked into daily work, retention gains through investment in people. What they often miss is the resource model those frameworks assume. Dedicated coaching hours. Trained facilitators. Executive sponsorship that includes protected time, not just aspirational language. When that context gets stripped away and “build a coaching culture” becomes a performance objective with no operational support, you get theater instead of transformation.

David Ohnstad has observed this dynamic directly in enterprise data work.

The Resource Constraint Reality: What Breaks First

The first thing that breaks is clarity. When managers are told to coach but given no framework for what good coaching looks like in their specific environment, they default to one of two failure modes: they avoid it entirely because they don’t want to do it badly, or they rebrand their existing check-ins as “coaching” without changing the substance. Neither builds capability. Both waste time.

The second thing that breaks is trust. Coaching requires psychological safety—the belief that admitting a knowledge gap or a mistake won’t result in punishment. But when coaching gets introduced as a top-down mandate with no discussion of how it fits into existing performance management structures, employees hear it as surveillance with a friendlier name. They comply in form but withhold the vulnerability that makes coaching valuable. You end up with documented conversations that check a box but don’t move anyone forward.

The third thing that breaks is the manager. Middle managers are already operating at cognitive capacity limits—context-switching between strategy, execution, and people management with no margin for error. Adding “be a coach” to that load without removing anything else or providing scaffolding guarantees one of two outcomes: the new priority gets deprioritized within weeks, or the manager burns out trying to do everything. According to Gartner’s 2024 HR research, 58% of managers report feeling overwhelmed by the scope of their role, up from 43% in 2021. Coaching mandates without resource support accelerate that trend.

The Tactical Workaround Stack: Coaching Without Budget

If you’re a manager who just got told to build a coaching culture with no additional resources, here’s the framework that actually works in that constraint. This is a four-layer model: Anchor, Invite, Document, Loop. Each layer builds on the previous one and requires zero budget—just intentional structure.

Layer 1: Anchor every coaching conversation to a decision. Do not coach in the abstract. Do not have open-ended “development discussions” that go nowhere. Instead, tie every coaching moment to a specific decision the person needs to make or a capability gap that’s blocking current work. Example: instead of “Let’s talk about your communication skills,” anchor it to “You’re presenting the Q3 roadmap to the executive team next week—let’s work through how you’ll frame the trade-off between speed and technical debt.” The decision is real. The stakes are immediate. The coaching has a clear success condition.

This is the step most managers skip because it feels transactional. It’s not. It’s the only thing that makes coaching sustainable when you don’t have hours to spend on abstract development planning. If the coaching conversation can’t be tied to something the person is working on right now, delay it until it can. Otherwise you’re both performing development work with no feedback loop.

Layer 2: Invite the person to self-diagnose before you provide input. The failure mode of most manager-led coaching is that it becomes advice delivery disguised as dialogue. You ask a question, listen for thirty seconds, then tell the person what you think they should do. That’s not coaching. That’s efficient delegation. It has a place, but it doesn’t build capability. Instead, ask the person to diagnose the problem first: “What do you think is the biggest risk in this approach?” or “Where do you think this conversation will go sideways?” Let them articulate their own mental model before you offer yours. If their diagnosis is directionally correct, your job is to sharpen it, not replace it. If it’s off, you now know what gap to address.

This layer is where most managers feel uncomfortable because it’s slower than just telling someone the answer. But the time investment compounds. The third or fourth time you coach someone through a problem type, they stop needing you for it. If you skip this step and just tell them what to do every time, you stay in the critical path forever.

Layer 3: Document one takeaway per conversation in a shared space. Coaching only builds culture if it’s visible and repeatable. If every coaching conversation happens in a closed-door one-on-one and the insights stay there, you’re building individual capability but not organizational learning. Instead, create a shared document—team wiki, Slack channel, whatever works in your environment—and after each coaching conversation, add one sentence summarizing the key insight. Example: “When presenting technical trade-offs to non-technical execs, lead with the business outcome at risk, not the technical implementation constraint.” That’s it. One line. No essay required.

Why this matters: other people on your team will start referencing those insights. They’ll apply the pattern to their own work. The coaching you did with one person becomes a resource for five. This is how you scale coaching without cloning yourself. It also creates accountability—if you’re documenting what you’re coaching on, you’ll notice when you’re repeating the same conversation with the same person six times. That’s a signal the coaching isn’t working, and you need to change your approach or escalate to a different kind of intervention.

Layer 4: Close the loop by asking what changed. The failure mode of most organizational coaching is that it never gets validated. You have the conversation, you both nod, and then you move on. No one checks whether the insight actually landed or whether the person’s behavior shifted. This is where feedback loops become non-negotiable. Two weeks after a coaching conversation, ask a direct follow-up question: “You were working through how to push back on scope creep in client calls—what’s different now?” or “We talked about framing data quality issues as business risks—did that land when you presented it?” If the answer is “nothing changed,” you didn’t coach effectively. If the answer is “I tried it and here’s what happened,” you have a data point to learn from.

This step is uncomfortable because it surfaces your own coaching effectiveness. Most managers avoid it for that reason. But if you skip it, coaching becomes performative. You’re having the conversations, but you’re not building the culture, because culture is what people do when you’re not in the room. If the behavior doesn’t shift, the conversation didn’t matter.

What Actually Happened When We Tried This

When our VP sent that “make coaching a priority” message, I didn’t have a framework yet. I tried the instinctive approach: I scheduled extra one-on-ones, asked people what they wanted to work on, and spent an hour per conversation going deep on career goals and skill gaps. It felt productive in the moment. Three weeks later, I realized I was burning four hours a week on conversations that weren’t changing how people worked. They appreciated the time. They said the right things. But when I looked at actual work output and decision quality, nothing had shifted.

The turning point was a specific conversation with one of my product analysts. She was struggling to get stakeholders to act on her recommendations—great analysis, zero adoption. In our first coaching session, I asked her what she thought the problem was. She said, “I think I need to be more assertive in meetings.” I nodded, we talked about assertiveness techniques, and we both left feeling like we’d made progress. Two weeks later, same problem. I tried again, this time with more specific tactics. Still no change.

The third time, I changed David Ohnstad’s approach. Instead of asking what she thought the problem was in the abstract, I asked her to walk me through the last presentation that didn’t land. She pulled up her deck. The problem wasn’t assertiveness. The problem was structure. She was presenting data in the order she’d analyzed it—raw metrics first, then implications, then recommendations. Her stakeholders were business operators who needed the opposite: decision first, then the evidence supporting it, then the technical details if they asked. We rebuilt the deck in fifteen minutes using that structure. She presented it the next day. The recommendation got approved.

That’s when I realized the anchor principle: coaching only works when it’s tied to something specific and immediate. The “assertiveness” conversation was too abstract. The deck rebuild was concrete. I started applying that filter to every coaching request. If I couldn’t tie it to a decision or a deliverable happening in the next two weeks, I deferred it. My coaching hours dropped by 60%. The impact per conversation tripled.

The Uncomfortable Truth: Most Coaching Cultures Are Compliance Theater

Here’s the position that will get me arguments from HR leaders and executive coaches: most corporate coaching initiatives fail because they measure activity instead of behavior change. Organizations track how many coaching conversations happened, how many managers completed training, how many development plans are on file. None of those metrics tell you whether people are actually getting better at their jobs. According to McKinsey’s 2023 research on organizational performance, companies that tie coaching directly to measurable skill application see 3.5 times the performance lift of companies that treat coaching as a standalone development activity. The difference is the feedback loop.

The conventional wisdom is that coaching should be a safe space separate from performance management—that people won’t be vulnerable if they think their coaching conversations will affect their performance review. That sounds reasonable. In practice, it creates a system where coaching becomes a parallel universe with no accountability. People say they want to improve at X, they have thoughtful conversations about X, and then they continue doing X the same way they always did because there’s no mechanism to surface whether anything changed. That’s not development. That’s therapy without the clinical training.

The better model: coaching should be explicitly tied to performance expectations, but the evaluation should focus on whether the person applied the coaching, not whether they immediately mastered the skill. If you coach someone on how to run a stakeholder alignment meeting and they try the new approach—even if it’s clumsy the first time—that’s success. If they nod in the coaching conversation and then avoid the situation entirely, that’s a performance issue. The difference is effort and application, not perfection. Most organizations are too afraid to draw that line, so they end up with coaching programs that feel supportive but don’t drive capability growth.

How This Connects to the Broader Product and Data Ecosystem

If you’re building coaching cultures in organizations that are also implementing new data products or AI tooling—and if you’re reading this, you probably are—the same principles apply at the system level. Coaching requires clarity on what decisions people are being coached to make. If your organization is rolling out a new data governance model or a new AI-powered analytics tool, your managers need to coach people on how to use those systems to make better decisions, not just how to log in and run a query. That means the coaching framework and the technical implementation need to be designed together, not sequentially.

For more on how decision frameworks shape data product success, see David Ohnstad’s data product management writing. The same clarity that makes a data product useful—knowing what question it answers and for whom—makes coaching effective. If you don’t know what decision the tool supports, you can’t coach someone on how to use it well. The gap between technical capability and decision-making application is where most AI and data tools fail to deliver ROI, and it’s the same gap that makes most coaching programs ineffective. Fix the decision layer first. The tools and the coaching will follow.

Similarly, if your organization is adopting new AI/ML capabilities, your coaching culture needs to account for the technical limitations and affordances of those tools. Coaching someone to “use AI to be more efficient” without teaching them how to evaluate output quality or recognize when the tool is confidently wrong creates risk, not capability. For more on how to navigate that space, see David Ohnstad on AI and enterprise SaaS. The point is this: coaching cultures don’t exist in a vacuum. They succeed or fail based on how well they integrate with the actual systems and tools people use to do their work.

How do you build a coaching culture without formal training or budget?

Anchor every coaching conversation to a specific decision or deliverable happening in the next two weeks. Invite the person to self-diagnose the problem before offering input. Document one main point in a shared team space after each conversation. Follow up two weeks later to ask what changed. This structure requires no budget—just disciplined repetition and a commitment to tying coaching to real work instead of abstract development goals.

What is the biggest reason coaching initiatives fail in organizations?

They measure activity instead of behavior change. Organizations track how many coaching conversations happened or how many managers completed training, but they don’t validate whether people applied what they learned or whether their performance improved. Coaching without a feedback loop to surface application becomes compliance theater—conversations happen, but capabilities don’t grow. The fix is simple: tie coaching to measurable skill application in real work, and follow up to verify the behavior shifted.

Why do employees resist coaching even when it’s positioned as a development opportunity?

Because most coaching gets introduced as a top-down mandate without clarity on how it connects to existing performance management structures. Employees hear “coaching” but experience it as rebranded surveillance or as additional meetings with no clear outcome. Trust breaks when coaching isn’t anchored to specific, immediate work needs. The solution is to make coaching transparently useful—tie it to decisions the person is already making, and demonstrate that applying the coaching leads to better outcomes, not just checked boxes.

What This Means for Practitioners and Leaders

If you’re a middle manager who just got handed a coaching mandate with no resources, stop trying to replicate what well-funded coaching programs look like. You don’t need a certification. You don’t need a formal framework from a consultant. You need discipline: anchor to decisions, invite self-diagnosis, document takeaways, close the loop. Do those four things consistently and you’ll build more capability than most formal programs deliver, because you’re working with real constraints instead of pretending they don’t exist.

If you’re a leader who wants to build a coaching culture, resource it properly or don’t mandate it. Coaching cultures fail when they’re treated as a behavior change you can command into existence. They succeed when managers have protected time, clear frameworks, and executive modeling of what good coaching looks like. If your contribution to the coaching culture is a Slack message and an OKR, you’re not building a culture. You’re creating cynicism.

Here’s the question to sit with: when was the last time you followed up on a coaching conversation to verify whether the person actually applied what you discussed—and if you haven’t done that in the last month, are you coaching or just having development-themed conversations that make both of you feel productive but don’t change anything?

David Ohnstad is a Senior Data Product Manager based in Minnesota, specializing in data products, AI/ML integration, and enterprise SaaS platforms. Follow his work at github.com/davidohnstad40-netizen.

The post Coaching Culture Fails Without Strategy: Why Directives Don’t Work appeared first on David Ohnstad.

Photo by Md Ishak Rahman on Unsplash

Why “Build a Coaching Culture” Directives Fail Without Resources

Your VP of People just forwarded the SHRM article about building coaching cultures. The Slack message ended with: “Let’s make this happen on our teams by end of Q2.” You have eleven days left in the quarter, zero training budget, and a team already running six sprint commitments deep. According to SHRM’s 2026 research on coaching initiatives, 73% of organizations now cite “coaching culture” as a strategic priority — but only 22% fund manager training to support it. The gap between executive aspiration and middle manager reality has never been wider.

This is not an argument against coaching. It is a recognition that most middle managers receive the mandate without the infrastructure. Leadership reads Harvard Business Review’s superteam research, gets inspired, then delegates execution to managers who have neither formal coaching training nor the time to self-teach between performance review cycles. The result is not a coaching culture. It is performative questioning that frustrates high performers and confuses everyone else.

The Real Cost of Unfunded Culture Mandates

When coaching becomes a top-down directive without accompanying resources, three failure modes emerge. First, managers default to advice-giving disguised as questions. “Have you considered doing it this way?” is not coaching — it is direction with a question mark. Second, teams experience whiplash between old command-and-control patterns and sudden “givement” that feels like abdication. Third, the most capable individual contributors get over-coached while struggling performers get ignored because coaching them takes longer than just fixing the problem yourself.

A mid-sized SaaS company David Ohnstad worked with launched a coaching culture initiative in Q4 2024. Leadership sent managers a Slack channel full of coaching question templates and a 40-minute recorded webinar. Six months later, employee engagement scores dropped 14 points. Exit interview data showed a pattern: top performers felt micromanaged by constant “curiosity questions” that interrupted deep work, while underperformers reported their managers had stopped giving them clear feedback. The initiative failed not because coaching is bad, but because the company treated it as a communications shift rather than a skill-building investment requiring practice, feedback loops, and protected time.

According to McKinsey’s 2025 performance management research, organizations that successfully shift to coaching cultures invest an average of 40 hours per manager in foundational training, provide ongoing peer practice groups, and reduce other administrative workload by 15-20% to create space for the new approach. Most middle managers receive none of that. They get a directive and a deadline.

The Constraint-Based Coaching Stack

If you are a middle manager told to build coaching capacity with no budget and no time, you need a framework optimized for constraints — not an ideal-state model designed for organizations with dedicated L&D teams. The Constraint-Based Coaching Stack is a four-layer approach that prioritizes high-leverage changes you can implement this week without approval, training programs, or additional headcount.

Layer 1: Stop Fake Coaching. Most managers start by trying to add coaching conversations on top of their existing advice-giving habits. This doubles workload and confuses teams. Instead, identify the three situations where you currently jump straight to solutions — usually recurring problems, time-sensitive decisions, or areas where you have strong domain expertise. In those three contexts, continue giving direct answers. Coaching is not appropriate everywhere. Trying to coach someone through a production incident while customers are waiting is malpractice. Reserve your limited coaching capacity for situations where the person has time to think, the stakes allow for learning, and you genuinely do not know the best answer. This is counterintuitive: the advice is to coach less, not more. But scoped coaching executed well beats universal coaching executed poorly.

Layer 2: Audit Your Current 1-on-1s for Hidden Coaching Opportunities. You already have recurring meetings with your team. Most of those meetings follow the same pattern: status updates, blocker removal, quick decisions. Coaching does not require new meetings — it requires repurposing 10 minutes of existing time. Pick one person on your team. In your next three 1-on-1s with them, replace the first agenda item with a single open question about a project they own: “What is the hardest decision you are facing on [project name] right now?” Then stop talking for two minutes. The silence will be uncomfortable. Let them fill it. You are not fixing anything in this moment — you are learning what they think is hard. After three sessions, you will see patterns in how they frame problems, where their confidence sits, and what kinds of support actually help them grow. This costs zero dollars and requires no formal training. For more on when this approach backfires, see coaching managers leadership decisions.

Layer 3: Create a Shared Decision Framework, Not Coaching Scripts. Most “coaching culture” implementations fail because managers are given question templates (“What do you think we should do?”) without giving teams a shared mental model for making decisions. If your team does not know what good looks like, asking them open-ended questions just creates anxiety. Build a simple decision rubric for recurring choices your team makes — prioritization decisions, trade-offs between speed and quality, when to escalate versus decide independently. Write it down in a shared doc. Reference it in meetings. When someone asks for your input, point them to the framework first and ask which part they are uncertain about. This shifts coaching from “guess what is in my head” to “apply this shared model to your specific context.” The framework does not need to be sophisticated. A two-by-two matrix with clear examples in each quadrant is enough. It gives you something concrete to coach toward. As David Ohnstad’s data product management writing demonstrates, clear decision frameworks turn abstract principles into measurable outcomes — the same logic applies to coaching conversations.

Layer 4: Practice One Coaching Move Until It Becomes Automatic. Trying to learn six coaching techniques at once guarantees you will default to old habits under pressure. Pick one move and drill it for 30 days. The highest-leverage move for most managers: after someone proposes a solution, ask “What would have to be true for that to fail?” This forces second-order thinking without requiring you to know the answer. It works in technical decisions, project planning, and interpersonal conflicts. It takes five seconds to ask and creates space for the other person to stress-test their own thinking. Practice it until it becomes reflexive. Then add a second move. Building coaching capacity is skill acquisition, not knowledge transfer. You cannot read your way into it.

When David Ohnstad Stopped Trying to Coach Everyone

Three years ago, David Ohnstad managed a team of five data analysts and two engineers at a mid-stage SaaS company. Leadership had just rolled out a “coaching-first management” initiative. David attended the kickoff session, received a PDF of coaching questions, and started trying to apply them everywhere. Within two weeks, his highest performer — a senior analyst who had been with the company for four years — asked for a skip-level meeting with David’s manager. The feedback: “He has stopped giving me answers and started asking me questions I do not have context to answer. I feel like he is testing me instead of helping me.”

David realized he had been treating coaching like a communication style instead of a situational tool. He was asking open-ended questions about database schema decisions when the analyst needed technical guidance, and he was giving direct answers about stakeholder prioritization when the analyst needed space to develop her own judgment. The mismatch was not intentional — it was the result of applying a one-size-fits-all approach to situations that required different responses.

David rebuilt his approach around context. For recurring technical problems where he had deep expertise, he gave direct answers and explained his reasoning. For ambiguous stakeholder decisions where the analyst had more context than David did, he asked questions and let her build the solution. For project planning and prioritization, he created a shared framework the team used to make decisions independently. Within a month, the senior analyst’s feedback shifted: “I know when to expect coaching and when to expect answers. That clarity helps me learn faster.” The shift was not about coaching more — it was about coaching in the right situations and giving clear direction everywhere else. Coaching culture without that discernment becomes noise. For a deeper look at why universal coaching mandates backfire, see manager coaching skills leadership.

Stop Measuring Coaching by Question Count

Most organizations that mandate coaching cultures measure the wrong proxy. They track how many “coaching conversations” managers have, how often they ask open-ended questions, or whether they complete coaching training modules. None of this predicts whether teams actually get better at making decisions independently. According to Harvard Business Review’s 2025 analysis of manager effectiveness, the strongest predictor of team performance is not manager coaching frequency — it is decision velocity on recurring problems. Teams that can solve the same class of problem faster each quarter without escalating to their manager are learning. Teams that keep escalating the same decisions are not.

Measure coaching effectiveness by tracking decision latency on repeated problem types. If your team had to escalate a database performance issue to you in January, and they handled the same class of issue independently in March, your coaching worked. If they are still escalating the same decision in May, it did not. This is a hard metric. It does not care about your question-asking technique or your empathetic listening skills. It cares whether your team is building judgment that compounds over time.

The contrarian claim here: stop trying to be a better coach until you have built better decision infrastructure for your team. Coaching without a shared framework for evaluating options is just Socratic theater. Your team needs to know what good looks like before they can learn to identify it themselves. Build the rubric first. Coach to the rubric second. Track whether decision-making improves third. Most organizations do this backward — they train managers to ask better questions without giving teams the mental models to answer them well. That is why coaching culture mandates create frustration instead of capability. For teams implementing AI systems, this clarity becomes even more critical — as explored in David Ohnstad on AI and enterprise SaaS, where unclear decision frameworks turn technical tools into organizational confusion.

How do you build a coaching culture without a training budget?

Focus on behavior change in existing meetings rather than adding new programs. Identify one recurring decision type your team escalates frequently, create a simple decision framework for it, and coach team members to apply that framework independently. Measure success by whether escalation frequency decreases over 60 days, not by how many coaching questions you ask. This requires zero budget and works within current meeting structures.

What is the biggest mistake managers make when trying to adopt coaching?

Treating coaching as a universal communication style rather than a situational tool. Managers try to coach in contexts where direct answers are appropriate — like production incidents or highly technical decisions — and give direct answers in contexts where coaching would build long-term judgment, like ambiguous prioritization trade-offs. The skill is knowing when to coach and when to instruct, not coaching more frequently.

Why do coaching culture initiatives often reduce team performance initially?

Because they disrupt established feedback patterns without replacing them with clear alternatives. High performers interpret sudden question-based management as micromanagement or lack of direction, while struggling performers interpret it as their manager abdicating responsibility. Teams need a transition framework that explains when coaching will replace direction, what decision-making authority is shifting, and how to ask for direct guidance when needed. Without this clarity, coaching feels random rather than developmental.

Two Actions for Practitioners and Leaders

For middle managers: Stop trying to implement the entire coaching culture vision leadership forwarded you. Pick one decision type your team repeatedly escalates. Build a two-by-two decision matrix with clear examples in each quadrant. In your next three 1-on-1s, when that decision type comes up, ask the team member to map their situation to the matrix before you give input. Track whether escalations decrease over the next 60 days. If they do, expand to a second decision type. If they do not, your matrix is missing context — revise it with input from the team member who knows the problem best.

For leaders mandating coaching culture shifts: Stop measuring manager participation in coaching training and start measuring team decision velocity on recurring problem types. Identify the five most common decisions teams escalate to managers. For each decision type, measure time-to-resolution and escalation frequency monthly. A successful coaching culture should show both metrics improving over two quarters. If escalation frequency stays flat or increases, your managers are not coaching effectively — or you have not given teams the decision-making frameworks they need to act independently. Fund that infrastructure before you fund more manager training.

When was the last time you audited whether your team is making the same decisions faster each quarter — or whether they are still escalating the same problems at the same rate they did six months ago?

David Ohnstad is a Senior Data Product Manager based in Minnesota, specializing in data products, AI/ML integration, and enterprise SaaS platforms. Follow his work at github.com/davidohnstad40-netizen.

The post Coaching Culture Failures: Why Directives Need Real Resources appeared first on David Ohnstad.

Photo by Vitaly Gariev on Unsplash

The Coaching Trap: Why “Ask More Questions” Is Bad Advice for Most Managers

A director at a Fortune 500 tech company spent six months perfecting her coaching skills—active listening workshops, Socratic questioning frameworks, the whole SHRM playbook. Her team’s velocity dropped 22% during that period. The problem wasn’t her coaching technique. It was that her engineers needed clear decisions about API deprecation timelines, and she kept asking them how they felt about the options instead of making the call. According to Gartner’s 2024 Leadership Development Survey, 68% of newly promoted managers report anxiety about “not being directive enough” after coaching training—a number that’s doubled since 2021.

The current wave of business-driven coaching culture articles misses something critical: the difference between coaching skills and coaching as a management philosophy. SHRM’s latest guidance on building coaching cultures and HBR’s superteam framework both conflate the two, creating a false binary that’s making mediocre managers worse. You don’t need to transform into a therapist. You need to know when to ask questions and when to just tell someone what needs to happen.

David Ohnstad has watched this play out across product teams for years. The worst performance conversations he’s seen weren’t the ones where managers were too directive—they were the ones where leaders abdicated decision-making authority under the guise of “developing” their reports. Coaching skills are essential. Pretending you’re a professional coach when you’re a product manager with budget authority and delivery timelines is organizational theater that wastes everyone’s time.

Why the Coaching-First Model Fails in High-Velocity Environments

The stakes here aren’t theoretical. When managers mistake coaching for management, three things break down fast. First, decision velocity collapses. A team waiting for their manager to “coach them to the answer” on a database migration strategy isn’t being developed—they’re blocked. According to McKinsey’s 2023 Organizational Health Index, teams with managers who over-index on coaching vs. directing report 31% longer cycle times on technical decisions compared to teams with balanced leadership styles.

Second, accountability evaporates. If every conversation is a developmental discussion, there’s never a moment to say “This didn’t ship on time, and that’s a performance issue we need to address directly.” The performance review process—already broken in most organizations, per HRMorning’s 2026 analysis showing 73% of employees say annual reviews don’t improve their work—gets worse when managers treat feedback delivery as a coaching session instead of an evaluation.

Third, high performers leave. The best individual contributors don’t want Socratic questioning when they’ve already done the research and need executive air cover to move forward. They want a manager who will make the call, remove blockers, and take the heat when things go sideways. David Ohnstad saw this firsthand at Veeam: a senior data engineer left for a competitor specifically citing “too many coaching conversations, not enough decisions” in her exit interview. She didn’t need development—she needed her manager to pick a data governance model and defend it to the executive team.

The Directional Clarity Stack: A Four-Layer Framework for Knowing When to Coach vs. Command

Here’s the model David Ohnstad uses to decide whether a situation calls for coaching skills or directive leadership. It’s a four-layer stack, and you evaluate from bottom to top. Each layer asks a specific question, and the answers determine your approach.

Layer 1: Capability Assessment. Does this person have the technical knowledge and experience to solve this problem independently? If yes, move to Layer 2. If no, this is a teaching moment—not coaching, not directing, but actual skills transfer. You’re not asking them how they feel about writing SQL queries if they’ve never written one. You’re showing them how it works, pairing with them, and checking their output until they’re competent. This isn’t coaching—it’s onboarding or upskilling, and it requires a different set of tools entirely.

Layer 2: Decision Authority. Who owns this decision, and what are the organizational consequences if it’s wrong? If the decision is genuinely theirs to make and the blast radius is contained—a dashboard layout, a testing framework choice for a non-critical pipeline—then coaching skills apply. Ask questions. Help them think through trade-offs. Let them own it. But if the decision has cross-team dependencies, budget implications, or exec visibility, your job isn’t to coach them to an answer. It’s to make the call or explicitly delegate the authority with guardrails. According to Forrester’s 2024 Product Leadership Report, 54% of product managers cite “unclear decision rights” as the top friction point in their role. Coaching conversations that avoid naming who actually owns the decision make this worse, not better.

Layer 3: Time Constraint. How much time is actually available before this decision must be made? If you’re two days from a release and the API contract isn’t finalized, this is not the moment for a developmental conversation about stakeholder management. This is the moment to say: “Here’s what we’re doing, here’s why, and here’s what I need you to execute in the next 48 hours.” The best managers David Ohnstad has worked with are explicit about this: “Right now I’m directing because we’re out of time. Next sprint, we’ll debrief this decision and I’ll walk you through how I made the call so you can own it next time.” That’s clarity. Pretending you’re coaching when you’re actually just issuing orders with question marks at the end is condescension.

Layer 4: Relationship Context. What is your actual relationship with this person, and what do they need from you right now? If someone just failed a major deliverable, they don’t need you to ask them what they learned—they already know. They need you to assess whether this was a capability gap, a process failure, or a performance issue, and then be direct about what changes. If someone is burned out, they don’t need coaching on prioritization—they need you to reprioritize their work or add capacity. The HBR superteam article gets this half-right: psychological safety matters. But psychological safety doesn’t mean endless Socratic dialogue. It means your team trusts you to be honest, make decisions when needed, and have their back when things go wrong.

The Performance Review Season Reality: What Managers Actually Need Right Now

It’s mid-June 2026. Most organizations are either in the middle of mid-year performance reviews or approaching Q3 planning cycles. Managers are drowning in development conversations, feedback sessions, and goal-setting meetings—all while trying to ship actual product work. The SHRM coaching culture model assumes managers have infinite time to develop every team member through inquiry-based dialogue. The reality is that most product managers have 12-15 direct reports, four active projects, and a VP who wants to know why last quarter’s OKRs missed by 30%.

David Ohnstad ran into this at Veeam during a Q2 planning cycle. He had two product managers who needed radically different management approaches in the same week. One was a senior PM who’d been at the company for four years—she needed him to make a call on whether to deprecate a legacy reporting feature that still had 200 enterprise users but was blocking a platform migration. Coaching her through that decision would have been a waste of her time. She’d already done the analysis. She needed executive coverage to absorb the customer backlash. So David made the call: deprecate it, here’s the communication plan, I’ll take the exec meeting.

The other PM was nine months into the role and struggling with stakeholder conflict on a data pipeline project. Two engineering teams wanted different schemas, and he kept trying to find a compromise that made both sides happy. That was a coaching moment. David didn’t tell him what to do—he asked him what decision criteria he was using, why he thought consensus was the goal, and what would happen if he just picked the schema that best served the end user and told the other team no. Three questions, 20-minute conversation, and the PM had a framework he could apply to the next ten conflicts. That’s what coaching skills look like when applied correctly: helping someone develop a decision-making model they’ll use repeatedly, not hand-holding them through every choice.

The distinction matters because most organizations are now measuring manager effectiveness through engagement scores and retention metrics—both of which correlate with clarity, not just empathy. Pragmatic Institute’s 2025 Product Management Survey found that product managers who rated their direct manager as “clear about priorities and decision authority” had 43% higher engagement scores than those who rated their manager as “supportive but unclear.” Coaching without clarity is just nice.

The Contrarian Position: Stop Asking Questions When You Already Know the Answer

Here’s the claim that will make every L&D professional in your organization uncomfortable: if you’re asking a question and you already know the answer you want to hear, you’re not coaching—you’re manipulating. And your team knows it.

The Socratic method works when the teacher genuinely doesn’t know what the student will discover and is guiding them through a reasoning process. It fails when a manager asks “What do you think we should do about the API timeout issue?” while mentally already committed to a specific solution. The team member can feel the performance. They’re not being developed—they’re being tested on whether they can guess what you’re thinking. That dynamic kills trust faster than just being directive ever would.

David Ohnstad’s position: if you’ve already made the decision, say so. “Here’s what we’re doing and why. Let me know if you see a technical blocker I’m missing, but the strategic call is made.” That’s respectful. It’s honest. And it frees up your team’s cognitive capacity to focus on execution instead of trying to reverse-engineer your preferred answer through a series of leading questions. According to Reforge’s 2024 Product Leadership research, teams with managers who were “clear and directive when needed” reported 27% higher trust scores than teams with managers who “always use coaching techniques.” Clarity builds trust. Faux-Socratic questioning erodes it.

This doesn’t mean you never ask questions. It means you ask questions when you genuinely want to learn something—when your report has context you don’t, when they’ve been closer to the problem, when their judgment on this specific issue is better than yours. That’s the appropriate use of inquiry. Asking questions to make someone feel like they came up with your idea is theater.

What This Means for Product Managers Building Data-Driven Teams

For product managers specifically—especially those building data products or leading analytics teams—the coaching vs. directing balance has an extra layer of complexity. Data work is both deeply technical and highly ambiguous. A junior analyst working on a customer segmentation model might genuinely benefit from coaching: What assumptions are you making about the data? How would you validate those? What would change your confidence in this approach? Those are real questions that help someone develop statistical thinking.

But when that same analyst asks whether they should use Python or R for the project, and your organization has already standardized on Python for deployment and tooling consistency, the answer isn’t “What do you think the trade-offs are?” The answer is “We use Python here because it integrates with our production stack. If you want to prototype in R, that’s fine, but the final deliverable needs to be in Python.” That’s not stifling creativity—it’s providing the organizational context that lets someone make productive decisions instead of relitigating settled architecture choices.

David Ohnstad has seen teams waste entire sprints because a manager wanted to “let the team discover” a constraint that was obvious from day one. Governance models, data access policies, compliance requirements—these aren’t areas for discovery learning. They’re areas where you tell people the rules, explain why they exist, and move on. Recognizing that building high-performing teams around data products specifically demands clarifying governance models upfront is critical, since ambiguous data ownership creates the friction that coaching alone cannot resolve.

Similarly, as teams integrate AI agents and machine learning workflows, managers need technical literacy to know when their reports are making a technical decision (where coaching might apply) vs. when they’re encountering a hard platform limitation (where you just need to explain the constraint). Leaders adopting a coaching culture need technical literacy to understand AI agent capabilities and limitations when integrating them into team workflows—you can’t coach someone through a problem that requires a different tool, not a different thought process.

How to Build Coaching Skills Without Losing Directional Authority

The goal isn’t to reject coaching skills—it’s to integrate them into a broader leadership toolkit that includes directive decision-making, technical mentorship, and clear accountability. Here’s how David Ohnstad approaches it with his team at Veeam.

First, separate coaching sessions from performance management. If you’re having a quarterly development conversation, that’s coaching time. You’re asking about career goals, skill gaps they want to close, projects they’re excited about. You’re genuinely in discovery mode. But if you’re in a sprint retro and a deliverable missed its target by two weeks, that’s not a coaching session—that’s a performance conversation. You’re asking what happened, assessing whether it’s a pattern, and being clear about what needs to change. Conflating the two makes both conversations worse.

Second, name your mode explicitly. David Ohnstad tells his team at the start of one-on-ones: “This is a coaching conversation—I’m going to ask a lot of questions because I want to understand your thinking.” Or: “This is a decision meeting—I need to make a call by end of day, so I’m going to be directive.” That level of transparency eliminates the guessing game. People aren’t trying to figure out whether you want input or compliance. You’ve told them.

Third, build feedback loops that tell you whether your approach is working. After major decisions, ask: “Did you feel like you had enough context to execute on this, or did I leave you guessing?” After coaching conversations, check: “Was that conversation useful, or did it feel like I was avoiding giving you a straight answer?” Those aren’t rhetorical questions—they’re actual data collection. If multiple team members tell you they’re unclear on priorities, your coaching-to-directing ratio is off. Adjust.

What’s the difference between coaching skills and being a professional coach?

Coaching skills—active listening, asking open-ended questions, helping someone think through options—are tools any manager should have. Being a professional coach is a distinct role with different training, accountability structures, and objectives. Managers have decision-making authority, budget responsibility, and performance evaluation duties that professional coaches don’t. Conflating the two leads managers to abdicate decisions under the guise of development, which slows teams down and erodes trust in leadership clarity.

When should a manager use directive leadership instead of coaching?

Use directive leadership when time constraints are tight, when decision authority is unclear and needs to be established, when the decision has significant cross-team or financial consequences, or when you have organizational context the team member lacks. Coaching works when the person has the capability to solve the problem, the decision is genuinely theirs to own, and there’s time for them to work through the reasoning. The Directional Clarity Stack—capability, authority, time, and relationship context—provides a framework for evaluating which approach fits the situation.

How do you give feedback without turning every conversation into a coaching session?

Separate feedback from development. Feedback is direct, specific, and tied to observed behavior or outcomes: “This deliverable was two weeks late, and that blocked three other teams. What happened, and what’s changing?” Development conversations are forward-looking and exploratory: “What skills do you want to build this quarter?” If you’re in a feedback conversation, be clear and concise. If you’re in a development conversation, ask questions and listen. Mixing the two creates confusion and makes both less effective. Name which mode you’re in at the start of the conversation.

What High-Performing Teams Actually Need from Managers in 2026

The data is clear: teams don’t want managers who only coach, and they don’t want managers who only command. They want managers who know which tool to use when, and who are transparent about it. According to Harvard Business Review’s 2024 research on high-performing teams, the single strongest predictor of team performance wasn’t psychological safety, givement, or coaching—it was “role clarity and decision transparency.” People need to know who owns what, how decisions get made, and what success looks like. Coaching skills help you understand individual motivations and development needs. Directive leadership provides the structure that lets people execute without constant second-guessing.

David Ohnstad’s take: the best managers he’s worked with—and the model he’s trying to build at Veeam—are fluent in both. They ask genuine questions when they don’t know the answer. They make fast calls when the situation demands it. They’re explicit about which mode they’re in. And they measure effectiveness not by how many coaching conversations they had, but by whether their team shipped valuable work, grew their skills, and trusted leadership to be honest with them.

Father’s Day is this weekend, and a lot of product managers with kids are thinking about the balance between guidance and autonomy—when to let your kid figure it out, when to just tell them not to touch the hot stove. The same logic applies at work. Sometimes the best thing a manager can do is get out of the way. Sometimes the best thing you can do is make the call and take the heat. Knowing which is which—and being honest about it—is the skill that separates good managers from the ones people actually want to work for.

For practitioners: Audit your last five one-on-ones. How many times did you ask a question when you already knew the answer you wanted? If it’s more than once, you’re not coaching—you’re testing. Be more direct.
For leaders: If your management training emphasizes coaching but doesn’t teach when to be directive, you’re setting your managers up to fail in high-velocity environments. Build frameworks that help them toggle between modes, not just master one.

When was the last time you told your team “I’m making this call” instead of asking them what they thought—and did anyone thank you for the clarity?

For more on this topic, visit David Ohnstad’s data product management writing. For more on this topic, visit David Ohnstad on AI and enterprise SaaS.

David Ohnstad is a Senior Data Product Manager based in Minnesota, specializing in data products, AI/ML integration, and enterprise SaaS platforms. Connect on LinkedIn or read more at davidohnstad.com.

The post Coaching Managers: When Questions Hurt Team Performance appeared first on David Ohnstad.

Photo by Vitaly Gariev on Unsplash

The Myth That Great Managers Must Be Great Coaches

A product manager at a mid-sized SaaS company pulled David Ohnstad aside after a leadership workshop and said, “I just spent three hours asking coaching questions to help my engineer figure out a solution he already knew. He finally said, ‘Can you just tell me what you want me to build?’ I felt like I failed.” According to SHRM’s 2024 Business-Driven Coaching Culture report, 68% of first-time managers report anxiety about being expected to “coach” rather than direct, despite lacking formal training in either pedagogy or therapeutic technique. The problem isn’t that managers can’t coach. It’s that the business world has conflated coaching skills with the professional coaching industry, creating a false expectation that leadership requires becoming a neutral facilitator rather than a directive decision-maker.

This confusion costs teams time, clarity, and trust. When managers abdicate their responsibility to make calls—hiding behind Socratic questioning when a direct answer would save hours—they create friction disguised as givement. The goal isn’t to transform every manager into a certified coach. The goal is to teach managers when to ask questions, when to give answers, and how to recognize which mode a situation requires.

What Actually Breaks: The Cost of Misapplied Coaching

When managers treat every conversation as a coaching opportunity, three specific failure modes emerge. First, decision velocity drops. A senior engineer doesn’t need to be walked through discovering the architectural trade-offs between microservices and a monolith—they need you to tell them which constraints the business prioritizes this quarter so they can make the call. Second, team members stop asking questions. If every question triggers a 20-minute exploratory dialogue when they needed a yes-or-no answer, they learn to avoid their manager entirely. Third, accountability becomes murky. Coaching-style management often avoids direct feedback in favor of reflective prompts, which means underperformers don’t know they’re underperforming until a performance review catches them off guard.

A 2023 Harvard Business Review study on high-performing teams found that the most effective managers spent 34% of their one-on-one time giving direct guidance and only 19% using open-ended coaching questions. The ratio flipped for low-performing teams, where managers spent 41% of conversations asking exploratory questions and only 12% providing specific direction. The pattern held across industries: clarity outperformed curiosity when execution mattered more than discovery.

David Ohnstad saw this firsthand at Veeam when a data engineering lead spent six weeks “coaching” a junior analyst through building a reporting pipeline. The lead asked questions like, “What do you think the right granularity is for this aggregation?” and “How would you think you would validate this data quality?” The analyst eventually delivered a pipeline that worked but took three times longer than it should have. The lead later admitted, “I knew the answer in week one. I thought I was supposed to let him figure it out.” The business cost wasn’t just time—it was the opportunity cost of what that analyst could have built if he’d been told the standard approach upfront and coached only on the edge cases where judgment mattered.

The Directive-Collaborative Balance Framework

Effective management requires knowing which mode to use and when. The Directive-Collaborative Balance Framework breaks this into four quadrants based on two variables: problem complexity and team member experience level. For low-complexity problems with low-experience team members, default to directive guidance—tell them what to do and why. For low-complexity problems with high-experience team members, confirm alignment and get out of the way. For high-complexity problems with low-experience team members, use structured coaching: narrow the problem space, ask targeted questions within defined constraints, then provide a decision if they’re stuck. For high-complexity problems with high-experience team members, shift to true collaborative coaching—your job is to surface blind spots, challenge assumptions, and help them think through second-order consequences.

The mistake most managers make is defaulting to one mode regardless of context. Junior managers over-index on directive because it feels safe and efficient. Managers who’ve been through leadership training over-index on collaborative because they’ve been told that’s what “good leaders” do. Neither extreme works. A senior data scientist doesn’t need you to walk them through statistical fundamentals—they need you to tell them which business metric the executive team actually cares about so they stop optimizing for the wrong thing. A junior product manager building their first roadmap doesn’t need you to ask, “What do you think the prioritization framework should be?”—they need you to teach them RICE or MoSCoW, then coach them on applying it to edge cases.

The framework’s counterintuitive step is step three: give the answer when coaching stalls progress. If you’ve asked two clarifying questions and the person is still stuck, continuing to ask questions isn’t giveing them—it’s wasting time and eroding their confidence. According to Gartner’s 2024 Leadership Effectiveness Study, managers who capped coaching sessions at three questions before providing guidance had 22% higher team satisfaction scores than those who insisted on “letting the team figure it out.” The skill isn’t endless patience. The skill is recognizing when exploration has diminishing returns.

David Ohnstad applies this when reviewing data architecture proposals. If an engineer presents a design with a clear technical flaw, he doesn’t ask, “What do you think might go wrong with this approach?” He says, “This will break under load because you’re doing a full table scan on every query—here’s why, here’s the pattern that fixes it, now apply that logic to the next section and let’s review again.” The engineer learns the principle faster, respects the feedback more, and doesn’t waste a week debugging something that could have been caught in five minutes. Coaching works when someone has the foundational knowledge but needs help connecting dots. Directive guidance works when they’re missing a foundational piece and need to be taught it directly.

Myth #1: Good Managers Always Ask Questions, Never Give Answers

This myth persists because leadership development programs—many adapted from professional coaching certifications—teach that questions unlock insight while answers create dependency. The logic sounds right: if you give someone a fish, they eat for a day; if you teach them to fish, they eat for life. The problem is that most workplace situations aren’t about teaching someone to fish. They’re about confirming that the person already knows how to fish, or quickly teaching them where the pond is so they can start catching fish tomorrow instead of spending three weeks philosophically exploring the concept of ponds.

What’s actually true: managers need to give answers frequently, especially early in a team member’s tenure or early in a project. The goal isn’t to make people dependent—it’s to establish a shared baseline so future conversations can focus on judgment calls rather than foundational questions. When David Ohnstad onboards a new product manager, he doesn’t ask, “How do you think we should structure sprint planning?” He says, “Here’s how we do it, here’s why we made these specific trade-offs, here’s where you have discretion to adjust, and here’s where you don’t.” The new PM gets to productive work faster, learns the reasoning behind the structure, and knows which parts of the process are negotiable.

A 2024 MIT Sloan study on management training outcomes found that managers who were taught to balance directive and collaborative modes had 31% better team retention than those trained exclusively in coaching-based leadership. The teams didn’t feel micromanaged—they felt supported. The difference mattered most for remote teams, where the cost of a misunderstood question is an entire day lost to asynchronous back-and-forth instead of a two-minute clarifying conversation.

Myth #2: Coaching Skills and Professional Coaching Are the Same Thing

The phrase “coaching culture” has become shorthand for giveing teams, but it conflates two unrelated activities. Professional coaching—what a credentialed ICF coach does—requires neutrality, non-directiveness, and a client-driven agenda. The coach doesn’t have opinions about what the client should do. The coach helps the client surface their own answers. That works beautifully when the client is a CEO trying to decide between two strategic paths and needs space to think. It fails catastrophically when a manager uses it on a junior employee who genuinely doesn’t know the answer and is hoping their manager will teach them.

What’s actually true: managers need coaching skills—active listening, asking clarifying questions, summarizing to confirm understanding—but they should almost never act like professional coaches. A manager has context the employee doesn’t have. A manager has accountability for outcomes the employee isn’t responsible for. A manager is paid to make calls when the team can’t converge on one. Pretending to be neutral when you’re not wastes everyone’s time and erodes trust. According to Forrester’s 2023 Leadership Development Benchmarking Report, 74% of employees preferred managers who “tell me what you think, then ask for my input” over managers who “only ask questions and never share their perspective.”

David Ohnstad encountered this when a Veeam engineering director started using pure coaching-style questions in technical design reviews. The director would ask, “What trade-offs do you see here?” instead of saying, “This won’t scale past 10,000 users because the database writes aren’t batched.” The engineers interpreted it as the director not knowing the answer, which damaged credibility. When the director switched to, “Here’s the scaling issue I see—do you agree, or am I missing something?”—the reviews became faster, the feedback landed better, and the engineers trusted the director more because the expertise was visible instead of hidden behind facilitation.

Myth #3: Directive Leadership Means You Don’t Trust Your Team

This myth persists because corporate culture has pathologized decisiveness. Telling someone what to do has been rebranded as a failure of givement, a lack of psychological safety, or evidence that you hired the wrong people. The fear is understandable: nobody wants to be the micromanaging boss who stifles creativity. But the pendulum has swung so far that many managers are now afraid to make any decision without facilitating a consensus-building process, even when the decision is straightforward and the team is waiting for someone to just make the call.

What’s actually true: directive leadership, done well, is a signal of respect. It says, “I have information you don’t have, or I’ve made this mistake before and I’m going to save you time by telling you what works.” High-trust teams don’t need every decision to be collaborative. They need clarity about which decisions are collaborative and which are directive, and they need managers who can explain the reasoning either way. A manager who says, “We’re using Postgres for this, not MongoDB, because our data access patterns are relational and I’ve seen MongoDB cause problems in this exact scenario—but I’m open to revisiting if you find evidence I’m wrong” is being directive and trustworthy.

Gartner’s 2024 Workforce Analytics Survey found that teams with managers who made unilateral technical decisions 40% of the time reported higher autonomy scores than teams whose managers insisted on consensus for every choice. The reason: when managers absorb the low-leverage decisions, the team has more cognitive space for the high-leverage ones. Debating which CI/CD tool to use is a waste of time if the manager has already evaluated three and knows which one integrates with the existing stack. Debating the product roadmap priority is worth the time because the team’s input changes the outcome.

David Ohnstad applies this when prioritizing data product features. He doesn’t ask the engineering team to vote on whether to build a new integration or fix technical debt. He makes the call based on business priorities, user impact data, and strategic timing—then explains the reasoning in a Slack thread so the team understands the trade-offs. The team doesn’t feel excluded. They feel like their time is being respected because they’re not being asked to weigh in on decisions where they lack the full context.

Myth #4: If You Have to Tell Someone What to Do, You Hired Wrong

This myth is the final boss of the “coaching culture” movement. It suggests that A-players never need direction, and if you’re giving direction frequently, it’s evidence of a hiring or delegation failure. The myth is seductive because it lets managers avoid the discomfort of being directive. If the only acceptable reason to give an answer is that you hired poorly, then giving answers feels like admitting failure. So managers contort themselves into asking leading questions that everyone knows are just instructions with extra steps.

What’s actually true: even A-players need direction in new contexts, ambiguous situations, or when speed matters more than perfect alignment. Hiring great people doesn’t mean hiring people who intuitively know your company’s priorities, your technical constraints, or the political history of why a certain stakeholder will kill a proposal if it’s framed the wrong way. It means hiring people who can execute well once they have that context. Providing context quickly is directive leadership. Withholding it and hoping they’ll discover it through trial and error is negligence disguised as givement.

According to McKinsey’s 2024 Talent Development Report, high-performing teams averaged 12 minutes of directive guidance per week per team member, compared to 4 minutes for low-performing teams. The high-performing teams weren’t micromanaged—they were getting the information they needed to make better decisions independently. The low-performing teams were “giveed” to figure things out on their own, which meant they spent hours solving problems their manager could have answered in two minutes.

David Ohnstad saw this when Veeam hired a senior data engineer from a competitor. The engineer had a decade of experience and didn’t need to be taught how to build pipelines. But he did need to be told that Veeam’s executive team prioritized deployment speed over architectural purity for the next two quarters, and that proposals framed as “technical elegance” would get deprioritized while proposals framed as “time-to-market” would get funded. That’s not a hiring failure. That’s onboarding. The engineer adapted immediately, delivered faster, and later said, “I wish my last manager had just told me how decisions actually got made instead of making me guess.”

When Coaching Actually Works: The 80/20 Rule for Managers

The solution isn’t to abandon coaching. It’s to recognize that 80% of management conversations benefit from directive clarity, and 20% benefit from coaching-style exploration. The 20% are the high-stakes, high-ambiguity moments: career development conversations, strategic pivots, interpersonal conflicts, or situations where the team member has more domain expertise than you do and needs help structuring their own thinking. Those are the moments where asking, “What are you optimizing for?” or “What would change your mind?” unlocks value that a directive answer couldn’t.

The other 80%—task delegation, technical feedback, priority alignment, process clarification—benefit from speed and specificity. A product manager doesn’t need to be coached through the discovery that the CEO wants the feature shipped before the board meeting. They need to be told that, then coached on how to cut scope without sacrificing the core value proposition. The directive part takes 30 seconds. The coaching part takes 20 minutes. Both are necessary. Neither replaces the other.

Recognizing that building high-performing teams around data products specifically demands clarifying governance models upfront, since ambiguous data ownership creates the friction that coaching alone cannot resolve. And leaders adopting a coaching culture need technical literacy to understand AI agent capabilities and limitations when integrating them into team workflows. The directive-collaborative balance applies to both: governance decisions are directive (someone has to own the call), while workflow integration is collaborative (the team knows their pain points better than you do).

How do you know when to coach versus when to direct as a manager?

Coach when the team member has the foundational knowledge but needs help prioritizing, structuring their thinking, or navigating ambiguity. Direct when they’re missing key context, facing a time-sensitive decision, or solving a problem you’ve already seen fail. If two clarifying questions don’t move them forward, switch to directive mode and explain the answer directly.

What is the difference between coaching skills and professional coaching in a management context?

Coaching skills—active listening, asking clarifying questions, summarizing to confirm understanding—are tools managers use within directive leadership. Professional coaching requires neutrality and a client-driven agenda, which doesn’t work when the manager has accountability for outcomes and context the employee lacks. Managers should use coaching skills frequently but rarely act like professional coaches.

Why do directive managers often have higher-performing teams than coaching-focused managers?

Directive managers who explain their reasoning provide clarity faster, which lets teams execute on high-leverage work instead of spending time solving low-leverage problems. According to Gartner’s 2024 study, teams with managers who made unilateral decisions 40% of the time reported higher autonomy because they weren’t being asked to weigh in on decisions where they lacked full context, freeing cognitive space for strategic work.

For practitioners: Default to directive when onboarding, setting priorities, or providing technical feedback. Save coaching for career conversations, strategic ambiguity, and moments where the other person has expertise you don’t. Speed and clarity aren’t the opposite of givement—they’re what make givement possible.

For leaders: Stop measuring management effectiveness by how many questions a manager asks. Measure it by whether their team knows what’s expected, understands the reasoning behind decisions, and has the context to make good calls independently. A manager who gives answers frequently but explains the reasoning is building capability faster than one who withholds answers in the name of development.

When did you last audit whether your one-on-ones are actually helping your team move faster, or just making you feel like you’re “doing leadership” the way the training deck said you should?

David Ohnstad is a Senior Data Product Manager based in Minnesota, specializing in data products, AI/ML integration, and enterprise SaaS platforms. Connect on LinkedIn or read more at davidohnstad.com.

The post Great Managers Don’t Need to Be Great Coaches appeared first on David Ohnstad.

Organizations that sustain trust long-term frequently do so not by constantly redefining themselves, but by demonstrating reliability through consistent operational behavior.

Why Predictability Creates Organizational Confidence

People tend to trust organizations when expectations are clear and outcomes are dependable.

Predictability helps create confidence by supporting:

• Consistent communication
• Reliable execution
• Stable leadership behavior
• Clear operational standards

When employees and stakeholders understand how an organization operates, uncertainty and confusion often decrease significantly.

The Difference Between Adaptation and Constant Reinvention

Healthy organizations evolve, but evolution differs from continuous reinvention.

Adaptation may involve:

• Improving existing systems
• Responding thoughtfully to market conditions
• Refining operational processes

Constant reinvention, however, may create the following:

• Strategic inconsistency
• Operational instability
• Employee uncertainty
• Reduced organizational clarity

Frequent dramatic shifts can make it difficult for teams to maintain alignment and long-term confidence.

Why Consistency Strengthens Internal Culture

Organizational culture often becomes stronger when employees experience consistency in leadership expectations and operational processes.

Consistency may help support:

• Clear accountability
• Stronger collaboration
• Reduced confusion
• Greater workplace stability

When priorities change too frequently, employees may struggle to understand long-term organizational direction.

How Predictability Improves Decision-Making

Organizations with stable systems and communication structures often make decisions more effectively because teams spend less time adjusting to unnecessary operational disruption.

Predictable environments may improve:

• Workflow coordination
• Resource planning
• Strategic alignment
• Team confidence during execution

Operational stability frequently creates more room for thoughtful long-term planning.

Why Stakeholders Value Reliability

Clients, partners, and investors often prioritize reliability over constant novelty.

Trust grows when organizations demonstrate:

• Consistent follow-through
• Stable service quality
• Dependable communication
• Long-term operational discipline

While innovation may attract attention temporarily, reliability often sustains long-term professional relationships.

The Hidden Risks of Constant Organizational Change

Frequent operational changes can create unintended instability inside organizations.

This may involve:

• Process confusion
• Reduced employee confidence
• Misaligned priorities
• Declining operational efficiency

Even positive changes can create friction when organizations introduce them too rapidly or without sufficient clarity.

Why Employees Need Stability to Perform Consistently

Employees generally perform more effectively when expectations remain understandable and relatively stable.

Stability supports:

• Stronger role clarity
• Better workflow coordination
• Reduced operational stress
• Greater confidence in long-term direction

Constant uncertainty can gradually weaken morale and reduce organizational cohesion.

How Predictable Leadership Builds Trust

Leadership trust often develops through repeated patterns of consistent behavior rather than occasional moments of inspiration alone.

Predictable leadership may involve:

• Consistent communication
• Stable decision-making principles
• Reliable accountability standards
• Clear organizational priorities

Over time, employees often trust leaders more when behavior remains disciplined and dependable.

Why Organizations Sometimes Overcorrect

Businesses facing market pressure occasionally attempt to solve problems through rapid restructuring or dramatic operational shifts.

This may lead to:

• Frequent strategic pivots
• Constant procedural changes
• Leadership inconsistency
• Reduced operational continuity

While responsiveness is important, excessive change can weaken organizational stability if not managed carefully.

The Relationship Between Trust and Operational Discipline

Operational discipline helps organizations maintain consistency even during periods of uncertainty.

Disciplined systems often support:

• Reliable execution
• Strong communication standards
• Better accountability
• Reduced organizational confusion

This consistency frequently strengthens trust across teams and stakeholder relationships.

Why Predictability Supports Long-Term Growth

Organizations that maintain stable internal systems often position themselves better for sustainable long-term growth.

Predictability may improve:

• Strategic planning accuracy
• Team coordination
• Operational scalability
• Organizational resilience during uncertainty

Stable organizations often adapt more effectively because their foundations remain clear and disciplined.

How Organizational Identity Is Strengthened Over Time

Businesses develop stronger identities when employees and stakeholders consistently understand the organization’s values, expectations, and operational approach.

Strong organizational identity often depends on:

• Repeated behavioral consistency
• Clear long-term priorities
• Stable leadership direction
• Reliable communication patterns

Constant reinvention can sometimes dilute organizational identity rather than strengthen it.

Why Trust Develops Gradually

Organizational trust is rarely built through single announcements or short-term initiatives.

Instead, trust usually develops through:

• Repeated consistency
• Predictable operational behavior
• Reliable decision-making
• Long-term accountability

These repeated experiences gradually shape confidence in the organization itself.

Final Thoughts

Long-term organizational trust is often built through predictability rather than constant reinvention because employees, stakeholders, and partners generally place greater confidence in organizations that demonstrate consistency, reliability, and stable operational behavior over time. While adaptation remains essential in modern business environments, excessive change without clear structure can create confusion and weaken long-term confidence.

Strong organizations frequently sustain trust not by constantly redefining themselves, but by maintaining disciplined systems, clear communication, and dependable leadership through changing conditions.

The post Why Long-Term Organizational Trust Is Built Through Predictability Rather Than Constant Reinvention appeared first on David Ohnstad.

As businesses become more interconnected and digitally dependent, the challenge is no longer simply obtaining information. The greater challenge is determining which information actually matters.

Why More Information Does Not Always Improve Decision-Making

Many organizations assume that increased access to data automatically leads to better strategic outcomes. In reality, excessive information can sometimes complicate decision-making rather than strengthen it.

This may occur when businesses face the following:

• Too many performance metrics
• Constant reporting cycles
• Continuous communication streams
• Excessive external market commentary

When organizations struggle to separate critical insights from background noise, strategic focus can weaken significantly.

How Information Saturation Creates Decision Fatigue

Leaders and teams often process enormous amounts of information every day.

Such information may include:

• Emails and internal updates
• Performance dashboards
• Market reports
• Financial projections
• Operational analytics

Over time, the volume of incoming information can create cognitive overload, reducing the ability to make clear, confident decisions consistently.

Why Speed of Information Increases Organizational Pressure

Digital communication systems allow businesses to receive information almost instantly. While this speed creates faster visibility, it also increases pressure to react quickly.

This environment may encourage:

• Premature decision-making
• Constant reprioritization
• Reactive operational behavior
• Reduced long-term strategic focus

Organizations sometimes mistake rapid responsiveness for strategic effectiveness, even when frequent reaction creates instability.

The Difficulty of Identifying What Matters Most

One of the greatest modern business challenges is distinguishing between useful information and distracting information.

Not every metric, trend, or operational update deserves equal strategic attention.

Without prioritization, businesses may struggle to identify the following:

• Core operational risks
• Long-term opportunities
• Structural weaknesses
• High-impact strategic decisions

Strategic clarity often depends on simplification rather than constant information expansion.

Why Excessive Reporting Can Reduce Clarity

Organizations frequently increase reporting requirements in an effort to improve oversight and accountability. However, excessive reporting can sometimes create the opposite effect.

This may result in:

• Information duplication
• Reduced focus on actionable insights
• Slower decision-making cycles
• Greater administrative burden

When too many reports compete for attention, truly important signals may become harder to recognize.

How Constant Connectivity Affects Leadership Focus

Modern leaders operate in environments where communication rarely stops completely.

Continuous connectivity may involve:

• Real-time notifications
• Immediate response expectations
• Ongoing operational updates
• Continuous digital engagement

This constant informational pressure can make sustained strategic thinking more difficult.

Why Organizations Sometimes Overvalue Data Quantity

Businesses often focus heavily on collecting more information without fully considering whether the information improves operational understanding.

More data does not automatically create the following:

• Better strategic direction
• Stronger leadership judgment
• Improved organizational alignment

In some cases, excessive complexity may actually reduce organizational responsiveness and clarity.

The Relationship Between Clarity and Prioritization

Strategic clarity often depends on an organization’s ability to define priorities clearly and consistently.

This includes identifying:

• Which goals matter most
• Which metrics are most meaningful
• Which risks require immediate attention
• Which information can be filtered out

Organizations with stronger prioritization systems often make decisions more efficiently even in complex environments.

Why Reactive Information Consumption Creates Instability

Many organizations unintentionally develop reactive operating patterns because constant information flow encourages continuous adjustment.

This may lead businesses to the following:

• Shift priorities too frequently
• Overreact to short-term trends
• Lose long-term strategic consistency

Constant reaction can gradually weaken organizational stability and decision confidence.

How Communication Overload Affects Teams

Information saturation affects employees as well as leadership teams.

Communication overload may contribute to:

• Reduced focus
• Slower execution
• Increased confusion
• Difficulty identifying key objectives

When teams receive excessive or inconsistent information, operational alignment often becomes more difficult to maintain.

Why Simplicity Has Become Increasingly Valuable

As business environments become more complex, organizations often benefit from simplifying communication, priorities, and strategic direction.

Operational simplicity may support:

• Faster execution
• Better coordination
• Improved accountability
• Stronger long-term consistency

Clear priorities frequently create more organizational stability than excessive operational complexity.

The Importance of Strategic Filtering

Strong organizations increasingly rely on filtering systems that help separate high-value insights from unnecessary informational noise.

This may involve:

• Focusing on core performance indicators
• Streamlining communication channels
• Reducing unnecessary reporting layers
• Clarifying organizational priorities

Strategic filtering helps organizations maintain focus despite increasing informational complexity.

Why Long-Term Thinking Requires Mental Space

Strategic planning often requires uninterrupted focus and the ability to evaluate long-term implications carefully.

Constant informational interruption can reduce opportunities for:

• Deep analysis
• Long-range planning
• Reflective leadership thinking
• Structured organizational assessment

Businesses that protect space for long-term thinking are often better positioned to maintain strategic clarity.

Final Thoughts

Information saturation is making strategic clarity more difficult for modern businesses because the constant expansion of data, communication, reporting, and operational input often overwhelms decision-making processes instead of strengthening them. While access to information remains valuable, excessive informational complexity can create confusion, reactive behavior, and reduced strategic focus when organizations fail to prioritize effectively.

Long-term organizational clarity increasingly depends not on collecting the most information, but on identifying the most meaningful information and maintaining disciplined focus amid constant informational pressure.

The post Why Information Saturation Is Making Strategic Clarity More Difficult for Modern Businesses appeared first on David Ohnstad.

Over time, the ability to reduce unnecessary emergency decision-making becomes an important indicator of organizational maturity and long-term operational health.

Why Emergency Decision-Making Creates Long-Term Strain

Businesses occasionally face genuine emergencies that require rapid action. However, some organizations operate in a near-constant reactive state where urgent decisions become routine rather than exceptional.

This can create:

• Leadership fatigue
• Reduced strategic focus
• Employee confusion
• Inconsistent execution
• Higher operational stress

When organizations spend excessive time responding to emergencies, long-term planning often becomes more difficult to sustain.

How Preventable Crises Develop

Many operational emergencies begin as smaller unresolved issues that gradually intensify over time.

These may involve:

• Delayed communication
• Weak internal processes
• Inconsistent accountability
• Poor workflow visibility
• Lack of operational planning

Without early intervention, manageable inefficiencies can eventually evolve into larger disruptions requiring urgent action.

Why Strong Systems Reduce Reactive Pressure

Organizations with stronger operational systems often identify risks earlier because processes create greater visibility into performance and workflow patterns.

Well-structured systems may help organizations:

• Detect inefficiencies sooner
• Clarify responsibilities
• Improve coordination between teams
• Reduce operational confusion

As a result, fewer situations escalate into last-minute emergencies.

The Relationship Between Planning and Stability

Long-term organizational stability usually depends heavily on preparation rather than constant improvisation.

Effective planning may include:

• Resource forecasting
• Workflow management
• Risk assessment
• Communication protocols
• Contingency preparation

Organizations that invest consistently in planning often experience fewer operational surprises over time.

Why Communication Reduces Organizational Emergencies

Communication problems frequently contribute to preventable crises because small misunderstandings can compound across departments or teams.

Clear communication helps organizations:

• Align priorities more effectively
• Address concerns earlier
• Reduce duplicated work
• Improve response coordination

Strong communication systems often prevent operational issues from escalating unnecessarily.

How Reactive Cultures Develop

Some organizations unintentionally normalize urgency by rewarding rapid reaction more heavily than consistent preparation.

This may create cultures where:

• Short-term fixes replace long-term solutions
• Teams operate under constant pressure
• Planning receives less attention than immediate response

Over time, employees may begin expecting operational instability as part of everyday business operations.

Why Predictability Supports Better Decision-Making

Organizations that maintain operational consistency often create environments where leadership can focus more effectively on strategic priorities rather than constant crisis management.

Predictability helps support:

• Clearer long-term planning
• More stable execution
• Better resource management
• Improved organizational confidence

Stable systems reduce the cognitive and operational burden associated with continuous emergency response.

The Impact of Leadership Structure

Leadership structure often influences how organizations respond to operational pressure.

Strong leadership environments may prioritize the following:

• Clear accountability
• Defined decision-making authority
• Consistent operational oversight
• Long-term organizational alignment

Without these structures, businesses may struggle to respond efficiently during periods of uncertainty.

Why Bottlenecks Create Emergency Conditions

Operational bottlenecks can quietly create pressure points that eventually produce urgent problems.

Common bottlenecks may involve:

• Delayed approvals
• Limited decision-making capacity
• Poor information flow
• Overdependence on key individuals

As workloads increase, unresolved bottlenecks often magnify operational instability.

How Employee Clarity Reduces Organizational Stress

Employees generally perform more effectively when expectations and processes remain clear and consistent.

Organizational clarity may improve:

• Workflow efficiency
• Accountability
• Team coordination
• Decision confidence

When teams understand priorities and systems clearly, fewer avoidable problems escalate into emergencies.

Why Sustainable Organizations Prioritize Prevention

Strong organizations often devote substantial attention to prevention rather than relying exclusively on reaction.

Preventive operational thinking may involve:

• Reviewing systems regularly
• Improving communication processes
• Identifying recurring inefficiencies
• Investing in long-term infrastructure

This mindset helps reduce the frequency of operational disruptions over time.

The Hidden Costs of Constant Urgency

Businesses operating in persistent emergency mode may experience consequences beyond operational inefficiency alone.

Constant urgency can contribute to:

• Employee burnout
• Reduced morale
• Leadership exhaustion
• Higher turnover
• Declining strategic focus

Even financially successful organizations may struggle long term if reactive pressure becomes deeply embedded within the culture.

Why Operational Discipline Matters

Operational discipline helps organizations maintain consistency during both stable and uncertain periods.

Disciplined systems often support:

• Reliable execution
• Stronger communication
• Better long-term planning
• More effective problem identification

This consistency frequently reduces the need for reactive decision-making.

How Long-Term Stability Is Built Gradually

Strong organizational stability is usually developed through repeated operational habits rather than dramatic one-time changes.

Over time, businesses strengthen their resilience by:

• Improving systems incrementally
• Building communication clarity
• Strengthening accountability structures
• Reducing unnecessary complexity

These gradual improvements often create fewer emergencies and more sustainable long-term operations.

Final Thoughts

Strong organizations create fewer emergency decisions over time because operational discipline, communication clarity, long-term planning, and well-structured systems reduce the likelihood that manageable problems escalate into larger crises. While uncertainty remains unavoidable in business, organizations with stronger internal alignment are often better equipped to identify issues early and respond with greater consistency.

Long-term organizational strength frequently depends not on how effectively businesses react to constant emergencies, but on how successfully they reduce the need for preventable emergency decision-making altogether.

The post Why Strong Organizations Create Fewer Emergency Decisions Over Time appeared first on David Ohnstad.

As businesses become more complex, accurately diagnosing internal friction becomes increasingly important for maintaining long-term stability and performance.

Why Internal Friction Often Appears Gradually

Many operational challenges develop slowly rather than through sudden disruption. Small inefficiencies may initially seem manageable, but over time, they can compound into larger organizational problems.

This friction may appear through the following:

• Slower decision-making
• Repeated communication breakdowns
• Delayed project completion
• Employee frustration
• Inconsistent execution across departments

Because these issues emerge incrementally, organizations sometimes normalize inefficiency before recognizing its broader impact.

How Businesses Mistake Symptoms for Root Causes

One of the most common organizational mistakes is focusing on visible outcomes without investigating the systems contributing to them.

For example:

• Missed deadlines may reflect unclear workflows
• Low morale may stem from communication failures
• Reduced productivity may involve operational overload rather than lack of effort

Without identifying the underlying source, organizations may repeatedly address symptoms instead of solving the actual problem.

Why Communication Gaps Frequently Create Friction

Communication issues are often underestimated because they rarely appear as dramatic operational failures initially.

Common communication problems may include:

• Unclear expectations
• Inconsistent information sharing
• Misaligned priorities between departments
• Delayed feedback loops

Over time, these gaps can create confusion, duplicated work, and declining efficiency across teams.

The Role of Structural Misalignment

As organizations grow, operational structures sometimes evolve unevenly. Teams may continue using systems or processes designed for smaller operations even after complexity increases significantly.

Structural misalignment may involve:

• Overlapping responsibilities
• Unclear reporting structures
• Bottlenecks in approval processes
• Excessive dependence on a small number of decision-makers

When organizational structure no longer matches operational demands, friction often increases.

Why Employee Performance Is Sometimes Misdiagnosed

Organizations occasionally assume that individual employee performance primarily causes operational struggles, even though broader systemic issues may contribute more significantly.

Employees operating within unclear systems may experience: Reduced efficiency Conflicting priorities Difficulty meeting expectations consistently

• Reduced efficiency
• Conflicting priorities
• Difficulty meeting expectations consistently

Even highly capable teams can struggle when workflows and communication systems create unnecessary obstacles.

How Complexity Increases Operational Pressure

As businesses expand, internal operations often become more interconnected and difficult to manage.

Growth may increase.

• Coordination demands
• Information flow challenges
• Cross-department dependency
• Decision-making complexity

Without strong operational clarity, expanding complexity can gradually intensify internal friction.

Why Reactive Decision-Making Creates Additional Problems

Organizations under pressure sometimes respond reactively to operational issues without fully diagnosing the cause.

This may involve:

• Constant procedural changes
• Short-term fixes replacing long-term solutions
• Increased managerial intervention
• Frequent shifts in priorities

Reactive environments often create instability that compounds existing friction rather than resolving it.

The Impact of Unclear Priorities

Internal friction frequently increases when teams lack clarity regarding organizational priorities.

This may result in:

• Competing objectives between departments
• Resource allocation conflicts
• Inconsistent execution standards
• Reduced accountability

Clear organizational direction often becomes essential for reducing operational confusion.

Why Organizational Silos Create Inefficiency

Departments operating in isolation may unintentionally weaken broader organizational coordination.

Siloed operations can contribute to:

• Information duplication
• Delayed collaboration
• Inconsistent decision-making
• Reduced operational visibility

As organizations become larger, maintaining alignment across teams becomes increasingly important.

How Leadership Visibility Changes With Growth

Leadership teams often lose direct visibility into daily operational friction as organizations become more layered and complex.

This can create situations where

• Small inefficiencies remain unnoticed
• Employee concerns surface too late
• Communication gaps widen gradually

Operational problems sometimes persist not because leadership ignores them, but because structural distance limits visibility.

Why Process Clarity Matters

Strong organizations typically rely on clearly defined systems that reduce confusion and improve consistency.

Process clarity may support:

• Faster decision-making
• Better accountability
• Reduced operational duplication
• Stronger collaboration across teams

Well-structured systems often help organizations operate more efficiently even during periods of growth or uncertainty.

The Importance of Diagnosing Problems Accurately

Accurate organizational diagnosis requires looking beyond immediate symptoms and examining how systems, communication, and structure interact over time.

This may involve evaluating:

• Workflow efficiency
• Reporting structures
• Team coordination
• Decision-making processes

Organizations that identify root causes more effectively are often better positioned to implement sustainable improvements.

Why Internal Friction Affects Long-Term Performance

Operational friction does not only affect short-term productivity. Over time, unresolved inefficiencies can influence:

• Employee retention
• Organizational morale
• Strategic execution
• Customer experience
• Long-term scalability

Even moderate inefficiencies can compound significantly if you leave them unaddressed for extended periods.

Final Thoughts

Organizations often misidentify the real source of internal friction because visible operational problems frequently mask deeper structural, communication, and process-related challenges. You can often observe symptoms such as delayed execution, declining productivity, or employee frustration more easily than the underlying systems that contribute to those outcomes.

Long-term organizational stability often depends on the ability to diagnose operational problems accurately, improve structural clarity, strengthen communication, and align internal systems with the growing complexity of modern business environments.

The post Why Organizations Often Misidentify the Real Source of Internal Friction appeared first on David Ohnstad.