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 involved with all these teams will need to be involved to coordinate. How fortunate we are to have mechanisms in place to coordinate all of this. (Think PI/Quarterly planning, JIRA Align, Product Owners with their different backlogs, Solution Trains, and a complex network of cascaded OKRs) Sound familiar? This is what I call the coordination tax—that hidden cost of trying to innovate across organizational boundaries that weren't designed for the outcomes you're pursuing. Read How to Evade Coordination Tax By Organizing Around Outcomes for a case study of how we evaded coordination tax when developing the Gillette Exfoliating Razor and a set of suggested coordination tax evasion ideas for you to consider. |
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.
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...
“GenAI can enable cheaper, faster experimentation / discovery (it compresses the truth curve by reducing the cost of pretotyping style product experimentation techniques)” (Yours truly, in yesterday’s insight on how AI can really help you build better products) This statement seems to have hit a nerve with reader Elad, who is product leader at a cybersecurity scaleup: “Not everyone can do this… New companies, sure. Larger, established companies are knee-deep in mountains of code,...
While the jury is out on the extent of impact GenAI and vibe coding will have on building mission-critical enterprise products… Here are some thoughts on how AI can help turn the product flywheel: Use GenAI to enable fuller-stack engineers and reduce tech debt This will enable you to organize smaller product/outcome oriented teams These teams can achieve more with fewer dependencies and streamlined processes (even without looking at opportunities to streamline product dev processes themselves...