Enterprise UX 2015 Recap Lean Engineering and Additional Takeaways
1. Recap: Enterprise UX 2015
Lean Engineering, Lean UX, and Additional Takeaways
Slide material from @billwscott and @jboogie --among other EUX ‘15 speakers
Stephen M. James • @tweetllama • Enterprise UX 2015 Recap
2. Design for throw-away-ability
Change is the norm. Majority of the experience
code is thrown away in a year.
UI = experience layer = experimentation layer
UX is not about delivering documentation. It’s
about delivering experience.
3.
4. Engineering is traditionally about
engineering,
not about learning.
Most organizations have a culture of delivery.
Cultivate a culture of learning.
6. We want great experiences.
More or less features doesn’t matter.
If an engineering teams is not trying to solve the
learning problem, they often see prototyping as
outside of engineering.
Make prototyping a first class member of your tech stack.
7.
8. Give agile a brain.
Agile is a machine. It will crank stuff out.
It could be good stuff or bad stuff.
Story in agile and story in UX are different. At Netflix, the
customer needs weren’t soaked in actual exposure to
customers - that’s where the UX team comes in. The
customer is the brain. We are the voice of the customer.
People -> people’s outcomes -> features [LAST!]
UX runs ahead of the agile team - a few weeks.
Prototype, then transition to production release.
26. Use and know the product you are making.
The whole UX department should be
"product certified" if possible.
Familiarity of products (and not just your own)
will eventually create consistency.
Idea: Create a task script created by each application’s designer
for everyone to complete.