Illustrative demonstrationFictional organisation · synthetic data · composite employee voices

CONVERSATIONAL INTELLIGENCE · AI–HI USE CASE

People Potential / Illustrative evidence hub

Explore the idea.
Shape how it could work.

Before committing to AI-assisted client work, explore the proposal with the people who would make it work. Their experience helps reveal what to protect, what to change and what to test before implementation.

People Potential interpretation · Conversations powered by Haven, a FeedbackRocket innovation

START WITH A POSSIBILITY

Explore an idea with the people who would make it work.

Ask how the proposal fits the organisation before investing in delivery. Early involvement can build familiarity and readiness while surfacing practical requirements and concerns.

01 / STRATEGY

Is it worth pursuing?

What client outcome matters? Where could AI extend human judgement, and what must remain human-owned?

02 / TACTICS

What would enable it?

Which decision rights, quality standards, resources and management practices would the pilot require?

03 / OPERATIONS

How would it land?

Where would it help daily work? What exceptions, extra load or risks do the people doing the work anticipate?

In this demonstration, the findings describe the starting conditions. They guide design and trials; they do not demonstrate successful implementation.

ONE ENGINE · FOUR LAYERS

A question becomes evidence for a decision.

01

Detection

Client + People Potential

Frames the proposed use case and selects tensions and layers to explore. Directional signals target the enquiry; they are not a diagnosis.

02

Extraction

Haven · a FeedbackRocket innovation

Uses adaptive follow-ups to explore experience, examples, concerns and conditions for the idea to work.

03

Identification

People Potential · human interpretation

People Potential interprets patterns and affect in business context, forming hypotheses about process, people and organisational layer.

04

Recommendation

People Potential

Turns working interpretations into sequenced options with authority boundaries, measures and assumptions to test.

WHY THESE OUTPUTS ARE DISTINCTIVE

More than a theme list or a sentiment score.

Traceable interpretation

Connect each finding to anonymised evidence and its strategic, tactical or operational layer. Separate observed experience from a possible explanation.

How it is experienced

The Affective Signal Codebook distinguishes 11 feelings and 6 language registers, with cited words, intensity and uncertainty. Pride, guardedness and resignation can call for different responses to the same process issue.

A practical route to test

The Intervention Mapping Playbook adds a response family, sequence, delivery adjustments, moves to avoid and re-measurement markers. People Potential tailors these to the organisation.

Evidence and reporting discipline

Participants review and approve their conversation summary. Reporting uses agreed anonymisation and cohort boundaries. Codes describe speech, not a person. Thin coverage and scripted positivity lower confidence; ambiguity stays visible. Conversations support hypotheses and do not establish cause.

Method basis: AI–HI Integration Brief; Affective Signal Codebook v1.0; Intervention Mapping Playbook v1.0. The numbers and voices shown here are synthetic, not coded client findings.

THE TENSION ARCHITECTURE

What would it take to make this idea work here?

The same illustrative findings now inform a proposed pilot. Select a tension to connect the signal, organisational layer, participant evidence and possible response. These are working hypotheses, not established causes.

Live — priority for design and testing
Watch — emerging; keep under review
Monitored — present, but not a current priority

The number is a friction signal out of 100: the nearer it is to 100, the stronger or more concentrated the pressure. It is not a percentage of employees.

15 tensions considered · 3 prioritised. Scores are synthetic; higher means more friction.

Human–AI relationship

Organisational design

Complexity & sensemaking

Execution rhythm

Live tension

Human–AI relationship

Human Judgment vs Automation

63/100 friction signal
Human Judgment
Automation

Where does accountability end and the algorithm begin?

Strategy66
Tactics69
Operations55
LIKELY ORIGINStrategy & Tactics
WORKING INTERPRETATIONBoth: process and people
WHAT MEASUREMENT SHOWS

Informal AI use is already present, but authority boundaries, disclosure expectations and accountability are not consistently understood.

WHAT CONVERSATION REVEALS

People are using judgment, but often privately. Unclear rules are producing both concealment and unnecessary checking.

Perception gap

22% of participants are unsure who carries accountability when an AI-supported recommendation is wrong.

