FlowStatus

How it works

From Figma activity to a clear picture of flow

FlowStatus helps design leaders see how work moves through Figma: where it stalls, how capacity is used, and which conditions support better outcomes. Inputs are activity logs: actors, timestamps, action types, and names.

Jump to FAQ

01. Data in

Bring activity in. Keep design files where they are.

FlowStatus connects to Figma Activity Logs through an app your organisation owns. The scope is read-only. We keep a small set of fields: actors, timestamps, action types, and names of files, projects and teams.

Prefer a slower start? Upload a Figma activity CSV from Admin. Add a members CSV when you want seat utilisation and licence questions answered alongside flow.

  • ·OAuth with org:activity_log_read
  • ·First sync covers recent history; later syncs stay incremental
  • ·CSV path still available for Enterprise-restricted environments
FigmaActivity logsProcessClean · score · storeDashboard
ORGANISATION OVERVIEW62%Focus78%Momentum54%Iteration

02. Overview

One organisation view of how work moves

The intelligence overview shows Focus, Momentum and Iteration as the shared language for how work is flowing. Separately, planning metrics cover Capacity (how much concurrent work the team can sustain), Throughput (completions over a trailing window) and Speed (calendar duration from first to last activity on live projects).

Trends over months help you see whether conditions are improving after a reorganisation, a hiring wave or a process change. The aim is system health.

03. Drill in

Same metrics, scoped to where work lives

Open a team to see flow and load for that group. Open a project to inspect Focus, Momentum, Iteration and health for a single piece of work. Compare divisions when your organisation is structured that way.

These views answer operational questions design leaders ask: where attention is fragmented, which projects linger, which teams are carrying too much concurrent load. They are framed around teams and workstreams.

Teams
Full dashboard for one team
Projects
Health, flow and files
Divisions
Compare aggregates
OrganisationTeamsProjectsDivisions
CAPACITY30.8Concurrent load the team can sustainLICENCE USE18%Seats with little recent activity

04. Capacity

Plan load and question idle seats

Planning views estimate how much concurrent project load the organisation can sustain, how many projects completed in a trailing window, and how long live work tends to stay open. That helps when you need efficiency gains inside the headcount you already have.

With a members CSV, licence optimisation highlights seats with little recent activity so finance and design ops can reclaim or reallocate before renewal. Figures are operational signals. Confirm against your contract and Figma Admin.

Beyond Figma

Optional lenses when other tools matter

Some organisations also want visibility into discovery boards, design-to-code handoff, and where work stalls between tools. Those panels appear when matching data is available. The dependable foundation remains Figma activity and, where you add it, seats.

Privacy

Built around activity metadata

No Figma passwords. No write access to files. Revoke the connection in Figma whenever you need to.

No storage of designs, prototypes or canvas contents. Event payloads are reduced to the fields we need for metrics.

Processing sits under UK GDPR-framed terms. Hosted EU options and offline installs are available for stricter environments.

FAQ

Questions design leaders ask

Common questions about efficiency, stalls, KPIs, data and how to get started.

Book a walkthrough, or ask about pricing

Demos are arranged with us. There is no public product tour on the site. Enterprise customers are onboarded offline on purchase order and invoice.

Home · · Log in · © 2026 FlowStatus