In 2018, a paying passenger was dragged off of a United flight by law enforcement officers because United needed the seat to reposition crew members so that they’d be in place to start the next day. The passenger was injured in the incident, which was captured and shared on social media, creating a public relations […]
Katherine’s Latest Post
Start Here: Rapid Learning Cycles 101
To accelerate innovation, we have to push decisions later.
This is the most challenging idea within the Rapid Learning Cycles framework — the one that generates the most raised eyebrows — and the most essential concept to embrace if you want to accelerate innovation.
It seems to go against everything we think we know about how to get things done fast…
My controller, Shivaun is on a quest this month to find a new accounting system for us. We need to change systems because our current provider experienced a major product failure. They needed to replace some obsolete technology in their software to make them compatible with the latest Mac operating system — and they worked on that project for years. But ultimately, they were forced to admit that they simply could not get the new version out the door.
Sometimes people come to Rapid Learning Cycles because they have either experienced such a catastrophic failure or they see that they are at risk of one. Yet some innovation thought leaders think we should embrace failure to achieve speed. Why can Rapid Learning Cycles promise faster innovation — and fewer failures?
Agile for Physical Products
In this series so far, I’ve discussed the principles of Agile, and how they express fundamental truths about good process management that apply broadly: cut batch sizes, work in a cadence, focus on delivering value early, strive for technical excellence.
I’ve also discussed some things that hardware teams need to do differently in order to act in accordance with a principle that manifests differently in hardware than in software.
This week, I’ll share five things that are completely missing from Agile Software Development — but essential for Agile Hardware development.
I’ve started working on my next book, When Agile Gets Physical: How to Adapt Agile Principles to Accelerate Hardware Development, with my long-time colleague, Kathy Iberle. Today, the information available is mostly written by Agile software experts — and it shows. They mostly take a “Just Use Agile” approach that does not account for the real differences between hardware development and software development.