© 2026 Richard Masters

last touched: kitchen table, late.

© 2026 Richard Masters

last touched: kitchen table, late.

© 2026 Richard Masters

last touched: kitchen table, late.

The Senior Designer and the Feature Factory

The Senior Designer and the Feature Factory

You join a startup because you want to make a difference. The product has energy, the problem is real and the interface looks as though it was assembled during a turbulent flight by three engineers who had recently discovered CSS. Perfect. There is work to do.

Fresh eyes are useful in a young company. You can see the accumulated inconsistencies that everyone else has stopped noticing. The navigation changes its mind from one screen to the next. Important actions are hidden, minor actions shout, and a form that should take two minutes asks users to complete a small administrative pilgrimage. You start mapping the system, talking to customers and imagining how much better it could be.

Then reality arrives with a calendar invitation.

The sales team needs a feature for a prospect who might sign this quarter. The chief executive wants a deck tidied before lunch. Someone has promised a new workflow without asking whether it fits the product. There are meeting notes to transcribe, screenshots to annotate and a collection of small requests described as urgent because nobody has taken the trouble to decide what matters.

By Friday, the designer hired to improve the product is moving boxes around a screen while the company congratulates itself on moving quickly.

The feature factory always has a convincing story

Early-stage companies do not become feature factories because everyone is foolish. They become feature factories because the pressure is real. Runway is finite. Investors want evidence of traction. A single customer can represent a meaningful percentage of revenue, and losing one opportunity can feel less like a commercial setback and more like an existential event.

Under those conditions, almost any request can be made to sound strategic. A prospect asks for a dashboard, so the dashboard becomes the route to revenue. A customer wants an export, so the export becomes proof of market fit. The loudest request acquires the costume of product strategy and marches directly into the sprint.

The trouble is not that startups build features. Of course they do. The trouble begins when the organisation loses the distinction between learning and delivering. A feature is shipped, but nobody defines what it is meant to prove. A customer request is implemented, but nobody asks whether it represents a broader need or one buyer's private collection of habits. Output becomes the metric because output is easy to count.

This is how a team can be extremely busy while the product remains strangely unimproved.

A bad interface is rarely just a visual problem

When the UI is visibly poor, redesigning it feels like the obvious first move. Sometimes it is. Credibility matters, especially in specialist industries such as aviation, maritime and enterprise software, where customers are being asked to trust a young company with expensive, operationally important work.

But ugliness is often only the surface symptom. Beneath it sits unclear product ownership, inconsistent data, exceptions created for individual customers, half-finished workflows and decisions that were never written down. Giving that system a nicer coat of paint may make the confusion more attractive, but it does not make it less confusing.

A good designer starts by understanding why the interface became incoherent. Which parts were built for a specific deal? Where are users leaving the product for spreadsheets? Which actions require support from a member of the team? Which concepts mean different things to sales, operations and engineering? The answers reveal the real design work.

This is why the best redesigns are not beauty treatments. They are acts of clarification. My work on an AI co-pilot for complex enterprise workflows dealt with exactly this problem: the visible interface only made sense once the underlying approvals, roles and operational constraints had been understood. The useful work was not making the screens prettier. It was making the system more legible.

Senior designers are expensive task routers

In a small company, everyone helps. Seniority should not create an allergy to ordinary work. There will be weeks when the most useful thing a designer can do is fix the presentation, clean up the prototype or write the notes because the alternative is that nobody does it.

But there is a difference between pitching in and becoming organisational compost.

If a highly experienced product designer is routinely transcribing meetings, formatting internal documents, producing decorative mock-ups for pre-decided features and responding to every stray request from the leadership team, the company does not have a designer. It has an expensive task router with Figma access.

The cost is larger than the designer's frustration. Every hour spent polishing low-value material is an hour not spent understanding customers, testing risky assumptions, improving the design system or identifying the workflow that is quietly damaging adoption. More importantly, it teaches the organisation to use design as a service desk. People arrive with solutions, the designer makes them presentable, and the company loses the benefit of design thinking before any thinking has occurred.

This waste is particularly absurd in a startup. Large companies can absorb a surprising amount of badly allocated talent. Small companies cannot. If six people are building the product, using one of them at twenty percent of their ability is not scrappy. It is careless.

The tyranny of the urgent

