Whether I’m coaching an associate designer or managing an experienced team, my role is to build trust and psychological safety and help people thrive. The same curiosity I bring to understanding users is the mindset I bring to understanding the people I lead.
I’ve collected tactics over many years through self-directed learning (talks, readings, podcasts), structured professional development (conferences, courses, Melbourne Business School) and from other leaders.
You’ll notice a pattern in every tactic. None of them involves guessing.
They also aren’t forms to complete or assessments to run. They’re structured conversations to have with your team members, individually, early in your journey together
Design hire number one and don't know what to do? Read about the 6 steps I used to set up a design practice from scratch
If no one is listening, it's probably a design problem. The tips in the article will help you craft messages people can actually understand and act on.
Is your style guide being ignored? It’s not just a branding issue — it’s a usability problem. Learn why consistency is core, not optional — and how to get teams on board.
In 2015, I embarked on the journey of buying my first home. At that time, I wrote a blog post critiquing the UX of real estate websites through a, somewhat sarcastic, persona named ‘Kayla’ and listed out ‘her’ (my) user needs and how they weren’t being met. Discover how real estate websites have evolved from 2015 to 2024 through a personal lens. Spoiler alert – it still sucks, but it sucks a little less.
In this blog post, I evaluate how current real estate platforms address user needs such as viewing new properties, staying within budget, accessing accurate information, and managing inspection schedules. It suggests key improvements and practical recommendations for improving real estate website UX.
Bugs, put simply, are errors or defects in a software system. If you work in tech, you’ve probably heard someone say the half-joke, half-truth line “it’s not a bug, it’s a feature”. Often this is used in jest or to justify not wanting to fix a particularly difficult bug. But when is a bug really a feature? And what does this mean for your users?
