Design practice
The deliverable is a tool now.
More of what we hand over runs instead of sitting in a folder. The design moved into the rules and the limits.
For most of my career, a design job ended with a file. Screens, a style guide, a folder of exports, handed to someone who turned them into the real thing. Over the past year that quietly stopped being true at our studio. More and more, what we hand over runs.
Sometimes it is a small internal tool that produces a hundred banner variants from one approved layout. Sometimes it is a page with a few sliders on it, so a client’s team can tune an effect without calling us. Sometimes it is a set of written instructions an AI coding agent follows to build a component the way we would have. The design is all still there. It has moved, from the picture to the rules that make pictures.
Code became the sketchbook.
The shift started with how we explore, not with what we deliver. When an agent can assemble a working prototype in the time it takes to draw the static version, the static version starts to look like the long way round. The fluid reveal on this site’s hero video was never designed as a still frame. It was tuned in a browser, with live controls for how fast the ink spreads and how long it lingers, until it felt right under a real cursor. No mockup could have told us what right was.
Fig. 01Tuned under a cursor, not drawn
Design software has not left our process. It has moved later in it. It is where we refine and document an idea that has already proved itself in motion, not where the idea is first tried.
Agents are fast. None of them can see the whole.
A typical session now has several agents working side by side: one writing a component, one producing image candidates, one checking copy against the voice rules. Each is quick and narrow. None of them knows whether the results belong together, whether the motion fights the type, whether the third screen breaks a promise the first one made. That is still a person’s job, and it is now most of the job.
This is why I don’t believe the tools flatten experience. Telling a considered easing curve from a lazy one, or a comfortable line length from a cramped one, takes years of looking. What agents change is how many of those calls you make in a day. For a junior designer that is a gift: more options seen, more judgements practised, faster proof of whether they were right. The work of choosing grows as the work of making shrinks.
Designing the limits is the design.
When the deliverable is a tool, the hardest question is not how it looks. It is how much it lets someone else change. Too few controls and the client’s team comes back to you for every variation, which defeats the point. Too many, and within six months the brand is a blur of reasonable-looking choices nobody approved.
So we set the ranges as carefully as we used to set the layouts. Which colours may appear together and which never do. How short a headline can get before the composition falls apart. Which values are fixed and which are free. A constraint with its reason written next to it survives being used by someone who wasn’t in the room, which is also how we brief the agents that build our components.
Fig. 02Fixed, ranged, free
- Fixed
- The black and the white. The typeface. The colour pairs that never meet.
- Ranges
- Headline length, before the composition breaks. Image crop. Spacing, in set steps.
- Free
- The copy, inside the voice rules. Which product is shown. The language.
Put something working on the table early.
Working tools changed the conversation, too. A client looking at a static frame is imagining how it will behave, and everyone imagines it differently. A client sent a link and asked to scroll it, click it and try to break it is reacting to the real thing. Developers see on day two what they would otherwise have found in week six. Disagreements surface while they are still cheap to settle.
The caution is that a convincing demo is not a tested one. Something that feels great in a meeting can still be wrong for the people who will use it, or for the business paying for it. An early prototype earns a better conversation. It doesn’t replace the research.
What to ask of a studio now.
Ask what you will be left with when the engagement ends. A folder of finished assets is useful for a quarter. Templates, generators and documented rules your own team can run are useful for years, provided someone has thought hard about where their edges are. That is the part we now spend most of our time on, and if it sounds like what you need, tell us about it.
The file was never really the point. It was just the only thing we knew how to hand over.
Asked often.
How are AI agents changing the design process?
They make working prototypes nearly as quick to produce as static mockups, so more exploration happens in code, and the designer’s time shifts from making each asset to directing agents and judging whether the results fit together.
What does a design studio deliver if not design files?
Increasingly, working tools: templates, generators, configurable components and documented rules that a client’s team or an AI agent can use to produce on-brand work without the studio in the loop.
How do you stop a brand tool from diluting the brand?
By designing its limits deliberately: fixed values where the brand must not move, set ranges where it may, and a written reason for each, so people who use it later understand what they can change and why.