Founders know that scaling their company to Unicorn status requires extending beyond a singular focus. Launching a product extension. Complementing your established Go-to-market motion. Entering new markets (Different ICP, Geography, etc. ) Often, companies approach these extensions using the same processes they use for their established Products/Markets. They approach a new product opportunity with unwarranted conviction. They go into a new market using established/scaled revenue operations. They implement new motions using "big design up front" They often spread too thin by working on multiple extensions simultaneously. They work on them using the same processes and structures that are tuned for "efficiency" and "margin expansion" That often turns out to be an expensive mistake. Because unlike your established Product/Market, these extensions are often bets. They often require multiple departments to collaborate tightly to find the extension's Product-Market-Motion Fit. They require an experimentation mindset (like the same company had in its pre-PMF days...) Whether it's new leaders brought in to "scale" the company, or the same leaders who were around during the initial leaner days, running a dual operating system - efficient and scrappy side by side - is hard. I find it helpful to be explicit about your portfolio of activities - which can benefit from efficiency-focused operating systems, and need agile scrappiness. Here's one technique that can help you improve organizational traction on these strategic bets:
NOTE: This post is inspired by a Science of Selling Podcast episode on Extending to Multi-Product Selling. Yours, |
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.
Today's email is more about my business than about agility or product itself. Hang in there - there's a connection to product discovevry/validation as a bonus sidenote ... A follower reached out earlier today - "Yuval, When’s the next time you’re teaching a SAFe RTE class?" Here’s the deal. I rarely schedule open enrollment training workshops anymore. Why? The market is crowded with more and more trainers. There’s less demand for certification classes compared to the past The whole dynamics...
Should you focus on mastering organizational traction or on establishing portfolio agility? Let me tell you a secret: In my experience, mastering organization traction involves realizing you have a portfolio of investments you’re managing. So actually the paths converge… The difference is that mastering organizational traction extends beyond the IT/Product world. It intercepts business initiatives before becoming mandates for the technology organization. It also manages non-digital...
“Agile is so great we need to use it for EVERYTHING” “Agile is so much overhead, we stopped using it for ANYTHING” Are you also trying to navigate what to do with Agile? Whether it’s worth the overhead? After years of helping a diverse group of organizations figure out where and how to use agile methods, here's what I've learned... If you want the TL;DR version - Agile has the potential to shine when …. There’s enough risk and uncertainty to justify the overhead of frequent feedback loops....