figjamcreativeAPP-027

The FigJam Product Team Facilitator

#figjam#whiteboard#workshop#facilitation#product-team#figma

Aha Moment

“What was the moment this product clicked?” —

Identity

A product manager, design lead, or team facilitator at a product company who uses FigJam for team whiteboarding because their team already lives in Figma. They chose FigJam over Miro because the context switch is lower — design references, wireframes, and working files can be linked or embedded directly from Figma. They run planning sessions, retrospectives, decision workshops, and design crits on FigJam. Their team knows how to use it. This matters more than they expected it to.

Intention

What are they trying to do? —

Outcome

What do they produce? —

Goals

→Run collaborative sessions where their cross-functional team participates from the start
→Connect whiteboard work to the design files and documentation it references
→Capture session outputs in a format that's useful after the session ends

Frustrations

—Feature depth that trails Miro for advanced facilitation — fewer built-in templates,
—weaker voting and timer tools
—The occasional teammate for whom "open a FigJam" is a different level of friction
—than it is for the design team members
—Output organization that requires manual cleanup — the board after a session doesn't
—naturally produce a summary without someone doing the work
—Linking to Figma files that works in one direction (FigJam to Figma) better than the other

Worldview

The best workshop tool is the one the team already knows how to use
Facilitation quality matters more than template quality
The output of a workshop is a decision, not a board

Scenario

It's Monday. The team is doing a feature prioritization session. Ten people on the call — 2 engineers, 2 designers, 1 data analyst, 2 PMs, a marketing lead, and the VP of Product. They're using a FigJam board with an impact/effort grid. Each person has 5 sticky notes — features they're advocating for. They'll vote after everyone has placed their items. The facilitator is managing the session from their own FigJam view, watching the board populate, and already noting which two items are going to create the most discussion.

Context

Runs 2–6 FigJam sessions per month. Uses FigJam for planning, retros, journey mapping, and feature prioritization. Has a template library built from sessions that worked. Works with a team of 6–20 where design and product members are active, and engineering and other stakeholders participate with varying familiarity. Uses FigJam's sticky notes, shapes, connectors, and voting widgets. Embeds Figma frames into FigJam for design crits. Shares FigJam links in Notion pages for post-session documentation.

Impact

→Timer and voting features that match Miro's facilitation toolkit close the gap
→that currently makes FigJam a second choice for users who facilitate externally
→AI-generated session summary that synthesizes sticky notes into grouped themes
→removes the manual post-session cleanup that currently takes 20–40 minutes
→Bidirectional Figma linking that lets FigJam reference and update Figma files
→deepens the ecosystem integration that FigJam's primary differentiation is built on
→FigJam templates contributed by the Figma community with facilitation guides
→embedded in the template reduce the session prep time for common workshop types

Composability Notes

Pairs with `figma-primary-user` for the design team's full creative workflow from ideation to production. Contrast with `miro-primary-user` for the Figma-ecosystem vs. dedicated-whiteboard-tool facilitation choice. Use with `linear-primary-user` for the FigJam planning session-to-Linear roadmap workflow.