The Quiet Signal System

Assignment 6: Three Isolated Ideation Sessions

Three separate browser windows. Only the anonymised POV as input. No shared context, no financial data, no knowledge base. Convergence across isolated sessions is evidence, not artefact. Community Vocabulary Shift appeared independently in all three sessions — the single most structurally validated idea in the 161-idea corpus. If an idea surfaces in three sessions that cannot see each other, its emergence is structural rather than prompted.

The Transition: Knowledge Base Curation

21 documents assessed against a single question: does this document provide context that Assignment 7 needs, without prescribing outputs that the taught frameworks should determine? The Concept Development document transfers (defines what the system is). The feasibility study is excluded (prescribes how to assess viability using the wrong framework — bespoke RAG, not D/F/V). The implementation plan is excluded (48-week full deployment, not MVP). The methodology critique is excluded (references excluded outputs as validated — a contamination chain).

The Financial Context document is also excluded — but its content is embedded verbatim in the project instructions, making it available to every prompt without creating a separate document dependency.

Assignment 7: Five Prompts in Five Separate Chats

Each prompt executed in its own chat session. Dependencies stated explicitly; prior outputs present in the shared knowledge base, not carried through conversation history. This prevents the known risk that long threads erode contextual fidelity, causing later outputs to drift from the original evidence base. The knowledge base contains only reviewed, finalised outputs and source material — not hedged responses, abandoned reasoning, or intermediate drafts.

Process Notes

HITL gating: No prompt was executed without Tim's review and explicit confirmation. Each output was reviewed and challenged before it fed into the next prompt.

Session isolation: Each prompt is self-contained. Where a prompt depends on a prior output, the dependency is stated explicitly and the output is in the shared knowledge base — not carried through conversation history.

Framework derivation: Structure derives from the course material frameworks, not the Concept Development document's internal architecture. When these sources suggest different structures, the course material governs.

MVP scope discipline: 'Launch' means launch the MVP prototype, gather feedback from relationship stewards, and determine what happens next — then return to the start of the double diamond for the next iteration. Not full system deployment.

Assignment 6 gates: POV validation before ideation begins; after the feasibility study before concept development proceeds; after concept development before success criteria are written; after the full critique output before submission. At each gate, a human assessor reviewed AI output against source evidence before the next stage was authorised.

Transition gate: The include/exclude decision on all 21 documents was a human assessment of what context the new project should inherit. The overshoot documents were identified, assessed, and deliberately excluded — not retrofitted to the correct frameworks. The exclusion is the learning.

Assignment 7 gates: Each of the five prompts was reviewed and challenged before it fed into the next. Tim's HITL role included: challenging whether scenario selection in Prompt 4 was the right one; confirming that Approach C was selected on genuine constraint analysis rather than convenience; verifying that the cultural shifts in Prompt 5 are specific to this organisation and this project, not generic change management. The outputs in this appendix reflect the finalised, reviewed versions — not the first draft in every case.

1.1 The NPS Blind Spot: Increasingly Documented, Rarely Acted On

Quitlo, a churn intelligence platform, analysed over 50,000 AI exit conversations with churned SaaS subscribers and found a consistent pattern: companies with reportedly healthy NPS scores were losing customers at rates their survey data never predicted. Their analysis identified the structural reason: NPS captures sentiment from the roughly 4.5% who respond, while churn happens among the 95.5% who stay silent. The most common reason churning customers gave for not completing exit surveys was that they did not believe anyone would read it — a learned response to years of feedback going nowhere.

CustomerGauge, a B2B retention platform, makes a complementary observation: the majority of churn they have observed across enterprise accounts is preceded not by negative feedback but by an absence of signal. Their framing is direct — churn comes from a lack of feedback and data, not from the feedback itself. The absence of complaint is not evidence of satisfaction; it is the signal itself.

Relevance to this project: These findings directly validate the core insight of the Quiet Signal System. The metric-truth gap is not a quirk of Naked Wines' data. It is a structural feature of prompted satisfaction measurement. A group NPS of 76 coexisting with a 24% annual churn rate in the highest-LTV cohort is consistent with the pattern documented across the industry. The anomaly is not the churn. The anomaly is the NPS.

1.2 The Customer Health Score Ecosystem: Instructive Limitations

The current industry standard for churn prediction is the customer health score, operationalised by platforms such as Gainsight, ChurnZero, and Planhat. These systems aggregate product usage, support ticket history, NPS/CSAT responses, and engagement data into composite health scores, typically visualised as red/amber/green. Gainsight reports that 84% of companies with formal customer success programmes use health scoring as a cornerstone of their retention strategy.

