Design Process As a Philosophy
More of a philosophy than a process, all actions take root in thoughts first, otherwise they just become a checklist for the sake of checklist without any intensions.
1
Collaboratively construct the world from outsider's POV
Identify Building Blocks
actors, tools, physical environment, digital environment, and their relationship with each other
Nature of interconnections
relationships between each of the elements as cause and effect.
System Goals
this could be business goals
To Identify Root Causes
of pain & inefficiencies both for system and people
Using Tools
Stakeholder mapping/analysis, stakeholder interviews, contextual inquiry, sociogram, process mapping etc.
2
Change POV to That of People / Users / Actors
Cultural & Social Aspects
that people embody as a result of their lived experiences
Physical & Cognitive Abilities
for solutions and systems to be designed for
Respective Effect
on their goals, motivation, abilities, sensibilities etc
Their Goal & Role
in the current context
Sources of Pain Points
direct and indirect ripple effects on users / people from element(s) of the system
3
Locate Leverage Points & Deliberate Course of Intervention..
Structural Interventions
they could be small or big change in processes, connections etc outside digital systems,
UX Interventions
Solving for digital experience, tasks etc or backend interventions
Back-end Interventions
These could be simply data related issues that might be initially flagged as UX issues or affect UX.
4
Design / Re-design Solutions or Recommend Other Interventions..
for most efficient flows - task, processes etc
by minimising physiological and cognitive cost borne by people/users.
in return minimising all sorts of delays that introduce inefficiencies
5
While Continuously Testing Efficiency of Solutions as a Function of..
a
cost to cognition
b
delays