A bit of background about me
I've been designing user experiences for ten years. Along the way I've worked with every role under the sun. I've crafted amazing experiences for small clients, huge clients and every size in between. I've also had the pleasure of designing websites, mobile apps, and various digital tools. Below, I've listed some important lessons I've learned along the way.
7 lessons that have shaped my approach
|
|
Half of UX design is teaching, the other half is sales. All of it is design.
Whether it’s your team, a client, or stakeholders, you’re constantly explaining why a particular design approach works best for the user and aligns with business goals. At the same time, you’re also selling your ideas—both internally and externally—to get buy-in. It’s not just about creating good design; it’s about showing its value in a way that resonates with others. |
|
|
Attitude is everything. A good attitude makes for a good project.
Bringing a positive attitude, staying approachable, and showing kindness (even in challenging situations) helps build trust and keeps collaboration running smoothly. I’ve found that even difficult clients can shift their tone when treated with respect and care, and that shift can turn the tide of an entire project. |
|
|
People are visual. Use visual aids liberally when explaining abstract ideas.
Abstract concepts are hard to communicate without something tangible. I’ve learned that taking the extra time to create a quick visual—whether it’s a rough wireframe, flow diagram, or even a sketch on a whiteboard—can make all the difference. |
|
|
You have to understand the database to design a good user experience.
Great UX design doesn’t exist in isolation; it’s tied directly to the systems it relies on. If you don’t understand how data is stored, pulled, or structured, you’re designing on shaky ground. Knowing where data comes from and how it’s structured helps you design practical solutions and advocate for technical improvements when needed. |
|
|
Learning how to speak to business roles is a vital skill for UX designers.
Explaining design to non-designers requires translating ideas into business terms. I’ve found that learning how to communicate the value of a design in terms of ROI, customer satisfaction, or efficiency makes it easier to gain buy-in from stakeholders who may not think in terms of wireframes and user flows. |
|
|
Great ideas can come from non-designers. Seek their feedback frequently.
Some of the best ideas come from developers, project managers, or other non-designers. Non-designers bring unique perspectives to the table, and their insights can often lead to creative solutions that you might not have considered. |
|
|
Annotate your thoughts. Otherwise you won't remember why you did what you did.
Months after handing off a design, you’ll likely be asked why you made a particular decision—and if you haven’t documented your reasoning, it’s hard to remember. It’s not just for clients or stakeholders—it’s for you, too. Clear annotations make the work more transparent, defensible, and easier to pick up again later. |
Companies I've worked with
|
|
|
