The design team

When to call this team

Design is the team for everything users see and everything your brand quietly implies before a word is read. Reach for it when:

• The product grew feature by feature and now looks like five different apps.
• Sign-ups land on the same screen, click around, and leave, and you cannot say why.
• Your deck, your site, and your product each use a different shade of your own brand.
• A launch needs visuals that carry a story rather than decorate a page.
• You need real art direction for AI-generated photography that does not look AI-generated.

The common thread is intention. Each of these is a place where the product looks accidental, and design is how it starts looking deliberate.

Who shows up

The design orchestrator runs a tight bench of craft specialists and pairs them to the job:

• UI designer, who builds visual systems and component libraries to the pixel.
• UX architect, who turns those into CSS systems and implementation guidance developers can use.
• UX researcher, who grounds decisions in observed behavior rather than taste.
• Brand guardian, who holds identity consistent across every surface.
• Visual storyteller, for narrative and multimedia design.
• Image prompt engineer, who writes photography-grade prompts for AI image generation.

Three worked examples

"Unify this interface." The UI designer audits your current screens and pulls out what should become the system: the type scale, the spacing, the color roles, the recurring component patterns. Back comes a design-system starter with components ranked by how often they actually appear, so you build the load-bearing ones first. The UX architect attaches implementation notes to it, which is what lets the system survive contact with the codebase instead of dying in a Figma file.

"Why do users stall on this screen?" The UX researcher walks the flow as a first-time user would, marks the friction against established usability patterns, and returns findings ordered by likely impact. Each finding arrives attached to a concrete revision, not a design principle, so you can act on it the same day rather than interpret it.

"Make the launch assets feel like one campaign." The brand guardian sets the boundaries first, the palette, the type, the voice, so everything downstream stays coherent. Then the visual storyteller builds the asset narrative across formats, from the announcement graphic to the spine of the deck. What returns is a small system that holds together, not a folder of one-offs that happen to share a logo.

What they need from you

Whatever already exists: screenshots, the live site, brand guidelines even if they are out of date, and the audience definition sitting in your profile. Connecting Figma moves design work from MEDIUM to HIGH evidence, because the team then reads real files and component states instead of working from your description of them.

Hand-offs

Design sits between the teams that decide what to build and the ones that ship it. It takes user problems from product (chapter 12), sends finished campaign assets to marketing (chapter 10), and returns implementation-ready specifications wherever engineering picks up next. Visual deliverables meant to be shared as documents land in Drive (chapter 25).