Insights Topic
Your organization is a product. Apply continuous discovery, feedback loops, and iterative design to your operating model.
On this page:
This page covers my frameworks for organizational design. Below, I’ll share how to treat internal capabilities as products, how to build organizational feedback loops, and how to scale evolutionary change.
Internal product management means treating operating models, prompts, platforms, and processes as products that must be discovered, designed, and continuously improved based on feedback from internal users.
Many companies roll out change as a top-down mandate: a new tool or process is pushed down, and adoption is poor. This fails because the team did not discover the internal user needs.
When we treat capabilities as products, we research internal bottlenecks, design solutions that solve those specific pains, and track actual user adoption. We build telemetry and iterate based on usage data, creating a pull-based change system.
Evolutionary change avoids disruptive reorgs by starting with what you do now, defining clear intents, and launching lightweight, evidence-based experiments to continuously improve flow.
Big-bang restructurings trigger organizational immune responses: teams get anxious, work slows down, and legacy power structures push back. The change backslides as soon as the consultants leave.
We use evolutionary design. We map the current value stream, identify the current constraint, and design a 90-day experiment to resolve that specific pain point. By solving problems sequentially, we build capability and momentum without disruption.
Crucial for internal change agents to understand how to design interventions that are supportive rather than threatening, facilitating pull-based adoption.
The definitive text on the evolutionary approach to organizational design: starting with what you do now, respecting current roles, and enabling change through flow economics.
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.
AI initiatives die in the proof-of-concept stage when they are run as fixed-scope projects. Clemens Adolphs and I unpack why AI work needs real product discovery, internal market validation, and outcome-based steering instead of a gantt chart with the labels filed off.
Why scattering AI initiatives without identifying bottlenecks wastes effort — and how a Theory of Constraints lens helps you aim GenAI at the right problems before you automate.
Adopting AI (or Agile, or OKRs) out of FOMO almost always turns into JOMO — the Joy of Missing Out. A five-question framework for connecting any initiative to your most expensive problems before you commit.
Cross-org initiatives are strategic bets, but traditional project management consistently fails them. What product-oriented initiative ownership looks like — and why it applies even to non-product transformations.
Internal tool adoption stalls for the same reason products fail: building without understanding the user. What IT and Ops leaders can borrow from product management to actually move the needle on adoption.
Every major tech wave has a cart-before-the-horse phase. What product-led AI looks like instead: starting with customer outcomes, embedding cross-functional ownership, and exploring problems before solutions.
Organizational traction and portfolio agility are the same path. Why leaders pursuing either goal inevitably arrive at the need to manage a portfolio of investments with flow-based thinking.
A practical framework for deciding when and where agile methods are worth the overhead — and when simplified approaches are more effective than formal agile frameworks.
GenAI transformation is a classic VUCA challenge — high uncertainty, fast-moving, multi-disciplinary. How organizations can use agile operating principles to navigate AI investments without drowning in hype.
Most meetings fail because they lack clear purpose, preparation, and decision-making structure. How to design meetings that people actually want to attend — because they produce real outcomes.
The Product-Market Fit survey asks "how would you feel if you could no longer use this product?" The same question, applied internally, reveals how fit for purpose your ways of working really are.
AARRR (Acquisition, Activation, Retention, Referral, Revenue) applied to change management: treating agile adoption as a product and measuring it with the same rigor as customer-facing products.
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 itself as a product — continuously discovered, iterated, and improved with the same discipline as your customer-facing products.
The next frontier for agility is applying it to the company itself — not just delivery teams. A look at the scaling challenges (lost innovation, slow time-to-market, leadership bottlenecks) that call for treating the company as a product.