Articles

Writing on Product Velocity

Updates

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

  • Product Velocity emerges from interactions across four stakeholder domains

    Product Velocity emerges from interactions across four stakeholder domains

    Velocity Loop Explained #2. Product Velocity emerges from interactions across four stakeholder domains, including academics and innovators.

    Product Velocity is not a framework owned by a single discipline. It emerges from interactions between practitioners, educators, innovation leaders, and tool vendors. Each group sees different bottlenecks, uses different language, and operates on different time horizons. Progress depends on information flowing between them.

    This resource network exists to make those interactions more visible and more useful.

    (more…)

  • Why MIT Press Said Yes to Product Velocity

    Writing Product Velocity #8. Why Product Velocity resonated strongly enough to become an MIT Press book project.

    It’s final: I signed the contract and will write the book with MIT Press. I am very excited.

  • What I Looked for in a Publisher

    Writing Product Velocity #7. Choosing a publisher for Product Velocity required alignment on vision and long-term positioning.

    It took a while to get through at MIT Press, but once I did, I felt right at home. Today, I had a zoom conversation with Andrew Kinney. I really feel that we have a good fit here.

  • 2nd offer from Apress

    Excited to get another offer, this time from Apress. It’s nice to have options.

    Excited to get another offer, this time from Apress. It’s nice to have options.

  • Why I Renamed Lean Systems to Product Velocity

    Writing Product Velocity #5. Why Product Velocity communicates the problem and solution more clearly than Lean Systems.

    Conversations and publisher feedback made me rething the book title: Product Velocity is a great title. It clearly states the “What” of the book. Further, practitioners can see this as the answer to the “Why” question in their head.

    The subtitle “Build Physical Products at Software Speed” should make immediately clear what this is about.

    And: The .org domain was still available. Time to migrate.

  • How I Chose a Publisher for Product Velocity

    Writing Product Velocity #4. Publishing Product Velocity required balancing reputation, collaboration, and intellectual control.

    Nobody gets rich publishing a technical book, and that’s not my goal here. Now that I have the first offer, I started to outline criteria that are important to me. These include:

    • Continuous dialog and support during the writing process
    • A publisher willing to engage in co-marketing
    • Control over the book IP, especially regarding AI training
    • Publisher’s reputation
    • Watermarked ebook (instead of DRM)

  • The First Signal That Product Velocity Resonated

    Writing Product Velocity #3. The first publisher offer validated the relevance of Product Velocity as a market problem.

    I got the first book offer, from CRC Press (Taylor & Francis Group). This is an encouraging milestone, as it shows that there is interest in the market.

  • Sending the Product Velocity Proposal to MIT Press

    MIT Press was first on my list. Is it wise to send the proposal to them first, without trying some 2nd choice publishers? Too late it’s out.

    MIT Press was first on my list. Is it wise to send the proposal to them first, without trying some 2nd choice publishers? Too late it’s out.

  • The Hardest Part Was Defining the Problem Clearly

    Writing Product Velocity #1. Defining the core problem behind slow product development was harder than writing the proposal itself.

    Okay… I think I have a decent proposal. I’ll start by sending it to a small number of select publishers, for testing.

  • Why I Started Product Velocity

    Product Velocity began as an attempt to understand how physical products can evolve at software speed.

    The idea was brewing for a long time: Should I write a book about building hardware like software? Especially after doing literature research, the answer was yes: While Joe Justice publicly talked about this over 10 years ago, there is surprisingly little literature about what he calls “Extreme Hardware”.