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.

Instead of saving up for major announcements, treat every feature release as a launch. This "Always Be Launching" philosophy creates constant excitement, surfaces surprising user favorites, and provides continuous feedback loops. Even a 10-minute demo can generate massive engagement.

Walmart reframed planning around desired outcomes, not feature lists. This gave engineering teams the flexibility to innovate on solutions, increasing engagement and productivity, despite initial resistance from leadership accustomed to feature-based roadmaps.

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.

Facing a critical frontend rewrite that ballooned from 6 to 24 months, Canva couldn't ship new features. To maintain morale during this "dark tunnel," they gamified the process with a physical game board and rubber duckies representing components, making the grueling work bonding and even partly fun.

The pivot from Arc to Dia was also a cultural and technical reset. The Browser Company gave their team a "blank page," allowing engineers to build a new, faster architecture and designers to rethink the experience. This chance to fix old problems and pursue new ideas was key to getting team buy-in.

Launches are powerful internal tools. The 'artificial importance' of a launch date creates a deadline that forces product and engineering to ship while getting sales and marketing educated and excited, preventing endless iteration cycles.

Instead of relying solely on internal timelines, create public-facing product events. This establishes an unmissable, external deadline that serves as a powerful forcing function, ensuring teams are aligned and deliver high-quality work on time.

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.