Identify our goals. Prototype a possible solution. Evaluate its effectiveness.

Wash, rinse, repeat.

I’ve spent decades demystifying design and user experience—the terms, the process, the deliverables—for new practitioners, software developers, hiring managers, clients, tech recruiters, business partners, you name it. Often, these folks are confused by industry jargon and befuddled by beautifully elaborate process models that look impressive but require industry experience to understand.

To cut through the noise—and get us closer to doing the work—I’ve adopted a simple yet scalable framework of “Identify > Prototype > Evaluate” when educating or working with these various audiences. In this simplicity lies a ton of complexity—and a bunch of work that needs to get done. But that’s the really exciting part! I’d rather focus on doing and explaining the work itself than justifying an overcomplicated process model.

With a simple framework in place, my approach is medium-agnostic, context-sensitive, and rooted in visualizations.

Any effective process starts with a bit of research to enable effective question asking and active listening to the answers. I am curious about the people and the context in which the problem exists or seeks to be solved, and am skilled at  externalizing and visualizing complex systems and nebulous ideas while we work.  I get especially energaized when I can help to unlock teams through a quick sketch, collaborative Miro board, or system map. Often, this visibility makes for richer discussions, identifies misalignments quickly, and gets teams excited about what’s next. 

Throughout the process, I strive to practice compassionate honesty—mindfully asking tough questions or addressing challenging matters—with peers, reports, stakeholders, and anyone invested in the work. Collaboration isn’t always comfortable, but I believe that discomfort is where we grow and accomplish big things!