TBM 333: Lean Graph Theory

The note argues that organizations are best understood through three overlapping models: path, DAG, and network. Different company situations make different models more useful, and Lean ideas matter most when they are matched to the current context and to where the main friction sits.

Reading notes

#

• The text says that Lean ideas are often applied selectively, and this shows up both in fast-growing companies and in larger, more structured companies.
• It proposes three models for understanding an organization as a sociotechnical system: path graph, directed acyclic graph and network graph.
• The path model serves linear processes, sequential flows, pipelines, assembly lines, schedules, ticket resolution and journeys with fixed stages.
• The DAG serves approval flows, change propagation, goal decomposition, workforce management and projects with constraints.
• The network serves supply chains, knowledge graphs, collaboration between teams, feedback loops, emergent behavior, resilience and cyclical dependencies.
• The text states that humans, organizations and product development are complex, so the three models appear at the same time and at different scales.
• In the product launch example, leadership, teams, GTM and platform services use the three models together, with different degrees of overlap.
• The hypothetical company grew quickly between 2022 and 2025, accumulated organizational debt, prioritized revenue over the platform ecosystem and became misaligned with the strategy of the moment.
• In 2025, pressure to deliver large cross-functional projects increases, while team autonomy matters less and collaboration across areas becomes a central requirement.
• The text says that discussions about Lean in product work are usually more useful in large companies, with complex dependencies and misaligned structure, where the goal is to stabilize and deliver value.
• In companies with independent teams, part of Lean works locally, but scaling that to the whole organization can seem heavy and overly centralized.
• The author reports difficulty getting fast-growing companies to adopt portfolio-level kanban, even when it would have helped.
• The conclusion is that Lean has useful ideas at any level, but they need to be used carefully, according to the context and the current weight of the problem.
• The text ends by saying that a product organization with platform and enablement support tends to move more toward network and DAG models.