Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

To close the strategy-execution gap, Vasion uses 'Missions of Aspirational Performance' (MAPs), an OKR-like system. Leadership sets a high-level mission, and teams collaboratively build supporting missions from the bottom up. This model ensures alignment while empowering the organization's collective intelligence to adapt and execute.

Related Insights

To ensure alignment, Matt Spielman's coaching process starts with senior leadership. When managing partners define and share their "game plans," their goals become the organization's goals. This creates a natural cascading effect, as direct reports align their own objectives to support the firm's primary mission.

The "memo is the strategy" isn't just a CEO problem. Teams often run the same play, creating roadmaps, OKRs, or retro actions that serve as announcements of intent but lack any real execution or follow-through mechanism.

Instead of cascading goals directly from a vision, use "Strategic Themes." These are broad, directional choices (e.g., "Leverage critical partnerships") that act as guardrails, or "lanes on the interstate," guiding how teams set their specific, measurable objectives.

The Decision Stack is a framework answering five key questions to align an organization: 1. Where are we going? 2. How will we get there? 3. What's important now? 4. What actions will we take? 5. How do we choose? This connects high-level vision to daily execution.

To solve misalignment, the company cascaded OKRs from the CEO down. Critically, regional leaders were made 'champions' of key pillars like user acquisition. This gave them ownership and a direct voice in shaping product solutions, turning potentially adversarial relationships into collaborative partnerships.

Most business struggles stem from a misaligned or forgotten North Star Metric (NSM). A successful framework aligns the entire company by ensuring all OKRs ladder up to a single, durable NSM, with KPIs serving as health checks for those OKRs. This creates a clear hierarchy for decision-making and resource allocation, preventing strategic drift.

Instead of relying solely on one-on-one meetings for alignment, PMs should craft a compelling vision. This vision motivates engineers by showing how even small, tactical tasks contribute to a larger, exciting goal. It drives alignment, clarity, and motivation more effectively than just a roadmap.

Bottom-up goal setting often leads to conservative, achievable targets. Instead, leaders should set an ambitious top-down goal with a resource constraint ('achieve X with Y people'). This forces teams to rethink their approach, not just incrementally improve.

Companies often focus too much on the "what" (KPIs, OKRs, tasks). The real strategy lies in deeply understanding and articulating the "why"—the reason the company exists. When the team grasps this fundamental purpose, they don't need detailed instructions on what to do; they can derive the correct actions themselves, enabling effective, autonomous execution.

Don't build a feature roadmap and then write OKRs to justify it. Instead, start with the outcome you want to achieve (e.g., "move metric X to Y"). This frames all features as experiments designed to hit that goal, empowering teams to kill features that don't deliver value.