---
title: "Design project management with Claude on the board · Projectify"
description: "Design project management for product and UX teams: Figma files read into tasks, research notes sorted into findings, and Claude keeping the handoff in order."
url: https://projectify.si/for/design-teams
---

# Design project management that reads your Figma files.

> UX design project management that starts where the work lives. Figma files are read into tasks, research sessions become findings, and Claude writes the spec so engineers build from states and edge cases, not screenshots.

Start free: https://app.projectify.si/signup. A month of Premium free, no card. Agents never take a seat.

## Where a design team’s good work gets lost.

- "Our research lives in a folder nobody opens after the readout." Session notes and transcripts are read as they land. Claude groups them into findings, each linked to the task it should change.
- "Engineers keep building from an old frame." Read the Figma file into the task and the frame sits next to the spec and the acceptance notes, so the build card and the design point at the same thing.
- "Critique ends with a page of opinions and not one decision." Drop the critique notes into chat. Claude separates decisions from open questions and records each decision on the task it belongs to.

## A design ops partner for the whole team.

- **Turns sessions into findings.** Transcripts, notes and survey exports are read as they arrive. Ask what users said about a screen and get the quotes behind it. For example: Promo code: 3 of 8 missed it, 2 thought it was required.
- **Hands off the same way every time.** Show Projectify how your team hands a design to engineering once. It becomes a workflow with checks where the designer and the engineer look. For example: Address form: 4 of 6 steps done, the spec check waits for Ines.
- **Writes the specs nobody wants to.** States, error messages, edge cases and copy decks: Claude takes the next ready task, claims it, and leaves the draft for a designer to correct. For example: Spec for the address form: 9 states, 4 error messages.
- **Keeps the design system backlog.** Components get their own section on the project, with requests, owners and the Figma file for each. The outline view shows what depends on what. For example: Button variants: 3 requests, one blocks the checkout work.

## The board it starts with

- Statuses: Discovery, Designing, Design critique, Iterating, Ready for build, Shipped
- Fields: Product area, Figma file, Research round, Priority, Engineer, Designer
- Views: Board, Table, Timeline, Outline, Cards
- A workflow, Design handoff: Read the Figma file into the task → List states and edge cases → Write the spec → Designer checks the spec (a person checks) → Walkthrough with engineering → Engineer accepts (a person checks)

## Before the team switches boards.

### Does Claude design the screens?

No. Claude reads, sorts and writes around the design: findings, specs and critique notes. Designers make the calls, and every change Claude makes is signed and can be undone.

### Our engineers live in Azure DevOps or GitHub. Do tickets move?

Azure DevOps syncs both ways, and GitHub branches and pull requests show on the task, so design and build share one thread.

### Can we run a usability study from it?

Plan it here: the script, participants as cards, notes into Files. Run the sessions in the tool you use now, and Claude turns what you bring back into findings.

### Is this real UX design project management or a to-do list?

The starting board is shaped to design work: discovery, critique and handoff, with fields for the Figma file and research round. Rename any of it.

Related: [Creative teams](https://projectify.si/for/creative-teams.md), [Product management](https://projectify.si/for/product-management.md), [Web development](https://projectify.si/for/web-development.md), [SaaS](https://projectify.si/for/saas.md), [Sprint planning](https://projectify.si/for/sprint-planning.md). Every kind of work: [For your work](https://projectify.si/for.md).