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. Follow his work at github.com/davidohnstad40-netizen. Read more of David Ohnstad’s data product management writing and David Ohnstad on AI and enterprise SaaS.

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

Photo by Vitaly Gariev on Unsplash

Myth #1: Mid-Year Reviews Should Focus on Performance Measurement

Most managers treat mid-year performance reviews as scorecards. They pull up metrics, review KPIs against targets, and deliver a verdict: you’re on track, slightly behind, or exceeding expectations. The conversation follows a template. The employee nods. Everyone walks away having checked a box. According to Gartner’s 2023 research on performance management practices, 58% of HR leaders reported that their mid-year review process “creates compliance documentation but minimal behavior change.” That’s the problem in one sentence.

This myth persists because organizations conflate evaluation with development. HR systems are built around rating scales, calibration meetings, and documentation requirements. Managers receive templates that guide them toward assessment language: “meets expectations in most areas,” “needs improvement in stakeholder communication,” “demonstrates strong technical skills.” The structure of the review process itself—numerical ratings, comparison to peers, formal documentation—trains managers to think like auditors, not mentors. The toolkit determines the behavior.

What’s actually true: mid-year reviews are the highest-leverage mentorship moment most managers get all year. Unlike annual reviews, which carry compensation weight and force managers into justification mode, mid-year conversations happen when there’s still time to redirect, experiment, and course-correct. David Ohnstad, who has managed product teams at Veeam Software, sees this window as fundamentally different: “The annual review is about what happened. The mid-year review is about what could happen—if you use it that way.” The distinction matters. A mentorship conversation asks different questions than an evaluation: Where is this person trying to go? What’s blocking them that they can’t see? What capability, if developed now, would change their trajectory in the second half of the year?

The shift in framing changes everything. Instead of “Your dashboard adoption metric is at 62%, below the 75% target,” a mentorship approach asks: “What would need to be true for your dashboard to become indispensable to the sales team by Q4?” The first statement closes the conversation. The second opens it. One measures the past. The other builds capacity for the future. The metrics still matter—you’re not ignoring performance—but they become diagnostic tools for development rather than verdict statements.

Myth #2: Good Feedback Is Clear, Direct, and specific

This is the advice every manager has heard: be specific, tie feedback to behaviors, make it specific. Don’t say “improve communication.” Say “join the weekly standup on time and provide a written update when you can’t attend.” The logic is sound. Vague feedback doesn’t drive change. But something gets lost in the translation. Managers deliver perfectly structured feedback—clear problem statement, specific example, recommended action—and watch nothing improve. According to MIT Sloan’s 2024 study on managerial effectiveness, teams with “highly structured feedback processes” showed only marginal improvement over teams with no formal process at all when measuring actual skill development over six months. The gap isn’t in clarity. It’s in context.

The myth survives because it’s partially true. Vague feedback is useless. But the remedy—hyper-specific behavioral correction—treats the employee like a machine with a misconfigured setting. Adjust this parameter, get this output. People don’t work that way. Behavioral change requires understanding why the current behavior exists, what trade-off the person is making, and whether the prescribed action aligns with how they actually think and work. A manager who tells a data analyst to “be more proactive in stakeholder meetings” without understanding that the analyst has been burned twice for speaking up in front of senior leaders is prescribing a solution to the wrong problem.

What works instead: feedback as collaborative diagnosis. David Ohnstad’s approach with underperforming team members starts with a question, not a prescription: “Walk me through what happened in that stakeholder meeting. What were you trying to accomplish? Where did it go sideways from your perspective?” The analyst might say: “I had data that contradicted the VP’s assumption, but I wasn’t sure if I should surface it in the room or send it in a follow-up email. I chose email. It got ignored.” Now you have something real to work with. The issue isn’t lack of proactivity. It’s uncertainty about when and how to challenge authority with data. The solution isn’t “speak up more”—it’s role-playing how to present contradictory data in real-time without triggering defensiveness, or identifying which battles are worth fighting in public versus private channels.

This takes longer than delivering a bullet-pointed action plan. It requires the manager to be genuinely curious about the employee’s perspective rather than rushing to fix the problem. But the payoff is sustainable behavior change rather than short-term compliance. The employee doesn’t just do the thing you told them to do—they understand the principle behind it and can apply it to new situations. That’s the difference between feedback and mentorship.

The Redirect-Before-Remediate Framework

Most managers approach underperformance with a remediation mindset: identify the gap, assign training, track improvement. It’s logical. It’s also backwards in most cases. The Redirect-Before-Remediate Framework flips the sequence. Before you fix the skill deficit, make sure the person is working on problems they’re wired to solve. This matters especially in mid-year reviews, when there’s enough time to redirect someone toward better-fit work rather than spending six months trying to force capability development in an area where they’ll always struggle.

Step 1: Map Current Work to Energizers vs. Drainers. In the review conversation, ask the employee to categorize their current projects and responsibilities into two lists: work that energizes them (they’d do more of it if given the choice) and work that drains them (they procrastinate, it feels like a grind, they’re relieved when it’s done). Don’t ask them to justify or explain yet—just map it. David Ohnstad used this with a product manager who was underperforming on stakeholder communication but excelling at data architecture work. The PM’s energizer list was 80% technical problem-solving; the drainer list was 80% meetings and presentations. The performance problem wasn’t a skill gap. It was a role misfit.

Step 2: Identify the Highest-Leverage Energizer That Solves a Real Problem. Most people’s energizer list includes work that matters to the organization—it’s just not weighted heavily in their current role. Find the energizer activity that, if the person did more of it, would deliver measurable value. For the underperforming PM, that was designing data integration architecture for cross-functional product teams. The company needed that. The PM was good at it and wanted to do it. But it was treated as a side project while the core role demanded 30 hours a week of stakeholder alignment work the PM hated and was mediocre at. The fix wasn’t communication training. It was role redesign.

Step 3: Negotiate a Role Shift with the Employee and Their Stakeholders. This is the hard part. You’re not pulling someone off their current work entirely—you’re rebalancing the portfolio toward the energizer work while finding other ways to cover the drainer work. Sometimes that means redistributing responsibilities across the team. Sometimes it means hiring differently for the next open role. Sometimes it means acknowledging that this person’s current role isn’t the right long-term fit and exploring internal transfers. The conversation requires honesty: “You’re struggling with X because you don’t want to do X and you’re not built for it. That’s okay. Let’s figure out how to get you doing more Y, because you’re exceptional at Y and we need more of it.” According to Pragmatic Institute’s 2023 Product Management Survey, teams that allowed role specialization based on natural strengths reported 34% higher employee retention and 28% faster time-to-proficiency for new hires than teams that enforced uniform “full-stack PM” role expectations.

Step 4: Set a 90-Day Experiment with Clear Success Metrics. Don’t make this a permanent change immediately. Frame it as a pilot: “For the next 90 days, you’re spending 60% of your time on data architecture work and 40% on stakeholder communication instead of the reverse. We’ll measure impact by integration delivery timelines and stakeholder satisfaction scores. If it works, we formalize it. If it doesn’t, we revisit.” This removes the fear of making an irreversible mistake and gives both sides a clear evaluation window. The employee knows what success looks like. The manager has a decision point. The organization gets to test whether the redirect actually improves performance before committing resources.

The framework is counterintuitive because it suggests that sometimes the right response to underperformance is not to fix the person but to change what they’re working on. Managers resist this because it feels like letting someone off the hook—they’re not developing the hard skill, they’re just avoiding it. But here’s the reality: if someone has been underperforming in an area for six months despite feedback and support, forcing another six months of remediation rarely works. Redirecting them toward work they’re genuinely capable of excelling at creates immediate performance improvement and frees up capacity to hire or develop someone else who’s energized by the work the first person was struggling with. That’s a win for the employee, the team, and the business. Mentorship isn’t about making everyone good at everything. It’s about helping people find the problems they’re built to solve and getting out of their way.

Myth #3: Development Plans Should Focus on Closing Skill Gaps

Every development plan David Ohnstad has seen follows the same structure: assess current capabilities, identify gaps relative to the target role, assign training or stretch projects to close those gaps. The employee finishes the mid-year review with a list of courses to complete, certifications to earn, or skills to practice. The manager checks the “development planning” box. Six months later, the employee has completed two of the five courses, hasn’t applied anything, and the skill gaps remain. According to Deloitte’s 2024 Human Capital Trends report, 72% of employees reported having a formal development plan, but only 19% said their plan “significantly influenced their actual skill development or career progression.” The mismatch is structural, not motivational.

The myth persists because gap-based development feels rigorous and objective. You can measure it: the employee can’t do X, we train them on X, now they can do X. It maps neatly to competency frameworks and job leveling rubrics. HR can track completion rates. Managers can report progress in calibration meetings. But the underlying assumption is flawed: that career progression is primarily about acquiring missing skills. It’s not. Most high performers don’t advance because they became competent at everything—they advanced because they became exceptionally good at a few high-value things while finding ways to delegate, automate, or restructure work that required skills they didn’t have and didn’t want to develop.

What actually drives career velocity: doubling down on signature strengths and building capability stacks that are rare in combination. A data product manager who is excellent at SQL, stakeholder negotiation, and technical writing doesn’t need to become great at visual design or machine learning engineering to advance. That combination—technical depth, communication clarity, and business translation—is already rare and highly valued. Spending six months closing a gap in data visualization skills adds marginal value. Spending six months becoming the best in the organization at turning ambiguous executive asks into scoped, shipped data products creates exponential value. The difference is focusing development energy on extending leads rather than patching weaknesses.

David Ohnstad’s mid-year development conversations ask a different question: “What could you become the go-to person for in this organization by the end of the year?” Not “What skills are you missing?” but “What unique value could you own?” For a junior analyst struggling with executive presentations, the gap-based plan would assign public speaking training. The strength-based plan asks: what if this person became the best on the team at translating messy data into written executive summaries that get read and acted on? That leverages their writing strength, delivers immediate value, and positions them as indispensable without requiring them to become a confident public speaker. If the organization needs someone who can present live to executives, hire or develop that person separately. Let this analyst own the written communication lane.

This approach requires managers to resist the urge to make everyone well-rounded. Most development plans are secretly designed to sand down edges and create interchangeable team members. That’s a mistake. The highest-value employees are not the ones who can do everything reasonably well—they’re the ones who can do a few things exceptionally well that nobody else can. Mid-year reviews are the moment to identify what those few things should be and clear the path for the employee to pursue them without distraction. That’s mentorship. Everything else is just performance management.

