Unified Figma + FigJam File Structure
One piece of feedback I've consistently run into as a designer is the separation between Figma files and FigJam files. While they're closely connected in the design process, they're treated as completely separate artifacts in the file structure.
In practice, many designers use a single file as the source of truth for a project. Research, workshops, journey maps, IA exercises, brainstorming sessions, requirements, explorations, wireframes, design concepts, and final designs are all part of the same workflow. Today, that work often gets fragmented across multiple files, making it harder to find information, maintain context, and keep project history connected.
I'd love to see an option where FigJam and Figma coexist within the same file structure. For example, when creating a new page, users could choose between:
- Design Page (Figma)
- Whiteboard Page (FigJam)
Both page types would live within the same file, similar to how pages already exist today.
Benefits could include:
- A single source of truth for project work
- Better discoverability and searchability across research, workshops, and designs
- Reduced file sprawl and duplicate project structures
- Easier onboarding for teammates trying to understand project context
- Stronger connection between ideation and execution
- Better project documentation and historical traceability
For larger organizations, it's common to maintain parallel Figma and FigJam files for every initiative. Over time this creates significant overhead in organizing, naming, linking, and maintaining related files. Allowing both experiences to exist within a unified file structure would create a more seamless end-to-end workflow and better reflect how many design teams actually work.
Curious if others have experienced similar challenges and whether this is something the Figma team has explored.