2. Table of contents
STRATEGY INFORMATION ARCHITECTURE USER FLOW
Affinity Map Card Sorting Task Analysis
MOSCOW Method Site Map Task Flow
Mind Map User Flow
User Journey
Job Story
Goals and Actions
Montenashi Approach
5. AFFINITY DIAGRAM
1. Present the topic or define the problem clearly.
IMPLEMENTING a strategy
2. Write an idea or issue per card.
3. As a team, dort the ideas or issues into categories. (Eliminate duplicate ideas.)
Capture Group Label
6. M.O.S.C.O.W. METHODIMPLEMENTING a strategy
Must have Should have Could have Won’t have
Helps understand priorities and create your MVP..
8. CARD SORTING
1. Write one item per card.
information architecture
2. Organise the cards in groups that relate to each other
3. User testing : Find patterns on how users would expect to find content.
Capture Group Label
11. What is the business objective or action you want the visitor to take
Answering these questions. (Answers will come from your users)
What is the user objective or desire/needs that they want to satisfy
What are all the questions they have
about this task?
What information do they need
to take action?
PREPERATIONuser flows
13. KEYuser flows
Process / Task /Action
EX. Create a postBegin
Yes
Decision
EX.Post on blog?
Explains how a user completes a task
14. STEPS THAT NEED
TO BE COMPLETED
CONSIDERATIONS/
INFLUENCERS
PAINPOINTS EMOTION
TASK ANALYSISuser flows
Helps understand how users perform tasks and achieve their intended goals.
15. USER JOURNEYuser flows
Negative
Timeline
Positive
What questions/ comments
do they have about the task?
What is the desire/
need they want to
satisfy
What questions/ comments
do they have about the task?
What questions/ comments
do they have about the task?
What questions/ comments
do they have about the task?
What questions/ comments
do they have about the task?
PhasePhasePhase
18. PHASE PHASE
TASK ANALYSIS Task
BREAKDOWN
1. What you need to accomplish task
2. What you need to accomplish task
MOSCOW Shade in MOSCOW. Add and remove as you go along the project
TASK ANALYSISuser flows
A functional breakdown of the user’s journey
19. GOALS You want to... (ex. Setup An Account)
ACTIONS
You need to ... (ex. Fill out a form)
You need to .. (ex. Accept T&Cs)
SCREEN
REQUIREMENTS
Screens needs to have .. (ex. T&Cs checkbox)
GOALS & ACTIONSuser flows
Helps breakdown must-have components of each screen.
20. SHITSUARIO
“put the user at ease”
Signal a clear beginning and
end to the interaction
"A good host does not
bother the guest but gives
a well balanced amount
of information,"
FURUMANI
“mutual attainment”
How you might treat a
"regular" versus a newcomer
"Knows when interactions
ought to be formal and
when they ought to be,"
MONTENASHI APPROACHuser flows
Method to improve Human-Machine Interaction, into "principles of attitude":