Myth #4: Mentorship Is About Giving Advice

The standard image of mentorship: a senior leader shares hard-won wisdom with a junior employee. “Here’s what I learned when I was in your position. Here’s what I wish I’d known. Here’s what I’d do if I were you.” The employee nods, takes notes, and walks away with a clearer sense of direction. It feels productive. It’s also the least effective form of mentorship for most people in most situations. According to Harvard Business Review’s 2023 analysis of mentorship programs across 150 companies, mentorship relationships rated as “highly valuable” by participants were characterized by questions asked rather than advice given, with a 4:1 ratio of inquiry to prescription in the most successful pairings.

The advice-giving model persists because it’s efficient and it makes the mentor feel useful. Sharing lessons learned is faster than helping someone figure out their own answer. It also reinforces the mentor’s expertise—they get to be the person with the answers. But advice is context-dependent, and the mentor’s context is almost never identical to the mentee’s. What worked for a senior PM navigating a product roadmap conflict at a 500-person company in 2019 may be irrelevant for a junior PM facing a stakeholder alignment problem at a 50-person startup in 2026. The variables are different: company stage, team dynamics, leadership style, market conditions, technical constraints. Advice that ignores context is noise.

What transforms mid-year reviews into genuine mentorship moments: asking questions that force the employee to articulate their own mental model of the problem. David Ohnstad’s default in these conversations is: “Talk me through your decision-making process on that project. What did you consider? What did you dismiss? What would you do differently now?” The employee has to reconstruct their thinking, identify where it broke down, and propose their own correction. The manager’s job is to notice gaps in the reasoning, surface assumptions the employee didn’t examine, and ask follow-up questions that push the analysis deeper. “You said you dismissed the API integration approach because it was too complex. What specifically made it complex? Was that a technical constraint or a timeline constraint? If you had another two weeks, would that have changed your decision?” This is harder than giving advice. It’s also more durable. The employee doesn’t walk away with a prescription—they walk away with a better process for making the next decision on their own.

The shift from advice to inquiry doesn’t mean the manager never shares their own experience. But when they do, it’s framed as data, not prescription: “When I faced a similar stakeholder conflict, I tried X and it backfired because of Y. I don’t know if that’s relevant to your situation, but it’s something to consider.” The employee gets the benefit of the mentor’s pattern-matching without being told what to do. They can take the lesson or leave it. The locus of decision-making stays with the mentee. That’s what builds independent judgment over time. Employees who are mentored through inquiry become leaders who can think through novel problems. Employees who are mentored through advice become followers who wait for someone to tell them the answer.

How do you structure a mid-year performance review as a mentorship conversation?

Start with the employee’s self-assessment of what’s working and what’s not, then shift to forward-looking questions: where do they want to grow, what’s blocking them, and what experiment could they run in the next 90 days to build a new capability or test a role shift? Focus on capability development and trajectory rather than performance scoring.

What’s the difference between feedback and mentorship in a performance review?

Feedback evaluates past behavior and prescribes corrections. Mentorship diagnoses why the behavior occurred, explores the employee’s thinking, and helps them build better decision-making frameworks for future situations. Feedback is transactional; mentorship is developmental and compounds over time as the employee internalizes the reasoning process.

Why do most development plans fail to drive actual skill growth?

Most development plans focus on closing skill gaps rather than amplifying strengths. Gap-based plans feel rigorous but lack motivational pull—employees complete courses without applying them. Strength-based plans identify what the employee could become uniquely excellent at and clear obstacles to deep practice in that area, creating immediate value and career differentiation.

When Mentorship Breaks the Performance Review Script

The most effective mid-year review David Ohnstad ever conducted lasted 90 minutes and covered none of the template questions HR provided. The employee was a data engineer who had missed three delivery deadlines in Q1 and was flagged as underperforming. The standard playbook would have been: review the missed milestones, discuss accountability, set clear expectations for Q3 and Q4, document the conversation. Instead, David Ohnstad opened with: “What’s the most interesting technical problem you’ve worked on in the last six months?” The engineer lit up talking about a pipeline optimization experiment he’d run on his own time that reduced query runtime by 40%. It wasn’t on his official project list. It wasn’t tied to any OKR. But it was the work he was actually energized by and excellent at.

The conversation shifted to why that work wasn’t part of his core role. The engineer explained that his assigned projects were integration tasks—connecting systems, debugging API calls, writing glue code. Necessary work, but not the kind of problem-solving that motivated him. He was slow on those projects because he was disengaged, not because he lacked capability. The solution wasn’t a performance improvement plan. It was a role conversation: could his responsibilities shift toward infrastructure optimization and performance tuning, with integration work redistributed to a teammate who preferred that type of problem? The answer was yes. Within 90 days, the engineer was back on track, the team’s infrastructure performance improved measurably, and the integration backlog cleared faster because it was assigned to someone who didn’t view it as grunt work.

That outcome required the manager to ignore the script and treat the review as a diagnostic conversation, not a judgment session. It required believing that underperformance is often a signal of misalignment rather than incompetence. And it required the willingness to redesign work rather than just demand better execution. Most managers don’t have the flexibility or the trust from leadership to make those calls. But the ones who do—and who use mid-year reviews as redirection opportunities rather than scorecard sessions—build teams where people stay, grow, and do their best work. That’s the legacy piece. Not the quarterly numbers. The people who look back five years later and say, “That conversation changed my career.”

For leaders: ask yourself whether your mid-year review process creates space for that kind of conversation or just enforces compliance with a template. If it’s the latter, the process is working against you. For individual contributors: if your manager opens with a scorecard, redirect the conversation. Ask the questions you need answered: “What could I become uniquely good at here? What’s blocking me from doing my best work? What experiment could I run in the next 90 days that would prove I’m capable of more than my current role allows?” Those questions turn a performance review into a mentorship session, regardless of what the manager came prepared to discuss. The best career moves David Ohnstad has seen didn’t come from following the development plan HR approved. They came from mid-year conversations where someone asked a better question than the one on the form.

Here’s the question to ask in your next mid-year review, whether you’re the manager or the employee: What would need to change about this person’s work—not their behavior, but their work—for them to be performing at the next level six months from now? If the answer is “nothing, they just need to execute better,” you’re missing the real opportunity. Execution problems are usually symptoms. Mentorship finds the cause.

For more on how David Ohnstad’s data product management writing connects technical decision-making to leadership development, or to explore his Minnesota-based perspective on building remote-first product teams, visit David Ohnstad Minnesota. His approach to career development decisions leadership emphasizes redirecting energy toward strengths rather than patching weaknesses, and his work on rotational programs career development explores how cross-functional exposure builds the pattern-matching capability that separates good mentors from advice-dispensers. Additional resources on team-building and development strategy can be found at Leadership, Mentorship & Career Development.

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 Mid-Year Reviews: Beyond Performance Metrics appeared first on David Ohnstad.

Photo by Vitaly Gariev on Unsplash

Why Rotational Programs Feel Like Internal Limbo (But Aren’t)

Marcus Torres accepted a six-month rotation into supply chain operations even though he’d spent eight years building expertise in enterprise software sales. His director sold it as “strategic development.” His team assumed he was being sidelined. Three months in, he nearly quit to take an external offer paying $15K more — until he realized the rotation had given him access to three VPs, two cross-functional project streams, and operational context his previous role never touched. According to Gartner’s 2025 Talent Mobility Report, 68% of employees who complete structured rotational programs receive promotions within 18 months, compared to 34% who stay in static roles. The paradox: rotational leadership programs feel like career delays but function as accelerators — if you know how to use them.

This matters now because Q2 is decision season for mid-career professionals. Performance reviews are done. Annual goals are half-complete. Hiring activity peaks between May and August, and LinkedIn messages from recruiters multiply. The question isn’t whether you’re good at your job — it’s whether you’re building skills that compound or repeating the same year of experience for the eighth time. David Ohnstad’s data product management writing explores how technical depth accelerates product strategy, but rotational programs offer something complementary: lateral skill acquisition that changes how you think, not just what you know.

The Mid-Career Plateau Myth: Expertise as a Ceiling, Not a Foundation

The Myth: Deep expertise in one function is the safest path to senior leadership. Stay in your lane, become indispensable, and promotions follow.

Why It Persists: Early-career success rewards specialization. You get promoted from analyst to senior analyst to manager because you’re the best at that specific thing. Companies reinforce this by creating narrow job descriptions and function-specific career ladders. The implicit message: mastery equals value.

What’s Actually True: Expertise becomes a ceiling when it’s the only thing you have. According to Built In’s 2026 analysis of 16 companies offering rotational programs, organizations explicitly design these tracks to break functional silos for high-potential employees. The companies investing in rotation programs — Verizon, GE, Deloitte, IBM — aren’t doing it for employee satisfaction. They’re doing it because they’ve realized that mid-level managers with cross-functional fluency make better executives than deep specialists who’ve never operated outside their domain.

David Ohnstad has seen this pattern repeat at scale: product managers who understand data architecture make better prioritization decisions than those who rely entirely on engineering to tell them what’s possible. The difference isn’t intelligence — it’s exposure. A PM who’s spent three months embedded with a data engineering team during a rotation understands pipeline constraints, schema design tradeoffs, and cost implications in ways that no amount of stakeholder meetings will teach. That contextual knowledge changes what questions they ask, what requirements they write, and what tradeoffs they’re willing to defend.

The data backs this up. McKinsey’s 2024 research on internal mobility found that employees who move laterally within an organization before moving up have 1.7x higher engagement scores and 2.3x lower flight risk than those promoted vertically within the same function. The reason: they’ve built a network across the company, understand how decisions ripple through adjacent teams, and aren’t dependent on a single manager or department for career growth.

The “I’ll Lose My Edge” Fallacy: Confusing Activity with Progress

The Myth: Taking six months away from your core function means falling behind. You’ll lose credibility, your skills will atrophy, and you’ll return to find someone else doing your job.

Why It Persists: Activity feels like progress. If you’re not closing deals, shipping features, or presenting analysis every week, it feels like stagnation. Add to that the fear of being forgotten — if you’re not visible in your function, you assume others will fill the gap permanently.

