Bridging users, clients,
and engineers.

When a design is doing its job, all is quiet. And when there is a miss, I’m the first to hear, and the one who has to find a fix.

Sadie Forrester, outdoors in a yellow shirt, smiling at the camera

Working together

As a project manager in life sciences healthtech, confusion isn’t an option. Here’s what wrong looks like: a parent logging a 40-second seizure with a picker that starts at one minute. Zero or one, who knew? Since then, I push in every design session for requirements tight enough that users have the experience we promised.

Sitting between clients and technical teams, I understand the build process as well as the design process. I advocate for users in language that engineers understand, and I clarify design decisions with clients in language they get.

I mostly learned this fluency by asking the right questions. What is the client trying to create and why? What is the technical constraint the engineer just flagged to me? How do I explain it? What solutions do we have?

The questions change, but the reason doesn’t. Asking them runs through more than eight years in product. Earlier in my career, research with medical residents at a global STEM publisher taught me that speed and ease of use mattered more than the print structure we’d inherited.

And now I’m having fun asking the right questions to design and ship iOS apps with AI. Fortunately, the models don’t seem to mind questions.

A simple hello

Home is NYC, where I’ve learned sailing (sort of), Chinese calligraphy (sort of), and child’s pose (to perfection).