Articles

Writing on Product Velocity

Updates

2 x per month. New articles, webinars, videos, trainings. Unsubscribe any time.

  • The Velocity Loop Solves a Communication Problem and Is Free to Use

    The Velocity Loop Solves a Communication Problem and Is Free to Use

    Velocity Loop Explained #4. The Velocity Loop is free to use, even commercially. Use it and other free resources to achieve Product Velocity.

    Many organizations struggle to talk about product development problems coherently. Business talks about priorities. Engineering talks about architecture. Delivery teams talk about automation and toolchains. Everyone describes a different bottleneck.

    The Velocity Loop creates a shared map.

    A systems engineer can point to verification debt while management discusses slow decision making. A delivery team can explain release friction while architects discuss unstable interfaces. The loop shows these are connected parts of the same system.

    The Velocity Loop is available free under CC BY, including commercial use. It can be used in presentations, workshops, internal training or consulting material with attribution.

    (more…)
  • Why Product Velocity Needs a Shared Language

    Why Product Velocity Needs a Shared Language

    Velocity Loop Explained #3. Why organizations need a shared language to identify where product development slows down.

    The talk from ReConf is now online. It presents Product Velocity as a model to analyze how products move from idea to operation. The focus is on flow across the full system.

    The recording is in German. Auto-generated English subtitles are available.

    (more…)
  • Why Nobody Owns the Whole System

    Why Nobody Owns the Whole System

    System Stewardship #1. Why long-term product outcomes depend on stewardship across organizational boundaries.

    Language shapes behavior, it steers attention, priorities, and decisions. The choice of system stewardship reflects the work of guiding a socio-technical system through uncertainty, growth, trade-offs, and change over time.

    Systems Stewardship is one of the four practices of the Velocity Loop, next to Business, Engineering and Delivery.

    Stewardship signals responsibility without assuming full control. Products, architectures, and operations evolve within markets, organizations, and ecosystems that no team controls. Stewardship focuses on sensing context, making informed interventions, and protecting long-term system health while delivering near-term outcomes.

    (more…)
  • The Equation Behind Fast Product Development

    The Equation Behind Fast Product Development

    Product Velocity Principles #1. Product development is the management of economic exposure under uncertainty.

    We often consider product development as the production of features, but in reality is the management of economic exposure under uncertainty. The formula that expresses this relationship consists of just four variables.

    (more…)
  • 3 Organizational Patterns That Quietly Slow Development

    3 Organizational Patterns That Quietly Slow Development

    Why Companies Stay Slow #3. Organizational anti-patterns silently increase coordination cost and delay feedback.

    Sometimes it is more helpful to know what not to do. Anti-patterns turn that idea into a diagnostic habit: they describe the failure shapes that show up repeatedly when organizational mechanisms do not match system demands. In practice, the value of anti-patterns is that they compress years of experience into a quick set of checks we can apply while the work is still malleable.

    (more…)
  • What the First 30 Days of Product Velocity Actually Look Like

    What the First 30 Days of Product Velocity Actually Look Like

    A practical starting point for identifying and reducing flow bottlenecks in product development.

    Over the next three months there will be several opportunities to participate in a Product Velocity workshop. The workshop is the entry point for gaining speed. It does not promise instant transformation, but initiates a 30-day improvement cycle that teams can run themselves or with external support.

    Participants leave with a workbook that guides the process. The workbook allows the work to continue inside the organization after the workshop ends.

    (more…)
  • Why Product Thinking Is No Longer Enough

    Why Product Thinking Is No Longer Enough

    Architecture and Flow #1. Platform strategies reduce coordination cost and accelerate product evolution.

    Many organizations still organize development as a sequence of projects. That is not enough: To survive, you need at least a product mindset. Teams must treat product development as a lifecycle responsibility rather than a temporary effort. But even that is not enough any more: In order to lead, you need a platform strategy. Instead of optimizing individual products, they invest in shared foundations that allow many products to evolve on top of the same architecture.

    (more…)
  • What Writing 74,000 Words Taught Me About Product Velocity

    What Writing 74,000 Words Taught Me About Product Velocity

    Writing Product Velocity #9. What writing the Product Velocity manuscript revealed about engineering, flow, and organizational learning.

    The manuscript for Product Velocity is nearing completion. I am on schedule to meet the March deadline. Current status:

    • 73,789 words
    • 5 parts
    • 26 chapters
    • 16 chapters complete, the remainder partially drafted
    • 10 case studies already published online and referenced from the book

    The manuscript will be submitted to MIT Press at the end of March. Publication is planned for late summer 2027.

    (more…)
  • Architecture Determines How Fast Organizations Learn

    Architecture Determines How Fast Organizations Learn

    Architecture and Flow #2. Architecture controls how quickly economic intent influences engineering decisions.

    We usually describe architecture in technical terms, like modularity or reuse. These are important qualities, but they obscure a deeper function: In complex cyber-physical products, architecture defines how the Business loop and the Engineering loop are structurally coupled. It determines how quickly economic intent can influence technical decisions and how quickly technical reality can correct economic assumptions.

    (more…)
  • The 4 Principles Behind High-Velocity Product Development

    The 4 Principles Behind High-Velocity Product Development

    Product Velocity Principle #2: Four principles explain why some organizations develop products dramatically faster than others.

    Understanding the principles of Product Velocity does not require a transformation program, but conceptual clarity. Once you understand the underlying principles, you begin to see where velocity is unnecessarily constrained, where friction accumulates, and where relatively small structural changes can unlock disproportionate impact. In that sense, understanding the principles often reveals the low-hanging fruit in product development immediately.

    This article explains what these principles are, how they differ from other well-known frameworks, how they relate to the Velocity Loop, and how each of them can be applied in practice.

    (more…)