What is HEIDI Manual Map?
HEIDI Manual Map is a versioned graph of application pages, elements, and navigation flows. Operators capture structure via the Chrome extension Manual Mode; reviewers approve diffs to merge discoveries into the shared map. HEIDI uses this map to guide users step by step through internal tools.
Capabilities
What you can do with HEIDI
Chrome extension capture
Manual Mode in the extension records pages and flows as operators work — no separate documentation project.
Diff review workflow
New discoveries arrive as pending diffs. Reviewers approve or reject pages and routes before they join the map.
Pages, elements, and flows
The map models page nodes, UI elements, and the routes between them — not just screenshots.
Versioned team map
Each project keeps a versioned map so guidance stays aligned as applications change.
Powers voice and chat guidance
Once approved, the map feeds HEIDI's navigation skills — highlight fields, walk through menus, explain next steps.
Use cases
Where teams apply HEIDI
Real workflows that benefit from visual design, automation, and governance.
Onboard a new ERP screen
Capture the screen in Manual Mode, approve the diff, and HEIDI can guide the next hire through it.
Approve a new navigation route
Review the proposed route between two pages before it becomes part of the shared map.
Highlight where to enter a PO number
With map context, HEIDI points to the correct field on the form the user is viewing.
Walk through contractor onboarding
Multi-page flows in the map let HEIDI guide each step without the user hunting menus.
Keep map current after a UI change
New Manual Mode sessions propose diffs; reviewers merge only what is still accurate.
How it works
From chaos to clarity in 4 steps
Capture in Manual Mode
Operators use the Chrome extension while working; HEIDI records pages and navigation.
Propose a diff
New pages, elements, or routes appear as pending diffs with explanations and risk flags.
Review and approve
Reviewers approve or reject each page and route — governance before the map grows.
Merge into the team map
Approved diffs update the versioned graph visible to the whole project.
Guide users via HEIDI
Voice and chat assistance use the map to navigate, highlight, and explain the next step.
Avoid these
Common mistakes (and how to avoid them)
Documenting UIs in static PDFs only
Static docs drift from production UI and cannot power interactive guidance.
Grow a live navigation map from Manual Mode capture with reviewed diffs.
Auto-merging every extension capture
Unreviewed map changes introduce wrong routes and unsafe guidance.
Keep a human review step for pages and routes before they join the shared map.
Diff review and governance
Manual Map is deliberately not fully automatic — accuracy matters for operational guidance.
Each capture session can propose new pages and routes. Reviewers see explanations and risk flags, then approve or reject individually. Only approved structure becomes part of the map HEIDI uses for navigation.
Pair Manual Map with screen-aware voice for guided walkthroughs, or Assistance Hub for the full operational surface.