Adopt the tool that compresses the boring half of the work, not the creative half.
Every AI tool pitches itself as a designer replacement. The good ones quietly do something different. They take the parts of the job nobody wanted in the first place (writing tickets, summarizing research, generating boilerplate, drafting copy variants) and give the time back to the team. That is the lens I use. If a tool tries to replace taste, I stop testing it. If it removes friction from the boring half, I keep it.
The other rule has saved my team months of churn: a tool only stays in the stack if at least three designers are using it daily after the trial ends. Anything below that bar gets cut. The cost of a tool is not the subscription. It is the cognitive load of remembering it exists, the integration debt, and the half-trained team that uses it badly because nobody owns it. Cut early, cut often.
Hey Marvin, Dscout, and Granola sit at the top of our research stack.
Research used to die in transcripts. Now it lives in synthesis. Hey Marvin transcribes and clusters interviews in minutes, surfacing patterns my team would have taken a week to write up by hand. Dscout has matured into a serious diary study and unmoderated testing platform that designers can run without a dedicated researcher. Granola sits in every internal meeting and turns hallway conversations into searchable notes. Together, insight cycle time drops from weeks to days, and that changes the kind of decisions a team can make.
The unlock is not the transcription. It is what becomes possible when synthesis is cheap. A designer can run six customer conversations on a Monday, have clustered themes by Wednesday, and walk into Thursday’s roadmap meeting with evidence. The team that used to do one round of research per quarter now does two per month. Decisions get sharper because they rest on user voice that is hours old, not weeks old.
- Hey Marvin for interview transcription and pattern clustering.
- Dscout for unmoderated tests and longitudinal diary studies.
- Granola for ambient meeting capture and shareable summaries.
- UserTesting for fast unmoderated tasks when you need quantitative signal in 24 hours.
Figma as our canvas. Lovable, Cursor, and Claude for everything around it.
On my team, Figma is still the canvas and the source of truth for the design file, but it is no longer where ideas are born. We start in Lovable when we want to see a working prototype with real data behind it, often within an hour. Cursor and Claude sit next to Figma for the in-between work: generating component variants, writing helper text, refactoring tokens, and turning rough flows into shippable code. Designers who learned to prompt well are operating at roughly twice the speed they were six months ago. Designers who did not are slowly being out-produced by their peers.
What changed in 2026 is that prototyping moved from a designer activity to a designer plus engineer activity that lives in code. The fidelity gap between a Figma prototype and a working app collapsed. The teams that adapted fastest stopped treating Figma as the final artifact. It became the place to think, while the prototype lived in code from the second week of the project. That shift alone has been worth more to my team than any single tool.
The new design seniority is not visual taste. It is judgment about which AI output to keep, which to throw out, and which to ship.
Claude Cowork for management work. ChatGPT for everyday drafting.
For me personally, as a director, the highest leverage tool has been Claude Cowork. I use it for weekly digests, leadership update drafts, performance review prep, and structured deep research. I wrote up the full workflow in How design managers and directors can use Claude Cowork. It does not replace judgment. It compresses the eight hours of reading, formatting, and chasing that used to sit in front of every leadership decision. ChatGPT stays in the stack for everyday drafting (emails, copy variants, quick comparisons) because the muscle memory is hard to break and the latency is unbeatable.
The pattern I push on my team is one heavy tool and one light tool per workflow. The heavy tool is for work that compounds: Cowork for management, Cursor for code, Hey Marvin for research. The light tool is for quick tasks that don’t need to compound: ChatGPT for drafting, Granola for meeting capture. Trying to make one tool do everything is how teams end up with the worst version of three different workflows.
Obsidian as a second brain. ChatGPT and Claude as thinking partners.
Every designer on my team keeps an Obsidian vault. Notes from research, decisions from reviews, links to artifacts. It compounds. Pair it with Claude or ChatGPT and a leader can interrogate six months of context in seconds, which makes coaching conversations and quarterly reviews a lot sharper.
The tools matter less than the habit. If your team is not writing things down, no model will save you. If they are, AI turns that written history into the most valuable asset on the team.
The tools that did not survive the trial.
Naming what we dropped matters as much as naming what we kept. A leader who only talks about the wins creates a culture where everyone is afraid to admit a tool did not work. We post the kill list in the team channel every quarter. It makes it normal to try things and walk away when they do not earn their place.
- Standalone AI design generators that produce “final” UI. The output looked finished, but never fit our system or our brand voice.
- Heavy AI plugin suites inside Figma. The cognitive overhead and slow updates made them a net negative compared with lightweight Claude prompts in a side window.
- Auto-summarizers attached to Slack and email. They saved minutes and lost nuance. The team stopped trusting the summaries within a month.
- AI “copilots” for design reviews that promised to score work. Scoring design without context is worse than not scoring it at all.
A 90 day plan for taking your team from curious to fluent.
Month one. Pick one workflow per designer to AI-assist. Not a whole job, one workflow: research synthesis, copy variants, or ticket writing. Write down the time it takes before and after.
Month two. Pair people up and run a 48 hour hackathon on a real product problem. The hackathon is where fluency actually lands. I wrote up the format in the design hackathon playbook.
Month three. Name a tool owner per category (research, prototyping, writing, knowledge) and have each one publish a one page “how we use this” doc for the rest of the team. The team that has owners ships faster than the team that has tools.
Skip the all-hands training session for tools. People do not learn AI tools by being lectured at. They learn by trying to ship something with a peer who is six weeks ahead of them. Build that into the rollout from day one and you will not need a single training session. If your designers have never opened a terminal, my Age of Builders lesson covers the setup.