Stephen ReaProduct, design & AI strategy
← Thinking

Breadth is not
being a generalist.

The value of breadth is transfer: recognising what kind of problem is in front of you, and bringing the right experience to bear.

Breadth gets misunderstood because people often use it as a softer word for being unfocused. That is not the useful version. The useful version is transfer: the ability to carry judgement from one material, medium or organisation into another without pretending the contexts are identical.

A designer who has moved through 3D, games, mobile, brand, SaaS, fintech and enterprise products has met different kinds of constraint. In games, timing and feedback matter because a tiny delay can break the feeling of control. In mobile, hierarchy has to survive a small screen, an impatient user and a distracted moment. In enterprise products, the visible interface is often the tip of a much larger system of roles, permissions, data quality, adoption, risk and internal politics. In design leadership, the work is not only the product. It is the organisation that keeps producing the product.

That range matters more now because AI is blurring old production boundaries. A team can generate interface options, drafts, flows, research summaries and code-shaped prototypes at a pace that would have seemed absurd a few years ago. But faster production does not create better product judgement by itself. The person leading the work needs to understand what kind of problem is in front of the team. Is the issue visual? Behavioural? Organisational? Commercial? Ethical? Technical? Is the interface confusing because the screen is badly designed, or because the business model behind it is incoherent?

The value of breadth is not that one person can do every task. It is that they can recognise the nature of the task before the team wastes weeks solving the wrong version of it. They can tell when craft is being used to hide weak strategy, when strategy is too abstract to survive contact with users, when research is becoming theatre, and when a team has enough information but not enough courage to make a decision.

That is the through-line of this site. Paper Design is not trying to present a tidy linear career. It is showing how a long body of work creates pattern recognition. The modern design leader has to connect interface detail to product strategy, product strategy to team behaviour, team behaviour to business consequence, and business consequence back to the human experience. Breadth only matters when it makes those connections stronger.

A conversation is a good place to start.

Let’s make
something better.

Get in touch