HOW I WORK

When I approach a project for a client, I ask a lot of questions so I can get to know their business and their customers' needs. It's important that I keep discovering answers to the most basic unanswered questions even when I've learned a lot more.
​

EXPECTATIONS

My job is to understand customer expectations and to work independently or as part of a team to meet them in the simplest, most compelling way.

LIMITATIONS

Creating and advocating for solutions that can be realized in the real world requires me to understand and respect technology, budget, or structural limitations, and to limit their impact.

GOALS

Defined goals of the project ensure that guiding principles are in place when decisions are made, and that the project is measurable once it's been delivered.

best practices

I spend a good amount of time making sure I am able to deliver design using the most effective process tools and collaboration techniques available.

research

I conduct audits of comparable products and experiences as well as user research whenever possible. Analytics and qualitative feedback fuel iteration and optimization. 

DOCUMENTATION

GENEROSITY

No design exists unless it is documented consumably for current and future vendors and development teams and is sharable so others can adopt its components.

It's important to me to support the enduring success of a design project by making myself highly available to anyone after the project is complete.

mechanics

I use the mechanics that are best suited to the audience and the phase of the project. These frequently include: 

• Audits, user research, and design discovery  See an example of a small user research project
• Whiteboard like hell with SMEs, stakeholders, and developers, and create discussion documents, sketches wireframes, flow diagrams and sitemaps See a few examples
  
  (Often I begin by sharing nascent thoughts and concepts in whatever expedient way makes sense, even quick ascii-type conceptual wireframing in email to a colleague. Sketching then helps me tease through which patterns and components can come into play and what states they may need to reflect. It ain't pretty and gets less so when during meetings/discussions they get layered with markup capturing "Oh yeah!" thinking.)
  ​
• ​Create and contribute to collaborative wikis See an example of a wiki I seeded that has become an important maintained touchstone for the company

deliverables

I deliver whatever is most appropriate for efficient implementation, including:

• ​Hi-fi interactive prototypes, composite walkthroughs, and screen images
• Source and production files: I use Figma and Adobe CC as authoring/design tools. My output can be opened and commented upon by stakeholders in any corporate role, thus obviating version control problems/duplicate files and creating scalable source files that can be output for any need.
  • Icon and brand assets are typically .svg files so they look great on any device or resolution
• Complete identity systems