Most businesses don't operate inside one clean system. Work is spread across tools, spreadsheets, emails, and manual steps.
This step captures that reality.
Step 1: List the Official Systems
Start with the systems leadership believes run the business.
For each, record:
- System name
- What it's used for
- Which team owns it
Example: Salesforce – used by sales to track deals and contacts.
Step 2: Identify the Tools People Actually Use
From end-user interviews, list what people say they use daily.
Pay attention to:
- Spreadsheets
- Shared folders
- Email threads
- Personal tracking systems
- Notes apps or docs
Simple example: Finance officially uses an ERP but tracks approvals in a shared Google Sheet.
Complex example: Customer data lives in the CRM, but support decisions rely on emails, Slack messages, and manual notes copied into tickets.
Step 3: Map Systems to Tasks
For each major task, write down:
- Which tool starts the task
- Which tools are used in the middle
- Where the task ends
This shows how data moves (or doesn't move).
Step 4: Identify Data Gaps and Breaks
Look for:
- Double entry
- Copy/paste between systems
- Manual exports or downloads
- Data that lives only in someone's head
These are early signs of automation and AI opportunities.
Step 5: Flag System Friction
For each system, note:
- Common complaints
- Slow steps
- Missing features
- Workarounds people rely on
Focus on how it's used, not judging the tool itself.
Step 6: Confirm Ownership and Access
For each system, confirm:
- Who owns it
- Who can approve changes
- Who has access to the data
Unclear ownership is a risk and a bottleneck.
What You Should Have Now
✅ Tool & System Inventory List with:
- System name
- Owner
- Purpose
- Tasks supported
- Known friction points
✅ Task-to-system mapping notes
✅ List of unofficial tools and workarounds
Quality Check
- Inventory reflects real usage, not org charts
- Shadow tools are included
- Each system has a named owner
- Data handoffs and breaks are visible
- Anyone reading can see where work truly happens
Next Step: With your systems mapped, you're ready to capture where work fails and gets redone.