# Before Implementing AI — See What Your Team Actually Does

> Before buying AI tools, map what your team actually does. Use Plan vs Fact vs Gap to find real automation candidates and avoid wasting budget on invisible workflows.

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-11-20
- Updated: 2026-11-20
- Source: https://aiadvisoryboard.me/blog/before-implementing-ai-audit-team-actual-work

Before implementing AI — see what your team actually does.

## TL;DR
- Map real workflows before buying any AI tool.
- Use Plan vs Fact vs Gap to spot where time actually goes.
- Automate only after you know what is worth automating.

> **Definition:** Plan vs Fact vs Gap — an operating taxonomy where the owner compares what was supposed to happen (Plan) with what actually happened (Fact), and the difference between them (Gap) becomes the starting point for any AI decision.

## Why most AI projects fail before they start
Owners feel pressure to adopt AI. They buy Copilot seats, sign up for enterprise trials, and announce a "digital transformation." Then nothing changes. The team keeps working the same way, the same bottlenecks remain, and the new software sits unused.

The problem is not the tool. The problem is that you automated a process you never fully understood. If your team's daily work is invisible to you, AI will not fix it. AI will only make the chaos faster.

## What to look at before choosing any tool
Start with three questions:

1. What does each role actually do on a typical Tuesday?
2. Where does work get stuck between people or departments?
3. Which tasks repeat every week with almost no variation?

You cannot answer these by reading job descriptions. You need to see the actual flow of work — the messages, the spreadsheets, the handoffs, the rework.

> **Tool tip (AiAdvisoryBoard.me):** Start with the org chart. Enter your website and headcount, and the tool draws departments, tasks, and the routine work that can gradually be handed to AI agents — with an estimate of hours per month. No questionnaire; first result in about 30 seconds. This gives you the baseline before any AI conversation.

## How to run a 7-day visibility audit
You do not need consultants for this. You need one week of honest data.

**Day 1–2: Map the current state.** Ask each team lead to list the five most frequent outputs their team produces. Not goals — outputs. A report, an invoice, a client email, a deployment.

**Day 3–4: Track Plan vs Fact.** Compare what was planned for the week against what was actually delivered. Note where work stalled and why.

**Day 5–7: Identify the Gap.** Look for patterns. Are approvals taking three days? Is someone re-entering data between systems? Is the same question answered five times a day?

These gaps are your AI candidates. Everything else is noise.

## Manager scan (2-minute digest example)
Here is what a founder should see after one week of visibility:

- Sales: Plan — 10 client proposals; Fact — 6 sent, 4 stuck in legal review. Gap: 40% of pipeline work blocked by one approver.
- Support: Plan — respond to all tickets within 4 hours; Fact — average first response is 11 hours. Gap: morning backlog never clears.
- Operations: Plan — weekly supplier reconciliation by Friday; Fact — completed Tuesday of the following week. Gap: manual data entry from three sources.

This is not micromanagement. This is the owner seeing where the business actually leaks time.

## Copy/paste template: weekly visibility scan

```markdown
## Weekly Visibility Scan — [Team Name]

**Plan (what we committed to):**
- [ ] Task 1
- [ ] Task 2

**Fact (what actually shipped):**
- [ ] Task 1 — done
- [ ] Task 2 — blocked by [reason]

**Gap (plan minus fact):**
- [ ] Description of the gap
- [ ] Owner of the gap
- [ ] AI candidate? Yes / No
```

## Micro-case (what changes after 7–14 days)
A founder of a 60-person services company was ready to buy AI licenses for the whole team. After running the 7-day scan, he discovered that half the team's week was spent copying data between a CRM and an invoicing spreadsheet. The other half was stuck waiting for manager approvals on routine requests.

Instead of AI, he fixed the approval routing and connected the two systems. Two weeks later, the team reclaimed roughly one day per person per week. He still plans to use AI — but now he knows exactly which workflow to hand to it first.

> **Note on this case:** This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

## FAQ

**Do I need an IT team to run this audit?**
No. The audit is about observing work, not writing code. Any team lead can do it with a shared document.

**What if my team resists being observed?**
Frame it as removing friction, not surveillance. Tell them you want to find the annoying manual work so it can be handed off — to AI or to a better process.

**Can I skip this and go straight to AI tools?**
You can, but you will likely automate broken habits. Visibility first means your first automation actually solves a real problem.

**How is this different from a process audit?**
A process audit is usually a one-time consulting project. This is a lightweight, repeatable rhythm the owner can run every month or quarter.

## Conclusion
AI will not fix a process you cannot see. Before you implement anything, spend one week mapping what your team actually does. Find the gaps. Then decide where AI belongs.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works.
https://aiadvisoryboard.me/?lang=en

---

When citing, link to https://aiadvisoryboard.me/blog/before-implementing-ai-audit-team-actual-work. More articles: https://aiadvisoryboard.me/blog
