In fast-moving product teams, clear and timely feedback is everything. But when it comes to design tools like Figma, many product managers (PMs) feel like outsiders—uncertain where to click, what to comment on, or how to participate without stepping on toes.
Good news: Figma is built for collaboration, and with a few practical habits, you can give feedback that’s clear, constructive, and doesn’t disrupt the design flow.
This guide is for product managers who want to contribute meaningfully—without derailing timelines or confusing designers.
🧭 Understand Your Role in the Design Flow
Your job as a PM isn’t to pixel-push. It’s to ensure that:
- Design decisions align with product goals
- User stories are represented accurately
- Business and tech constraints are considered early
- The team stays aligned on what’s being built
Figma lets you support these goals in real time, without needing a design background.
👀 Learn to Navigate Figma Without Fear
You don’t need to be a designer to use Figma confidently.
Here are a few navigation tips for PMs:
- Use View-only mode to avoid accidental edits
- Use the left sidebar to explore pages and layers
- Tap “Present” to view flows and prototypes
- Hit “C” to comment anywhere on the canvas
- Use the section labels (purple frames) to see which parts belong to which features or flows
💡 Pro Tip: Ask your design team to set up a “Start Here” page that orients stakeholders.
💬 Commenting Best Practices
The most valuable thing you can do in Figma is leave smart comments.
✅ DO:
- Be specific: “This button label might be clearer as ‘Continue’ instead of ‘Next’.”
- Ask questions: “Should this dropdown be pre-filled for returning users?”
- Point out business logic: “This step might not be required anymore after the new backend update.”
🚫 AVOID:
- Vague feedback: “Doesn’t feel right”
- Over-prescriptive notes: “Make it blue and add a shadow”
- Dropping comments without context
💡 Use @mentions to assign comments and keep the loop tight.
🔁 Create Feedback Loops, Not Feedback Bombs
Surprising your designer with 27 comments the day before handoff? That’s a feedback bomb.
Instead, establish a rhythm:
- Daily async reviews: 5–10 min in Figma
- Weekly design syncs: Review work-in-progress as a team
- Structured feedback windows: e.g., “Leave comments by EOD Wednesday”
If your team uses Jira, Linear, or Notion, link relevant Figma frames directly into tickets for tighter loops.
🗂️ Know What Stage the Design Is In
Designers often work in progressive stages—from wireframes to high-fidelity mockups to production-ready components.
Before commenting, ask:
- Is this a concept, or is it ready for implementation?
- Are the flows complete, or still being explored?
- Is this version linked to a current sprint?
Figma’s branching, versions, and labels help designers signal what’s ready for feedback—and what’s still cooking.
🧩 Leave Feedback on the Right Level
Design work spans multiple levels. Your comments should match the level:
| Level | PM Feedback Focus |
|---|---|
| Flow / UX | Does the user journey make sense? |
| Microcopy / Labels | Is this copy clear and aligned with UX tone? |
| Visual hierarchy | Is the emphasis in the right places? |
| Components / Reuse | Are consistent patterns being used? |
Avoid diving into pixel-level spacing or color choices unless it has direct product implications (like accessibility).
🤝 Be a Partner, Not a Backseat Driver
The best PMs in Figma don’t micromanage—they advocate.
They:
- Share user insights from research
- Surface edge cases early
- Clarify business constraints
- Collaborate on naming, flows, and onboarding UX
They treat Figma like a shared product canvas, not a design playground.
🧠 Tips to Boost Your PM Figma Game
- Use Dev Mode: It’s not just for engineers—it gives clarity on design specs.
- Keep track of feedback: Resolve your own outdated comments.
- Request access wisely: If you’re unsure, ask the designer before branching or editing.
- Stay current: Bookmark important files and subscribe to file updates.
✅ Quick Reference: PM’s Figma Feedback Checklist
- Did I view the latest version or branch?
- Did I ask the designer if they’re ready for feedback?
- Are my comments actionable and contextual?
- Am I clear on product goals and constraints?
- Have I tagged the right people?
Figma is a team sport—and product managers play a key role in shaping how ideas become experiences.
By giving feedback that’s timely, relevant, and respectful of the design process, you build trust—and ship better products.
➡️ Next up: “How to Build a Design Audit Checklist for Your Figma Files”
Designilo 