# What a 7-Day Diagnostic Actually Produces — Sample Artefacts for Founders

> A 7-day diagnostic produces four concrete artefacts — an org chart, a routine map, a Plan vs Fact vs Gap report, and an automation candidate shortlist — so founders can see where AI actually fits…

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-11-18
- Updated: 2026-11-20
- Source: https://aiadvisoryboard.me/blog/what-a-7-day-diagnostic-produces-sample-artefacts

Before you buy AI subscriptions or launch a pilot, you need to see what your team actually does. Most founders operate on a plan that exists in their head, while the team works on something else entirely.

## TL;DR

- A 7-day diagnostic produces four concrete artefacts: an org chart, a routine map, a Plan vs Fact vs Gap report, and a shortlist of automation candidates.
- The output is not a strategy deck; it is a working baseline you can act on immediately.
- You decide where to apply AI only after you see the gap between what should happen and what is happening.

> **Definition:** Plan → Fact → Gap — a visibility taxonomy that compares what was planned (Plan), what the team actually delivered (Fact), and the difference between them (Gap).

> **Definition:** Org chart — a department-by-department map of roles, recurring tasks, and routine work that can gradually be handed to AI agents.

> **Definition:** Automation candidate shortlist — a prioritised list of workflows ranked by time spent, error rate, and feasibility of AI handoff.

### What the diagnostic covers in seven days

Day 1–2: Org chart and department task inventory.
Day 3–4: Routine mapping and time estimates for repetitive work.
Day 5: Plan vs Fact vs Gap report across key functions.
Day 6–7: Automation candidate shortlist and next-step recommendation.

### Artefact 1: The company org chart with tasks

The first artefact is not an org chart in the HR sense. It is a working map: departments, roles, and the recurring tasks each role owns. You mark which tasks are routine, which require judgment, and which are already being handled informally by AI without your knowledge.

This is the baseline. Without it, any AI rollout is a guess about which department needs help most.

> **Tool tip (AiAdvisoryBoard.me):** The diagnostic starts with building your company's org chart: enter your website address and headcount, and the tool draws departments with tasks, marks routine work that can gradually be handed to AI agents, and estimates hours per month. No questionnaire; first result in about 30 seconds. See how the org chart view works at https://aiadvisoryboard.me/?lang=en

### Artefact 2: The routine map

The second artefact lists every repetitive operation across the company: invoice entry, meeting notes, status chasing, report compilation, data copying between systems. For each operation you capture frequency, who does it, and roughly how many hours a month it consumes.

This is where most founders discover that their team spends a significant share of its week on work that does not require human judgment — only human presence.

### Artefact 3: Plan vs Fact vs Gap report

This is the core output. You take a function — for example, sales operations or client onboarding — and compare three columns:

- Plan: what the founder expects to happen weekly.
- Fact: what the daily reports and async updates actually show.
- Gap: where work stalls, duplicates, or disappears.

The gap is where AI belongs — not in the parts of the business that already work, but in the parts where the plan and reality diverge.

### Artefact 4: Automation candidate shortlist

The final artefact is a short list — usually three to five workflows — ranked by impact and implementation effort. Each candidate includes the current owner, the time consumed, and the proposed AI handoff pattern (assist, draft, or autonomous with human review).

This is not a vendor recommendation. It is a decision document you can take to your team or to an external partner without starting from a blank page.

## Manager scan (2-minute digest example)

Here is what the diagnostic output looks like when it reaches the founder's desk:

- Sales: Plan — 10 new demos booked weekly. Fact — 6 booked. Gap — 4 demos lost to manual CRM entry and follow-up delays.
- Operations: Plan — vendor invoices processed within 48 hours. Fact — average 9 days. Gap — manual 3-way matching and email chasing.
- Support: Plan — first response under 4 hours. Fact — 11 hours during peak days. Gap — repetitive ticket triage that could be drafted by AI.
- Marketing: Plan — weekly campaign report every Monday. Fact — delivered Wednesday or Thursday. Gap — data pulled manually from three tools.

Each gap has an owner and a suggested first automation. The founder does not need to micromanage; the artefacts make the problem visible.

## Micro-case (what changes after 7–14 days)

A founder of a 120-person services company ran the diagnostic because the leadership team kept saying everything was under control while delivery dates slipped. The org chart revealed that two operations managers were spending most of their week copying data between a project tool and an invoicing system. The Plan vs Fact vs Gap report showed that the planned weekly delivery review was happening, but the facts behind it were outdated by the time the meeting started.

Within two weeks, the founder had a shortlist of three automation candidates and stopped approving new AI subscriptions until the team cleared the routine map. The change was not a new tool; it was visibility that made the next decision obvious.

> **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

**How long does the diagnostic take?**
Seven calendar days. The first artefact — the org chart — is produced in minutes; the full report and shortlist are ready by day seven.

**Do we need an IT team to run it?**
No. The diagnostic is a visibility exercise, not a technical implementation. It uses existing reports, daily updates, and team interviews.

**What happens after the seven days?**
You receive the four artefacts and a recommendation on where to start. You can run the first automation internally, with a partner, or not at all — the diagnostic gives you the data to decide.

**Is this the same as an AI audit?**
No. An audit checks security, compliance, and vendor contracts. A diagnostic maps what your team actually does so you know where AI can help before you spend budget.

**Will this disrupt daily work?**
Minimally. It relies on reports and updates the team is already producing, plus a few short conversations with department heads.

Stop guessing where AI fits in your company. See the Plan → Fact → Gap across your team before you commit to any tool or subscription.

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/what-a-7-day-diagnostic-produces-sample-artefacts. More articles: https://aiadvisoryboard.me/blog
