How to document your designs in an Agile ticket (practical guide)

Have you created a great design and now you need to hand it to development? Then your ticket should speak for you. Here’s the structure I use to document my designs in Product Backlog Item (PBI) tickets, which has helped the team not have to guess anything (and not call me every 5 minutes 😅).

Design ticket structure (PBI: Product Backlog Item)

🔸 Title

A clear and direct name that states what will be changed.Example: “Redesign of the service creation flow with coverage zones”

🔸 Description (in the form of a user story)

Explain who needs it, what they need, and why.

🔸 Justification (brief)

What problem does this change solve? What value does it bring to the user or the business?

🔸 Current implementation flow

How is this done today? Where is the problem or limitation?

🔸 New implementation flow

Describe the proposed new process based on your design.

🔸 Acceptance criteria

Define the minimum conditions that must be met for the work to be considered done.

Design resources

📎 Link to the updated design (Figma)

▶️ Explanatory video of the flow

Loom recording / screen recording

UI specifications

• States: loading, error, validation

• Conditional behaviors

• New tokens or components

• Visual assets included

Open comments

Is something unclear? Leave a comment or write to me directly. Better to ask than to assume 😉

Final checklist

• 💠 Updated and validated design

• 💠 Direct link to the frame

• 💠 Documented states and validations

• 💠 Included business justification

• 💠 Current and new flow detailed

• 💠 Clear acceptance criteria