Making Room for customer centricity
•Download as PPTX, PDF•
1 like•245 views
1. Collaborate iteratively on user stories and design for multiple entry points and a shallow core like search, cart, and separate user categories. 2. Enhance the UI as often as you have actionable hypotheses, validate hypotheses, and automate and scale. 3. Organically bind the UI structure and presentation layer by linking strategy, scope, structure, and design to product thinking layers from user research to design, release, and scalability.
Recommended
Recommended
More Related Content
Viewers also liked
Similar to Making Room for customer centricity
Similar to Making Room for customer centricity (20)
Recently uploaded
Recently uploaded (16)
Making Room for customer centricity
- 1. Hi!
- 2. 5 Key takeaways on customer centrality in UX
- 3. 1 Collaborate / iterate on the story
- 6. 2 Design for multiple entry points And a shallow core.
- 7. Search page Cart page Or separate user categories user facing collateral One step access User In User sees This from the next login
- 8. 3 Enhance the UI as often as you have actionable hypothesis.
- 10. 4 Organically bind the UI structure and the Presentation layer
- 11. strategy scope structure skeleton surface Concrete Abstract Product Thinking Layers: Jesse James Garrett
- 12. 1 User research 2 Product Concept 3 User validation 4 Design Release, Institutionalization & scalability 4 Stages of UX
- 13. Adopt extreme acceptance criteria Subtraction is the best form of addition
- 14. 5 Gauge the need and not the manifest
- 15. Long term passive observations of the end user group. Placement of cultural probes instead of the finished product to gauge its cultural absorption Immersion into user categories, from Etic to the Emic.
- 16. +1 The Kano way
- 17. time User satisfaction wow Done Bare Minimum: Delivering Only the essentials. Stuff customers assume as given Linear Quality Got what I would have asked for Thank you. Who could think of this
Editor's Notes
- Not usability 101 More like an ice breaker
- User accepts that the impact is significant and signs off on the workflow Tech accepts that it is doable or highlights dependencies PM defines the minimal viable product. Easy to kill easy to move fast prototyping.
- Sketch all storyboards and get them tested for early use case validation. Start writing acceptance criteria , part of which becomes the Usability testing scenario. Collaborate with the customer to write these scenarios.
- Traditional information architecture was like push, considered the entire application a monolith. The application can appear in various states to the user as a mobile app does
- When you hypothesize, bucketize/ compartmentalise build a test sandbox and experiment. If validated see how this can be implimented without manually replicating for all instances And then once automation is done try deploying it on the entire application
- A need can be solved in multiple ways. What way should you pick and why. A lot of products get rejected not because they are bad but how they are perceived.
- Long term passive observations of the end user group. Placement of cultural probes instead of the finished product to gauge its cultural absorption Immestion into user categories, from etic to the emic. The consumption mode->deconstructing the consumption mode-> the mind of the power user creates the next generation prod.
- Give the mac: magnetic latch example (not spoken but observed) Stuff consumers assume as given: the bar constantly becomes heigher: good secondary research and feature-feature mapping helps