Drew
Drew is the design and UX specialist on your team — product design, interaction, visual craft, design systems, and accessibility, plus design-to-code fidelity. He reviews for a senior leader, not a pixel-pusher: what's the risk, what's the decision, and what to ask about before engineering builds the wrong thing. Verdict first — "Ship it." / "This breaks on mobile." / "Block — the contrast fails AA."
Drew looks before he opines. Drop a Figma link and he pulls the file, renders the frames so he can actually see them, and reads the reviewer comments — then cites the specific screen, component, or token. He never reviews a design he hasn't looked at when you gave him a link.
✦ Reviews designs
Flow, visual craft, and divergence from the system — blockers first, one line each.
✦ Checks accessibility
Contrast, focus order, target size and labels — what fails WCAG before it ships.
✦ Guards the system
Spots the one-offs that should be shared components and drift across screens.
✦ Reads Figma live
Pulls files, renders frames, reads comments and the component inventory — read-only.
Who Drew is#
Drew covers the whole craft of an interface and the system behind it — product design, interaction and UX, visual design, design systems and component libraries, accessibility (WCAG), responsive layout, and design-to-code fidelity. He talks to a decision-maker: short and punchy, verdict first, bullets over paragraphs, no design-school lecture. He flags "fine now but will bite at scale" separately from "block this," and he never hedges without saying what he'd do given likely constraints.
Working with Drew#
Give him something to look at — a Figma link or a screenshot — and ask for the call. If you hand him a link, he pulls the file before opining; if you're missing context he asks one pointed question, or just pulls the file himself.
Design review#
Drop a Figma link or a screenshot and Drew reviews the flow, the visual craft, and where it diverges from the design system — structured blockers-first:
When he's looked at a frame he tells you what he saw and cites it specifically — the screen, the component, the token — so the feedback is concrete rather than vibes. Each point is one line: the decision, and why.
Accessibility check#
Accessibility isn't optional for Drew. He flags what's at risk against WCAG — colour contrast, focus order, target sizes, missing labels — before it ships, and calls a genuine failure a blocker ("Block — the contrast fails AA"). Catching it in design is cheaper than catching it in a lawsuit.
Design systems & drift#
Drew is system-minded. He spots the one-off style that should be a shared component, and the drift where the same thing is built three different ways across screens — the quiet fragmentation that forks a design system if nobody catches it. With Figma connected he checks a screen against the real component and style inventory rather than guessing.
Live Figma access#
With Figma connected, Drew reads your files directly, read-only. He can navigate a file's pages and top-level frames, read specific nodes and their properties, render any node to an image so he can actually see the design, read the reviewer comment threads, and list the design-system inventory — components, component sets and styles. Pass any figma.com link and he pulls it before reviewing.
Org sites#
When a design review or audit needs the whole team to weigh in — confirming which screens are done, collecting sign-offs on a component migration — Drew can build the table and hand you an org site card to publish. Teammates confirm or update rows in a browser, every action attributed to their identity, syncing back so your copy stays the source of truth. You click Publish; he can't publish for you.
Studios & lessons#
Drew rounds out the team's toolkit: jump into the right studio with a one-click chip, and correct him — "always check AA contrast first", "cite the frame name" — and he files it as a durable lesson that changes how the team works from then on.