The Modern Product Designer's Tool Stack, Reconsidered

Asked to list the tools they use, a product designer in 2018 would have produced a clean three-item list. A canvas tool. A prototyping tool. A handoff tool to throw the work over to engineering. The list was crisp because the discipline was crisp. The designer worked in design tools, the engineer worked in engineering tools, and the handoff was the boundary between them.

Asked to list the tools they use, a product designer in 2023 would produce a list of fifteen items, of which the original three are still present and have shrunk to a handful of buttons used per session. The other twelve items live in the territory the discipline used to consider out of scope. The shift is not because designers are encroaching on adjacent disciplines, it is because the boundaries that used to separate the disciplines have eroded under the weight of the work itself.

What stayed in the centre, and what shrunk

The centre of the design tool stack today is smaller than it was five years ago. Almost all serious product design happens in two tools, a vector canvas tool with collaborative editing and a prototyping tool that approximates real interaction states. A third position is sometimes occupied by a motion tool, when the work demands it, and a fourth by a research repository, when the team has resourced one. Beyond those, the dedicated design category has narrowed.

The narrowing is not a story of designer laziness or tool fatigue. It is a story of consolidation, the same way most industries consolidate over time. The vector canvas tool absorbed the wireframing tool, the mockup tool, the redlining tool, and the basic prototyping tool. The prototyping tool absorbed motion timing and state machines. The component library absorbed pattern libraries and style guides. What used to take five tools now takes two, and the two have become so dominant that the conversation about which tool to use has effectively ended for most teams.

This is good news for designers in the abstract. It also means that learning the dedicated design stack is a smaller fraction of the job than it used to be, and learning the adjacent stack is a larger fraction. The total amount of tool learning has not gone down. The tool learning has migrated to a different territory.

What grew at the edges

The territory at the edges has grown to include some tools that used to belong unambiguously to engineering, some that belonged to product management, and some that belonged to operations. A modern product designer is now usually expected to be functional in a code editor, comfortable enough with a version control client to push small visual fixes without help, capable of running a database query to pull a sample of real user data, fluent in at least one analytics platform to interpret usage patterns, and competent in at least one documentation system that the team uses for design decisions. Most of these tools were not on the designer’s list five years ago.

The expectation is rarely written down. No job description for a product design role lists “comfortable enough with the codebase to land a CSS-only pull request” as a requirement, but the senior designers who can do that are the ones who get the projects that need design decisions and engineering decisions to land at the same time, which is most of the projects worth having. The unstated expectation has become a real selection mechanism, and it has tilted the discipline toward designers who treat the engineering stack as part of their habitat.

The same has happened with writing. The product designer of 2018 wrote occasionally, mostly in artefact form. The product designer of 2023 writes constantly, mostly in document form. Specs, design proposals, retros, decision memos, post-mortems. The writing surface has become a primary tool, and the designers who treat writing as part of the craft have an advantage over the ones who treat it as overhead.

This expansion is not weightless. It costs the designer attention, and the attention is finite. A designer learning a new analytics platform is not learning a new typography technique. A designer maintaining proficiency in three documentation systems is not maintaining proficiency in three motion patterns. The trade is real, and the trade has been made implicitly across the discipline without much discussion.

The hidden cost of the wider stack

A wider stack means more context switching. The designer who works on a single feature in a single afternoon now opens, on average, six to eight tools, each with its own interface, its own conventions, and its own performance cost. The mental load of moving between tools is a tax most discussions of designer productivity ignore. The tax compounds across a sprint, and the compounded tax is one reason designers in 2023 report feeling busier than designers in 2018 while shipping fewer screens per quarter.

The other hidden cost is the dilution of expertise. A designer who used to be deeply expert in a small set of design tools is now functionally competent in a much wider set of tools that includes the design tools. Functional competence is enough to ship most work. It is not enough to push the craft forward, and it is rarely enough to teach. The discipline ends up with more designers who can do more things, and fewer designers who can teach any of those things deeply. This shows up in the apprenticeship problem, which most product design teams now have and which most teams have not yet recognised as a tool stack problem.

A junior designer joining a team in 2018 could shadow a senior designer in two tools and learn a craft that compounded over years. A junior designer joining a team in 2023 has to shadow several seniors across many tools to learn the same craft, and each senior is a half-expert in each tool, which means the apprenticeship is more diffuse and slower to compound. The fix for this is real but boring. Teams have to invest in deeper proficiency in fewer tools, and accept that the wider stack is a cost the discipline pays whether or not the team likes it.

What the new stack looks like, honestly

A working product designer in 2023, listed honestly, uses something close to the following. A vector canvas tool. A prototyping tool. A code editor opened often enough to navigate. A version control client that does not require the terminal for everyday tasks. A terminal opened occasionally for the things the client cannot do. An analytics platform read regularly, sometimes daily. A documentation system used for proposals, specs, and decision memos. A writing tool for longer-form work. A presentation tool for stakeholder reviews. A diagram tool for system maps. A motion tool when the work calls for it. A research repository when the team has one, and a notes app when it does not. The list is twelve to fifteen tools deep, and the centre of gravity is no longer purely in design.

The honest job description that matches this stack does not exist yet. The job descriptions still describe the dedicated design tools and treat the wider stack as a bonus. The reality is that the wider stack is the job, and the dedicated design tools are a foundational subset of it. The first companies to write job descriptions that match the actual stack will hire faster and retain better, because the candidates who match the actual stack will recognise themselves in the description for the first time.

The stack got smaller in the centre and larger at the edges, which is the same thing as saying the centre stopped mattering.

The discipline still calls itself design. The discipline now includes more than the design.