“I am accountable for the recommendation, but nobody has told me when I am expected to disagree with it.”Illustrative composite employee voice
“I disclose AI use to people I trust. I do not know whether the firm wants transparency or plausible deniability.”Illustrative composite employee voice
DIRECTION TO TEST

Name the authority model for each use case, establish a safe challenge protocol and make disclosure expectations explicit.

What “perception gap” means here

Within a tension, it is the fraction of coded passages where an employee describes the organisation’s stated position as out of step with lived experience. It is not the percentage of employees who disagree.

FROM FINDINGS TO IMPLEMENTATION CHOICES

Use the hypotheses to design the next move.

The illustrative findings suggest clarifying decision rights and management signals before extending AI use. Leadership can accept, adapt, investigate or decline each option. Implementation is a separate engagement.

ONE EVIDENCE-TO-ACTION EXAMPLE

Decision delays may be a design issue.

Evidence: people learn authority boundaries through rejected requests. Hypothesis: unclear decision rights at the Tactics layer contribute to delay.

Test: co-design a named ownership map and trial one low-risk approval flow, with AI suggesting and a manager authorising. If resignation is evident, deliver a small visible improvement before introducing the wider redesign; avoid a large programme announcement with no follow-through.

Read the outcome: compare cycle time, escalation and quality with the baseline; use Conversational Intelligence Pulse to explore clarity, trust and whether the change is felt. Revise the hypothesis if the evidence does not support it.

01 · Name AI decision rightsAI-suggested · human-authorised

Human Judgment vs Automation · Strategy & Tactics

Define who initiates, recommends, authorises and remains accountable for each priority use case.

Measures to agree: Boundary clarity · challenge rate · unresolved accountability cases

02 · Redesign low-risk approval flowAI-suggested · human-authorised

Centralisation vs Empowerment · Tactics

Use explicit thresholds and AI-supported routing to remove back-and-forth without removing managerial authority.

Measures to agree: Cycle time · escalations avoided · decision-confidence score

03 · Reset the quality signalHuman-led

Speed vs Quality · Strategy–Tactics boundary

Align leadership language, management behaviour, delivery thresholds and recognition with the stated quality commitment.

Measures to agree: Rework · quality exceptions · perception-gap movement

04 · Create safe challenge practiceHuman-led · AI diagnostic

Judgment + Psychological Safety

Make it legitimate and easy to question, override and disclose AI-supported work without diffusing accountability.

Measures to agree: Overrides disclosed · near misses surfaced · psychological safety

05 · Build practice, not just accessAgentic with checkpoints

Capability vs Readiness · Tactics & Operations

Create role-based practice loops, exemplars and peer learning around real client work, with defined risk checkpoints.

Measures to agree: Adoption quality · repeat use · time redirected to higher-value work

CHOOSE · TRIAL · LEARN

Build an implementation plan from what you learn.

01

Agree a bounded trial

Execution Intelligence →

Define the scope, ownership, resources and measures, then put the agreed change into practice. Agree human authority, the baseline, success criteria and conditions for pausing before work begins.

02

Listen alongside delivery

Conversational Intelligence Pulse →
Powered by Haven, a FeedbackRocket innovation.

Explore how people experience the trial and what needs attention. Test a focused assumption before it begins, listen during delivery or revisit a finding afterwards. Read this alongside operational evidence.

03

Reframe what comes next

Reframe What’s Next →

Bring the evidence together, reconsider assumptions and decide what to adapt, investigate or pursue next. Compare outcomes with the hypothesis and report back what was heard, what changes and why.

These are connected options, with each engagement scoped to what you need.

What would we watch in this example?

Approval time and escalation alongside decision clarity; rework and quality exceptions alongside the stated-versus-experienced priority gap. Protect professional pride and client commitment as work changes.

More candid frustration can sometimes reflect returning engagement rather than deterioration. Examine the language and context across the cohort, alongside delivery evidence, before judging progress. No post-implementation results are claimed here.

BEGIN WITH YOUR BUSINESS QUESTION

Make the next decision better informed.

Explore a proposed use case, understand the conditions it would need and shape a practical route into action.