Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
Unfortunately, it’s not as simple as talking to customers every week. That’s a good start. But we also need to consider the rest of our continuous-discovery definition: At a minimum, weekly touchpoints with customers By the team building the product Where they conduct small research activities In pursuit of a desired outcome I’ve met many teams who are good at talking to customers. But they forget that the purpose of these customer touchpoints is to conduct research in pursuit of a desired outcome. Those last two lines of the definition are critical. We aren’t doing research for research’s sake. We are doing research so that we can serve our customers in a way that creates value for our business.
Continuous Discovery Habits
Teresa Torres
In his article “Searching for the Center of Design,” service design expert Jess McMullin defines value-centered design as follows: Value-centered design starts a story about an ideal interaction between an individual and an organization and the benefits each realizes from that interaction.
Mapping Experiences
James Kalbach
Outcome-based road maps work because they help create a multiteam implementation of mission command. They are a way of articulating, in a cascading manner, the key elements we need when we direct the work of teams: The strategic intent (“We want to increase the organization’s impact by a factor of 10”) The strategic constraints (“We will do this by creating an online matching service that must be live by X date”) The definition of success (“The service will match parties at X rate”) When implemented well, outcome-based road maps help organizations create alignment, which is critical to making mission command work.
Sense and Respond
Jeff Gothelf, Josh Seiden
...catch up on these, and many more highlights
Readwise