Articles

Writing on Product Velocity

Updates

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

  • 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…)
  • Why Most Case Studies Are Useless

    Why Most Case Studies Are Useless

    Product Velocity Case Studies #1. Useful case studies explain mechanisms, trade-offs, and organizational structure.

    Case studies play a strange role in product development. Everyone claims to value them, yet most case studies end up as polished success stories, stripped of the very details that would make them useful.

    With Product Velocity, I want to treat case studies differently.

    (more…)
  • Architecture Decisions That Silently Destroy Velocity

    Architecture Decisions That Silently Destroy Velocity

    Architecture and Flow #3. Architecture determines whether change flows smoothly or stalls in coordination.

    Most organizations experience slowing delivery as a problem of execution. Teams are too slow, integration takes too long, releases slip. The instinctive response is to optimize process, tooling, or staffing. Yet in many cases, velocity was already lost long before design started. It was lost when architecture decisions fixed how change would propagate through the system.

    Architecture does not make products fast or slow by itself. It determines the cost of change. Once boundaries, interfaces, and dependencies are in place, every future decision either flows smoothly or stalls in coordination. This post is anchored in Part III – Systems Architecture and distills a simple but uncomfortable thesis: architecture is an economic decision about delay. Get it wrong, and no amount of process optimization will recover velocity later.

    (more…)
  • What Value Stream Mapping Misses in Product Development

    What Value Stream Mapping Misses in Product Development

    DevOps for Physical Products #1. Product development requires mapping information flow, not only material flow.

    The book Learning to See by Mike Rother and John Shook is the canonical introduction to value stream mapping. Its scope is unapologetically grounded in production and logistics. Physical material moves. Inventory piles up. Lead time can be measured with a stopwatch and a clipboard.

    That focus is a strength, not a limitation. The book teaches a way of seeing systems. Once you understand the logic, the leap from shop floor to product development is smaller than it looks. This post first reviews the book as written. Then it explains how its ideas apply directly to Product Velocity.

    (more…)
  • Why Faster Teams Still Deliver Slowly

    Why Faster Teams Still Deliver Slowly

    Why Companies Stay Slow #2. Local efficiency improvements rarely solve systemic development bottlenecks.

    Traditional product companies face an uncomfortable reality. Competitors emerge seemingly from nowhere with products that are more innovative, faster to market, and often dramatically cheaper. The instinctive response is to look for efficiency gains: faster tools, leaner processes, more automation at the workstation level. Yet organizations that pursue this path often discover that their overall development velocity remains stubbornly unchanged, or even declines.

    This is not a failure of execution. It is a failure of paradigm.

    (more…)
  • The Velocity Loop Explained: A Map for Product Velocity

    The Velocity Loop Explained: A Map for Product Velocity

    Velocity Loop Explained #1. The Velocity Loop is a map to diagnose where queues form and decisions wait in product development.

    Product Velocity is how quickly you learn what matters and turn it into valuable product change.

    Most organizations sense that their product development is slower than it should be. Fewer can point to where the slowdown actually happens. The Velocity Loop gives you a system-level map for doing that. It helps you see:

    • Where intent stalls
    • Where decisions pile up
    • Where feedback gets lost
    • Where unnecessary coordination slows the system

    The Velocity Loop grew out of an observation familiar from software development. DevOps accelerated software delivery by closing the loop between development, deployment, operation, and feedback. Complex physical products need the same basic logic, but they face an additional problem: hardware, software, manufacturing, business decisions, and lifecycle constraints evolve at very different speeds.

    The Velocity Loop adapts closed-loop thinking to that environment.

    It connects four interacting practice loops: Business, System Stewardship, Engineering, and Delivery. Each has its own internal cycle. Together they determine how quickly an organization can learn what matters and turn that learning into useful product change.

    The Velocity Loop is a map, not a process. It does not prescribe a sequence of stages. It shows where work, decisions, and evidence need to flow.

    (more…)
  • Product Velocity Is Now a Competitiveness Problem

    Product Velocity Is Now a Competitiveness Problem

    Why Companies Stay Slow #1. China Speed. Organizations that cannot accelerate product development risk losing competitiveness entirely.

    Speed has long been discussed as an efficiency topic. Shorter lead times. Fewer handovers. Better tools. These conversations miss the point. It is no longer optional to follow a new approach for Product Velocity.

    Product Velocity is not about doing the same work faster. It is about whether organizations remain viable at all.

    (more…)
  • Product Velocity at 4 Events in Spring 2026

    Product Velocity at 4 Events in Spring 2026

    Register now for the Product Velocity half-day workshop on April 27, 2026 in Munich and save 10% with the discount code below.

    Not just ReConf a talk and a workshop on Product Velocity have been accepted. Here are all my spring events:

    If you are working on accelerating hardware or cyber-physical product development, meet me there!

    👉 Register now and get 10% off with Promo code: REC26_SPRE_2523

    (more…)