Startups often describe themselves as fast when they are merely interruptible. The distinction matters.

A genuinely fast team makes clear decisions, limits work in progress and learns quickly from what it releases. An interruptible team changes direction whenever a senior person has a thought. It starts many things, finishes some of them and leaves the product carrying the archaeological evidence.

Design suffers first because design work is easy to fragment. A screen can be produced in an afternoon, which creates the illusion that the decision behind it also took an afternoon. Research, synthesis, systems thinking and validation disappear from view. The designer becomes measured by responsiveness rather than judgement.

The phrase “can you just” does a great deal of damage here. Can you just add a field? Can you just make a version for this customer? Can you just tidy this deck? Each request is small enough to sound unreasonable to resist. Together they consume the week, fracture the product and leave the important work permanently scheduled for later.

Commercial urgency should sharpen design, not remove it

The answer is not to ask a startup to behave like a mature design organisation. Nobody needs a six-week discovery phase for every button. Nor should designers retreat into process and complain that the business is insufficiently pure.

Commercial pressure can make design better. It forces the team to identify the smallest useful intervention, test assumptions with real buyers and connect product decisions to measurable outcomes. The healthiest version of startup design is pragmatic, close to customers and suspicious of ceremony.

That requires a better question than “what can we ship for this prospect?” The question is “what is the underlying problem, how many customers share it, and what is the smallest change that teaches us something useful?”

Sometimes the answer will still be a feature for one important customer. Fine. But the team should know whether it is building a strategic capability, a paid customisation or temporary scaffolding. Pretending all three are the same is how roadmaps become storage cupboards.

The same logic shaped my work on maritime procurement at ShipServ. Users had established habits, spreadsheet-based workarounds and understandable resistance to abrupt change. Progress came from improving the workflow without dismissing the reality around it. That is very different from simply accepting every request exactly as it arrives.

What good use of a product designer looks like

A startup gets more from an experienced designer when it gives them access to the problem, not merely custody of the pixels.

Bring them into customer conversations before the solution has been promised. Let them see the commercial context, including why a deal matters and what the buyer is actually resisting. Give them access to product data, support tickets and the people doing the operational work. Ask them to challenge the shape of the problem, then expect them to propose something proportionate to the company's stage.

Protect some capacity for systemic work. That might mean one day a week improving foundations, a fixed percentage of each cycle for usability debt, or a rule that repeated customer requests trigger a proper pattern rather than another exception. The mechanism matters less than the acknowledgement that the product cannot survive entirely on emergency calories.

Most importantly, judge design by the quality of decisions it improves. Did the team understand the customer better? Did the change reduce failure or support effort? Did it make a sales conversation easier without making the product worse for everyone else? Did it create a reusable capability rather than a bespoke dead end?

These are not indulgent design questions. They are business questions with longer memories.

The designer has responsibilities too

It is easy for a frustrated designer to become professionally superior. Everyone else is chasing revenue while the designer alone can see the sanctity of the user experience. This is not especially useful.

Designers joining startups need to earn influence by understanding the commercial machine. Learn how the company sells, where deals stall, which customers are profitable and what the runway actually means. Translate design concerns into consequences the team recognises. “The hierarchy is inconsistent” is weaker than “users are missing the approval state, which is creating support calls and delaying invoices.”

Choose battles carefully. Not every ugly corner deserves immediate rescue. Some parts of an early product are temporary, and polishing them is simply well-crafted waste. The skill is knowing which imperfections damage trust, which create operational cost and which can wait.

And when low-value work arrives, make the trade-off visible. Do not silently absorb it and become resentful. Explain what will move if the new request takes priority. A company may still choose the deck over the research, but at least it is making a decision rather than benefiting from invisible overtime.

Use the person you hired

A startup does not need to worship design. It does need to understand what it bought.

If you hire an experienced product designer and use them mainly to decorate predetermined features, absorb executive errands and turn unfiltered customer requests into screens, you are not moving quickly. You are paying for judgement and declining to use it.

The best early-stage teams retain urgency without becoming frantic. They know that customers matter, revenue matters and investors matter. They also know that a product built from a hundred short-term promises eventually becomes difficult to sell, difficult to use and exhausting to change.

Fresh eyes are valuable precisely because they have not yet learned to accept the mess. The sensible response is not to bury them under it.