Graden Hudson

Before products, there were pixels. Learning to guide attention through intentional form. Using instinct (AKA trial and error) to decide what to show, what to shrink, and what to cut entirely.

Good design removes choices rather than adding them. That discipline carried forward into how I think about products: knowing what to cut is its own kind of craft, and it only becomes more tricky when the stakes are higher.

The hardest brief is always some version of the same thing: make something complicated feel like it was never complicated at all. Same job, just at a different scale.

Managing timelines and resources across competing priorities taught me something I still believe: constraints are creative. Deciding what not to build is just as important as deciding what you do build, and that clarity doesn't come naturally. You have to be intentional.

Getting alignment across teams is a communication skill, but it's also a design problem. You're working with people who have different incentives, different information, and different definitions of "done."

Shipping on time and being straight when you can't. Those turned out to be the foundation of every credible product relationship I've built. Delivery is a trust metric before it's anything else.

Field research humbles you fast. With how often I've been wrong about my assumptions, I've learned that the gap between what users say, what they do, and what they actually need is where almost every real product opportunity lives. And you can't find it without being in the room with people.

The Master's in Human-Computer Interaction didn't just teach me how to run studies. It taught me to model human cognition as a system: people bring mental models, contexts, and constraints to every interaction.

Qualitative tells you why. Quantitative tells you how much. Knowing which question needs which method (and when to hold both in tension) is a skill that rarely shows up on a resume but helps shape product decisions I make.

Stepping into a PM role used all of what came before simultaneously. Design instincts, project discipline, research methodology. In retrospect, the arc felt natural. Every stage added something that stays with me to this day.

Real input, genuine decisions, accountability for both. I've seen "collaborative" used as cover for avoiding hard calls or delaying decisions. The value is in knowing when to stop asking and start acting.

Nearly a decade leading the core product area at a growing HR software company. 400+ customer conversations. Outcomes that moved the business in measurable ways. A squad built around humility and a commmitment to understanding our customer's needs.