What’s Actually True: The highest-value skills in modern organizations are synthesis and translation — not execution speed. A rotation doesn’t slow you down; it changes the altitude at which you operate. You stop being the person who executes tasks and start becoming the person who connects dots across silos that nobody else sees.

David Ohnstad experienced a version of this when transitioning from data engineering to product management. The initial months felt like moving backward — less technical depth, more ambiguity, constant translation work between stakeholders who spoke different languages. But that translation layer became the skill that separated good PMs from great ones. Understanding how to frame a business requirement in terms a data engineer would respect, while simultaneously explaining pipeline limitations to an executive who only cared about dashboard delivery dates, wasn’t a dilution of expertise. It was a force multiplier.

Rotational programs formalize this. You’re not abandoning your core skill — you’re adding context layers that make your core skill more valuable. A finance professional who spends six months in operations doesn’t become worse at financial modeling. They become better at understanding which operational levers actually impact the numbers they model, which assumptions are realistic, and which cross-departmental dependencies their forecasts need to account for.

The Forbes Human Resources Council notes that companies with formal rotation programs report 40% faster time-to-competency for new senior leaders compared to external hires. Why? Because internal rotators already understand company culture, decision-making patterns, and political dynamics that take external hires 12-18 months to decode.

The Torres Navigation Model: How to Rotate Without Losing Momentum

David Ohnstad calls this the Torres Navigation Model, named after Marcus Torres’s experience using a six-month rotation to reposition his entire career trajectory. This isn’t about passively accepting a rotation assignment and hoping it works out — it’s about treating the rotation as a strategic project with defined outcomes, feedback loops, and success metrics you control.

Step 1: Anchor to a Business Problem, Not a Job Description. Most rotation participants think their job is to “learn the new function.” Wrong. Your job is to solve a specific problem the host team has that your outside perspective uniquely positions you to address. Before the rotation starts, identify one thing the team has been struggling with that your background gives you an advantage in fixing. For Torres, that was sales pipeline visibility into supply chain lead times — a problem neither sales nor ops could solve alone because they didn’t speak the same language. He positioned himself as the translator, not the trainee.

Step 2: Build Dual Accountability Structures. Rotation programs fail when participants report only to the host team and their home team forgets they exist. Build a formal check-in rhythm with both. Weekly tactical updates with your rotation manager, biweekly strategic updates with your home manager. The home manager check-in isn’t a status report — it’s a forcing function to synthesize what you’re learning in terms your original function can use. This keeps you visible and ensures the rotation builds value for both sides.

Step 3: Document the Translation Gaps. Every time you encounter a communication breakdown between your home function and the rotation function, write it down. These aren’t complaints — they’re the raw material for process improvements, cross-functional playbooks, and the executive summary you’ll present when the rotation ends. Torres kept a running log of every time sales and ops misunderstood each other’s constraints. By month four, he had 37 documented examples. That became the basis for a shared forecasting model both teams actually used.

Step 4: Exit with Artifacts, Not Anecdotes. The worst outcome from a rotation is returning with vague statements like “I learned a lot about how ops thinks.” The best outcome is returning with deliverables: a process improvement you implemented, a cross-functional dashboard both teams now use, a training module you built to onboard future rotators. Artifacts prove value and make your rotation legible to people who weren’t there to see the work.

When to Rotate vs. When to Jump: The Q2 Decision Framework

Not every plateau requires a rotation. Sometimes the right move is an external jump. Here’s the decision heuristic David Ohnstad uses when coaching mid-career professionals stuck between staying and leaving:

Choose rotation if: You respect the organization’s leadership, your learning curve has flattened in your current role but hasn’t flattened across the organization, and you have a specific skill or domain you want to learn that an internal move would unlock. Rotations work when the organization has something you don’t — and you have leverage to negotiate the terms.

Choose external if: The organization’s leadership isn’t people you want to learn from, your compensation is significantly below market, or the rotation being offered is a placeholder to keep you busy rather than a genuine development opportunity. The tell: if the rotation doesn’t come with clear executive sponsorship and a defined project scope, it’s a holding pattern disguised as development.

The Built In research shows that 72% of professionals who complete rotational programs stay with their organization for at least three additional years — but that number drops to 41% if the rotation was poorly structured or felt like busywork. The program design matters as much as the decision to participate.

The Network Compounding Effect Nobody Talks About

Here’s the contrarian claim: Stop optimizing for skill development in rotations — optimize for relationship density instead. Most participants treat rotational programs as learning opportunities. That’s the wrong frame. Skills are a byproduct. The real asset is the network you build across functional boundaries that would take five years to develop organically.

David Ohnstad has watched this play out repeatedly: the PM who rotated through finance doesn’t just understand budgeting better — they now have a direct line to the FP&A director when they need to negotiate headcount. The engineer who rotated through sales doesn’t just understand customer pain points — they know which account executives to call when they need early signal on feature demand. These aren’t soft benefits. They’re the difference between waiting two weeks for a stakeholder meeting and getting an answer in a Slack DM because you worked together for six months.

According to Harvard Business Review’s 2023 analysis of internal mobility, employees with cross-functional relationships in three or more departments are 3.2x more likely to be selected for high-visibility projects and 2.1x more likely to receive unsolicited promotion opportunities. The mechanism isn’t mysterious: senior leaders staff critical projects with people they trust, and trust comes from working together under pressure. Rotations manufacture that trust at scale.

David Ohnstad on AI and enterprise SaaS explores how AI reshapes technical roles, but the human relationship layer remains the unlock for career velocity. You can’t automate the judgment call a finance VP makes when deciding whether to fund your project — but you can dramatically improve the odds if you’ve already proven you understand their constraints during a rotation.

The Post-Rotation Trap: Returning to Your Old Role Like Nothing Changed

The most common failure mode happens after the rotation ends. You return to your home function, everyone welcomes you back, and within three weeks you’re doing exactly what you did before — except now you’re bored and frustrated because you’ve seen how other parts of the organization operate.

David Ohnstad calls this the “re-entry stall.” The rotation expanded your perspective, but your role didn’t expand to match it. The fix: negotiate the scope change before you return. During your final month of rotation, meet with your home manager and propose three specific ways your role should evolve based on what you now know. Not vague “I’d like to do more strategy” asks — concrete deliverables that use your new cross-functional fluency.

For Torres, that meant ownership of a new sales-ops alignment initiative that didn’t exist before his rotation. He didn’t return to his old territory and quota. He returned to a newly created role that formalized the translation work he’d been doing informally. That’s the win condition: the rotation doesn’t just develop you — it creates organizational value that justifies a new role.

How long should a rotational program last to be effective?

Most effective rotations last between four and nine months. Shorter than four months provides exposure but not enough time to deliver meaningful work or build deep relationships. Longer than nine months risks losing connection to your home function and can feel like a permanent transfer rather than development. Six months is the most common duration because it allows one full project cycle and two quarters of performance visibility without creating ambiguity about your long-term trajectory.

What’s the difference between a rotation and a lateral move?

A rotation is temporary with a defined return path to your home function or a new role that leverages both experiences. A lateral move is a permanent position change within the same level. Rotations are structured development programs with explicit learning objectives and dual reporting. Lateral moves are standard transfers where you leave your old role entirely. Rotations build breadth while maintaining your functional identity; lateral moves trade depth in one area for depth in another.

Why do rotational programs fail for some employees?

Rotations fail when they lack executive sponsorship, clear project scope, or accountability structures. If you’re rotated into a team that doesn’t have real work for you or treats you as temporary help rather than a development investment, you’ll spend six months observing instead of contributing. Failed rotations also happen when participants don’t actively manage the transition back to their home function, returning to find their old role unchanged and their new skills unused. Success requires intentional design from both the organization and the participant.

Two Takeaways and One Audit Question

For practitioners: If you’re five to ten years into your career and feel plateaued, audit whether your constraint is skill depth or organizational visibility. Rotational programs solve the visibility and context problem — external moves solve the compensation and leadership problem. Choose the intervention that matches the actual constraint, not the one that feels easier to justify.

For leaders: Stop treating rotations as rewards for high performers. Treat them as infrastructure for building a leadership pipeline that doesn’t require expensive external hires every time you need a director who understands more than one function. The ROI is in retention and faster time-to-competency for senior roles, not employee satisfaction scores.

Here’s the audit question: If you left your current role today, how many people in other functions would pick up the phone when you called asking for help — not because they have to, but because they trust you? If that number is below five, your network density is your career bottleneck. A rotation fixes that faster than three years of conference attendance.

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.

Leadership, Mentorship & Career Development

The post Rotational Programs: Why They’re Career Accelerators, Not Setbacks appeared first on David Ohnstad.

Photo by Vitaly Gariev on Unsplash

The Mid-Year Review I Almost Ruined

I walked into a mid-year performance review with a script. Fourteen bullet points, organized by competency category, color-coded by severity. The employee sitting across from me — we’ll call her Maya — had missed three deadlines in Q2, delivered a stakeholder presentation that landed flat, and stopped contributing in team standby meetings. I had the receipts. I was prepared to be fair, direct, and professional. What I wasn’t prepared for was the question Maya asked eleven minutes in: “Do you think I should look for another role?”

That question broke the script. Because the honest answer wasn’t yes or no — it was “I don’t know what you actually want to build toward, so I have no idea if this role still fits.” We’d been working together for nine months. I knew her output. I knew her gaps. I didn’t know her goals. According to Gallup’s 2024 State of the Global Workplace report, only 32% of employees strongly agree that their manager involves them in goal-setting. I was part of the 68% — and it showed. That review turned into a two-hour conversation that reset Maya’s trajectory, but it shouldn’t have taken a near-resignation to trigger it.

Why Mid-Year Reviews Fracture More Relationships Than They Strengthen

Most performance reviews fail because they’re backward-looking audits, not forward-looking mentorship conversations. Managers arrive with a scorecard: what went well, what went poorly, what needs to improve. The employee arrives defensive, transactional, or disengaged. Both sides treat the meeting as a compliance checkpoint rather than a pivot point. The result: 58% of employees say their annual review process doesn’t help them improve, according to Gallup’s employee engagement research. Mid-year reviews, when done poorly, compress that dysfunction into a tighter cycle — twice the friction, half the patience.

