What I learned as the first designer at Pocket FM

Being the first designer sounds exciting.
No design debt. No old process. Full freedom.
It is exciting.
It is also very easy to become the person who makes every screen, every banner, every empty state, every quick fix, and then wonders why nothing feels strategic.
So what is the actual job?
At first I thought it was making good screens.
Later I understood the bigger job: help the company make better product decisions.
A solo designer should not try to be a hero. A solo designer should make the team clearer.
But if I am the only designer, should I touch everything?
No. That is how you become busy without being useful.
Some work needs deep thinking. Some needs a quick fix. Some should become a reusable component. Some should not be done yet.
Your time is also a product resource.
How do I get people to value design then?
Explain the thinking, not only the screen.
Instead of saying "this improves usability," say "earlier the user had to think too much here. Now the main action is clear."
Instead of saying "better hierarchy," say "the most important thing is now easier to see first."
What changed when you stopped thinking in screens?
I started looking for influence, not output.
If a team wants to add more information to a page, the work is not only arranging it nicely.
The better question is: what decision is the user making here, what can we remove, and what needs to come first?
What about systems?
A big design system feels impossible when everything is moving fast.
Do not start with a big system.
Start with one button style, one type scale, one spacing rule, one way to show errors, one way to show empty states.
The goal is less repeated thinking, not a perfect library.
And the messy cases?
Fast teams usually ignore them.
That is exactly why design should hold them.
What happens when there is no data? When loading takes time? When text gets long? When the user comes back after many days?
A product is not complete because the happy path looks clean.
What should I document?
Only the decisions worth remembering.
What problem were we solving? What options did we consider? What did we decide? Why did we decide it? What is still open?
A short note can save the team from repeating the same confusion two months later.
How does a solo designer scale?
By helping other people think better.
Ask small questions in reviews and planning: what is the user trying to do, where can they get stuck, what can we remove, what does success look like?
You scale design by making design useful in the room.
So being first is not about proving design matters.
Right.
It is about being useful enough that people feel the value.
Bring clarity again and again. For users, for teams, and for decisions.