Work Radical Owner on Fractal Product Development: An Organizational Framework for Enterprise Product Development

What does fractal product development look like? Product managers and product leaders in most enterprises find themselves drowning in work requests. Between a flood of requests from internal business stakeholders, internal technical leadership, legal and compliance, teams within other functional lines — not to mention external business partners and third-party vendors and service providers — the customer gets lost, and the product managers and product leaders slowly lose a grip on their sanity.

It doesn’t have to be this way. A small but growing number of companies around the world (ranging in size from very small to very large) are pioneering ways of organizing themselves, based on internal market dynamics, that allow them to sense and respond to internal and external customer and market opportunities in a way that both scales to meet demand while also ensuring those making demands are living within their means.

In this talk hosted by Rahul Chaudhari, Work Radical Owner Matt K. Parker will explore these ways of working and organizing that make it possible for a large enterprise to achieve large scale alignment without resorting to draconian, self-defeating, centralized planning and resource allocation.

Join us for new conversations with leading product executives every week. Roll through the highlights of this week’s event below, then head on over to our Events page to see which product leaders will be joining us next week.

Show Notes:

1. Organizations often feel overwhelmed by a constant flood of requests and demands, leading to burnout.
2. This phenomenon is self-inflicted, as the organizational structure incentivizes unlimited requests without consequences.
3. The bakery analogy illustrates how providing free custom cakes can undermine the core pastry business.
4. Similarly, enterprise IT organizations often get pulled away from core product maintenance and innovation to fulfill endless internal requests.
5. The solution is to bring market dynamics within the company, treating product development teams as “businesses within a business.”
6. This involves establishing a “subscription cost” to fund core product and engineering work, and charging for additional requests.
7. Adopting this mindset requires a shift from a bureaucratic to an entrepreneurial paradigm.
8. It empowers product leaders to focus on strategic product innovation, while centralized teams handle core discipline development.
9. Transactional relationships drive accountability, but do not preclude collaboration towards common goals.
10. Handling conflicting priorities from multiple internal stakeholders requires pushing them to resolve tradeoffs themselves.
11. The accounting and funding mechanisms for this model can vary, but the key is aligning authorities and accountabilities.
12. Implementing this change requires courage, as it disrupts the status quo and sense of security.
13. Leaders must be prepared that structural changes alone may not solve all organizational issues.
14. Even individual contributors can adopt a “business within a business” mindset to drive more empowerment in their roles.
15. Reflecting on your own authorities versus accountabilities is a good starting point for experimentation.
16. Raising misalignments with leadership, despite the fear, can be an important first step.
17. Writing a book is a circuitous process of discovery, requiring patience and discipline.
18. Support networks can be invaluable during the challenging aspects of writing.
19. Organizations often find this approach terrifying, due to the scale of change required.
20. Starting small, within one’s own sphere of influence, can be an effective way to drive incremental progress.