All people, businesses, dates and events below are fictional teaching material.
How does an approved agency scope reach the delivery team, and where does ownership become unclear? This interview will inform whether to run a manual handoff test, not whether to build a reminder feature.
Interview ID: INT-001. Date: 2026-10-05. Role: operations lead at a small agency. Interviewer: research lead. Notes permission: permitted in this fictional example. Recording and attributed quotation reuse: not requested. Source: fictional notes, paragraphs 2–4. In real work, record the actual decision and keep restricted source files in your approved system.
The fictional participant described a client job that began using an outdated scope link. They later searched for the approved version. The same interview produced two excerpts about the same handoff problem.
Faithful fictional paraphrase, paragraph 2: the team began the job from an old scope link. Paragraph 4: the operations lead later asked which version had been approved. These are two evidence items from one interview.
Approval information may not reach the delivery owner reliably. This is an interpretation to examine with other teams, not a validated market finding.
A later fictional interview, INT-003, describes a single owner and versioned scope link that already work. The issue might depend on the agency's handoff process rather than a missing software feature.
Observe a manual handoff with three consenting teams. Record whether a delivery owner and approved scope can be located without prompting. Owner: product lead. Review date: 2026-11-06. Three is a fictional planning choice, not a recommended statistical sample size.