These platforms are genuinely useful for B2B SaaS retention where the signals are digital and frequent — login frequency, feature adoption, support ticket volume. They are structurally weaker for consumer subscription models where the product is physical, the community is emotional, and the churn signal is expressed in peer-to-peer language rather than product telemetry.

ChurnZero's own analysis of enterprise account data reveals a specific failure mode relevant to this project: health scores perform well for customers in the early stages of a subscription (high sensitivity to early disengagement signals) but significantly underperform for tenured customers who are expected to renew. The long-tenure, high-NPS customer who churns is a known blind spot in health score architectures — exactly the profile of the Naked Wines Angel at risk of silent departure.

Relevance to this project: The health score ecosystem defines the existing state of the art. The Quiet Signal System is differentiated not by its goal (detecting churn) but by its data source (unmanaged community language) and its interface design (verbatim-first, not score-first). The existing platforms solve a different problem for a different customer profile.

1.3 Community Sentiment as a Leading Indicator: The Slack and Reddit Research

Several academic and commercial research programmes have examined whether sentiment in brand-adjacent online communities predicts customer behaviour. The most relevant evidence base is from the open-source software and gaming communities, where product forums function similarly to the Naked Wines community — unmediated peer-to-peer conversation, not brand-managed channels.

Research from the Wharton School (Netzer et al., "Mine Your Own Business") found that analysing customer discussions in product forums predicted market share movements more accurately than surveys, with a lead time of several months. The mechanism was not sentiment polarity (positive/negative) but semantic content — what customers were discussing, how they were framing the product's role in their lives, and whether the framing was changing over time.

Supportbench, a customer success platform, identifies linguistic changes as a leading indicator of disengagement: the shift from collaborative language ('we should fix this') to transactional language ('your product does not do X') to observational language ('I noticed that other products handle this differently') tracks a consistent trajectory toward departure. The emotional register cools before the cancellation is submitted. This directly validates the Silence Classifier's design: not just what the customer says, but how they say it and whether the register is changing.

Relevance to this project: These findings establish that language trajectory — how customers talk about a product over time — is more predictive than point-in-time sentiment. The Community Vocabulary Shift signal is the operationalisation of this principle: longitudinal NLP analysis of individual posting histories, detecting the shift from inside-the-community language to outside-the-community language.

1.4 The 'We' to 'They' Vocabulary Shift: Pronoun Research

Academic research by Iñigo-Mora (2004) on pronoun use in group discourse establishes that first-person plural ('we', 'our', 'us') versus third-person references ('they', 'them', 'the company') are measurable indicators of group identity alignment. When group members refer to the group in the third person, they have psychologically departed even if their formal membership continues. This finding has been replicated across organisational, political, and consumer contexts.

The application to subscription churn has not been commercially operationalised — no known retention platform currently uses longitudinal pronoun trajectory as a primary churn signal. This represents both the theoretical validity and the practical novelty of the Community Vocabulary Shift component. The academic evidence is strong; the commercial application is untested at scale.

The strongest indirect validation for this project: the Community Vocabulary Shift idea emerged independently across all three isolated ideation sessions. If the idea surfaces in three sessions that cannot see each other, its emergence reflects something the evidence base supports — not a prompt artefact.

1.5 Silent Churn Detection in DTC Subscription Businesses

Peloton's retention model (documented in their investor materials following the 2022 subscription crisis) is the closest documented example of multi-dimensional community engagement analysis in a DTC subscription context. Their retention analysis found that churn was 60% lower among subscribers who engaged with two or more content disciplines per month — and critically, that engagement variety was more predictive than engagement frequency. A subscriber who used the platform every day for one type of content was more at risk than one who used it three times a week across multiple content types.

The relevant insight is not the specific finding but the methodology — they identified that multi-dimensional engagement patterns were more predictive than any single metric. The Quiet Signal System's three-signal corroboration approach (Forum Divergence Score, Silence Classifier, Community Vocabulary Shift) follows the same structural logic: no single signal is dispositive; convergence across signals is the reliable indicator.

1.6 The HITL Verbatim-First Interface: No Direct Precedent

