Why hybrid designers are making pure specialists less relevant in startups

I came to IT and product design from traditional architecture. My last year at a state architecture company was spent designing a single entrance area for a shopping mall. It was an endlessly slow process: tons of paper drawings carried around in bags, long approval cycles, no flexibility, and zero impact on the final result. I left for IT because of the speed, the excitement, and the chance to test ideas quickly. But it turned out that the tech industry often reproduces the same clumsy conveyor belt.

In the process of working on digital products, I came to the conclusion that the role of a pure execution designer gives too little leverage on the business outcome. A well-drawn screen on its own adds maybe a few percent of real value at best. And if aesthetics are not grounded in tested business logic, they are useless.

The old model and why it breaks

The usual interface design process works like this: a product manager brings a clearly defined problem and a detailed brief, and the designer converts it into neat mockups. The cycle repeats: got a task → handed over the screens → picked up the next one.

In large corporations with well-oiled processes, this kind of narrow specialisation works. I saw it from the inside while working at a company with 5,000+ employees. There is a rigid hierarchy there, where every employee has pre-defined boundaries of responsibility. Someone comes to you, gives you a task, and you calmly just design screens, staying completely isolated from the real business processes.

But if the team is smaller and the product is moving faster, this approach stops working. In an early-stage startup, it is a luxury to focus only on the visual layer. And waiting around for well-formulated briefs will get you nowhere.

In small teams, the expansion of a designer’s area of responsibility is a matter of product survival (ownership expands by necessity). A designer inevitably gets involved in the product roadmap, strategy, and experiment planning.

By nature, I am a person with a high level of healthy professional anxiety. It matters to me to understand how my work affects the world. The role of a passive executor, who does not know how his buttons affect the economics, quickly leads to burnout. This hunger for control over the outcome is exactly what pushes specialists like me out of Figma and toward business processes.

From handing off mockups to overlapping roles: where is the boundary now?

The blurring of boundaries between product design and management shows up most clearly during moments when the business model is being transformed. A good illustration of this kind of teamwork is the process of introducing paid subscriptions into a fast-growing viral service.

At early stages, a venture business demands explosive audience growth, and monetisation moves into the background. But at a certain point, investors need to see not only app install graphs, but real revenue too. A new task appears: get loyal users to start paying.

This task cannot be solved with UI design alone. Here you need to move from the handoff model to full functional overlap. A good solution here is to sit down in close partnership with the product manager and start generating business hypotheses. This kind of work goes beyond drawing the final payment screen. Design and product share accountability for the result. In very specific day-to-day tasks, my process looks like this:

1. Framing problem – the work starts with jointly formulating the problem itself. Before I even open the editor, I need to understand what business task we are trying to solve. Design begins with critical questions asked of the source data
2. Defining behaviour – my focus has shifted from creating static screens to designing user behaviour. I think through the logic of how the system reacts to user actions and build in mechanics that encourage users to return to the product
3. Onboarding and paywall logic – we design the entire user path to payment: we develop onboarding logic, test paywall structures, and experiment with entry points and pricing offers
4. Experiment design – every interface decision is framed as a hypothesis. Already at the stage of rough sketches, I plan the structure of the future A/B test, building the needed variability into the architecture of the mockups
5. Reading results – after release, I work directly with analytics. Relying on the numbers, the product manager and I adjust the interface together, launching new iterations until the hypothesis is confirmed by the metrics

Emotional design as a retention tool

This shift toward business does not mean abandoning empathy. On the contrary, emotional design becomes even more important as a pragmatic tool for influencing retention.

B2C apps have already passed the stage where they were just solving utilitarian needs. This is especially visible in generational change: if for millennials it was enough that an app simply worked without bugs, newer generations expect unconventional interaction mechanics. A dry product does not hold their attention.

A good example is the location-sharing app Bump by the developers at Amo. At its core, it is just a regular friend location tracker. But the product is designed in such a way that users open it every day just to send an emoji to someone close to them. The team plans sprints not only around features, but around specific emotions.

When an interface creates the right feeling at the right moment, active use of it turns into a habit. To defend emotional design in front of the business, you have to speak the language of numbers: introducing new mechanics pays off through engagement growth and increases the probability of conversion into a paid subscriber.

Hybrid roles in practice: what a real week looks like

If you put all of this together, what does a typical work week of a hybrid specialist look like? It is radically different from the routine of a pure visual designer.

On Monday, I do not open graphic editors. The product manager and I look at analytics and read the results of the A/B tests launched last week. If paywall conversion has dropped, we formulate the problem together.

See Also

5 mistakes you’re making with your digital marketing campaign

In the middle of the week, the validation stage begins. In early-stage startups, a specialist often works autonomously, and there may be no one to discuss the logic with. Here, AI has become a sparring partner. I use language models to test concepts at the stages of framing problem and experiment design. Dialogue with AI helps surface weak spots in the business logic and find edge cases.

And only closer to the end of the week do I move on to visual execution. Even then, the exaggerated focus on tooling and complex design systems disappears. In 80% of cases, a basic set is enough to test a new mechanic: a red button and a standard card. Functional minimalism saves resources and makes it possible to ship new iterations every week.

Skills beyond Figma and positioning yourself in the market

The designer’s role is now transforming around a new set of skills. High-level command of design software is just the baseline. What really matters beyond Figma is product analytics, an understanding of unit economics, and the basics of cognitive psychology. You need to be able to work closely with product managers in a way that helps move a hypothesis into production quickly, while arguing for the technical advantage of simple solutions.

How do you position this experience on the market or in a conversation about a promotion? Instead of saying, “I designed a new onboarding flow,” say: “We identified a problem with users dropping off on the first screen. I designed an experiment with three paywall variations, introduced an emotional feedback mechanic, and based on the A/B test results we increased paid subscription conversion by 12%.” What you are selling is the ability to connect design decisions to revenue.

Conclusion: which direction do you want to grow in?

Pure execution roles in early-stage companies are shrinking fast. But the choice of career path still depends on your personal goals. There is still a path where you keep a narrow specialisation – but for that you have to accept corporate approval cycles and isolated work on component libraries inside large companies.

But if results matter to you, the hybrid path is almost inevitable. Designers who keep expanding their scope gain real influence over the product. By refusing the position of a pair of hands in favour of broader responsibility for business metrics, you stop being just a creator of interfaces and become someone who helps drive the business forward. It is worth thinking about which of these paths is closer to you.