Company leaders who aren’t steeped in how software is designed and built can apply less-than-useful analogies for how software products are built. These analogies tend to highlight predictability, scheduling and cost management… but may not be that useful. This post unpacks a few of them.
Prioritization is hard, and we HOPE that a clear corporate strategy plus well-considered OKRs will get our internal stakeholders to agree on what’s most important: unambiguous #1 and #2 and #3 priorities. That our spreadsheets and analysis will sell everyone on our plan. But that rarely happen…
Everyone wants innovation, especially if we can plan and schedule into each sprint.
But innovation is uncertain. Can we shift the discussion to planning and scheduling and funding of discovery that can (often) lead to innovation?
How do we navigate when our internal stakeholders are misaligned (and they usually are)? It’s important to understand what drives this, see the pattern rather than get angry, and find some tools to keep our products/business moving forward.
Christian Strunk and Alex Dapunt host the Product Bakery podcast. In this episode, I joined them to talk about how Product Leaders work with executives, as well as the topic of negotiating and managing stakeholders and incoming requests. 👉 Listen to the episode on all platforms 🎙 Podcast Minutes/Table of Content 0:28 – Intro 5:45