Tag: Flow

Simplifying a sprawling, heavily customized Jira estate so the tooling reinforces a product operating model instead of substituting for it.

How a public e-commerce company re-cut domain-based teams around a single platform front door and cut roadmap WIP by more than half.

Deming's challenge to managers to establish and curate the process needed to achieve desired outcomes.

Software delivery has gone through three distinct eras with each one collapsing the distance between having an idea and learning whether it works.

Distribute quarterly planning across the quarter so the PI event becomes where the plan gets published, not where it gets made.

Strategies for coordinating work across team and portfolio boundaries in a product operating model.

The lived experience of shipping code in your organization, reduced to three measurable dimensions: feedback loops, cognitive load, and flow state.

The speed at which value moves from idea to delivered outcome with minimal friction.

Keep The Lights On and Business As Usual work -- what it is, how much is healthy, and what to do when the ratio gets out of control.

Thinking deliberately about how you work, surfacing habitual patterns and tacit knowledge so you can identify opportunities for improvement or automation.

Use the least process necessary to enable coordination and learning.

John Shook found the way to change culture is to change behavior, through doing. When we do this, mindsets and new cultural norms will emerge much quicker.

Develop small, vertical slices of work that create incremental value and generate feedback to validate your assumptions.

Configuring a tool to enforce discipline a team hasn't built. The tool becomes the process, and the process stops improving.

The end-to-end sequence of activities that delivers value from customer need to customer outcome.

AI feels like noise, not leverage — scattered usage, no compounding.

How perpetual urgency sabotages strategic work and what to do about it.

A 12-week planning system that distributes quarterly planning across the quarter, turning the PI event from where the plan gets made into where the plan gets published.

A practical guide to implementing flow metrics, starting with essential measurements and building sophistication as teams mature.

A reframe on estimation that focuses on what really matters in planning.

How platform capabilities show up on roadmaps — three outcome types and five patterns for keeping platform and business-portfolio roadmaps connected, visible, and accountable.

Daniel Vacanti's guide to using flow metrics and probabilistic forecasting in agile teams.

W. Edwards Deming's foundational work on systems thinking, quality management, and continuous improvement.

Mik Kersten's framework for connecting software delivery flow to business outcomes using the Flow Framework.

Donald Reinertsen's comprehensive treatment of flow-based product development economics.

Taiichi Ohno's foundational work on lean manufacturing, kanban, and the practice of going to the gemba.

A pattern where a stream-aligned team owns both its frontend and a use-case-specific backend, decoupling from shared platforms.

A visualization that makes WIP buildup, bottlenecks, and throughput trends visible at a glance.

Improving work processes through intentional observation and feedback sharing.

Opinionated but optional platform defaults that make the right thing the easy thing for stream-aligned teams.

Explicit constraints on the number of work items allowed in each stage of a workflow, grounded in Little's Law.

A hands-on workshop that moves teams from casual AI usage to intentional workflow engineering, teaching prompt engineering, context engineering, and compounding setup design using real work.