Here’s what goes wrong structurally. The review is scheduled because the calendar says it’s time, not because there’s a natural inflection point in the work. The manager prepares by pulling metrics, scanning Slack threads, and reconstructing a narrative from fragments. The employee prepares by listing accomplishments they think will land well. Neither party walks in asking: “What does this person need to grow into next, and am I the right person to help them get there?” That’s the mentorship question. It’s also the question most managers skip entirely because performance review templates don’t include a field for it.

The stakes are higher in June than most leaders realize. Q2 closes, budgets get locked for H2, and hiring pipelines either open or freeze based on team capacity assessments. A mid-year review that labels someone as “underperforming” without a development plan doesn’t just document a problem — it becomes a referendum on whether that person survives the next reorg. David Ohnstad’s data product management writing explores how performance assessments feed directly into resource allocation models, often without the employee knowing their review score is being used to justify headcount decisions six months later.

The Redirect Framework: Turning Reviews Into Mentorship Pivots

This is a four-part reframe. It doesn’t replace the performance review — it redirects it from audit to acceleration. The goal is to end the conversation with the employee knowing exactly what capability they’re building next and why it matters beyond this quarter’s OKRs. Each part below is a distinct shift in how you structure the conversation.

Part 1: Start With Their Next Role, Not Their Current Performance. The first question isn’t “How do you think Q2 went?” — it’s “What role do you want to be doing two years from now?” This flips the frame. Most employees walk into a review ready to defend what they did. Almost none walk in ready to articulate where they’re heading. If they can’t name the next role, you’ve just discovered the actual problem: they’re executing tasks without a growth target. That’s a mentorship gap, not a performance gap. Spend the first twenty minutes here. Do not move forward until you understand whether they want to go deeper (specialist track), go wider (generalist leadership), or go elsewhere (cross-functional pivot). The rest of the review is pointless without this clarity.

Part 2: Name the One Capability That Unlocks That Role. Not three development areas. Not a laundry list. One. If they want to move into a senior IC role, maybe it’s “influencing decisions without authority.” If they want to lead a team, maybe it’s “teaching someone else to do your current job well enough that you’re no longer the bottleneck.” If they want to shift functions, maybe it’s “building fluency in how [other team] measures success.” This is where most reviews go off the rails: managers try to fix everything at once. High performers don’t grow by addressing twelve feedback items — they grow by obsessively improving one leverage skill that changes what opportunities they’re considered for. According to McKinsey’s 2023 research on organizational capability building, employees who focus on one differentiated skill in a development cycle are 3.2x more likely to be promoted within 18 months than those with multi-item improvement plans.

Part 3: Co-Design a Proof Point, Not a Development Plan. Development plans are vague: “Improve communication skills.” “Build executive presence.” “Increase strategic thinking.” None of those are measurable, and none of them tell the employee what to actually do Monday morning. Instead, co-design one proof point: a project, presentation, or decision that demonstrates the capability you named in Part 2. Example: “By the end of Q3, you’ll run the quarterly business review for your product area — solo, with slides you built, taking questions from the VP without me in the room. That’s your proof point that you can represent the product to leadership.” Now there’s a target. Now there’s a forcing function. The mentorship conversation becomes: what support do you need from me to make that proof point successful?

Part 4: Pre-Commit to a Follow-Up That Isn’t a Performance Review. Most mid-year reviews end with “Let’s check in again in Q4.” That’s not mentorship — that’s a countdown to the next audit. Instead, commit to a specific follow-up in 4-6 weeks where the only agenda is: “How’s the proof point going, what’s blocking you, and what’s one thing I can do to help?” No scorecard. No competency assessment. Just coaching. This is where the mentorship relationship either solidifies or evaporates. If you ghost this follow-up, the employee learns that your interest in their growth was performative. If you show up prepared and focused, they learn that you’re invested in their trajectory, not just their output. That difference is what separates managers who retain high performers from managers who watch them leave.

What Changed After I Stopped Grading and Started Coaching

Maya and I rescheduled that mid-year review. The first one was a data dump — me listing gaps, her defending choices. The second one, a week later, followed the redirect structure above. We opened with the question: “Do you want to stay in this role long-term, or is this a stepping stone to something else?” She admitted she’d been trying to “prove herself” in a role she didn’t actually want, hoping it would open doors to product strategy. That reframed everything. The missed deadlines weren’t apathy — they were misalignment. She was optimizing for execution speed when she should have been building strategic thinking skills.

We co-designed a proof point: by the end of Q3, she’d lead a feature prioritization workshop with three stakeholder teams, present the trade-off analysis to leadership, and defend the roadmap decision in a VP review. That was her step toward product strategy. It was also terrifying for her — and that was the point. Growth happens at the edge of capability, not in the middle of comfort. I committed to three things: one prep session before the workshop, one feedback session after a dry run, and one debrief within 48 hours of the VP review. Those weren’t performance check-ins. They were coaching gates.

She delivered. The workshop surfaced conflicts between teams that had been simmering for months. The trade-off analysis forced stakeholders to put numbers on their priorities instead of lobbying for everything. The VP review didn’t go perfectly — she stumbled on a question about technical debt trade-offs — but she recovered and finished strong. More importantly, the VP asked her to present the same framework to another product team the following month. That’s proof. Six months later, Maya moved into an associate product manager role on a different team. She didn’t need me to fix her performance. She needed me to stop grading her execution and start coaching her toward the role she actually wanted.

The Contrarian Position Most Leaders Won’t Say Out Loud

Stop measuring mentorship by how much feedback you give. Most managers think they’re mentoring when they’re actually just narrating performance gaps. Real mentorship is measured by how many people you’ve helped get promoted, get hired elsewhere into better roles, or take on stretch projects they weren’t initially considered for. If you can’t name three people whose careers visibly accelerated because of your coaching, you’re not mentoring — you’re managing. According to LinkedIn’s 2024 Workplace Learning Report, employees who report having a mentor are 5x more likely to say they have opportunities to learn and grow, but only 37% of professionals say they currently have one. That gap exists because most leaders confuse giving feedback with giving direction.

The uncomfortable truth: some people on your team don’t need better performance reviews. They need to leave. Not because they’re failing, but because they’ve outgrown the role and you don’t have the next one to offer them. Career development decisions leadership requires honest conversations about when staying is stagnation. If someone has been “meeting expectations” for two years without a promotion or a scope increase, that’s not stability — that’s a holding pattern. A good mentor names that pattern and helps the person move, even if it means losing them to another team or another company. Retention for retention’s sake isn’t mentorship. It’s just org chart optimization dressed up as loyalty.

How Father’s Day Fits Into This (and Why It Matters)

Father’s Day lands in the middle of mid-year review season for a reason that’s worth naming. Both are about legacy. The question a father asks — “What did I teach them that will outlast me?” — is the same question a mentor should ask: “What capability did I help them build that will compound long after they’ve left David Ohnstad’s team?” David Ohnstad, as a father of two daughters, has built bookshelves and dressers for both their rooms — not because he’s a master craftsman, but because he wanted them to see that you can make something useful with your hands if you’re willing to measure twice and learn from mistakes. That lesson isn’t about woodworking. It’s about persistence, precision, and the confidence that comes from solving your own problems.

The same lesson applies to leadership. If you’re a manager conducting mid-year reviews this month, the question isn’t “Did my team hit their numbers?” It’s “Did I give them a skill they’ll carry into their next role, and the role after that?” That’s the mentorship standard. David Ohnstad Minnesota readers who are also parents recognize the parallel immediately: the best gifts you can give — to your kids or your team — are capabilities, not solutions. A solved problem disappears. A learned skill compounds.

Here’s the uncomfortable part: most managers won’t be remembered for the quarterly OKRs they hit. They’ll be remembered for whether they helped someone figure out what they were capable of becoming. That’s not soft leadership — that’s the hardest part of the job, because it requires you to invest in someone’s growth even when it means they’ll outgrow you. If you’re running mid-year reviews this June and you’re not asking “What’s the one capability I can help this person build that changes their trajectory?” — then you’re not mentoring. You’re just filling out templates.

What should I focus on in a mid-year performance review to make it a mentorship moment?

Focus on identifying the one capability the employee needs to unlock their next role, not on grading their current performance. Start by asking where they want to be in two years, then co-design a proof point project that demonstrates that capability by the end of the quarter. Schedule a follow-up coaching session in 4-6 weeks to remove blockers, not to audit progress.

How do I give constructive feedback without making a mid-year review feel like a performance audit?

Reframe feedback as gap identification, not judgment. Instead of “You missed three deadlines this quarter,” ask “What’s blocking you from delivering on time, and what capability would help you close that gap?” Then shift immediately to designing a proof point that builds that capability. Constructive feedback works when it’s tied to forward motion, not backward grading.

Why do mid-year reviews often damage manager-employee relationships?

Most mid-year reviews are backward-looking audits that focus on what went wrong without connecting it to what the employee is trying to build toward. Employees leave these conversations feeling evaluated, not coached. Reviews damage relationships when they become transactional scorecards instead of mentorship pivots that clarify the path to the employee’s next role.

Two Takeaways and One Question

For practitioners: if you’re conducting mid-year reviews in the next two weeks, replace your competency scorecard with the Redirect Framework above. Start with their next role, name the one capability that unlocks it, co-design a proof point, and pre-commit to a follow-up coaching session. That structure turns a compliance meeting into a career accelerator.

For leaders: audit your team’s mid-year review outcomes six months from now. How many people got promoted? How many took on stretch projects they weren’t initially considered for? How many left for better roles elsewhere and stayed in touch with you as a mentor? If those numbers are low, your reviews aren’t working — they’re just paperwork. Real mentorship shows up in other people’s career momentum, not in your documentation.

Here’s the question to sit with: when was the last time you asked someone on your team what role they want to be doing two years from now — and actually redesigned their current work to build toward that answer?

For more on this topic, see rotational programs career development.

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 Mid-Year Performance Reviews: When Good Intentions Go Wrong appeared first on David Ohnstad.

Photo by Vitaly Gariev on Unsplash

The Tuesday David Ohnstad Almost Turned in His Resignation

