Keeley Jones knows how to make people look good. At AFC Richmond, she helped footballers build their personal brands and landed the club a sponsorship with a dating app. Put her on a product team, and she’d do the same thing for an interface and for the people building it.
She’d show up to her first stand-up with snacks, learn everyone’s name by lunch, and know who was quietly struggling by the end of the week.
She reads the room before the requirements
Keeley notices how people feel, usually before they’ve said anything. In a project kickoff, she’d spot that the designer is nervous about the timeline and the engineer is annoyed about the API, then get them talking to each other before either problem turns into a grudge.
That same sense would make her great at user research. She’d notice the participant who says “Yeah, it’s fine” with a face that clearly says it isn’t. Then she’d ask the follow-up question everyone else skipped.
On-brand, all the way down
Keeley knows a brand is more than a logo. She’d care that the error message sounds like the same company as the homepage, that the loading state uses the same type scale as everything else, and that the confirmation email doesn’t look like it was designed in a different decade.
Design tokens would make immediate sense to her. “So it’s like a capsule wardrobe for the website? A few pieces that all go together?” Exactly, Keeley.
She helps quiet features shine
Keeley’s real gift is helping people show their best side. She’d do the same for features nobody can find. She’d rewrite the vague menu label, add an empty state that explains what to do next, and turn onboarding into something that feels like a friend showing you around.
The feature didn’t change. People could just finally see how good it was.
Feedback with a hug attached
Keeley is honest and kind at the same time. Her code reviews would say what’s wrong clearly, then point out what’s great, and she’d mean both.
Her error messages would work the same way: “That card number looks one digit short. Give it another go.” It’s specific, it tells you what to fix, and it never makes you feel silly for making a typo.
Demo day is her day
Sprint demos would be Keeley’s favorite meeting. She’d make sure the people who built the thing get the credit, by name. She’d tell the story from the user’s point of view instead of walking through tickets. And she’d make the accessibility work visible, so stakeholders understand why the keyboard support and screen reader testing took the time they did.
People would leave her demos excited about work they’d previously ignored.
Where she’d grow
Running her own PR firm taught Keeley that being the boss is different from being everyone’s friend. On a product team, she’d learn a similar lesson about saying no. Sometimes the kindest thing for users is turning down a stakeholder’s favorite feature request, clearly and warmly, with a better idea ready.
She’d get good at it, because she cares about the people on both sides of that conversation.
What we’d learn from Keeley
Keeley would remind us that interfaces are made for people and by people, and that both groups deserve to feel seen. She’d show that warmth and clarity work well together, in microcopy and in meetings.
And she’d probably remind you to celebrate the small wins. Then she’d bring cake to make sure you did.
This article is part of the Famous Fictional UX Engineers series.