Video Series Part 2
Organizations employ Agile practices to deliver value.
However, value is often not well defined.
We can clarify the meaning of value by looking at it through a UX lens.
Every product or service has a user experience.
This happens independent of whether UX people worked on the product or not.
A poor experience misses the users’ expectations and needs.
A good experience meets the users’ active needs and expectations.
Active needs are the needs users will tell you about.
A great experience anticipates the users’ latent needs and exceeds their expectations.
Latent needs are the needs users can’t tell you about.
However, they’ll be very happy when you meet them.
Agile focuses the team the smallest time scale activities:
Each level must have their own definition of ‘done’.
Agile teams spend most of their time thinking about the daily WIP and sprints.
Other people worry about epics, releases, and roadmaps.
It’s typically outside the Agile process.
When UX focuses on daily WIP and sprints, it can only be reactive.
This holds the UX teams back.
Forcing them to smallify everything down to fit sprint-sized work periods.
Proactive UX wants to start at the largest end:
It first needs a Vision - 3-5 years
Only then do we think about what the roadmap is.
Epics and sprints roll out from that.
Focusing on the vision first allows us to use Jen Cardello's approach:
Right Problem → Right Solution → Build it Right
In this approach, most UX research needs to focus on Are we solving the right problem?