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.
Collaboratively construct the world from outsider's POV
actors, tools, physical environment, digital environment, and their relationship with each other
relationships between each of the elements as cause and effect.
this could be business goals
of pain & inefficiencies both for system and people
Stakeholder mapping/analysis, stakeholder interviews, contextual inquiry, sociogram, process mapping etc.
Change POV to That of People / Users / Actors
that people embody as a result of their lived experiences
for solutions and systems to be designed for
on their goals, motivation, abilities, sensibilities etc
in the current context
direct and indirect ripple effects on users / people from element(s) of the system
Locate Leverage Points & Deliberate Course of Intervention..
they could be small or big change in processes, connections etc outside digital systems,
Solving for digital experience, tasks etc or backend interventions
These could be simply data related issues that might be initially flagged as UX issues or affect UX.
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
While Continuously Testing Efficiency of Solutions as a Function of..
cost to cognition
delays