Insights Topic
Your organization is a product. Apply continuous discovery, feedback loops, and iterative design to your operating model.
On this page:
Your operating model is not a static blueprint; it is a living product. Below, I explore how to design internal capabilities using product thinking and scale changes evolutionarily.
Start here · Cornerstone read
Treating internal capabilities, transformation initiatives, and the organization itself with the same discipline that great product teams apply to their products.
Read the full articleWe often build internal tools and processes via mandates, forcing employees to use them regardless of friction. Treating the organization as a product means recognizing that internal capabilities—such as developer platforms, HR processes, or AI prompt libraries—have actual users.
These internal products must be discovered and designed based on the real needs of your employees. We should track adoption metrics, gather qualitative feedback, and iterate, rather than relying on top-down enforcement.
Big-bang organizational restructurings are disruptive and frequently trigger a massive immune response that causes the company to backslide into old habits. True organizational agility requires scaling change evolutionarily.
We utilize targeted, 90-day flow experiments to resolve constraints sequentially. By proving value in one area without disrupting the entire system, we build momentum and organic pull for broader organizational transformation.
It means applying product management principles—continuous user research, MVP testing, metric tracking, and iterative releases—to the design and operation of your internal teams, policies, and operating models.
Measure it like a SaaS product: track active users (DAU/MAU), task completion success rates, cycle-time reductions for teams using the capability, and qualitative NPS scores from internal developers.
Insights Database
Browse the complete archive of articles and case studies related to developing your company like a product.
Why I pivoted from Scaling with Agility to Scaling AI from Activity to Impact. Agility is the "Powered by Intel" inside the AI-Native organization, and the lessons from scaling it are what turn AI ambition into impact.
The best time to solve a feature adoption problem is before development. Talk about the user's project, look for real pull, and don't build on polite interest.
AI initiatives die in the proof-of-concept stage when run as fixed-scope projects. Clemens Adolphs and I unpack why AI work needs real product discovery.
Scattering AI initiatives without finding your bottleneck wastes effort. A Theory of Constraints lens helps you aim GenAI at the right problem first.
Adopting AI, Agile, or OKRs out of FOMO usually ends in JOMO. Five questions that tie any initiative to your most expensive problems first.
Cross-org initiatives are strategic bets, and project management keeps failing them. What product-oriented ownership looks like instead.
Internal tool adoption stalls for the same reason products fail: nobody understood the user. What IT and Ops leaders can borrow from product management.
Every tech wave has a cart-before-the-horse phase. What product-led AI looks like instead: start with customer outcomes and explore problems before solutions.
Organizational traction and portfolio agility are the same path. Chase either one and you end up managing a portfolio of investments with flow-based thinking.
How to decide when and where agile methods are worth the overhead — and when a simpler approach beats a formal framework.
GenAI is a classic VUCA challenge — high uncertainty, fast-moving, multi-disciplinary. How to steer AI investments without drowning in the hype.
Most meetings fail for lack of clear purpose, preparation, and a way to decide. How to design meetings people actually want to attend.
The PMF survey asks how you would feel if the product went away. Ask it internally and you learn how fit for purpose your ways of working really are.
AARRR (Acquisition, Activation, Retention, Referral, Revenue) applied to change: treat agile adoption as a product and measure it with the same rigor.
A practical fable for running business initiatives as evidence-based bets using a right-to-left Think/Build/Ship/Tweak flow.
Jason Fried, Dharmesh Shah, and other founders on treating the organization as a product — discovered and improved with the same discipline as what you sell.
The next frontier for agility is the company itself, not just delivery teams — lost innovation, slow time-to-market, and leadership bottlenecks.