
Let's
Talk
FAQ
What’s your typical design process when working on a new project?
My process is flexible, but always grounded in research, collaboration, and clarity. I start by understanding the business context and user needs through stakeholder conversations and research. From there, I move into ideation, prototyping, and iterative testing. I keep communication open throughout, ensuring stakeholders and teams are aligned and involved at every step.
How do you adapt your approach for different teams or industries?
I don’t believe in one-size-fits-all design. I listen first—every team has its own culture, constraints, and pace. Whether you're a startup needing speed or an enterprise balancing complexity, I adapt tools, rituals, and processes to suit your needs while still maintaining design rigor and user-centered focus.
Can you collaborate with developers and other team members during implementation?
Absolutely. I believe strong cross-functional collaboration is key to successful outcomes. I work closely with developers to ensure design intent is preserved, provide specs and documentation, and stay available during implementation for feedback, QA, and iteration. I'm just as comfortable in design systems as I am in a dev handoff meeting.
What kind of companies or projects do you usually work with?
I’ve worked across industries—from sustainability to education to enterprise SaaS—but I’m drawn to teams that value design as a strategic tool. Whether it’s building a product from scratch, improving an existing experience, or mentoring a design team, I aim to contribute where thoughtful design can make a real difference.
Do you offer one-time sessions or ongoing support?
Both! I offer one-time services like audits, portfolio reviews, and mentoring sessions, as well as longer-term collaborations for research, design, or process strategy. If you're unsure what fits best, we can have a quick chat to figure out the right level of engagement for your needs.