One team.
Trusted information.
Capacity for more.
A documentary case study of manual work, trusted records, AI automation, and what the team can do next. Follow one operational case, a relevant official-record example, and evidence of additional work completed.
The visual rhythm
Colour represents the main picture on screen. The interview audio can continue over factory scenes, records, and diagrams. Click a block to inspect its chapter.
11:30: leave the table and follow the failed handoff on the floor. 21:30–24:30: stay with a focused, readable template setup on a prepared data connection. At 16:00, show what the team can now complete. At 25:30, assess the evidence of change.
Existing input → AI preparation or execution → person reviews or decides → checked result reaches the team’s working record → next check.
Show the same task before and after. Identify what starts the run, which repeated steps AI handles, what people still do, and where the result is used. Open the workflow filming map.
The case-study edit plan
Expand a chapter for its shot sequence. These blocks budget the final edit; they do not require a camera cut at every boundary.
00:00–01:15The decision
Where is the order, and what changed?
A recognizable task opens the case study.
| Episode time | Main picture | What happens |
|---|---|---|
| 00:00–00:08 | Factory / work | Meaningful detail of the main operational case; record natural factory sound. |
| 00:08–00:20 | Conversation | Employee describes the actual update and decision, or host uses a clearly labelled illustration. |
| 00:20–00:38 | Factory / work | Reveal the person and workplace; ask which information is trustworthy enough to act on. |
| 00:38–00:58 | Screen evidence | Show one useful clue and its original source, with the unanswered question still clear. |
| 00:58–01:15 | Factory / work | Host introduces the case study: trusted information, AI in everyday work, and capacity for more. |
01:15–03:00Birkan and its workflow
Who had to find the answer?
Establish the business, team, and existing workflow.
| Episode time | Main picture | What happens |
|---|---|---|
| 01:15–02:00 | Conversation | Leader establishes the business, participating team, scope, and why this task mattered. |
| 02:00–02:35 | Factory / work | Follow the real route through the team’s existing tools and handoffs. |
| 02:35–03:00 | Map / worksheet | Map the main operational case and identify where work waits for information. |
03:00–07:001 · The manual work
What manual effort kept recurring?
Show manual effort and the useful work it displaces.
| Episode time | Main picture | What happens |
|---|---|---|
| 03:00–03:50 | Conversation | Operator reconstructs the manual task and the repetitive effort it required. |
| 03:50–04:25 | Factory / work | Observe the lookups, copying, checking, or chasing in context; identify any reconstruction. |
| 04:25–05:00 | Screen evidence | Show the existing update and the records the colleague needed to assemble. |
| 05:00–05:55 | Conversation | Ask which work required judgment, what was repeated, and what useful tasks had to wait. |
| 05:55–06:30 | Map / worksheet | Show the decision brief and capacity baseline: task, frequency, effort, waiting, and backlog. |
| 06:30–07:00 | Factory / work | Move toward the colleague responsible for checking the information. |
07:00–11:302 · Trust and official records
What made the information trustworthy?
Connect trustworthy internal answers with a relevant official-record check.
| Episode time | Main picture | What happens |
|---|---|---|
| 07:00–07:35 | Factory / work | Introduce the data owner and the decision that requires a dependable answer. |
| 07:35–08:30 | Conversation | Employee explains what they needed to check before relying on an AI answer. |
| 08:30–09:30 | Screen evidence | Trace an actual conclusion to ERP source rows; show identifiers, definitions, dates, and unknowns. |
| 09:30–10:10 | Conversation | Introduce one relevant official-record task; clearly identify a different case or entity. |
| 10:10–10:50 | Screen evidence | Show the actual official source or authorized document, retrieval date, entity match, and comparison. |
| 10:50–11:30 | Map / worksheet | Trust worksheet: confirmed fact, source, scope, unknowns, reviewer, and limits of the conclusion. |
11:30–16:003 · AI in the working process
Where does AI fit in the working process?
Show the actual AI step and the process around the changed handoff.
| Episode time | Main picture | What happens |
|---|---|---|
| 11:30–12:05 | Factory / work | Return to the main operational case and walk into the production or quality handoff. |
| 12:05–12:55 | Conversation | Station owner explains what the physical process requires and which event records it. |
| 12:55–13:35 | Map / worksheet | Map the input, trigger, AI task, person, destination, and evidence of completion. |
| 13:35–14:25 | Factory / work | Observe the changed handoff and the actual working step supported by AI. |
| 14:25–15:20 | Conversation | Ask what the AI handles, what the person decides, and which process or ERP changes were needed. |
| 15:20–16:00 | Screen evidence | Show the supported run, its source-backed result, and where the next colleague uses it. |
16:00–20:304 · Adoption and team capacity
What can the team now complete?
Connect adoption, ownership, and additional useful work.
| Episode time | Main picture | What happens |
|---|---|---|
| 16:00–17:00 | Conversation | Employee explains initial doubts, learning, corrections, and ownership of the changed task. |
| 17:00–17:45 | Factory / work | Film additional work the employee can now complete; distinguish actual work from a demonstration. |
| 17:45–18:30 | Screen evidence | Show the accepted output and action record supporting the example of increased capacity. |
| 18:30–19:30 | Conversation | Ask what happened to the released effort, what review remains, and whether quality held. |
| 19:30–20:10 | Factory / work | Follow the additional work to the colleague or customer-facing function it helps. |
| 20:10–20:30 | Map / worksheet | Capacity chain: effort changed, review accounted for, additional work completed, quality checked. |
20:30–25:305 · Repeat the useful workflow
How do we check this next time?
Make the supported workflow and its repeat procedure understandable.
| Episode time | Main picture | What happens |
|---|---|---|
| 20:30–21:30 | Conversation | Team explains how the workflow fits its recurring review and how the run actually starts. |
| 21:30–22:10 | Screen evidence | SETUP 1: open the actual template and explain the recurring task and required input. |
| 22:10–22:25 | Conversation | Explain the prepared source and whether a person, schedule, or event starts the workflow. |
| 22:25–22:45 | Screen evidence | SETUP 2: select scope, dates, field meanings, and the supported AI step. |
| 22:45–23:25 | Screen evidence | SETUP 3: run the task; explain what AI performs and label any omitted elapsed time. |
| 23:25–23:40 | Conversation | Ask what a person must check and how they respond to missing or incorrect input. |
| 23:40–24:30 | Screen evidence | SETUP 4: check the result, retain an unknown, show the working destination and next run. |
| 24:30–25:05 | Conversation | Who uses the result, knows it completed, and remains responsible for exceptions? |
| 25:05–25:30 | Factory / work | Observe the checked output being used in the team’s real review routine. |
25:30–28:30Evidence of change
Which outcomes can the team substantiate?
Assess operational outcomes and team capacity with comparable evidence.
| Episode time | Main picture | What happens |
|---|---|---|
| 25:30–26:25 | Conversation | Leader and employee describe the supported operational and team-capacity outcomes. |
| 26:25–27:00 | Screen evidence | Compare effort, accepted output, quality, and dates for the same task; label estimates. |
| 27:00–27:35 | Factory / work | Return to the opening operational case and its documented outcome. |
| 27:35–28:05 | Conversation | Ask about remaining work, other causes of change, and which ambitions are still future plans. |
| 28:05–28:30 | Map / worksheet | Show the strongest supported result, its scope, and the remaining unanswered question. |
28:30–30:00A starting point for another team
Which update will you investigate first?
Offer one transferable starting point for another team.
| Episode time | Main picture | What happens |
|---|---|---|
| 28:30–28:55 | Conversation | Host invites viewers to choose one recurring task and define trusted inputs, AI work, and ownership. |
| 28:55–29:15 | Map / worksheet | Recap the case-study lessons and the relevant workflow, trust, and capacity worksheets. |
| 29:15–29:40 | Factory / work | Close on the team doing meaningful work; natural sound returns. |
| 29:40–30:00 | Map / worksheet | Templates CTA with the checked destination and current campaign offer, when ready. |
Seven worksheets for the case study
Read the master written case-study structure. The five workflow worksheets are joined by trust and team-capacity worksheets.
Show the original task, the repeated work AI handles, where the result goes, and what a person does next. Let each worksheet appear after its usefulness is clear. Show only actual supported product steps; retain missing information and the limits of the evidence.
Timed case-study treatment and interview questions · Editor’s running order CSV · Pack guide