I work with product teams to help them design and build more successful products. Unfortunately, I usually have bad news for them.
These teams are looking for the secret to creating great products. Like most things in life, there is no secret and there is no shortcut. Successful products don’t emerge from clever feature ideas or sexy screen designs. They come from teams that understand their stakeholders, customers, and users. They come from teams that know how users work today and empathize with their challenges. They come from teams that can imagine a better way for these people to work in the future using the software and technology they’re building. And they come from teams that test their ideas aggressively. Teams like this eventually create incredible products.
Why am I telling you all this? If you’ve picked up Tony and Jarrod’s book, you don’t plan on designing and building a product; you’re looking for a technology. But it turns out that the process of selecting technology for your organization is a lot like designing it yourself. It’s not going to work for you to assemble a wish list of features from within your organization and then select the vendor that says they have more of them than the next guy. You know that the best products aren’t necessarily the ones with the most features. Instead, the best approach is to understand the people in your organization, their work and challenges, and imagine a better future for them using the technology you select. That’s going to take some time and effort.
In this book, Tony and Jarrod lay out a straightforward way of selecting technology successfully. Brace yourself—these authors don’t mince words. They directly expose the traps most organizations fall into, as well as giving straightforward ways to avoid them. This book describes a process from beginning to end in a way that even I can understand.
By working the way Tony and Jarrod suggest, you’ll help your organization make one of its best investments ever. And, what’s more, you’ll know it when you see it, because you and your team will have already envisioned that better way to work, as well as tested it before committing. You should be proud. Well, you will be.
Oh, and the best thing is that you won’t actually have to build the whole solution yourself. And that’s a good thing.
Founder, Patton & Associates
Author, User Story Mapping