David Ohnstad had the email drafted. Subject line: “Notice – Transition Plan.” Body: professional, brief, exit date nine weeks out. The cursor hovered over Send for about forty seconds. Then his phone rang — the VP who’d been pushing for a new rotational leadership track, asking if David wanted the first slot in a six-month product-to-engineering rotation before making any “big career moves.” He closed the draft. Six months later, he was running a data infrastructure initiative he didn’t know existed when he almost quit. According to Gallup’s 2023 State of the Global Workplace report, 44% of employees worldwide are actively watching for new job opportunities — but fewer than 12% of organizations offer structured internal mobility programs that let people pivot without leaving. That gap is expensive: external replacement costs run 1.5x to 2x annual salary. Internal rotation costs a tenth of that and retains institutional knowledge most companies hemorrhage during turnover.

The choice David faced is playing out in thousands of mid-career professionals right now. You’re five to ten years into a role. You’re competent. Maybe even respected. But you’ve hit a plateau — not because you stopped growing, but because your current function has a ceiling and the next logical step is either a lateral move into someone else’s lane or a management track you don’t want. The external job market looks appealing until you calculate what you’d lose: the network you spent years building, the credibility you earned, the institutional shortcuts that make you effective. Rotational leadership programs are designed to solve this exact problem — but most people don’t know they exist until they’re already halfway out the door.

Why Mid-Career Professionals Leave When Internal Mobility Could Have Kept Them

The failure mode here is visibility, not opportunity. Most organizations have more internal mobility options than employees realize — but those options live in HR decks, leadership development memos, and skip-level conversations that never happen. By the time a high performer starts job hunting, they’ve already emotionally exited. The rot starts earlier: when someone realizes they’ve stopped learning, and nobody in their direct reporting chain has offered a path forward. According to McKinsey’s 2022 analysis on employee engagement and retention, lack of career development is the number one predictor of voluntary turnover among employees with 3-10 years tenure — outweighing compensation, work-life balance, and manager relationships.

David saw this firsthand at a SaaS company where three senior product managers left within five months. All three cited “limited growth opportunity.” Two of them had been informally offered rotation into data architecture and customer success engineering — but those conversations happened in hallways, not in formal development plans, and none of the three took them seriously because the offers felt offhand rather than strategic. The company replaced all three externally at significant cost, then six months later launched a formal rotational program. The irony was not lost on the team that stayed.

Here’s the tactical breakdown of what goes wrong: managers assume high performers know about internal opportunities because leadership talks about them in all-hands meetings. High performers assume internal opportunities are reserved for people in a different tier or function. HR assumes managers are having career development conversations. Managers assume HR owns that process. Meanwhile, the best people on the team are texting recruiters because nobody explicitly said, “Here’s a rotation path, here’s the timeline, here’s what you’d own, and here’s how we make sure you don’t lose ground in your current domain while you build a new one.”

The Rotation-Before-Resignation Model: How to Structure a Mid-Career Pivot Without Leaving

This is a four-phase model that treats internal rotation as a formal product launch, not a favor or a side project. The framework is called the Rotation-Before-Resignation Model, and it’s built around the insight that most people leave not because they want to, but because staying feels like stagnation and nobody offered a structured alternative with clear milestones and measurable outcomes.

Phase 1: The Explicit Offer (Week 0)
Rotational opportunities must be presented as formal offers with written scope, timeline, success metrics, and a named executive sponsor. The conversation cannot be “Maybe we could find you something in another department.” It has to be “We’re offering you a six-month rotation into [specific function], you’d own [specific outcomes], your current role would backfill with [name or plan], and at the end we’ll evaluate three paths: return to your original role with expanded scope, transition fully to the new function, or design a hybrid role.” The formality is the signal. Informal offers get declined or ignored because they feel like distractions, not investments.

Phase 2: The Protected Transition (Weeks 1-8)
The first eight weeks are about onboarding into the new function without abandoning the old one. This is the phase most rotations get wrong — they either fully pull someone out (creating chaos in their original team) or leave them half-in (so they’re doing two jobs badly instead of one well). The fix: assign a transition lead in the original function who owns handoff documentation and stakeholder communication, and assign a rotation mentor in the new function who owns onboarding and context-building. David Ohnstad’s rotation into data infrastructure included weekly check-ins with both a product mentor (his original domain) and an engineering lead (his rotation target). That dual accountability kept him from falling through the gap between teams.

Phase 3: The Ownership Milestone (Weeks 9-20)
By week nine, the person in rotation should own a discrete project or initiative in the new function — not shadow someone else’s work, but own an outcome with their name on it. This is where rotations either prove their value or reveal they were a mismatch. For David, the milestone was leading a database schema redesign for a customer-facing analytics product. It required him to learn query optimization, collaborate with engineers he’d never worked with, and present technical tradeoffs to stakeholders who didn’t know him. The project shipped in week eighteen. The credibility he built in that window became the foundation for everything that followed.

Phase 4: The Decision Gate (Weeks 21-24)
The final month is evaluation and decision architecture. Three questions get answered: Did the rotation achieve its stated outcomes? Does the person want to continue in the new function, return to the old one, or build something hybrid? Does the organization have a role that matches that preference? The mistake most companies make here is treating the decision as binary — stay in the new role or go back — when the real value often emerges in hybrid designs. David’s rotation led to a newly created role: Senior Data Product Manager with shared accountability across product and engineering. That role didn’t exist before the rotation. It exists now because the rotation surfaced a gap the organization didn’t know it had.

What Happened When David Chose Rotation Over Resignation

The decision to take the rotation instead of sending the resignation email wasn’t obvious at the time. David had been a product manager for six years. He knew the role. He was good at it. But he’d hit the point where every sprint felt like a variation on the last one — different features, same process, same stakeholders, same constraints. The external offers he was evaluating promised new challenges, better titles, more money. What they didn’t promise was continuity. He’d have to rebuild his network, re-prove his credibility, and relearn the institutional context that makes senior work efficient. The rotation offered something different: a chance to expand his skill set without abandoning the organizational capital he’d spent years accumulating.

The first month was disorienting. David sat in engineering standups where half the terminology was unfamiliar. He reviewed pull requests he couldn’t fully evaluate. He asked questions that revealed how much he didn’t know about database architecture and schema design. The team was patient, but he felt the gap between his product expertise and his engineering fluency every day. The thing that kept him from bailing: the executive sponsor checked in weekly, the rotation mentor normalized the learning curve, and the transition lead in his old team made sure nothing critical fell apart while he was ramping up.

By month three, something shifted. David started contributing to technical discussions — not just asking questions, but offering perspectives shaped by his product background that the engineering team hadn’t considered. A debate about query performance turned into a conversation about which user workflows actually required sub-second response times and which could tolerate latency if it meant better data accuracy. That’s a product question, but it required engineering context to ask it well. The synthesis of both domains became David’s new advantage. When the rotation ended, the organization created a role that didn’t fit neatly into either product or engineering — it sat at the intersection, bridging business requirements and technical architecture. That role exists because David stayed long enough to prove the value of the hybrid skill set the rotation revealed.

Stop Treating Rotations as Perks — They’re Retention Infrastructure

Most organizations position rotational programs as development opportunities for high performers, which makes them sound optional and aspirational. That framing is wrong. Rotations aren’t perks — they’re retention infrastructure for the people you can’t afford to lose. The professionals most likely to leave mid-career aren’t the ones struggling; they’re the ones who’ve mastered their current role and see no path forward. External offers look appealing because they promise growth. If your organization doesn’t offer a structured internal alternative, you’re choosing to lose those people.

According to Korn Ferry’s 2023 talent mobility research, organizations with formal rotational programs report 27% lower voluntary turnover among employees with 5-10 years tenure compared to organizations that rely on informal development conversations. The difference isn’t the quality of the opportunities — it’s the structure. Informal conversations feel like maybes. Formal programs with named timelines, success metrics, and executive sponsorship feel like investments. People stay when they believe the organization is investing in their growth, not just managing their retention risk.

Here’s the contrarian part: rotations should be hardest to access for your lowest performers, not reserved exclusively for your highest. The instinct most leadership teams have is to offer rotations only to people who are already exceeding expectations — but those people are also the most likely to have external options. The better filter is readiness, not performance rating. A mid-performer who’s plateaued because they’ve outgrown their role is a better rotation candidate than a high performer who’s still learning in their current function. The goal isn’t to reward past success; it’s to prevent future attrition by giving people a growth path before they start looking externally.

How Rotational Programs Intersect With Broader Strategic Skill Gaps

One often-overlooked advantage of rotational programs is that they surface and fill skill gaps the organization didn’t know it had. When David rotated into engineering, it became immediately clear that the product team didn’t understand how data architecture decisions constrained or enabled product features — and the engineering team didn’t understand how customer workflows shaped database query patterns. Both gaps were expensive. Product roadmaps included features that were technically impractical. Engineering optimizations solved problems customers didn’t have. The rotation didn’t just develop David — it created a bridge between two functions that had been operating with incomplete context.

This matters particularly as AI reshapes technical roles across organizations. Professionals who understand both the business strategy and the technical implementation have become critically scarce. David Ohnstad’s data product management writing explores this gap in depth — the best product managers now need fluency in data architecture, AI/ML capabilities, and technical feasibility in ways that weren’t required five years ago. Rotational programs are one of the few scalable ways to build that fluency without waiting for the external hiring market to produce candidates who already have it. You grow the hybrid skill sets internally, in people who already understand your organization’s strategy, customers, and constraints.

Another intersection worth noting: professionals in rotational programs often become the organization’s earliest adopters and most effective evaluators of new tools and platforms. When you rotate someone from product into engineering, they start asking questions like “Why are we building this manually when there’s a tool for it?” or “Why are we using this tool when it doesn’t match how our users actually work?” Those questions come from seeing both sides. The answers often lead to better tooling decisions, faster adoption, and fewer expensive pilot programs that fail because nobody bridged the gap between technical capability and business need. For more on how technical AI capabilities influence product and organizational decisions, the broader conversation about AI/ML implementation continues to reshape what mid-career professionals need to learn to stay competitive.

What Leaders and Practitioners Should Do Differently Starting This Quarter

For leaders: stop treating rotational programs as experimental or reserved for future cohorts. If you’re losing mid-career talent to external offers, you already have a rotation problem — you just haven’t formalized the solution. Identify three high-performing professionals who’ve been in their role for 4-7 years and ask them directly: “If we offered you a six-month rotation into [adjacent function], with a clear scope and a decision gate at the end, would that change your thinking about staying?” If the answer is yes for two out of three, you’ve just validated demand. Build the structure: timeline, success metrics, executive sponsor, transition plan. Treat it like a product launch, not a favor.