The design principle of surfacing verbatim community language at the top of every subscriber brief — before any model score or risk category — has no direct precedent in the retention technology stack. Every platform in the market (Gainsight, ChurnZero, Braze Predictive Churn, the Pedowitz Group's sentiment-driven churn framework) presents a score first and evidence second.

The Quiet Signal System inverts this deliberately. The rationale is architectural: if the steward sees a number first, the number becomes the decision input and the verbatim language becomes supporting evidence. The system then behaves like a more sophisticated version of the managed metric it was designed to replace. If the steward reads the subscriber's actual words first, the emotional register of the community signal is preserved through to the human decision point. The controlled comparison built into the Approach C prototype — verbatim-first versus score-first presentation of the same briefs — is designed to test whether this architectural commitment produces the expected advantage in practice.

1.7 Summary of Transferable Lessons

2.1 Regulatory and Legal

DPIA sequencing gate. The mandatory DPIA under UK GDPR Article 35 is a hard sequencing constraint on the critical path. The specific obstacle is not completing the DPIA itself — that is a procedural step — but the findings it may produce. If the DPIA concludes that community forum posts constitute special category data when processed through AI behavioural profiling, the lawful basis analysis becomes significantly more complex. The ICO's guidance on AI and data protection is clear that automated profiling with significant effects requires either explicit consent or a documented Legitimate Interests Assessment. Consent is unsuitable given the commercial power imbalance in a subscription context (GDPR Recital 43). The Legitimate Interests Assessment must demonstrate that the processing is necessary, proportionate, and that the data subject's interests do not override the business interest.

Community forum terms of service. Naked Wines' community forum presumably has existing terms governing how user-contributed content may be used. If those terms do not explicitly contemplate AI-driven behavioural analysis of individual posting patterns, there is a gap between what the subscriber consented to when posting and what the system does with their words. This requires legal review and potentially updated terms with grandfathering provisions for existing content. The legitimacy question — can the organisation honestly say to an Angel 'we read what you wrote and used it to understand how you were feeling about us?' — is distinct from the legal question, and both need answering.

ICO exposure. The AI Risk Register identifies the ICO maximum fine exposure at group level as approximately £8m at current revenue. Angel retention damage from a regulatory investigation would compound this materially. The DPIA gate is not a bureaucratic formality — it is the point at which the project either earns regulatory clearance to proceed with live data or determines that it cannot.

2.2 Data Access and Quality

System integration. The MVP requires access to individual subscriber forum posting histories linked to subscriber accounts, correlated with CRM data (tenure, referral history, pre-funded balance, email engagement). Forum data and CRM data are likely in different systems with different schemas. The technical effort to join them into a single subscriber record is non-trivial, and the data engineering team's capacity and willingness to prioritise this for an experimental MVP is uncertain. This is the single largest technical dependency for Approaches A and B; Approach C bypasses it entirely.

Coverage gap. Not all Angels post on the forum. If only a fraction of the 24,000 target cohort are active forum contributors, the system's coverage is immediately limited. The Forum Divergence Score and Community Vocabulary Shift signals only work for subscribers who generate community language. For the silent majority who never posted, only the behavioural telemetry signals (referral velocity reversal, email open-time decay) are available. The MVP must account for this coverage gap honestly — a system that covers 30% of the target cohort is a different proposition from one that covers 80%.

Data quality and longitudinal depth. The Community Vocabulary Shift detection requires longitudinal analysis of individual posting histories — not a single-point classification but a trajectory over months or years. This requires a well-structured historical dataset and a clear definition of what constitutes a meaningful shift versus normal linguistic variation. If forum posts were not consistently linked to individual subscriber records over the full tenure window, the longitudinal signal cannot be computed.

2.3 Organisational and Political

The NPS challenge. The system's core premise is that the company's primary measure of customer health (NPS 76) is structurally misleading. This is not a neutral analytical observation — it is a direct challenge to the metric that the leadership team reports to the board and the market. The HY26 interim results cite NPS 76 as evidence of customer health. A system that explicitly argues this metric is obscuring the departure of the highest-value customers will encounter resistance from anyone whose reporting, compensation, or credibility is anchored to NPS. This is the single most likely reason the project stalls at the organisational level.

The relationship steward role. The concept requires a 'relationship steward' with the authority to make relational intervention decisions. Naked Wines' current customer service structure presumably does not include this role in the form the system requires. Creating it — even for the MVP — requires someone with budget authority to allocate staff time. If the MVP is positioned as a technology experiment, it may get engineering resource but not operational resource. It needs both. The MVP cannot be tested without a human steward to review the briefs.

Operational culture and decision-making norms. The system asks stewards to make qualitative, interpretive decisions based on verbatim language rather than threshold-triggered scripts. Organisations whose customer service functions are built on scripted, metric-driven processes may find this genuinely uncomfortable — not because of resistance to the concept, but because the capability infrastructure for qualitative decision-making does not exist.

2.4 Technical

NLP classification difficulty. The classification task at the core of the MVP — distinguishing concluded departure from active complaint, and satisfied silence from concluded silence — is genuinely difficult. Standard pre-trained sentiment models will not do this out of the box. The system needs to recognise the specific linguistic signatures of conclusion: the absence of emotional language, the shift in pronoun framing, the decline in posting frequency interpreted as signal rather than noise. The MVP can use an LLM as the classifier rather than training a custom model, which reduces the technical barrier significantly, but the prompt engineering and validation work is still substantial.

Longitudinal analysis requirement. The vocabulary shift detection requires longitudinal analysis of individual posting histories — not a single-point classification but a trajectory over months or years. This is computationally straightforward but requires a well-structured historical dataset and a clear definition of what constitutes a meaningful shift versus normal linguistic variation. Context matters enormously: a subscriber who posts less in December may be on holiday rather than disengaging.

False positive rate and steward fatigue. If the system flags too many subscribers who are not at risk, the steward's attention will be diluted and the intervention quality will decline. If it flags too few, it misses the subscribers it was designed to catch. Calibrating the false positive rate requires real data, which Approach C — operating on synthetic signals — cannot provide. This means the threshold calibration problem is deferred to the next iteration.

2.5 Human and Ethical

Steward skill requirement. The steward's value depends on her ability to read verbatim community language and make a qualitative judgement about the subscriber's relational state. This is a skill that most customer service environments do not systematically develop. The MVP cannot be used to train this skill before the test — training before evaluation would contaminate the results. But deploying an undertrained steward risks invalidating the prototype results for a different reason. The orientation protocol in the action plan (Phase 3.3) navigates this tension by providing minimal orientation without interpretive instruction.

The experience of being watched. The system monitors language subscribers wrote in the context of speaking to each other, not to the brand. There is a version of this system that subscribers would experience as surveillance if they learned about it. The legitimacy of the system depends on whether Naked Wines can honestly say to an Angel: 'We read what you wrote in the community forum and used it to understand how you were feeling about us.' If that sentence sounds creepy rather than caring, the system has a legitimacy problem that no DPIA can resolve. The surveillance concern is raised as an explicit data capture point in the MVP review sessions (Phase 4.2 of the action plan).

4. Selection Framework

The choice between the three approaches is a strategic decision about what the MVP is for — which risk the project owner judges most material to test first.

None of the three approaches is wrong. They test different parts of the same system. They could also be sequenced: C first to validate the interface, then A to validate the signal, then B to validate the prediction — which is in effect a three-phase MVP development path. That sequencing decision sits with the project owner and informs the selection rationale in the Critical Assessment tab.

Criteria and Weights

Desirability (weight: 3) — Does the approach produce something that the intended user (the relationship steward) would genuinely want to use, find credible, and act on? Lower weight than Feasibility because a desirable approach that cannot be built is not an MVP.

Feasibility (weight: 5) — Can the approach be executed within the constraints that actually exist: no internal data access, no DPIA completed, project lead as sole resource? Joint highest weight. An approach that cannot be executed produces no evidence, regardless of its theoretical merit.

Viability (weight: 4) — Does the approach produce evidence that justifies further investment? A result that is internally interesting but insufficient to influence a senior stakeholder's decision is not viable in the context of this project.

HITL Integrity (weight: 5) — Does the approach preserve the HITL architecture as specified: verbatim community language surfaced before any model score, human steward as the decision-maker, no AI output reaching the subscriber without review? Joint highest weight because the HITL design is a non-negotiable constraint, not a preference.

2.1 Desirability

Approach A: Retrospective Validation — Score: 3. The steward reviews historical cases with known outcomes. Her decisions are retrospective rather than prospective — she knows, or can infer, that the subscriber in question has already churned. This makes the experience partially artificial. The HITL interface can be tested but the steward's confidence in a brief where the outcome is already determined is not the same as her confidence in a live decision. Scored at 3 rather than lower because the verbatim-first format can still be evaluated for its communicative effectiveness.

Approach B: Live Shadow System — Score: 5. The steward reviews live subscriber briefs with no knowledge of how the subscriber subsequently behaves. Her decisions are genuinely prospective, uncontaminated by hindsight. This is the highest-fidelity test of whether the system produces something the steward genuinely finds actionable. If she can make confident decisions on live briefs and later evidence shows those decisions correlated with actual subscriber behaviour, the Desirability case is conclusive.

Approach C: Simulated Signal Test — Score: 3. The steward reviews synthetic briefs constructed from public proxy data mapped onto fictional subscriber profiles. The interface can be tested and the HITL workflow validated. But the steward knows — or can reasonably infer — that the data is simulated. The emotional register of proxy language (Reddit, Trustpilot, app store reviews) may not match the specific tone of Naked Wines' community. The steward is evaluating a demonstration, not using a tool. Sufficient to test the interface design but not sufficient to test whether the steward would trust and act on the system in practice.

2.2 Feasibility

Approach A: Retrospective Validation — Score: 4. Operates on historical data for internal analytical purposes. The DPIA position is substantially more defensible than live profiling — retrospective analysis of anonymised historical data for internal model validation is a different regulatory proposition from live behavioural profiling of current subscribers. Requires access to historical forum data linked to CRM records at the individual subscriber level — an organisational dependency but not a regulatory one. Does not require real-time data infrastructure. Scored at 4 rather than 5 because it still requires internal data access, which depends on organisational approval that has not yet been secured.

Approach B: Live Shadow System — Score: 2. Requires the DPIA to be completed before deployment — live profiling of current subscribers, even without intervention, triggers UK GDPR Article 35. The DPIA is on the critical path and may add 8–16 weeks depending on DPO capacity and ICO consultation requirements. Requires the full forum-to-CRM data integration pipeline to be built — the single largest technical dependency in the entire project. Requires a suitably senior steward to commit real time over 90 days to reviewing briefs that produce no action. Scored at 2 because two of these three dependencies (DPIA completion and data pipeline construction) are substantial and neither is within the project's direct control.

Approach C: Simulated Signal Test — Score: 5. No DPIA dependency. No internal subscriber data is processed. No data integration pipeline is required. Operates entirely on public proxy data and synthetic profiles that the project team constructs. Can be built and tested in 2–3 weeks. The only organisational dependency is recruiting stewards for the review exercise, which can be done informally. This is the most executable approach by a significant margin.

2.3 Viability

Approach A: Retrospective Validation — Score: 4. Produces a specific, evidenced answer to the foundational question: does the signal exist in the historical data? If the retrospective analysis shows that the Forum Divergence Score, Silence Classifier, and Community Vocabulary Shift indicators were consistently elevated in the 12–18 months before high-LTV Angels churned, this is direct evidence that the signal is real and detectable. This is the evidence a senior leadership team would need to justify further investment. Scored at 4 rather than 5 because retrospective evidence is inherently weaker than prospective evidence — it demonstrates correlation in historical data, not prediction of future behaviour.

Approach B: Live Shadow System — Score: 4. Produces the strongest possible evidence: prospective predictions tested against actual subscriber behaviour over a 90-day observation window. If the system flags subscribers who subsequently churn, and does not flag subscribers who remain, the predictive case is made. This is the evidence that would convert the business case from 'plausible' to 'proven.' Scored at 4 equal to Approach A because, while the evidence it produces is stronger, the question of whether the project reaches the point of producing that evidence is a Feasibility problem — and evidence that is never generated has zero viability regardless of its theoretical strength.

Approach C: Simulated Signal Test — Score: 2. Validates the dashboard interface and the steward's decision-making workflow. Does not validate whether the AI can actually detect the signals in Naked Wines' real data. A board-level audience asking 'does this work?' would receive the answer: 'the interface works and the stewards find it usable — but we have not yet tested whether the underlying signal detection is accurate.' Useful evidence for the next iteration but insufficient evidence to justify significant further investment on its own.

2.4 HITL Integrity

Approach A: Retrospective Validation — Score: 4. The HITL architecture is fully testable: the steward reviews subscriber briefs with verbatim community language presented first, before any model score. The verbatim-first principle is preserved. However, the hindsight bias risk introduces a qualification: the steward who knows the subscriber has churned will read the verbatim language differently from one making a genuinely prospective decision. The HITL design is intact; the steward's cognitive state is not fully equivalent to production conditions.

Approach B: Live Shadow System — Score: 5. The HITL architecture is tested in the highest-fidelity conditions. The steward reads verbatim language for a subscriber whose status is genuinely unknown. She makes a decision — Intervene, Monitor, Escalate — without knowing whether it will prove correct. This is the authentic test of whether the verbatim-first design enables better decisions than a score-first format under real operational conditions. No qualification applies.

Approach C: Simulated Signal Test — Score: 4. The verbatim-first design can be tested in the prototype and the controlled comparison between verbatim-first and score-first formats can be run. The HITL workflow is validated. The qualification is that the verbatim language is synthetic, not algorithmically detected from real Naked Wines community data — so the test of whether the steward would trust the system in practice is limited by the artificiality of the data source.

Approach Profiles: Strengths and Weaknesses Visualised

The chart makes two things immediately visible: B is tall on Desirability and HITL but collapsed on Feasibility — the most rigorous approach that cannot be built within current constraints. C is tall on Feasibility but collapsed on Viability — the most executable approach that does not answer the foundational question. A occupies the middle ground on most criteria.

A sits closest to the sweet spot but carries residual risk of producing a 'dream' — retrospective evidence that the signal exists but insufficient proof that the steward can act on it in real time. B sits in the Desirability circle but outside the Feasibility circle — the most rigorous test that the project cannot currently execute. C sits firmly in the Feasibility circle but outside Viability — the most executable approach that does not answer the foundational question.

5.1 The Foundational Question Trade-Off

Approach A is the only approach that directly answers the foundational question: does the signal exist in the data? If it does not — if the Forum Divergence Score, Silence Classifier, and Community Vocabulary Shift indicators show no consistent pattern before historical churns — then the entire Quiet Signal System concept requires fundamental revision. Approach B would eventually answer this question too, but only after significantly greater investment. Approach C does not answer it at all.

The trade-off is: Approach A answers the most important question first, but under imperfect conditions (retrospective, with hindsight bias). The alternative is to answer a less important question under better conditions (Approach C), or to answer all questions under ideal conditions but at a cost that may prevent the test from happening (Approach B).

5.2 The Regulatory Sequencing Trade-Off

Approach B is the only approach that requires the DPIA to be completed before deployment. This is not a bureaucratic hurdle — it is a substantive gate. Live profiling of current subscribers, even in shadow mode without intervention, triggers UK GDPR Article 35 automated decision-making requirements. The DPIA timeline is not within the project's direct control and depends on DPO capacity and potentially ICO consultation. Approach A occupies an intermediate position: it uses internal historical data but for retrospective analysis rather than live profiling, which is a materially different regulatory proposition. Approach C sidesteps the question entirely.

The trade-off is: the most rigorous approach (B) carries the highest regulatory risk and the longest critical path; the most executable approach (C) avoids regulatory engagement entirely but also avoids the data that matters.

5.3 The Evidence Strength Trade-Off

The three approaches produce evidence of fundamentally different kinds. Approach A produces correlational evidence: the signal was present before historical churns. Approach B produces predictive evidence: the signal identified subscribers who subsequently churned. Approach C produces usability evidence: the interface enables effective steward decision-making. Each type of evidence serves a different audience and answers a different question. Correlational evidence tells the data science team the signal is real. Predictive evidence tells the board the system works. Usability evidence tells the operations team the dashboard is fit for purpose. None is wrong; they are different. The trade-off is which evidence gap the project owner judges most dangerous to carry into the next iteration.

5.4 The Sequencing Argument

The three approaches could be sequenced: C first to validate the interface, then A to validate the signal, then B to validate the prediction — a legitimate three-phase MVP development path. But it is important to recognise what that sequencing implies: if C is chosen first, the project spends its first iteration learning whether the dashboard is usable without learning whether the signal is real. If the signal turns out not to exist in the data (tested in the second iteration via A), the interface validated in the first iteration was validated against synthetic signals that the real system cannot reproduce. This is a real cost, acknowledged and accepted.

1.1 Mini-Planning Session

A focused effort to outline the immediate next steps required to build a basic, testable version of the Relational Health Dashboard. This is not a full project plan. It answers three questions: What are the absolute first actions? Who is responsible? What is the quickest way to create something stewards can react to?

1.2 Resource Identification

Pinpointing the essential people, tools, and materials required for the initial prototype. The guiding principle is to use what is readily available and cost-effective.

1.3 Defining the 'What' and 'How'

A clear decision on the scope and fidelity of the first prototype. The principle is Minimum Testable Prototype — the smallest thing that can be built to learn whether the verbatim-first HITL design produces better steward decisions than the current score-first paradigm.

1.4 Setting the Stage for Learning

The primary purpose of this prototype is not to build a perfect product but to enable rapid learning through steward testing. The mindset is 'build to learn,' not 'build to launch.'

1.5 Iterative Mindset

This phase is foundational for the iterative nature of Design Thinking. It prepares the project for a continuous loop of refinement, recognising that this first prototype is rarely the last.

2.1 Refinement and Polishing

The final stage of perfecting the prototype before it reaches the stewards. This involves addressing any interface issues and ensuring consistent design quality throughout.

2.2 Comprehensive Documentation

Creating clear, accessible materials for the stewards who will interact with the prototype and for the project record.

2.3 Legal, Ethical, and Compliance Review

A critical check to ensure the prototype adheres to all relevant laws, regulations, and ethical guidelines. Approach C sidesteps the DPIA sequencing gate because no internal subscriber data is processed, but this position must be formally confirmed.

2.4 Technical Readiness

Ensuring the prototype is technically stable and accessible for the steward review sessions.

2.5 Stakeholder Sign-Off

Final approval before the prototype is released to stewards. At the MVP stage, the stakeholder group is small — the project lead and the retention team lead at minimum.

3.1 Deployment Strategy

The deployment is the steward review sessions. Two to three individual one-hour sessions, each using the same protocol and the same ten briefs.

3.2 Market Introduction and Communication

At MVP stage, 'market introduction' means introducing the prototype to the stewards — not external communication.

3.3 Training and Support

At MVP stage, training is minimal and deliberately so. The steward's unguided response is the data.

3.4 Change Management

The MVP introduces a new workflow and a new decision-making paradigm. Even at prototype stage, the steward is experiencing something that may challenge her existing understanding of what the retention function does.

4.1 Performance Tracking

Quantitative analysis of the session data against the success and failure criteria established in Phase 1.

4.2 Gathering Post-Launch Feedback

Qualitative analysis of the debrief notes and free-text feedback. The most important data from this prototype may be what the stewards said, not what they scored.

4.3 Problem Identification and Opportunity Spotting

Proactively analysing the collected data and feedback to identify both issues and potential areas for growth.

4.4 Continuous Improvement and Iteration

Based on the evidence gathered, the project determines what happens next and returns to the start of the double diamond for the next iteration. This is where the Design Thinking loop closes and reopens.

Phases 1–2 are the common trunk: identical build and preparation across all three variations. Phase 3 (the steward review sessions) is where the paths diverge. All three paths return to the start of the double diamond — but with different questions, different entry conditions, and different timelines.

2.1 Stakeholder Analysis

The cultural changes required by this project affect different stakeholders in different ways. The following analysis identifies each stakeholder group, their relationship to the cultural shifts, and the nature of their interest — supportive, threatened, or conditional.

2.2 Impact Assessment

The cultural changes create operational, identity, and institutional impacts across the organisation. The following table maps each shift to its impact dimensions.

2.3 Communication Plan for Change

The communication challenge at the core of this project is that the founding message — 'our most trusted metric is not measuring what we think it is measuring' — is inherently threatening. If communicated as an accusation ('NPS has been misleading us'), it produces defensiveness. If communicated as a discovery ('we have found a signal that NPS cannot see'), it creates curiosity. The framing is everything.

Phase 1: MVP Phase — Evidence Before Argument

During the MVP phase, the communication strategy is deliberately narrow. The audience is the steward team and the retention team lead, not the broader organisation. The message is not 'NPS is wrong'; it is 'we are testing a new interface to see if there is useful information in community language that our current tools cannot surface.' This framing is honest — it accurately describes Approach C — and it does not require the steward to accept any of the five cultural shifts before the prototype has produced evidence.

The communication vehicle is the steward briefing document (produced in Phase 2 of the action plan), the session facilitation, and the debrief. Nothing is communicated to the broader organisation during the MVP phase. The evidence is gathered first; the argument is made from the evidence, not in advance of it.

Phase 2: Post-MVP — Data-Led Narrative

If the MVP validates the interface and the steward finds verbatim signal more useful than the model score, the communication shifts. The primary audience is the retention team lead and the data team lead. The message shifts to: 'We ran a test. Here is what the stewards found. The signal in community language is different from what NPS reports. Here is what that might mean for how we understand subscriber health.' The data from the MVP (steward confidence scores, format comparison results, debrief observations) is the argument. The financial context (£2.3m replacement burden, £478k per 5pp reduction) provides the business case.

The board conversation — the Metric-Trust Shift at its most challenging — does not happen until after the Approach A retrospective provides evidence that the signal is real in actual data. Approach C produces usability evidence; Approach A must produce correlational evidence before the investor narrative can be revisited.

Phase 3: Institutional Maturity — Reciprocal Transparency

At the institutional maturity phase, the communication extends to Angel subscribers themselves. The Honest Annual Report is the primary vehicle: a document sent exclusively to long-tenure subscribers that acknowledges what went wrong, what was learned, and what remains uncertain. This is the communication act that earns the right to use community language as a signal — the organisation has been transparent about what it hears and what it does with it.

2.4 Resistance Management

Resistance to this project will be specific, predictable, and legitimate in most cases. The management approach for each pattern is designed to take the resistance seriously rather than dismiss it as a misunderstanding.

2.5 Training and Capability Building

The capability gap this project creates is not primarily technical. The dashboard is a relatively straightforward interface. The capability gap is interpretive: the steward must be able to read verbatim community language and make a qualitative judgement about the subscriber's relational state. This is a skill that most organisations do not systematically develop, because most organisations do not use unprocessed qualitative data as an operational input.

MVP Phase: Orientation, Not Training

At the MVP stage, the action plan (Phase 3.3) specifies lightweight orientation: walk the steward through the interface, explain what each element of the brief contains, demonstrate the decision workflow with a sample brief. The orientation is deliberately not instruction on how to interpret the signals. The MVP's value depends on capturing the steward's unguided response — if they are trained to interpret before they evaluate, the prototype cannot distinguish between the interface's value and the training's influence. The capability is measured, not built, at this stage.

Post-MVP: Community Signal Literacy

If the MVP validates the interface and the subsequent iteration validates the signal, the steward team requires structured development in what might be called community signal literacy: the ability to read peer-to-peer community language and distinguish between active complaint (which demands operational response), satisfied silence (which requires no intervention), concluded departure (which warrants a relational response), and — as Variation 3 of the simulated variations reveals — the shifting language that precedes conclusion (which represents the highest-value intervention window). This capability is built through supervised practice with real examples, not through classroom instruction. The training model is closer to clinical supervision than to a learning module: the steward reviews flagged subscriber briefs, makes a decision, and discusses the reasoning with a senior steward or the project lead. The quality of the decision improves through calibrated repetition, not through rule-following.

Institutional Maturity: Qualitative Decision-Making as Organisational Capability

At the institutional maturity phase, the capability extends beyond the steward team. The Tenure Council requires facilitation skills for genuine subscriber deliberation. The Disagreement Forum requires moderation skills that preserve dissent rather than resolving it. The Honest Annual Report requires editorial judgement about what to disclose and how to frame failure honestly. These are all expressions of the same underlying organisational capability: working with qualitative, ambiguous, emotionally textured information as a basis for operational decisions. This is a multi-year capability development programme, not a training course.

2.6 Leadership Sponsorship

The Concept Development document identifies senior leadership sponsorship as Condition 5 for the system's feasibility. The Tenure Council and Disagreement Forum are deliberately sequenced as Ambitious-horizon initiatives requiring a separate governance conversation. They are not on the critical path for the first sprint, but they are present in the concept as the longer-term institutional architecture the Quick Wins are designed to support. Their inclusion signals the cultural commitment required.

Leadership sponsorship for this project must be visible, specific, and sustained. It is not sufficient for a senior leader to approve the project. They must be willing to do three things that are each uncomfortable in their own right.

First: Publicly Acknowledge the Metric Gap

A senior leader must be willing to say, in a context that matters (a board meeting, an all-hands, an investor communication), that NPS is not measuring what the organisation believed it was measuring. This is not the same as saying NPS is wrong — it is saying that NPS is incomplete in a specific, material way that has financial consequences. The £2.3m annual replacement burden is the evidence. The 24% high-LTV churn rate alongside a 76 NPS is the anomaly. The leader's role is to name it — not as a failure, but as a discovery that creates an opportunity. Without this act of naming, every other cultural change is building on an unstated foundation, and the resistance to that foundation will eventually surface in ways that are harder to manage.

Second: Protect the Steward's Judgement Authority

The stewardship model only works if the steward's decision is respected. If a steward recommends against intervention and is overruled by a manager who wants to hit a save-rate target, the system has failed at the human level regardless of what the algorithm produces. Leadership must explicitly protect the steward's judgement authority against operational pressure to maximise short-term retention numbers. This means accepting that the save rate will decline in the short term as concluded departures are respected rather than intercepted. It means saying publicly — in a context that the steward team can hear — that a steward who recommends against intervention and proves to be correct has done excellent work. Without this explicit protection, the stewardship role will revert to retention behaviour under pressure.

Third: Commit to Reciprocal Transparency

The legitimacy of monitoring community language depends on the organisation being equally transparent about what it learns and what it does with that learning. A senior leader must be willing to sponsor the Honest Annual Report — a document that tells long-tenure Angels what went wrong, what the company learned, and what it remains uncertain about. This is the institutional act that earns the right to listen. It is uncomfortable because it requires the organisation to say, in writing, to its highest-value subscribers, that it has made mistakes and that it is still learning. But without it, the Quiet Signal System is technically functional and relationally illegitimate. The technical function extracts signal from a community that the organisation has not yet earned the right to monitor at this depth. The reciprocal transparency is what converts extraction into relationship.