The product map shows the main features of your project and how they connect. Open one to see its sub-features or its user flow.
Specsight draws the map during analysis and redraws it on every sync. The canvas is read-only.
Open the map
In the project rail, click Product map.
Move around
- Pan — drag the canvas background
- Zoom — scroll, or use the zoom controls
- Fit to view — recentre so the whole map is visible
- Fullscreen — hide the rail, Esc exits
- Hover a feature — its connected features stay raised, the rest dim
- Hover a connection — read every connection between the two features, each with its type
- Search features — find a feature or sub-feature by name, matches stay raised and the rest dim
Connection types
Connections between features carry one of nine types:
- Leads to — one feature's output feeds into another
- Triggers — an action in one starts another
- Depends on — one requires another to function
- Shares data — two features exchange data
- Authenticates — one handles sign-in for another
- Notifies — one sends alerts to another
- Configures — one provides settings for another
- Extends — one adds capabilities to another
- Validates — one checks another's rules
Drill into a feature
Click a feature on the map. If it has sub-features, its sub-feature map opens, showing how they connect. Otherwise its user flow opens.
Features with a dotted outline are outside this feature, linked to its sub-features. Click any box to open it.
A user flow shows the path someone takes through one feature, from start to finish. Specsight builds it from that feature’s own scenarios.
Zoom, pan and fullscreen work the same on every level. Search is on the maps only.
What the boxes mean
Each box is one of six kinds. Click any box and the panel names its kind.
| Box | What it means |
|---|---|
| View | A page, modal or panel someone is on |
| Decision | Something the product checks, with the answers on the arrows leaving it |
| System | The product acting on its own |
| Outcome | What the product shows or produces when a journey ends |
| External | Something outside the product, like an email inbox or a payment provider |
| Waiting | Someone is waiting for something to happen |
Start, End and Error badges mark where a journey begins, finishes, or is blocked.
Read the arrows
- Hover an arrow — read the action that moves someone along it, like “clicks Check out”
- An arrow leaving a decision — carries its answer, like “expired”, so branches read at a glance
- A dashed arrow — the step happens on its own, with nothing for the user to do
See the scenarios behind anything
Click any box or arrow to open the detail panel. It lists the scenarios behind what you picked, each with its full Context, Action and Outcome. Click one to open that scenario in the spec.
Actions that keep someone on the same page, like filtering or favouriting, have no arrow of their own. They are listed in the panel of that page’s box.
One scenario can sit behind several parts of a flow, and one box can rest on several scenarios. Some parts cite none, and the panel says so.
A feature with no flow drawn yet shows No flow yet until Specsight’s next analysis.