We scan new podcasts and send you the top 5 insights daily.
When a project tanks, the headcount is at risk. A savvy manager immediately moves those engineers to a promising project. Then, they report to leadership, "Project A failed, but good news: I've moved the team to Project B, which is now moving twice as fast." This prevents headcount clawbacks by creating new value.
To solve resource overload, don't compare all projects directly. Categorize them into "buckets" (e.g., bold innovations vs. minor fixes). Then, rank and kill the lowest-performing projects *within* each bucket to reallocate resources effectively and protect bolder initiatives.
To combat the natural reluctance to admit failure and to foster decisiveness, some innovative companies offer bonuses to employees who kill their own underperforming projects. This practice creates a culture of honesty and overcomes the personal attachment that often keeps bad ideas alive far too long.
Surprising your manager with a major failure is one of the worst mistakes you can make. You must proactively communicate risks as soon as they arise. This gives your leader time to manage expectations up the chain and prevents them from being blindsided.
Treat your product and engineering teams as stewards of the company's most precious capital: their time. A capital allocation framework forces leadership to ask if this "investment" is being spent on the initiatives with the highest strategic return, not just fulfilling requests.
To accelerate strategic initiatives, companies must extract them from daily operations and staff them with dedicated, full-time talent. Assigning people part-time is a recipe for failure, as context switching and operational duties inevitably derail progress. The best people should work on the most important projects.
To combat the natural reluctance to abandon a failing project, leaders should actively incentivize objectivity. One effective, counter-intuitive tactic is to offer a bonus to employees who kill their own ideas, fostering a culture where resources are not wasted on projects that are not working.
The common mantra is 'hire slow, fire fast.' A more effective approach is to 'hire fast, fire faster, and promote fastest.' Immediately recognizing and rewarding top performers with promotions and compensation is more crucial for long-term retention and team quality than simply removing underperformers.
By centralizing oversight at the hub, the model prevents teams from becoming emotionally attached to a single asset. This structure allows leadership to make objective, data-driven decisions to terminate unpromising programs without it being seen as a personal or career failure for the team involved.
Instead of letting go of underperforming employees, adopt the philosophy that their failure is your failure first as a manager. This forces you to re-evaluate if you've provided the right goals, context, and support, which can often unlock their potential.
To justify pausing feature work at TripAdvisor, the product team got buy-in by clearly framing the long-term problem it would solve. They also appeased engineering by reallocating their time to tackle technical debt that was directly related to the future North Star, ensuring valuable progress was still being made.