Figma for product managers on Mac: FigJam roadmaps, shortcuts and voice help in 2026

Figma for product managers: FigJam first, design app second

Start by picking the right tool for the job. Figma's own product team uses FigJam for planning. Its blog describes a Gantt chart roadmap, a product vision board set before H2 planning, a Crazy 8's brainstorm, a retro template and a weekly sync file. It does not describe design-app work by product managers. That makes FigJam a good default for you. Open FigJam when the question is what to build and why. Open the design app when the question is how a screen looks, behaves or links to the next one.

Here is how a normal week can look. On Monday you open a FigJam file and sort ideas into a roadmap. On Wednesday you run the retro in the same file. On Thursday you open the design app, because a designer needs to show the new sign-up flow. Two tools cover three jobs. Switch only when the work changes.

Be careful with one assumption. The blog describes how one company's product team works, and parts of it date from the FigJam beta. Your team may plan in Notion, Jira or a slide deck. Copy the parts that fit your team, and skip the rest.

Roadmapping eats time in a few specific places. A 2020 survey by ProductPlan asked product managers where that time goes. ProductPlan sells roadmap software, and the survey gave no sample size. Read the numbers as direction, not measurement.

The biggest share, 27%, went to deciding which initiatives make the roadmap. Another 25% went to scoping and ordering them. Only 9% named editing visual elements. The hard part is choosing, not drawing boxes. Spend your FigJam time on the ordering step, and keep the styling short.

Install the Figma desktop app on your Mac

The desktop app suits most product managers on a Mac. Figma's guide says it offers the same features as the browser version. It also lets you develop plugins and widgets. It uses fonts installed on your Mac, without the font installer. That helps if your brand uses a licensed typeface.

Check your macOS version first. The app needs macOS 12 Monterey or later. It runs on Apple silicon and Intel Macs, and Figma optimizes for both. If your Mac runs an older system, use the browser version as a fallback.

1. Open the Apple menu > About This Mac and note your macOS version.
2. Download the Mac desktop app from Figma's download page.
3. Open the downloaded file and drag Figma into Applications.
4. Sign in, then open a FigJam file from your drafts.
5. Install any update the app offers. Support for older versions ends six months after release.

Read the full steps in How to install the Figma desktop app on Mac. If the app prompts you to update, do it before a planning session, not during one.

Keyboard shortcuts for Figma on Mac that save you time

Start with the shortcut panel. Press ⌃ ⇧ ? (Control, Shift and the question mark) and Figma lists the rest. Learn three shortcuts first. They cover most of the canvas work a product manager does.

• ⌘ + and ⌘ minus: zoom in and out of the canvas. Use them to move from a whole board to one sticky note.
• ⌥ Space: the keyboard box selection tool. Use it to select a group of layers without reaching for the mouse.
• ⌃ ⇧ ?: open the full shortcut panel. Check it when a shortcut in this guide does not match your version.

Two shortcuts we could not confirm. The Figma help page did not list redo or bring-to-front keys. Third-party cheat sheets disagree on them. Test both in the app before you rely on them.

Here is a quick drill. Open any FigJam board with a few sticky notes. Press ⌥ Space and drag a box over the cluster. Then zoom with ⌘ + until the cluster fills the screen. Repeat it twice and the motion sticks. Then try the same pattern on a frame in the design app. The full keyboard selection steps are on this page.

Roadmaps, vision boards and brainstorms in FigJam

The Gantt chart template is the one to start with. Figma's PM team uses it for roadmapping, including the roadmap for FigJam itself. Put one row per initiative, one bar per time window and one owner per row. Keep the same template each quarter, so people learn to read it fast.

A vision board comes before the roadmap. Use it to set priorities before H2 planning. Write the outcomes the team cares about, in plain words. Then sort each initiative under one outcome. An initiative that fits no outcome is a cut candidate.

The Crazy 8's brainstorm is short and fast. Figma's team sketches eight ideas for one problem in eight minutes. Run it like this. Put the problem at the top of a frame. Set a timer for eight minutes. Sketch eight ideas, one per box. Then vote and take the top two into design. If you want the timer on your Mac, ask Lazur to start it.

The retro template splits into two halves. Figma's PM team uses one split for product, engineering and design, and another for go-to-market teams. If sales or support joins your retro, give them a column of their own. Otherwise their notes get lost in the group.

The weekly sync file is the quiet one. Keep one shared FigJam file for the team. Duplicate last week's page at the start of each week. Move old pages into a single archive page. The common mistake is a new board for every meeting. After one quarter, nobody can find the board that matters. Create a frame to group each meeting inside one file instead.

Figma plan limits: what the free Starter plan covers

The Starter plan is free. It gives you one team with one folder and 3 files. Version history lasts 30 days. Professional removes those caps. It adds unlimited folders, unlimited version history and libraries for components, styles and variables.

Here is the trap. A product manager builds a roadmap, a vision board and a retro in three files. The next file has nowhere to go. Count your files before a planning cycle, not during it.

Paid seats come in types. Figma's pricing page lists Full, Dev and Collab seats. The prices we could read conflicted, so check the pricing page for current figures. Do not budget from a third-party list.

