On users, magic maps, and the permanent state of change


Here’s your What? Who? Where? When? Why? How? for the week.

WHAT matters the most to my stakeholders?

The magic of the X/Y map is that it clarifies that each alternative might be an option, depending on who you seek to serve. Can you see how this matrix would be totally different if an axis were changed to taste, price, cooking method, or variety?

The magic of the X/Y map | Joe Newbert (Text at Newbert’s Blog)

WHO should I be designing the solution for?

Hundreds of employees are playing a big role behind the scenes to support a stellar customer experience for most businesses. Too often, a bad experience for those enterprise users will reflect badly on the customer experience.  Designing with the customer in mind also means designing with the enterprise user in mind. 

Enterprise User Experience: 5 tips to get it right | Eric Provost (Text at Eric Provost)

WHERE should I use a product roadmap?

A product roadmap is primarily used for communicating your product strategy to people in your organization both inside and outside your product team. Some product people may also use a product roadmap to communicate plans to customers.

Product Roadmap | Kent McDonald (Text at KBP Media)

WHEN will we finish our agile transformation?

Under this new paradigm, change never ends. Agile transformations don’t have a finish line since agility is not an end in itself, but a means to the path of continuous adaptation. Given these truths, a more appropriate question is: “When will we start to be agile?”

Change Behavior to Adopt an Agile Culture | Alfred Maeso Aztarain (Text at Netmind)

WHY do organisations who say they are innovative fail to put their money where their mouth is?

Outsourcing capabilities defined as ‘non-core’ can lead to a reduction in your overall capacity for innovation. It can also lead to workplace dissatisfaction with career development options and can – in your determination to get cost off the books NOW – increase your costs in the medium term.

A Relentless Focus On Efficiency Can Kill Innovation | Paul Taylor (Text at Paul Taylor’s Blog)

HOW do I know how detailed to make the requirements? ?

There’s no single correct answer to this question, and as with many such questions, the correct—but not very satisfactory—answer is: “It depends.” Though I can’t give you a simple answer to this very important question, I can suggest some ways to think about how much detail is appropriate in a given situation.

How Detailed Should Requirements Be? | Karl Wiegers (Text at Medium)

Until next Sunday, keep growing,

— Joe

Chief Training Officer at the Business Change Academy
Editor for Inter-View Report and Podcast Host on OneSixEight FM.

P.S. What’s the most valuable thing you’ve learned in the last month?