For the fun of it – the next time a big consultancy gives a big presentation to your organization, pitching a POM – ask them how they recommend managing this transformation. And see if what they describe looks more like a Project or a Product. For example – Will they measure vanity metrics or product metrics? It just goes to show how tempting these vanity metrics are. How hard it is to talk about the real WHY (especially when the WHY is because a big consultancy firm sold us on it…) How frightening it is to look at the actual outcomes of our initiatives. Here’s the thing – As change agents driving a product operating model, we are asking people to start being accountable for outcomes. To avoid specifying a book of work and share the purpose, be open to a conversation where we look at the efficacy of delivering what they asked for. We should show some leadership by example. Here’s our initiative. Here’s the outcome we believe it will achieve. Here are the leading indicators we will track along the way. Here are our “kill criteria” for it. If we can use a product operating model to develop our product operating model, we stand a chance of actually getting the organization to use it. Both because it will be fit for purpose and because we will have a great case study to share. Check out the Product-oriented Portfolio Agility Trail Map for deeper insights on how to leverage product orientation to improve product orientation. Read How To Manage a Product Transformation Project 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.
Product development concepts come in handy every time you're developing something. Whether that thing is software, product, or even a point of view. The first sentence in this email is a point of view (POV). I want this point of view to be effective - I want people to understand what I mean, be intrigued by it, take action, and hopefully see me as a thought leader / expert in this space that they'll want to follow / listen to more. It took me a while to develop this point of view. To carve a...
Context is King You’ve probably encountered this term in the context of AI. You won’t get far with AI, even with amazing prompting techniques, if AI doesn’t have the right context. Many people focus on the Data aspect of context – what’s in our CRM, in our collaboration tools, in our ERP, in any of our vertical systems. Another interesting aspect is the intent – what are we trying to achieve? What is our strategy? What problems are we focused on? Who are the players? Some of that information...
Hey Reader, Before you fix teams, fix the system they operate in. Most organizations focus their improvement efforts at the team, program, or product level while maintaining the same organizational operating system—how they make decisions, fund work, and measure success. These teams might be using the latest and greatest processes (Agile, Product Model, Lean Startup, take your pick) but they still need to manage countless dependencies. The funding and GTM processes are still following classic...