Most of our work follows this trajectory, though we tend to adjust as we see fit, since no two engagements are alike.


Every project begins with a conversation that’s designed to help our founder understand your situation and discern whether we can help.

If everything looks and sounds good, then she’ll ask for some documentation on your product and organization (e.g. mission statement, press release, pitch deck) along with a run-through of your technology.

Deep Dive

Once the project begins, we’ll dive deep beneath the surface to figure out what’s really preventing you from achieving your ideal user experience. We’ll dissect your work on user empathy. We’ll peep inside your toolkits and design libraries. We may even examine your workflow.

Exactly what we look at and how we look at it depends on where you are and what you’ve got.


Now that we understand what’s happening for you, we’ll make our recommendations and help you devise an open and adaptable plan to overcome those obstacles.

We typically solve problems and seize opportunities in a agile fashion. However, if you’re new to user-centered design, agile development or lean startup methodologies, or if your leadership is leery of such approaches, then we may recommend a different strategy altogether.


Ideal: Design and learn. Build and learn. Repeat.

Reality: It depends on what we come up with during the planning stage.

Retro and Repeat*

Those who work with us for more than a month will repeat one or more of the steps until the work is complete. Before the loop-back, we’ll analyze the results and adjust for the next work cycle.

That’s not to say that we won’t adapt along the way. We will. However, we incorporate a larger feedback mechanism to ensure that your overarching plan and its moving parts are up to speed.

Some of our clients have handled this step (and future design cycles) on their own. That might be the case for you.

*Those who participate in our 1-Day UX Intensive handle the last two steps (Execute, Retro and Repeat) on their own.