HOW I THINK

01 — Start with the problem

Before choosing a technology, I want to understand what is actually preventing people from achieving the outcome they need.

02 — Understand the system

I look beyond the immediate problem: the people, workflows, information, dependencies, constraints and unintended consequences surrounding it.

03 — Listen to the people doing the work

The person experiencing the problem often understands something the system designer doesn't. Their experience is essential to designing something people will actually use.

04 — Bring the right people together

Complex problems rarely belong to one department. I connect the people who understand different parts of the system and help create a shared understanding of the problem.

05 — Build what is needed

Sometimes the answer is technology. Sometimes it is a process change, a policy, a communication pathway, or a combination of all of them.

06 — Make the change possible

A solution isn't successful because it was built. It is successful when people can use it, trust it, and incorporate it into the way they work.

07 — Never lose sight of the human outcome

Behind every system is a person affected by it.

That is the reason I build.