For practitioners: if you’re feeling plateaued and considering external offers, have the rotation conversation before you start interviewing. The script is: “I’ve been in this role for [X] years, I’m ready to grow, and I’d like to explore a rotation into [specific function] for [specific timeline]. Can we design that as a formal program with clear outcomes and a decision point, or is that not something the organization is set up to support?” If the answer is no or vague, that’s useful data — it tells you whether the organization is serious about internal development or just managing retention. If the answer is yes, you’ve created an option that didn’t exist before. Most people never ask, so they never know whether the rotation path was available.

One more tactical note: rotations work best when they’re tied to real organizational priorities, not just individual development goals. David’s rotation succeeded because the company needed someone who could bridge product and engineering on a data infrastructure redesign — the rotation solved a business problem, not just a career development request. If you’re proposing a rotation, frame it around what the organization needs, not just what you want to learn. The pitch is: “You have [specific gap or challenge], I have [current expertise], and a rotation into [target function] would let me build [hybrid capability] that solves [business problem].” That’s a business case, not a personal favor. It’s much harder to say no to.

What is a rotational leadership program and how does it work?

A rotational leadership program is a structured internal mobility initiative where employees spend a defined period (typically 6-12 months) working in a different function, team, or role within the same organization. Participants maintain their employment and benefits while gaining new skills, expanding their network, and building cross-functional expertise. The program includes formal onboarding, success metrics, executive sponsorship, and a decision gate at the end to determine the participant’s next role.

How do rotational programs reduce employee turnover?

Rotational programs reduce turnover by offering high-performing mid-career professionals a structured growth path without requiring them to leave the organization. According to Korn Ferry’s research, companies with formal rotation programs see 27% lower voluntary turnover among employees with 5-10 years tenure. The programs solve the “plateaued but competent” problem — where employees have mastered their role but see no advancement path, making external offers more appealing than staying.

When is the right time to propose a rotational opportunity?

The right time is before you start seriously interviewing externally but after you’ve identified a specific skill gap or adjacent function you want to learn. Rotational proposals work best when framed around organizational needs rather than personal development alone. If you’ve been in your current role 4-7 years, are performing well, but feel plateaued, and can identify a cross-functional business problem your rotation would help solve — that’s the signal to start the conversation with leadership.

When did you last evaluate whether your organization’s internal mobility options are visible and structured enough to compete with external offers — or are you losing people who would have stayed if someone had simply asked? For more on how to build systems that retain talent while driving strategic outcomes, see the full resource on Leadership, Mentorship & Career Development. And if you’re interested in how David thinks about building systems outside of work — from data pipelines to furniture — his approach to iterative making is documented at David Ohnstad’s woodworking and making.

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 Career Pivots: When to Stay and When to Leave appeared first on David Ohnstad.

Photo by Vitaly Gariev on Unsplash

Why Most Conference Attendees Leave Money on the Table (And How You Won’t)

You spent $2,400 on a Snowflake Summit pass, another $1,800 on flights and hotel, and three days away from shipping product. Six months later, your LinkedIn connection count went up by 11, you attended 14 sessions, and exactly zero executive relationships materialized into anything beyond a polite email exchange. According to Gartner’s 2024 Technology Conference ROI Study, 73% of mid-level professionals report “minimal career impact” from major industry conferences despite average per-attendee costs exceeding $4,000 when travel and opportunity cost are included. The problem isn’t the conference. It’s that you showed up without a positioning strategy.

David Ohnstad has attended dozens of these events—not as a passive session consumer, but as someone building deliberate executive presence in rooms where careers accelerate. The difference between professionals who extract real value from conferences and those who collect swag bags comes down to a repeatable framework that starts weeks before the opening keynote and extends months after the closing party. This isn’t about networking tips or personal branding platitudes. It’s about treating conference attendance as a product launch where you are the product, your positioning is the go-to-market strategy, and executive relationships are the distribution channel.

The Three-Phase Executive Visibility Engine

Most people prepare for conferences by scanning the session catalog and booking a hotel. That’s not preparation—that’s logistics. Building executive presence at data conferences requires a structured approach across three distinct phases: pre-event positioning, on-site leadership signaling, and post-event relationship leverage. Each phase has specific tactics, measurable outputs, and a clear success metric. Skip any phase and your ROI collapses.

Phase 1: Pre-Conference Positioning (Weeks -3 to -1)
This phase is about establishing credibility before you walk into the venue. Executives don’t take meetings with strangers who approach them in a hallway. They take meetings with people who already exist in their professional context. Your job in this phase is to become contextually relevant.

Start by identifying three executives attending the conference whose work intersects with yours. Not aspirational connections—people solving adjacent problems in similar environments. Use the conference speaker list, LinkedIn event attendance signals, and sponsor company leadership teams. Once you have your three targets, publish a short-form piece of content (LinkedIn article, blog post, or technical breakdown) that directly addresses a challenge they’re facing. Tag them thoughtfully—not as spam, but as a genuine extension of your work. According to McKinsey’s 2023 Professional Development Survey, executives are 4.2 times more likely to accept meeting requests from individuals who have demonstrated domain expertise in a public forum within the prior 30 days.

The surprise element here: you’re not networking yet. You’re building the conditions for networking to succeed. When you approach someone at the conference, you’re not introducing yourself—you’re continuing a conversation you started three weeks ago. This flips the power dynamic. You’re no longer asking for their time. You’re offering continuity.

Phase 2: On-Site Leadership Signaling (Days 1-3)
Conferences reward visible contributors, not passive attendees. Your goal in this phase is to position yourself as someone who adds value to the ecosystem, not extracts it. This means asking the best question in a session, hosting an impromptu hallway conversation on a trending topic, or sharing real-time insights on social media that conference attendees are already following.

David Ohnstad learned this at a previous Snowflake Summit when he noticed a gap in the data mesh conversation happening across three separate breakout sessions. Instead of passively attending, he posted a LinkedIn thread synthesizing the contradictions between the sessions and tagging the speakers. Two of them responded publicly. One invited him to a vendor dinner that evening. That dinner turned into a consulting engagement six months later. The post took 12 minutes to write. The session attendance alone would have generated zero follow-up.

The counterintuitive move: don’t attend every session. Executives don’t. They attend the sessions where decisions are being made or where they can be seen contributing. Your calendar should have white space—time to have unplanned conversations, write a quick synthesis post, or join a spontaneous discussion. If your schedule is back-to-back sessions, you’re optimizing for content consumption, not relationship development. David Ohnstad’s data product management writing frequently emphasizes that value creation happens in the margins, not the main event.

Phase 3: Post-Event Relationship use (Weeks +1 to +12)
The conference ends. Most people do nothing. A few send generic LinkedIn connection requests. Almost no one executes a systematic follow-up plan. This is where executive presence is actually built—not in the moment of introduction, but in the months of demonstrated follow-through afterward.

Within 48 hours of the conference ending, send a specific follow-up to every executive you had a meaningful conversation with. Not a “great to meet you” note—a continuation. Reference something they said, share a resource that addresses it, or introduce them to someone in your network who can help. According to LinkedIn’s 2023 Professional Branding Study, 61% of executive relationships that convert into ongoing collaboration started with a follow-up action delivered within 72 hours of the initial meeting.

Then, every 4-6 weeks, deliver value without asking for anything. Forward an article they’d care about. Introduce them to a candidate for an open role they mentioned. Share a data point that contradicts something they’re working on. The goal is to stay present in their context as someone who contributes signal, not noise. By month six, when you need to ask for something—a reference, an introduction, a partnership conversation—you’re not cold-calling. You’re cashing in relationship equity you’ve been building systematically since the conference ended.

What Happened When I Skipped Phase 1 (And Why It Cost Me Six Months)

Two years ago, David Ohnstad attended a major SaaS conference with a target list of five executives he wanted to meet. He skipped the pre-positioning phase—no content, no outreach, no context-building. He just showed up and tried to manufacture introductions through hallway conversations and session Q&A. Three of the five never materialized. One conversation happened but went nowhere. One turned into a polite coffee that generated zero follow-up. The problem wasn’t the quality of the conversations. It was that he was starting from zero credibility in a room full of people who had already built context with each other.

Six months later, David attended a similar event but executed Phase 1 properly. He published a breakdown of AI-driven data pipeline optimization two weeks before the conference and tagged three executives solving similar problems. Two responded publicly. One reached out privately. At the conference, all three approached him first—not the other way around. The shift was structural, not social. He wasn’t networking harder. He was positioning smarter.

The follow-up metrics told the story. From the first conference (no pre-positioning): 1 LinkedIn connection, 0 follow-up meetings, 0 ongoing relationships. From the second conference (with pre-positioning): 7 LinkedIn connections, 4 follow-up meetings scheduled within two weeks, 2 ongoing advisory relationships still active 18 months later. Same person. Same skillset. Completely different strategy. The lesson wasn’t about confidence or charisma. It was about treating conference attendance as a structured product launch where the prep work determines 80% of the outcome before you walk into the venue.

Stop Optimizing for Session Attendance—It Measures the Wrong Thing

Here’s the contrarian claim that most conference-goers will reject: attending more sessions does not correlate with better career outcomes from conferences. In fact, Snowflake Summit 2025 attendee surveys showed that professionals who attended fewer than 60% of available sessions reported 2.3 times more “high-value professional connections” than those who attended 90% or more. Why? Because session attendance optimizes for content consumption, not relationship development. You can watch the session recordings later. You cannot recreate the hallway conversation with the VP who was solving the exact problem you’ll face in six months.

The conventional wisdom is to pack your schedule, absorb as much content as possible, and “maximize the investment.” That’s the wrong proxy. The real ROI from conferences isn’t what you learn—it’s who you become contextually relevant to. Sessions provide content. Relationships provide access. Content is fungible. Access is not. When you prioritize session attendance over relationship development, you’re optimizing for the least scarce resource at the conference (information) while ignoring the most scarce resource (executive attention). David Ohnstad on AI and enterprise SaaS explores this same dynamic in product strategy: optimizing for activity metrics instead of outcome metrics is how teams burn budget without moving the business forward.

