The shift from making things look good to making things work.
My journey started in jewellery photography, then moved into design, brand, product, and operations. Across those roles, the work changed. So did the questions I asked.
Is this visually strong? Is the layout clear? Does everything feel consistent?
Those questions still matter. But when you become responsible for what happens beyond the design, they are no longer enough.
Can the team maintain it? Does the customer understand it? Can we deliver what this page promises?
Design becomes a different conversation when you also have to live with its consequences.
Good design starts before the screen
A brief might say, “We need a better website.” But that does not tell you what actually needs fixing.
Perhaps customers cannot understand the offer. Perhaps the business has added services without deciding which ones matter most. Perhaps the website generates enquiries, but nobody owns the follow-up.
A redesign can help with some of that. It cannot resolve all of it.
Before deciding how something should look, I want to understand what is getting in the way. Sometimes that leads to a new layout. Sometimes it leads to simpler content, a clearer offer, or a conversation about who is responsible for the next step.
That is still useful design work, even when the outcome is not another screen.
The handoff is part of the design
It is easy to judge a design when everything is controlled: the right image, a short headline, a carefully chosen example.
The real test comes later.
Someone adds a longer product name. Another person uploads a poor image. A team needs to publish something quickly without asking the designer for help.
Does the design still hold up?
Working across design and operations has made me care more about that everyday use. A template should be easy to update. A brand guideline should help someone make a decision. A product interface should account for more than the ideal scenario.
If routine changes require the original designer to step in every time, the work is not quite finished.
Consistency depends on how people work
I care about visual consistency. But keeping a brand consistent takes more than choosing fonts and colours.
People need to know where the approved assets are, which version to use, and who can answer a question. They need examples that reflect the work they actually produce.
Without that, even a carefully designed identity becomes difficult to maintain.
This is where brand and operations meet. The quality of the output depends partly on how easy it is for people to do the right thing.
A useful system gives the team enough structure to work confidently without turning every decision into an approval request.
Constraints make priorities visible
When you are responsible for delivery, design decisions compete with other needs.
There is a deadline. The team has limited capacity. Something needs fixing before something else can be improved.
That does not mean quality stops mattering. It means being specific about where quality matters most.
An unclear checkout deserves more attention than a decorative animation. A page people cannot read on mobile is more urgent than a subtle spacing adjustment elsewhere.
I still notice those smaller details. The difference is knowing which ones need attention now and which ones can wait.
I still care how it looks
Taking a broader view has not made me care less about design. It has made me ask more of it.
I want the work to look considered, communicate clearly, and hold up when other people use it. I want it to support what the business can actually deliver.
A portfolio shows the finished surface. The more interesting work often sits behind it: deciding what matters, making trade-offs, and helping people move forward.
That is what running a business has changed for me.
I no longer see the finished design as the end of the job. I see it as the beginning of its use.