What being the only product designer in a business has taught me

Some days I’m designing a user journey. Other days I’m untangling competing requests, talking through technical constraints and asking whether we actually need the feature everyone wants by Friday.

Being the only product designer has taught me how much of the job happens outside the design file. The polished screens are one part of a week that involves plenty of questions, negotiation and changing direction.

The request is where the conversation starts

“Can we add a dashboard?” might mean “Our customers can’t find what they need.”

“Can we add another field?” might point to a process that needs rethinking.

I’ve learned to ask a few questions before opening a design file. Who is struggling? What are they trying to do? What do we know about the problem?

There’s pressure to produce something tangible quickly. But a short conversation at the start can save days of designing and building something that doesn’t help.

Engineers make the work better

An engineer asking “What happens when this fails?” can expose a gap I’ve completely missed.

So can real data, permissions or a technical dependency I didn’t know existed.

Working with engineers early gives us room to explore those things together. Sometimes we find a simpler approach. Sometimes I need to explain why a detail is worth the extra effort. Sometimes the design changes because I understand the constraints better.

I’ve become more comfortable sharing work while it’s still rough. Those conversations are easier when we haven’t already committed to a solution.

Everything can’t come first

When you’re the only designer, requests arrive from across the business. Each person has a good reason why theirs matters.

It’s tempting to squeeze everything in. But that usually means switching constantly between tasks and giving each one less attention than it needs.

I’ve learned to make the trade-off clear: “I can pick this up, but it will delay what we agreed was next. Has the priority changed?”

That gives people something concrete to decide. It also means I’m not quietly carrying several competing promises.

Good ideas need more than a convincing presentation

I can see a usability problem clearly and still struggle to get it prioritised.

Other people are balancing delivery dates, customer commitments and commercial pressures. To influence those decisions, I need to understand what they’re weighing up.

It helps to explain the consequence: where people get stuck, what extra work it creates and what we risk by leaving it unresolved.

Often, that takes several conversations. I’ve learned to expect that and keep bringing useful evidence into the discussion.

A finished design isn’t a finished job

Questions come up during development. Details change. Real content breaks the tidy layout.

Staying involved helps me catch where a small implementation decision has changed the experience. It also gives us a chance to work through issues together while the feature is taking shape.

Then it launches, and we start learning from actual use. Feedback and support conversations can reveal problems that never came up in a prototype.

There isn’t always time to revisit everything. But I want us to know what still needs attention.

I have to choose where the effort goes

I can see more things to improve than I have time to fix. That’s one of the frustrations of being the only designer.

The judgement is deciding what needs careful exploration, what can use an existing pattern and which compromises we can reasonably live with.

I’m still learning to be comfortable with that. There will always be a detail I’d like to refine or a question I’d like more time to investigate.

Being senior hasn’t made the work feel perfectly under control. It’s made me better at asking questions, explaining decisions and working through uncertainty with other people.

Those moments rarely make it into a portfolio. They take up a fair amount of my week.