Get your free personalized podcast brief

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

When setting large goals, like an annual ARR target, don't just assign the number. Provide a rubric of expectations and require your team to develop and present their execution plan. This fosters ownership and allows for course correction before work begins.

Related Insights

To get buy-in for "uncomfortable" stretch goals, use data and transparency. Show the team their historical performance, then pinpoint specific missed opportunities from the previous year. Frame the new goal as achievable by simply capitalizing on those previously unexploited areas.

Instead of setting rigid goals, the OHL framework defines objectives as puzzles. Teams then form hypotheses on how to solve them and are measured on their learnings through a cycle of three questions: "How well did it work?", "What did you learn?", and "What will you try next?"

Effective leadership involves more than setting a high-level goal. Leaders must also share the strategic hypotheses, or "bets," on *how* the company will achieve that goal. This missing middle layer is crucial for guiding teams and ensuring their proposals are strategically relevant.

A common leadership mistake is setting impossible goals. This often stems from a flawed planning process that doesn't clearly distinguish between aspirational "stretch" goals and committed "planned" goals. Without this clarity, especially in financial planning, teams are set up for failure.

Instead of focusing on a large quota, leaders should reverse engineer it. Calculate the number of deals needed based on win rate and average contract value, then break that down into weekly opportunity creation goals for reps.

Contrary to keeping targets private to avoid failure, entrepreneur Mark Laurie advocates for announcing huge goals publicly. This act forces the team to reverse-engineer a plan, aligns stakeholders on the ultimate prize, and increases the probability of achievement—making the risk of public failure worth it.

Simply stating a goal, like "increase sales by 15%," is insufficient for autonomous teams. Leaders must also articulate the "anti-vision"—the negative outcomes to avoid, such as eroding customer experience. This rich context provides clearer guardrails and a more nuanced understanding of the mission.

To avoid incrementalism when setting goals, organizations should use zero-based budgeting to define 'moonshots' from scratch. Additionally, internal innovation tournaments empower teams to set their own goals; passionate employees often set more ambitious targets for themselves than leadership would have imposed from the top down.

Leaders often assume goal alignment. A simple exercise is to ask each team member to articulate the project's goal in their own words. The resulting variety in answers immediately highlights where alignment is needed before work begins, preventing wasted effort on divergent paths.

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.