If you finish a three-day conference having attended 22 sessions and had 3 substantive conversations, you didn’t maximize ROI—you minimized it. The inverse is more valuable: attend 8 sessions, have 15 conversations, write 2 synthesis posts, and host 1 impromptu discussion. That’s the profile of someone who leaves the conference with executive presence, not just a tote bag full of vendor swag.

How do you build executive presence at a tech conference if you’re mid-level?

Start by contributing publicly before the conference—publish a LinkedIn post or article addressing a problem your target executives are solving, and tag them thoughtfully. At the event, focus on asking the best question in sessions, sharing real-time insights on social media, and hosting informal hallway discussions rather than passively consuming content. Follow up within 48 hours with specific value—a resource, introduction, or insight tied to your conversation—and continue delivering value every 4-6 weeks to build relationship equity over time.

What is the biggest mistake professionals make when attending industry conferences?

The biggest mistake is treating conferences as passive learning events rather than active positioning opportunities. Most attendees optimize for session attendance instead of relationship development, leaving with notes but no executive connections. The professionals who extract real ROI treat conference attendance as a structured three-phase process: pre-event positioning to establish credibility, on-site leadership signaling to demonstrate expertise, and systematic post-event follow-up to convert introductions into ongoing relationships. Skipping any phase collapses your return on investment.

Why does pre-conference positioning matter more than on-site networking?

Pre-conference positioning establishes credibility before you walk into the venue, transforming cold introductions into warm continuations of existing conversations. Executives are far more likely to engage with someone who has already demonstrated domain expertise in their professional context—McKinsey’s 2023 research shows they’re 4.2 times more likely to accept meeting requests from individuals who published relevant content in the prior 30 days. Without pre-positioning, you’re competing for attention with hundreds of other attendees. With it, you’re already part of the executive’s mental landscape before the conference begins.

Two Takeaways and One Question

For practitioners: Stop treating conferences as content consumption events. Your ROI comes from becoming contextually relevant to executives solving adjacent problems—not from attending every session. Execute the Three-Phase Executive Visibility Engine: pre-position with public content, signal leadership on-site through contribution (not consumption), and systematically follow up with value delivery for 12 weeks post-event. Measure success by ongoing relationships formed, not sessions attended.

For leaders: If you’re sending your team to conferences without a structured positioning and follow-up strategy, you’re wasting budget. The difference between a $4,000 networking expense and a $4,000 strategic investment is whether your people leave with executive relationships that unlock partnerships, hiring pipelines, and competitive intelligence. Require pre-conference positioning plans and post-conference relationship status reports—or stop approving the travel.

When did you last calculate the actual ROI from your conference attendance—not by sessions attended, but by relationships that changed your trajectory six months later?

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 Conference ROI: Turn Networking Into Real Relationships appeared first on David Ohnstad.

Photo by Vitaly Gariev on Unsplash

The Three-Phase Executive Presence Framework for Tech Conference ROI

A product manager at a 200-person data platform company flew to Snowflake Summit last year with a $2,400 ticket, three nights of hotel costs, and a manager’s encouragement to “make connections.” She attended twelve sessions, collected seventeen business cards, and posted four LinkedIn updates during the event. Six months later, when I asked her what tangible career outcome resulted from that investment, she couldn’t name one. According to Harvard Business Review’s 2019 analysis of conference attendance ROI, that outcome tracks—most mid-level professionals fail to extract meaningful career advancement from industry events because they treat conferences as passive learning experiences rather than active positioning opportunities.

The problem isn’t attendance. It’s the absence of a deliberate system for building executive presence before, during, and after the event. David Ohnstad’s data product management writing has emphasized feedback loops and intentional process design across technical domains—the same discipline applies to career development at high-stakes industry gatherings. Most professionals show up hoping visibility will happen to them. Senior leaders arrive with a plan to make it happen.

What Happens When Conference Attendance Lacks Strategic Architecture

The financial cost of poorly used conference attendance compounds faster than most organizations realize. A mid-level professional attends two major conferences annually—Snowflake Summit, AWS re:Invent, Databricks Data + AI Summit, or similar events. Direct costs: $4,000–$6,000 in registration, travel, and accommodation. Opportunity cost: 15–20 hours of productive work time, plus the cognitive load of catching up afterward. Multiply that across a 40-person product and engineering team, and you’re looking at $200,000 in annual conference spend.

The return on that investment should be measurable: new partnerships formed, executive visibility gained, competitive intelligence gathered, or internal credibility elevated through thought leadership. According to McKinsey’s 2023 research on professional development ROI, organizations that tie conference attendance to specific career advancement outcomes see 3.2x higher retention of high performers compared to those that treat events as generic “learning opportunities.” Yet most companies send people to conferences with vague directives like “learn what’s new” or “network with peers”—goals so diffuse they cannot be evaluated or improved.

The failure mode shows up six months post-event. A director asks, “What did we get from sending you to Summit?” The answer defaults to session summaries, vendor conversations that went nowhere, or insights that could have been gained from reading the conference recap blog posts. The professional didn’t fail because they lacked effort—they failed because they lacked a framework for translating attendance into executive presence. Without that framework, conferences become expensive tourism with a professional veneer.

The Pre-Event Positioning Stack: Building Visibility Before You Arrive

Executive presence at a conference doesn’t start when you walk through the doors—it starts three weeks before the event when you begin shaping the narrative about why you’re attending and what you’re contributing. This is the phase most professionals skip entirely, and it’s the phase that determines whether you’re treated as an attendee or as a participant worth engaging.

Phase One, Step One: Publish a pre-event position piece. Write a 400-word LinkedIn post or a short article on your professional site stating a clear, defensible thesis related to the conference theme. For Snowflake Summit, that might be: “Why most data teams are over-investing in compute optimization and under-investing in query design education.” For AWS re:Invent, it could be: “The hidden cost of serverless: when abstraction layers create debugging blind spots.” The goal is not to go viral—it’s to establish a point of view that positions you as someone who thinks critically about the industry’s current direction, not just someone absorbing vendor messaging.

This step surprises people because it feels presumptuous. Who are you to publish a hot take before attending the industry’s flagship event? The answer: you’re a practitioner with daily exposure to the problems these platforms are supposed to solve. Your operational experience is more valuable than most keynote abstractions. Senior leaders don’t attend conferences to hear what everyone already agrees on—they attend to find people who see the landscape differently. Publishing a position piece three weeks early creates a searchable artifact that conference attendees can discover when they research who else is attending. It also gives you a conversation anchor: “I wrote a piece on query design education last week—are you seeing the same pattern at your company?”

Phase One, Step Two: Identify three executives you want to meet and send a pre-event message. Don’t wait until you’re standing in a crowded hallway hoping to make eye contact. Use LinkedIn, company websites, or conference attendee lists to identify three senior leaders whose work intersects with your domain. Send a brief, specific message two weeks before the event: “I saw you’re speaking on data governance frameworks at Summit. I’m working on a similar challenge at [your company]—would you have 15 minutes for coffee on Day 2 to discuss how you’re measuring governance adoption? I’m particularly curious about the metric you mentioned in your 2024 blog post on policy enforcement.”

The specificity matters. You’re not asking for generic advice—you’re referencing their public work and proposing a concrete exchange of ideas. According to Reforge‘s 2024 analysis of professional networking effectiveness, cold outreach that references specific prior work has a 47% response rate compared to 8% for generic “I’d love to connect” messages. Most people won’t send this kind of message because it requires research and exposes them to rejection. That’s exactly why it works—you’ve differentiated yourself from the 200 other people who will try to grab that executive’s attention during the event itself.

Phase One, Step Three: Prepare one non-obvious question for every session you plan to attend. Conference Q&A segments separate passive attendees from active participants. The goal is not to ask the first question that comes to mind—it’s to ask a question that demonstrates you’ve thought past the surface layer of the topic. Spend 20 minutes before each session reviewing the speaker’s recent work, their company’s product direction, or adjacent research in the same domain. Write down one question that connects their talk to a real operational tension you’re experiencing.

For example, instead of asking, “How do you handle data quality at scale?” ask: “You mentioned automated anomaly detection in your talk—how do you prevent alert fatigue when your detection system flags 40+ potential issues daily? We’re hitting a triage bottleneck where engineers stop trusting the alerts.” The second question reveals you’ve already implemented the concept being discussed and you’re dealing with second-order consequences. That positions you as a peer problem-solver, not a novice seeking instructions. Executives in the room take note of who asks questions that expose real operational complexity—not because those people are smarter, but because those questions signal hands-on credibility.

The On-Site Leadership Signaling Protocol: How You Show Up Determines Who Approaches You

Once you’re at the event, executive presence is built through consistent, deliberate signaling across multiple micro-interactions. Most professionals optimize for session attendance and treat hallway time as downtime. Senior leaders do the opposite—they treat sessions as optional and hallway time as the primary venue for building relationships and demonstrating expertise.

Phase Two, Step One: Arrive at sessions five minutes early and sit in the first three rows. This is the simplest, most overlooked visibility tactic. Sitting in the back signals you’re there to observe. Sitting in the front signals you’re there to engage. Speakers remember who sits up front—especially if you’re the person who asked the non-obvious question during Q&A. When that speaker later becomes a connection on LinkedIn or a reference for a future role, they’ll remember the person who engaged, not the person who sat in the back row scrolling their phone.

David Ohnstad learned this during his time playing basketball at The College of St. Scholastica—positioning matters before the play even starts. If you’re not in the right spot when the opportunity happens, you’ve already lost it. Conferences operate the same way. The person who sits in the front row and asks a sharp question is the person the speaker approaches after the session. The person in the back row has to fight through a crowd to make that same connection.

Phase Two, Step Two: Volunteer one specific operational insight in every conversation—don’t ask questions exclusively. Most networking conversations at conferences follow a predictable pattern: introductions, role descriptions, then a series of questions hoping the other person will say something useful. That structure positions you as an information seeker, not a peer contributor. Flip the dynamic by offering one concrete operational insight early in the conversation: “We just finished migrating our data warehouse to Snowflake last quarter—one thing that surprised us was the performance hit we took on semi-structured JSON queries until we restructured our staging tables. Are you seeing the same pattern?”

This approach does two things simultaneously. First, it demonstrates you have hands-on technical credibility—you’re not speaking in abstractions. Second, it gives the other person a concrete anchor point to respond to, which makes the conversation feel like an exchange rather than an interview. Senior leaders value peers who can trade insights, not juniors who can only absorb them. Even if you’re early in your career, you have operational exposure to specific problems that executives three levels above you do not see daily. Surfacing those insights positions you as someone worth staying connected to.

