We scan new podcasts and send you the top 5 insights daily.
When the COVID-19 pandemic halted their first-in-human trial for two years, the team pivoted from clinical activities to internal improvements. They focused on development, process optimization, and strengthening other company functions. This strategy of reallocating resources to what can be controlled maintains progress and ensures better preparation for when external blockers are removed.
When facing major life changes like a new child or a demanding job, the solution isn't to "hustle harder." Instead, successful founders intentionally pause large, demanding projects (like a new SaaS) and switch to smaller, "step one" businesses or maintenance mode. This preserves momentum without causing burnout.
Deciding to abandon a profitable product for a nascent one was difficult. The COVID-19 pandemic forced the decision by killing the old product's sales pipeline while accelerating demand for the new one's remote access capabilities, making the pivot clear and necessary overnight.
When Trello's PMM team shrank from ten members to two, the crisis forced them to build robust systems for tracking projects, assessing bandwidth, and prioritizing tasks. This extreme constraint became the necessary catalyst for developing a more strategic and organized workflow out of sheer survival.
Instead of over-analyzing and philosophizing about process improvements, simply force the team to increase its cadence and ship faster. This discomfort forces quicker, more natural problem-solving, causing many underlying inefficiencies to self-correct without needing a formal change initiative.
To solve the 'push vs. pivot' dilemma, use a simple framework. You should only pivot if a fundamental belief upon which you built the business has been proven false by the market. If your assumptions are still valid but progress is just slower or harder than you hoped, the correct action is to keep pushing forward.
Focusing the entire company on one critical path item creates "second grade soccer" syndrome, where everyone swarms one problem while others are neglected. Instead, deploy small, independent "SWAT teams" to attack blockers, allowing the rest of the organization to maintain progress on parallel tracks.
Instead of arguing for more time, product leaders should get stakeholder buy-in on a standardized decision-making process. The depth and rigor of each step can then be adjusted based on available time, from a two-day workshop to an eight-month study, without skipping agreed-upon stages.
To prevent post-sprint momentum loss, create structural "bookends" of support. An executive sponsor provides strategic alignment and resources from the top, while embedded innovation champions on the team provide the day-to-day passion and skills to navigate obstacles from below.
The purpose of setting impossibly aggressive deadlines isn't just to move faster. It is a strategic tool to force a team to identify the true critical path. By asking 'what prevents us from doing this in 6 months instead of 36?' you reveal the few real constraints that must be attacked or eliminated.
To avoid post-launch stalls, operate two parallel tracks. The 'delivery track' executes the current roadmap, while a separate 'discovery track' simultaneously researches and plans for the next 18-24 months. This ensures a continuous flow of validated ideas into the pipeline.