“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 ….
What this also means is that in the absence of the need for iterative collaborative work, no matter how streamlined and effective your agile process is, it might not be worth the time Read the full When is Agile worth the Overhead article to explore some example contexts where Agile might or might not be applicable. It’s all about Intent and ContextHere’s the thing. Applying a cookie cutter approach for everything might seem more straightforward and more consistent, but requires a frustrating uphill battle to conquer a hill not worth conquering. In my experience, aligning on the intent and then focusing on relevant contexts creates much healthier, gratifying, and impactful change. PS I also find this framing when navigating the human/people aspects of another capital A adoption. |
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.
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...
When Vered and I got married, my father-in-law gave me a very nice watch as a wedding gift. I didn’t wear a watch that often at the time. I wore the watch, but it didn’t transform me. It provided the service of telling the time, but even back in 2004, we had phones that had clocks. And I was and am pretty punctual so didn’t need that transformation. (And when you’re in Engineering/IT leadership, nobody cares about the watch you wear… at least in Israel… ) Don’t tell Eli, but that watch spent...