We scan new podcasts and send you the top 5 insights daily.
In complex domains with unknown unknowns, executive teams should avoid isolated strategy sessions. When strategy and technology roadmaps are co-created with senior engineers, technical teams understand project rationale upfront. This brings an estimated 20% to 30% of unofficial 'skunk work' pet projects into the open, allows the organization to fail fast on weak ideas, and empowers tactical staff to pivot independently when projects inevitably fail.
Organizations that adopt purely agile methodologies often iterate indefinitely without a coherent strategic direction, while purely linear processes prevent learning. The most effective innovation systems pair linear governance with go-kill decision gates at the macro strategic level—allowing executive leadership to plan long-term capital investments—with iterative, short learning loops (such as Design Thinking or Scrum) at the operational execution layer.
Instead of a traditional product roadmap, give engineers ownership of a broad "problem space." This high-agency model pushes them to get "forward deployed" with customers, uncover real needs, and build solutions directly. This ensures product development is tied to actual pain points and fosters a strong sense of ownership.
Don't make high-stakes decisions in a silo. Involve stakeholders throughout the discovery and analysis process. Having finance review your P&L or sales weigh in on customer pain builds shared context and turns your recommendation from 'your bet' into 'our bet.'
The idea of setting a yearly vision is outdated when new, compelling prototypes can be generated weekly. At Shopify, strategy now emerges organically as a powerful prototype gets shared, generates excitement, and a team forms around it, shifting priorities in near real-time.
When facing a major technical unknown or skill gap, don't just push forward. Give the engineering team a dedicated timebox, like a full sprint, to research, prototype, and recommend a path forward. This empowers the team, improves the solution, and provides clear data for build-vs-buy decisions.
Lacking deep technical expertise forces product leaders to trust their engineering counterparts as experts and ask fundamental "why" questions. This approach fosters partnership and pushes engineers to think from first principles, connecting their work to the broader business strategy.
Leaders, even visionaries like Steve Jobs, can be wrong. Tony Fadell ran secret 'skunk works' projects for features Jobs initially rejected, such as iPod on Windows. This prepared the company to quickly capitalize on these ideas once the need became undeniable.
To balance short-term needs and long-term goals, create accountable teams that own a component of the overall vision. These teams must control the entire product lifecycle—from discovery to implementation—so they can make intelligent near-term trade-offs without losing sight of the strategic goal.
To avoid becoming an "ivory tower" manager, engineering leaders should use side projects as a playground for new technologies. This practice ensures they understand the limitations of new tools like AI and can provide credible, concrete, hands-on guidance to their teams.
The traditional division between C-suite strategists and employee executors is obsolete. With rapidly shortening business cycles, strategy must be treated as a dynamic, iterative process developed collaboratively with the people on the ground executing it.