Visual reasoning in practice
Maps, models and prototypes I designed to help teams see relationships, test assumptions and make decisions.
Making the evolution of ideas visible
The proposals had roots in a collaborative workshop and developed further through internal analysis. The genealogy kept those connections visible, so the team could trace how a final concept took shape.
Finding the right plan for each project
Innovation projects shared a process, but the activities varied with the type of change. The matrix turned that variation into a planning reference. Teams could identify their project type, see which activities applied and find the corresponding schedule.
Taking donor feedback into app decisions
The same colour coding carries problem themes from the donation journey into a comparison of proposed app features. It lets the team read donor workshop preferences alongside the problems each feature was intended to address.
From journey evidence to opportunity priorities
This view brings together how often customers experienced each moment, how the service performed and how common individual pain points were. It then groups the resulting opportunities within each moment and across the journey, giving the team a way to compare local problems with recurring themes.
Untangling customers, accounts and addresses
A customer can have several energy accounts and use a single mailing address. Mapping those relationships made it possible to consider contact details at customer, account and property level, which matters when designing how people update them.
Seeing what surrounds a drinking occasion
The weekly grid puts beverage choices in the context of everyday routines. Using the same grid for both views makes it possible to compare what people drank with what they were doing and when.
Keeping the whole account-opening journey in view
The wall map brings customer steps, assisted and unassisted channels, proposed experiences and supporting systems into one shared view. It gave teams a reference for discussing individual changes in the context of the full journey.
Seeing where customer pain points concentrate
A simplified journey view shows where customer pain points concentrate. Counting and grouping issues by stage makes it easier to see where intervention is most needed, without displaying the qualitative detail behind each problem.