How it works
From Figma activity to a clear picture of flow
FlowStatus turns your team's Figma activity into a clear picture of flow for design and product leaders: where work will stall, who is overloaded, and which conditions support better delivery. Inputs are activity logs: actors, timestamps, action types, and names.
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. New to the logs? Read the Figma activity audit guide.
- ·OAuth with
org:activity_log_read - ·First sync covers recent history; later syncs stay incremental
- ·CSV path still available for Enterprise-restricted environments
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. That gives you a read on 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 and product leaders ask: where attention is fragmented, which projects linger, which teams are carrying too much concurrent load. They are framed around teams and workstreams.
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. Treat the figures as operational signals, and confirm them against your contract and Figma Admin.
Beyond Figma
Optional views when other tools matter
Some organisations also want visibility into discovery boards, design-to-code handoff, AI adoption, and where work stalls between tools. Upload the admin exports you already have and FlowStatus adds a panel for each, joined to your Figma activity.
These are optional, upload-based sources: they do not change Focus, Momentum or Iteration. Figma activity is still the foundation. Add seats when you need licence questions answered.
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 leaders ask
Common questions about efficiency, stalls, KPIs, data and how to get started.
Book a walkthrough, or ask about pricing
We will arrange a walkthrough with you. Enterprise customers are onboarded on purchase order and invoice.
Home · Design Telemetry Benchmark · Methodology · Figma activity audit guide · · Log in · © 2026 FlowStatus