When implementing agile portfolio management, leaders’ first—and often most daunting—question is: “Where do we start?” I’ve taught my share of frameworks. In some cases, a comprehensive blueprint or roadmap makes sense. They feel safer to people from traditional project/program management – who ARE often the exact people leading the move towards agile ways of working, especially at the portfolio level. But this sense of safety and predictability is often misplaced. It comes with the baggage of requiring people involved with the change to grasp a lot, plan in depth, and, most importantly, commit to comprehensive change. What often works better is a more straightforward, iterative, evolutionary approach. Think Trail Map rather than a blueprint. It highlights the trails but gives you options for approaching them. What does that look like when pursuing Portfolio-level agility?
By thinking of your portfolio as a living, evolving entity—and using a trail map to guide your early steps—you can gradually build a product‑oriented, agile portfolio without overwhelming your teams or leadership. As a side benefit, leadership will see, learn, and model the behaviors and culture needed for organizational agility… How are you thinking about bringing agility to your company/portfolio? What’s one first trail you can explore? PS The Portfolio Agility Trail Map is an email course where I share what I’ve learned about using this approach. Similarly, the Mastering Organizational Traction Trail Map applies this concept to improve organizational traction for growing companies. Read From Blueprints To Trail Maps On Your Browser Yours, Yuval |
Are You Struggling to Scale Your Organization ? Need agility but dubious of process BS/dogma? I share reflective, pragmatic, principled takes on how to approach scaling your organization leveraging the essence (rather than theater) of product operating models, agile practices and frameworks, and business operating systems such as EOS and OKRs.
Hey Reader, Most days, it feels like mentioning Agile anywhere in your online presence is like the GenAI Emdash. A troll magnet. That makes it harder (maybe even unsafe) to have a real conversation. share nuanced opinions. (And its even less safe to talk about SAFe...) If you're a leader working on improving your organization, should you only listen to people that DON'T talk about Agile? That don't have any SAFe association? Does not mentioning their Agile association immediately mean that...
Picture this: you've a breakthrough strategic initiative tied to one of your company-level goals that impacts 10 teams across two product groups, as well as your GTM organization. These are all busy, overloaded teams. Those same 10 teams are also juggling five other initiatives. And the business-as-usual whirlwind. You pull this work into the backlogs and roadmaps for all these teams. Fractional slices of people across the teams will work on this. Which means it will take a while. Leaders...
Please don’t write your OKRs using AI. OKRs should reflect YOUR strategy. Your choices. Your strong opinion. Your tradeoffs. What you CAN do is use AI to fix your OKRs. Here are some ways you could go about doing that: Collaborate with AI to create a prompt that reflects your perspective on what makes great OKRs Point AI at an OKR expert you’re following and tell it to create a prompt based on that expert’s advice. (Your OKR Hot Seat with that expert) Point AI at a set of OKR experts and ask...