Why a big Figma file feels slow on a Mac

Mac users often say the same file runs smoother here than on Windows. A September 2024 thread in the Figma community forum reports that. It is one user's account from 2024, not a benchmark, so treat it as a clue.

Figma staff give a different cause. In the same thread, a staff reply ties lag to the browser version's per-tab memory limit. The reply also names these sources of load.

• Large content across many pages. Split a huge file into a few smaller files, one per project.
• Many hidden layers. Delete what you no longer need, or move it to an archive page.
• Stacked masks and effects. Remove shadows and blurs you stacked on one layer and no longer need.
• The browser tab limit. If you use the browser, close other heavy tabs before you open the file.

Edge case: a teammate on an older install may see the file differently. The desktop app asks for updates when a newer version exists. Ask everyone to update before a shared review, so the review does not turn into a version debate.

Restore earlier versions and share Figma work safely

Version history is your safety net, and on Starter it has a short window. Starter keeps 30 days. If a change must survive longer, save a copy of the file before the window closes. When a stakeholder needs an image rather than the live file, export a frame as PNG.

To roll back, follow how to restore an earlier version in Figma on Mac. For outside reviewers, read how to share a file with view access first. View access gives feedback without edits.

The mistake to avoid is sharing an edit link with the whole company. Start with the people who must change the file. Then widen the audience to view only.

Lazur on your Mac while you work in Figma

Lazur is a voice assistant that lives in the notch of your Mac. Hold ⌥ ⌘, ask about anything on screen, and Lazur answers out loud. It listens and looks at the screen only while you hold the shortcut.

Ask where something is, and Lazur draws a circle and a label around it. That helps when a toolbar has grown and a tool hides behind another. Ask how to do something, and Lazur guides you one click at a time. It waits for each click before it moves on.

Example: hold ⌥ ⌘ and ask, where is box selection in this toolbar? Lazur circles the tool and waits. You make the click. That is the whole loop, and you stay in control of the file.

Dictation runs on fn. Hold fn to dictate clean, formatted text at the cursor in any app. Dictate sticky note text, retro comments or the summary of a weekly sync. A personal dictionary helps with product names your speech tool gets wrong.

Research runs in Lazur's own Chrome tabs through the Lazur for Chrome extension. Ask it to research how other product teams run retros. It comes back with a summary and a report you can read after the meeting.

Everyday tasks work too. Ask Lazur to remind you to review the vision board on Friday. Or ask it to add a Calendar event for the retro. It works with Apple Reminders and Calendar.

What Lazur does not do inside Figma

Lazur does not click buttons, edit files, or operate other apps for you. It is not a plugin or add-in for Figma. It works beside the app, by looking at your screen while you hold the shortcut.

The common mistake is expecting Lazur to draw the roadmap for you. It guides. It does not do the work in the file. Use it for the fiddly parts: where a tool is, what a shortcut does, and what to type next.

On data, audio and the screenshot go to AI providers so they can answer you. They are not stored. Content is never used to train AI models. Decide what is on screen before you hold the shortcut.

Edge cases and error states product managers miss in Figma

Product managers review the happy path. Designers draw it first. The gap sits in the states nobody draws first. Ask for the empty state, the error state, the loading state and the longest text string. Put each one in its own frame on the same page, so the review takes one scroll.

Worked example. A checkout flow needs an empty cart, a failed payment, a slow network and a success screen. Put all four in one row of frames. Read them left to right, the way a customer moves through them.

The mistake is reviewing only the prototype. A prototype shows the path someone linked, and it hides any state nobody connected. Read the frames, not only the clicks. For a longer checklist, read Figma designs miss edge cases and error states.

Pricing and trials before you commit on Mac

Lazur includes a Pro trial, and it needs no credit card. The trial starts when you first open the app. Check the pricing page for the current Pro and Power plans and their AI action limits.

Figma's Starter plan is free, and its pricing page lists unlimited drafts on it. Before you pay for seats, compare the plans on Figma's plan page. Confirm which seat type your team needs before you buy.

Want the voice layer on your Mac? Start at the download page. Figma works without Lazur, so you can run the steps in this guide first.

Mistakes product managers make with Figma on Mac

• Designing a roadmap in the design app. Use FigJam for roadmaps and keep the design app for screens.
• Letting one file grow across many pages and hidden layers, then blaming the Mac. Split the file first.
• Assuming version history lasts forever. On Starter, it lasts 30 days.
• Skipping updates. Old installs get a prompt, and support for old versions ends six months after release.
• Trusting a shortcut list you have not tested. Check the shortcut panel with ⌃ ⇧ ? first.

Next steps for Figma on your Mac

Work through these in order. Each one takes a few minutes.

1. Check your macOS version under Apple menu > About This Mac.
2. Install the desktop app, then open a FigJam file and run one Crazy 8's round.
3. Learn ⌘ +, ⌘ minus and ⌥ Space until they feel automatic.
4. Count your files against the Starter limit before the next planning cycle.
5. Hold ⌥ ⌘ and ask Lazur one question about the screen you are working on.