Tools the Vercel product design team actually uses
The Vercel product design team recently shared insights on the diverse tools they use for design work during a team meeting. The team exhibits a wide range of AI tool adoption, with varying opinions on their effectiveness in creative processes. As design workflows evolve, challenges arise from the integration of production and design, prompting the development of new tools to enhance collaboration and efficiency.
- ▪The team uses a variety of design tools, with each member having different preferences.
- ▪AI tools for design are perceived as lagging compared to those for engineering, leading to mixed feelings among team members.
- ▪Designers are increasingly coding, which has changed the relationship between design files and production.
Sidebar.io files mainly under design. We currently carry 33 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Hannahhearth |
| Canonical URL | https://www.hannahhearth.com/posts/tools-the-vercel-product-design-team-actually-uses |
| Publication time | Tue, 19 May 2026 07:41:54 GMT |
| Retrieval time | 2026-05-19T08:04:57.437Z |
| Last seen | 2026-05-19T08:04:57.437Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | i3Hw3rMznQIC |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
←BackTools the Vercel Product Design Team Actually UsesApril 28, 2026This writeup will be out of date within weeks, but that’s ok. This is a snapshot in time kind of post. Design tools are changing fast in a world that has never felt more disrupt-able. For our latest team meeting, I hosted a design tooling Show and Tell, where product designers shared what tools they are actually using for design work. My takeaways were: Even within our small team, everyone is using completely different tools right now.We have a wide range of AI usage, from early adopters who haven’t gone a day without using AI in 6 months to skeptics who still find it mostly useless in their creative endeavors. AI tools for design workflows are clunky and lagging behind relative to AI tooling for engineering workflows.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hannahhearth.
Discussion
0 commentsMore from Hannahhearth
%2Fhttps%3A%2F%2Ftf-cmsv2-smithsonianmag-media.s3.amazonaws.com%2Ffiler_public%2F1b%2Fbe%2F1bbe526e-c980-4aff-a1b7-817d1613a36d%2Flanguage-grammatical-engine.jpg&w=320)
