top of page

How Can Executives Lead Innovation Without Losing Momentum?

How Can Executives Lead Innovation Without Losing Momentum?

Murat Peksavaş – Senior Innovation Management Consultant

Talking about Apple, Airbnb, or Uber is easy; building an innovation engine inside your company is not. Half-day workshops create vocabulary, yet real progress requires executive mentorship (ongoing guidance), experience (applied practice), and decision rights (authority to unblock work). Leaders must learn how to evaluate projects, allocate evidence-based budgets, design an innovation strategy, and use open innovation and crowdsourcing responsibly. When executives receive targeted coaching, adopt stage-gated governance, and model measured risk-taking, employee energy translates into outcomes.

Why are workshops not enough for leadership—what is the missing capability?


Workshops transfer concepts (design thinking, MVPs, customer discovery), however they rarely change how leaders decide. Innovation lives in meetings where budgets, risks, and priorities are set; if those meetings follow a traditional finance cadence, discovery is squeezed out. Executives need a parallel operating mode for uncertainty—short cycles, hypothesis tracking, and go/kill rules. Mentorship fills this gap by turning abstract tools into leadership behaviors: asking for evidence (not volume of slides), approving time-boxed pilots (not big-bang business cases), and protecting teams during learning. Without this behavioral shift, managers learn to talk about innovation, yet default to legacy decision logic when it matters.


What should leaders actually learn—beyond name-dropping success stories?


Three skills change the game. First, project evaluation under uncertainty: judge ideas by problem evidence, time-to-first-signal, and reversible cost, rather than forecasted five-year revenue. Second, portfolio design: balance incremental, adjacent, and radical bets with explicit proportions and staged funding (explore, prototype, PoC, limited rollout, scale). Third, open innovation practice: use crowdsourcing, startup collaboration, and expert networks with clear scopes, IP rules, and data-privacy safeguards. Companies like GE, Starbucks, and Shell have used crowdsourcing to surface solutions precisely because internal structures had blind spots, whereas blocking such mechanisms (out of fear) quietly limits discovery and speed.


Why do executives also need decision rights—not only knowledge?


Knowledge without authority frustrates everyone. Innovation leaders must be empowered to fast-track pilots (procurement exceptions, vendor onboarding), grant access to sites and data, and release micro-budgets when predefined criteria are met. A standing Innovation Steering Committee (product, operations, finance, legal, IT) with a 10-day decision service level removes calendar friction. Publish the pathway: intake form, security checklist, success metrics, go/kill thresholds, and the adoption plan if a pilot works. Mentorship helps leaders use these rights wisely (coaching teams, sequencing risks), yet the rights themselves are non-negotiable if you want results rather than theater.


How is executive mentorship different from coaching for intrapreneurs?


Intrapreneurs need problem framing, customer interviews, and experiment design. Executives need evaluation discipline and organizational unblocking. Mentor sessions for leaders should simulate decision meetings: review a one-page experiment charter, test the strength of assumptions, price the risk, and practice the language of “approve, pivot, or stop.” Include case drills on open innovation (when to crowdsource, how to protect confidentiality), and on governance (how to reward “smart kills,” how to measure Return on Failure—learning gained per euro spent). When leaders rehearse these moves, they stop asking for perfect certainty and start funding small, reversible bets that move the portfolio forward.


What governance model helps executives steer innovation credibly?


Adopt a stage-gated, evidence-based model. Before the year starts, set portfolio targets (for example, 50% incremental, 40% adjacent, 10% radical). Require every proposal to specify the problem evidence, the riskiest assumption, the test design (6–12 weeks), and the success threshold tied to an operational metric (cycle time, defects, safety, carbon). Commit that if a pilot hits the threshold, scale funding unlocks automatically (budget code, vendor number, training plan). Report monthly on learning and conversion (not only spend). This model keeps executives honest—evidence moves money—and gives teams confidence that good data will be rewarded.


How should open innovation be used without triggering corporate antibodies?


Define why and where before how. Use crowdsourcing for well-scoped challenges (materials, process quality, data labeling, sustainability), publish rules up front (IP ownership, confidentiality), and run evaluation with external reviewers plus internal operators. For startup collaboration, standardize NDAs, PoC contracts, data-sharing, and site Safety-IT checks, then run small, concurrent pilots rather than one giant proof. Communicate outcomes—wins and “smart kills”—so the organization learns. When executives model transparent, well-governed openness, resistance drops, because people see risk controls and tangible value.


How do you build the mentorship supply when seasoned mentors are scarce?


Start with a mentor-of-mentors model. Contract a few senior experts to train internal leaders as mentors, using real proposals and decision rehearsals. Create a shared toolkit (experiment charters, evaluation rubrics, RoF close-out forms), record exemplar sessions, and pair each executive with a rotating set of teams for one quarter. Measure mentors on cycle-time reduction, clarity of decisions, and portfolio conversion, not on hours logged. Over two to three cohorts, you will have a sustainable bench of executive mentors who speak the same language as intrapreneurs and evaluators.


What is the practical equation for leadership in innovation?


Innovation Success = Education + Experience + Decision Rights. Education provides vocabulary and tools; experience converts tools into judgment through live reps; decision rights allow leaders to deploy judgment at speed (and in context). Remove any term and the product collapses—workshops alone produce fluent talk, experience without rights produces frustration, rights without judgment produce risk. Executives who accept this equation, seek mentorship, and institutionalize governance create environments where teams learn quickly, spend wisely, and scale what works.


FAQ


Can we run innovation reviews like finance reviews? Not effectively. Innovation needs short cycles, hypothesis tracking, and pre-agreed go/kill rules.

What if we lack external mentors? Train internal leaders using real cases and a common toolkit; measure them by decision quality and cycle time.

Will openness expose weaknesses to competitors? Good governance limits disclosure while expanding solution space; the risk of not learning is usually higher.


Key Takeaways


  • Workshops teach concepts; mentorship converts concepts into executive decision behaviors.

  • Give innovation leaders real authority (procurement exceptions, data/site access, micro-budgets) with clear guardrails.

  • Evaluate projects for evidence and time-to-signal, not only forecasted revenue, then fund in stages.

  • Use open innovation with explicit scopes, IP rules, and privacy safeguards; communicate outcomes transparently.

  • Grow a bench of executive mentors through a mentor-of-mentors program and shared toolkits.


References


  • Harvard Business Review — Executive decision-making for innovation and governance cases.

  • MIT Sloan Management Review — Experimentation portfolios, product operating models, and decision speed.

  • OECD — Innovation capability building and measurement guidance for firms.

  • European Commission — SME innovation policy, open innovation, and data-governance resources.

  • McKinsey — Stage-gated funding and scaling patterns for digital and operations transformations.

bottom of page