Phase Two, Step Three: Host a micro-meetup on Day 2. This is the step that surprises people most because it feels audacious. You’re not a conference organizer—why would you host anything? The answer: because nobody else is doing it, and because small, focused gatherings create disproportionate relationship value. On the evening of Day 1, send a message to 6–8 people you’ve met during the day: “A few of us are grabbing coffee at 7:30 a.m. tomorrow in the lobby to talk about real-world data governance challenges before the keynote. You’re welcome to join—no agenda, just practitioners comparing notes.”

According to research from Locally Optimistic, informal peer gatherings at conferences generate longer-lasting professional relationships than official networking events because they’re self-selected around shared operational challenges rather than vendor-sponsored abstractions. You don’t need permission to host this. You don’t need a formal structure. You just need to create a time and place for people to gather, then show up and facilitate a conversation. The people who attend will remember you as someone who created value during the conference, not just someone who consumed it. That reputation compounds—when one of those attendees later moves to a VP role and needs to hire a senior PM, they’ll remember the person who brought people together, not the person who handed them a business card in a vendor booth.

The Post-Event Relationship Leverage System: Turning Conversations Into Career Capital

Most conference ROI dies in the two weeks after the event. People return to work, get buried in email, and never follow up on the conversations they had. The connections they made decay into LinkedIn profiles they vaguely recognize but can’t remember why they connected. Executive presence isn’t built by having conversations—it’s built by systematically converting those conversations into ongoing relationships that compound over time.

Phase Three, Step One: Send a follow-up message within 48 hours that includes one specific artifact from your conversation. Don’t send a generic “great to meet you” message. Send a message that proves you were paying attention and that you’re offering value, not just seeking it: “It was great talking with you about query optimization at Summit. You mentioned you were struggling with identifying which queries were consuming the most compute—I ran into the same issue last quarter. I’m attaching a SQL script we use to surface the top 20 cost-driving queries in our Snowflake environment. Let me know if it’s useful.”

The artifact doesn’t have to be elaborate—it can be a script, a slide deck, a link to an article, or even a one-paragraph summary of a framework you use. The key is specificity and utility. You’re demonstrating that you listened, that you have operational tools worth sharing, and that you’re willing to offer value before asking for anything in return. According to Pragmatic Institute‘s 2023 research on professional relationship building, professionals who offer a tangible artifact in their first follow-up are 4.1x more likely to receive a substantive response compared to those who send generic pleasantries.

Phase Three, Step Two: Publish a post-event synthesis article within one week. Write a 600-word piece synthesizing the most important operational insights you gathered at the conference—not a session recap, but a practitioner’s take on the gap between what vendors are pitching and what actually works in production environments. Include at least one contrarian claim: “Three vendors at Summit pitched real-time data pipelines as the default architecture. But for 70% of analytics use cases, near-real-time batch processing is faster to build, cheaper to run, and easier to debug—real-time is over-prescribed.”

Tag the speakers and executives you met in the post. Not in a “look who I met” way, but in a “Jane Smith from [Company] made a point in her session that aligns with this observation” way. This creates a second touchpoint with people you connected with during the event, and it positions you as someone who synthesizes information and takes a stance—not just someone who attends and absorbs. Publishing this piece also creates a searchable artifact that future conference attendees will find when they research who else is thinking critically about the space. David Ohnstad has built his professional brand this way—not by waiting for opportunities to appear, but by creating artifacts that make him discoverable to people solving similar problems. You can read more of his approach at David Ohnstad Minnesota.

Phase Three, Step Three: Schedule a 90-day check-in with your three most valuable new connections. Don’t let the relationship fade. Three months after the conference, send a brief update message to the people you most want to stay connected with: “It’s been three months since we talked at Summit—wanted to share an update on the data governance project we discussed. We implemented the policy enforcement framework you mentioned, and we’re seeing 60% faster compliance review cycles. Would love to hear how your rollout is progressing.” Then propose a 20-minute call to compare notes.

This step separates casual conference acquaintances from genuine professional relationships. Most people connect at conferences and never speak again. The ones who build lasting career capital are the ones who create reasons to re-engage every few months—not by asking for favors, but by continuing to exchange operational insights. Over time, those relationships turn into references, referrals, collaboration opportunities, and job offers. Executive presence isn’t built in a single conference—it’s built through repeated, value-driven interactions that compound over years.

Why This Framework Challenges the “Just Be Yourself” Career Advice

The conventional wisdom around networking and career development is that authenticity and effort are enough—show up, be genuine, work hard, and good things will happen. That advice isn’t wrong, but it’s incomplete. Executive presence is not a passive outcome of good work—it’s an active process of strategic positioning, consistent signaling, and deliberate relationship building. Most professionals fail to advance at the rate their competence deserves because they treat visibility as something that happens to them rather than something they engineer.

Stop waiting for your manager to nominate you for high-visibility projects. Stop hoping someone at a conference will recognize your potential. Start building the artifacts, asking the questions, and hosting the conversations that make your expertise undeniable. According to McKinsey’s 2024 research on leadership development, professionals who proactively create visibility touchpoints—publishing insights, facilitating peer conversations, and maintaining structured follow-up systems—advance to senior leadership roles 2.7 years faster on average than equally competent peers who rely solely on performance reviews and manager advocacy.

The reason most people resist this framework is that it feels effortful and slightly uncomfortable. Publishing a position piece before a conference exposes you to criticism. Asking a non-obvious question in a crowded session risks looking foolish if you misunderstood something. Hosting a micro-meetup requires you to put yourself out there and risk nobody showing up. Those risks are real—but they’re also why this approach works. Everyone else is avoiding the same discomfort, which means the people who push through it differentiate themselves immediately. Executive presence isn’t built by doing what everyone else does—it’s built by doing what most people avoid because it requires intentional effort and visible accountability.

A Case Study in Conference Leverage: How One Director Built Executive Visibility in Six Months

David Ohnstad watched a director of analytics at a mid-sized SaaS company execute this framework almost perfectly in 2024. She was attending Snowflake Summit for the first time, and her goal was clear: she wanted to be recognized as a thought leader in data governance within the Snowflake ecosystem, which would position her for a VP-level role within the next 18 months. Most people in her position would have attended sessions, taken notes, and posted a few LinkedIn updates. She did something different.

Three weeks before Summit, she published a detailed post on LinkedIn outlining her team’s approach to policy enforcement in multi-tenant data environments. It wasn’t a hot take or a viral-bait post—it was a practitioner’s walkthrough of a real operational challenge with specific metrics showing what worked and what didn’t. The post generated modest engagement—about 40 likes and a handful of comments—but more importantly, it created a searchable artifact that positioned her as someone solving real problems, not just someone attending a conference. Two senior leaders at data-focused companies reached out before the event even started to set up coffee meetings. She didn’t have to chase them—they came to her because she made herself discoverable.

During the event, she attended six sessions but spent twice as much time in hallway conversations and vendor booths. She asked one carefully prepared question in each session—questions that revealed she was already implementing the concepts being discussed and dealing with edge cases. After one session on governance automation, the speaker approached her to continue the conversation. That speaker happened to be a VP at a company that was hiring a senior director of data platform six months later. The relationship started because she sat in the second row and asked a question that demonstrated operational depth, not because she handed someone a business card.

On Day 2, she hosted a 7:00 a.m. coffee meetup in the hotel lobby for people interested in governance tooling. She invited eight people—six showed up. The conversation lasted 45 minutes and covered real implementation challenges that weren’t being addressed in any official conference session. Two of the people who attended that coffee became references when she applied for VP roles later that year. One of them hired her as a consultant to help their team implement a similar governance framework, which generated an additional $25,000 in side income. The entire meetup required 30 minutes of setup and no budget—just the willingness to create a space for people to gather.

Within 48 hours of returning from Summit, she sent follow-up messages to the twelve most valuable connections she made. Each message included a specific artifact: a script, a framework document, or a link to a relevant article. She wasn’t asking for anything—she was offering value. Eight of those twelve people responded, and four of them scheduled follow-up calls within the next month. Ninety days later, she sent brief updates to her top five connections, which led to two consulting opportunities and one introduction to a board member at a fast-growing data platform company. Eighteen months after that conference, she was hired as VP of Data Products at a Series B startup—a role she learned about through one of the people she met at that 7:00 a.m. coffee meetup.

The outcome wasn’t luck. It was the result of a deliberate, repeatable framework applied consistently across three phases: pre-event positioning, on-site signaling, and post-event leverage. Most people attend conferences and hope something good happens. She attended with a system designed to make good outcomes inevitable.

Frequently Asked Questions

Two Immediate Actions and One Uncomfortable Question

If you’re attending a major tech conference in the next 90 days, execute two steps this week. First, write and publish a 400-word position piece on one operational challenge you’re currently solving—post it on LinkedIn or your professional site with the conference hashtag. Second, identify three executives speaking at the event and send each a specific, research-backed message proposing a 15-minute conversation during the event. Don’t wait until you arrive—build visibility before you walk through the doors.

For leaders sending team members to conferences, implement one structural change: require every attendee to schedule three executive-level conversations before the event and publish a post-event synthesis article within one week of returning. Then measure career advancement outcomes over the next 12 months. According to Gartner’s 2023 talent development research, organizations that tie conference attendance to structured visibility-building outcomes see 34% higher internal promotion rates among attendees compared to those that treat conferences as passive learning experiences. If you’re spending $200,000 annually sending people to conferences, you should be able to point to specific promotions, partnerships, or thought leadership outcomes that resulted from that investment.

Here’s the uncomfortable question for practitioners: when you attended your last major industry conference, how many of the connections you made are still actively contributing to your career six months later? If the answer is zero or one, you attended a conference but you didn’t build executive presence. You consumed content but you didn’t create visibility. The next conference you attend, apply this framework and measure the difference. Executive presence isn’t an innate trait—it’s a system you build, test, and refine the same way you’d build any other high-value professional skill.

For more on building career systems that compound over time, explore Leadership, Mentorship & Career Development frameworks that bridge strategic thinking with operational execution.

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 Executive Presence at Tech Conferences: Maximize Career ROI 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.