When we wrote #leanux we wanted to help product design and development teams collaborate more effectively and ultimately build better products for their customers. The overwhelming feedback from readers has been (no surprise) that they want to work this way. However...
What we didn't expect was the amount of teams out there telling us things like "my boss won't let me work this way" or "my company would never let us talk to customers." Hearing this again and again gave us the sense that there was (at least) another conversation to be had. So...
We wrote another book - #senseandrespond . That book took the conversation up a level to leaders and makes the case that to stay competitive in today's business world you have to build continuous learning loops with your customers. I believe many orgs heard this message but...
...what they actually did was go out and "hire" #agile in the hopes that this would bring them that learning. And it should have. But instead of optimizing this new way of working to build insight, they optimized it to ship features. So, now, the feedback we're hearing is...
...we're "doing agile" but the speed isn't there and the customers don't love the products any more than they did when we were "doing waterfall." What's going on? The answer...
...lies in the fact that while the rituals and cadences have changed, the incentives have not. Without the incentive to change teams started using new vocabulary but left their goals the same -- ship features. The learning loop was never implemented. If you find yourself...
in this situation, here's what you can do. First read this article: medium.com/neo-innovation… It's old but it's short and starts to get at ways to move your #agile process forward. Then, if you're inspired and want to learn more...
join me @AgileLeanIrl on April 25 for a 1-day workshop on getting your #agile process unstuck, increasing the amount of learning your team generates and changing the incentives for getting that work done. Tix here: eventbrite.com/e/agile-lean-i…
