the power of outside in thinking: providing a better user experience for both your clients and users
TRANSCRIPT
TAMARA OLSON · FEBRUARY 2015 · MAUI WORDCAMP
Providing a better user experience for both your
clients and end users
THE POWER OF OUTSIDE-IN THINKING
What is outside-in thinking?
INSIDE OUT THINKING
OUTSIDE IN THINKING
YOUR END USERS
Providing a better user experience for
PART ONE
“I already wrote my content and figured
out where everything should go!”
This isn’t just a small client problem.
2. What do your users want to do?
1. What do you want your users to do?
BUSINESS OBJECTIVES
USER OBJECTIVES
How to really see things from your users’ point of view?
Talk to them!
When should you talk to users?
All the time!
User interviews + Product Research Usability Testing (Low-Fidelity) Usability Testing (High-Fidelity)
Feedback Post Launch
How should you talk to users?
Creating personas and outlining objectives/tasks
Some fancy UX terminology
“We’ll be doing a series of cognitive walkthroughs in which we have users using the think-aloud protocol.”
Make it a party! Invite your clients.
And product managers.
And engineers.
Outside in thinking makes you not just a UI designer …
but also a UX designer.
A basic example
Newsletter Signups
BUSINESS VS. USER
Should we make newsletter signup a lightbox or put it in the footer?
(The UI Approach)
Exploring what would bring value to the user (The UX Approach)
Bonus: You can (and should) use outside-in thinking for SEO and keyword research!
YOUR CLIENTS
Providing a better user experience for
PART TWO
END TO END PROCESS
Discovery (Interviews + Analysis) Site Map + UX Brief
Wireframes Visual Designs
[Limited Number of Revisions] Development
Documentation + Client Training
No. No, no, no.
Developer
Designer
Developer
=
=
Some plugins to help you create a customized
bad-ass back-end
User Role Editor
Admin Menu Editor
Advanced Custom Fields
White Label CMS
Erident Custom Login and Dashboard
Documentation
Using Docs allows clients to ask follow up questions, and you
can provide the answers in the documentation:
Structure the doc as questions from your user’s point of view:
Client TrainingCall it “training,” charge for it, and record it.
