Elements of Experience Strategy

I’ve been reading through a number of blog posts over the last few weeks that examine the rise of experience architecture, experience strategy and content strategy, as part of the domain of the central domain of user-experience (UX). It’s an interesting discussion, and one that has prompted me to create a new model that covers my thoughts on these aspects of our work at Zen Ex Machina.
Certainly, many site’s experience suffers greatly because their content is poorly written, poorly contructed and poorly managed. As I discussed with a client recently, you can have a beautiful site but if the content is bad, then (even if someone manages to find the site) they won’t return. In my mind, therefore, a good experience strategy falls into two categories:

  1. Interaction design – how the components of information design (site structure and navigation), the user-interface, and the channel of delivery (e.g. mobile site, app, website, etc) come together in a seamless way
  2. Content design – how the governance, workflow and usability of the content serve both the need to communicate and engage as well as deliver information and services that meet the needs of its target users


About the author

Related Posts:

Better together: Agile + Lean UX

How do you make Design Thinking, Lean UX, and Agile work together. Sprint 0? Design Sprints? Upfront design and planning tends to delay the delivery of value, so there must be a better way to use Scrum but also engage in discovery work at the same time without devolving into parallel design work. Integrating design, user research, and experimentation into Sprints is the key.


Who *should* be your Product Owner?

Who should be your (Scrum) Product Owner? I’ve had a number of these conversations recently with small, boutique software development agencies and even design companies


Patterns for breaking down usability and UX re-work

So you’ve just finished usability testing in your Sprint and have a pile of changes for  your agile team to implement. How do you break down the UX changes that are needed to make a product useful, usable and accessible, into smaller, bite-sized User Stories?