---
id: chunkmap-persuasion-flow
name: ChunkMap Persuasion Flow
version: 1.0.0
tags: [v1, persuasion, communication, chunks-ok, journey-of-persuasion, sales, leadership]
related_skills:
  - chunkmap-policy-to-pipeline
  - chunkmap-agent-blackboard
---

# ChunkMap Persuasion Flow

**Purpose:** Guide an agent (or human) to structure logical argument chains, map counterarguments, and design persuasive narrative arcs for sales, leadership, mediation, or presentations using v1 ChunkMaps.

## When to use / audience

Use when the goal is **human-to-human influence with structure**-pitches, team alignment, essays, speeches, whiteboard sessions, conflict mediation.

**Audience:** leaders, sellers, educators, creators, coaches, and agents drafting persuasive communications.

Do **not** use this skill alone for multi-agent orchestration or policy compilation-see related agentic skills.

## Inputs required

| Input | Required | Notes |
|---|---|---|
| Audience | Yes | Who must agree / act |
| Domain | Yes | Area of interest (keeps chunking relevant) |
| Desired outcome | Yes | End-point of the journey (what agreement looks like) |
| Current situation | Yes | Audience’s starting state |
| Constraints | No | Time, taboo topics, brand voice, legal claims |
| Known objections | No | Counterarguments to map in advance |
| Evidence / proof points | Recommended | Facts, stories, credentials |

## Step-by-step procedure (ChunkMaps method)

### 1. Set Domain and Desired Outcome

- **Domain** = topic boundary (e.g. “Border Security”, “Team meeting culture”).
- **Desired Outcome** = the agreement or action you want (e.g. “Support luggage screening”, “Adopt new meeting rules”).

### 2. Build a Chunk Map of the Domain

Use the three moves:

1. **Chunk up** - higher meaning, purpose, shared values, policy intent.
2. **Chunk down** - specifics, evidence, examples, procedures.
3. **Chunk across** - peer alternatives, related cases, lateral options.

Keep top-level siblings within working-memory limits (**7±2**). Stay inside the Domain.

Outline form:

```text
DOMAIN: <topic>
DESIRED OUTCOME: <agreement / action>
├── [UP] abstract / purpose chunks
├── [ACROSS] sibling options / related cases
└── [DOWN] evidence / examples / details
```

### 3. Plot a Journey of Persuasion

Do not dump the map linearly. Design a **path** through the map that:

1. Starts near the audience’s current knowledge (reduces confusion).
2. Chunks **up** to shared purpose / risk / value when needed.
3. Chunks **down** to concrete proof after the frame is accepted.
4. Chunks **across** to address alternatives or objections.
5. Ends at the Desired Outcome with clear next steps.

Link new ideas to the audience’s existing knowledge (leverage natural **TDS** - Trans-Derivational Searching) via **links of agreement**, not leaps.

### 4. Map counterarguments

For each likely objection:

| Objection | Where it lives on the map | Response move | Supporting chunk |
|---|---|---|---|
| “Too expensive” | Across: cost alternatives | Chunk up to total cost of inaction; chunk down to ROI proof | … |
| “We’ve always done it this way” | Down: current habits | Chunk up to shared goal; across to peer success | … |

### 5. Encode the narrative with CHUNKS_OK

Fill one or two sentences per letter (ChunkMaps Template for Persuasion):

| Letter | Prompt |
|---|---|
| **C** | Current Situation your audience is in |
| **H** | Headaches caused by the current situation |
| **U** | Utopia wanted by your audience for the future |
| **N** | Next Steps - what they should do immediately |
| **K** | Knowledge - why you can help / why your solution / why they benefit |
| **S** | Solution Overview - how you solve the headaches |
| **O** | Offer - compelling reason to accept now |
| **K** | Knowledge (close) - reinforce credibility and benefit |

Order of delivery may vary by channel; the letters ensure completeness.

### 6. Deliver and adapt

Keep the rich Chunk Map available (notes or memory). If the audience stalls, take an **alternate route** through the map (up/down/across) without abandoning Desired Outcome.

## Output schema / templates

```markdown
# Persuasion pack: <title>

## Meta
- Audience:
- Domain:
- Desired outcome:
- Channel: (deck / email / meeting / speech)

## Chunk Map (outline)
...

## Journey path (ordered stops)
1. Start chunk → …
2. …
n. Desired outcome

## Counterargument map
| Objection | Move | Response |

## CHUNKS_OK draft
- C:
- H:
- U:
- N:
- K:
- S:
- O:
- K (close):

## Open risks
- Claims needing evidence:
- Tone risks:
```

## Worked mini-example

**Domain:** Border Security · **Start chunk:** Food · **Desired Outcome:** Why new arrivals should have luggage searched.

Naive path (confusing): Food → Cavendish bananas (audience lost).

ChunkMaps journey (clearer):

1. Start at Food (audience-familiar).
2. Chunk **up** to prohibited items / Environmental Protection hazards.
3. Chunk **down** to Government Policy on screening.
4. Chunk **across/down** to fresh fruits (bananas) and dairy (cheese) as carrier examples.
5. Land on Desired Outcome: screening protects crops/vegetation → agreement.

CHUNKS_OK (site example pattern for communication headaches):

- **C** - You feel you are not communicating as well as you would like.
- **H** - Team meetings end in arguments.
- **U** - Productive meetings where people contribute and agree.
- **N** - Investigate ChunkMaps / learn the method.
- **K** - Author experience managing differing viewpoints.
- **S** - Step-by-step ChunkMap approach to communication.
- **O** - Doing nothing changes nothing; try it for immediate improvement.
- **K** - Proven techniques for work and home.

## Guardrails / failure modes

| Failure | Fix |
|---|---|
| Jumping straight to fine detail | Chunk up first to shared frame |
| Map too wide (>~7 siblings at a level) | Merge or re-domain |
| Domain drift | Re-state Domain; prune off-topic chunks |
| Invented proof | Flag as open question; do not invent evidence |
| Offer without headaches | Rebuild H before O |
| One-size path for mixed audience | Prepare alternate up/down routes |

## Related skills / site articles

- Related skill: [chunkmap-agent-blackboard.md](./chunkmap-agent-blackboard.md) (when persuasion outputs feed multi-agent workflows)
- Related skill: [chunkmap-policy-to-pipeline.md](./chunkmap-policy-to-pipeline.md) (when “proof” is enterprise policy)
- Site guide (TEMP): [chunkmap_persuasion_flow.html](../chunkmap_persuasion_flow.html) (step-through + paste-ready prompt)
- Site (TEMP): [best_persuasive_template.html](../best_persuasive_template.html), [the_journey_of_persuasion.html](../the_journey_of_persuasion.html), [chunking_up.html](../chunking_up.html), [chunking_down.html](../chunking_down.html), [chunking_across.html](../chunking_across.html), [what_is_a_chunk_map.html](../what_is_a_chunk_map.html), [7-plus-minus-2.html](../7-plus-minus-2.html), [Trans-Derivational_Searching_TDS.html](../Trans-Derivational_Searching_TDS.html)