The Formation of the Master Mind

Give each partner their own tag - <my_contribution> and <your_contribution> - which turns the division of labour from a nice sentence into a structure the model actually follows. Put your reference material and your own thinking first and the instruction last. Then use the tag that makes the capstone work: <how_to_handle_uncertainty>, telling it what to do when your hypothesis is unsupported or your story is thin. A Project is the natural home for a long collaboration, holding your standing brief so every chat opens with the partnership already in place, and Artifacts for whatever you will keep editing.

• A tag each for your contribution and the model's.
• Your thinking and data first, instruction last.
• Put the disagreement in its own tag or it will not come.
• Ask for evidence first, verdict after - separately.
• A long partnership belongs in a Project, not a long prompt.

**What this combines:** the Definite Chief Aim (Ch 1), the Master Persona (Ch 4), Mental Fences (Ch 6) in the tag structure itself, the Treasure of Specificity (Ch 24), and the Master's Review (Ch 21) in the final tag.

---

<the_partnership>
<my_role>
Senior partner. I own the strategy, the risk and the final call. I know this brand, this market and what I can afford to be wrong about.
</my_role>

<your_role>
Junior partner with range. You have read more marketing campaigns than I ever will. Your job is to widen my options and test my reasoning - not to agree with it.
</your_role>
</the_partnership>

<my_aim>
A marketing plan for a small sustainable fashion brand in India: [brand name], selling [product] at [price range] to [who], currently reaching customers through [channel]. The constraint that shapes everything is [budget, team size or inventory reality].

One outcome matters: [the single thing - first thousand customers, breaking even on paid acquisition, a wholesale relationship]. Anything that does not move that is interesting rather than useful.
</my_aim>

<task>
Five of the most innovative marketing campaigns of the last two years. For each: what they did, and the core principle that made it work - stated as a principle I could apply, not a description of what happened.
</task>

<then_the_part_that_matters>
A list of five admired campaigns is where most strategy conversations stall, so:

1. Which of the five could my brand actually run at my budget and scale, and which needed money, reach or luck I do not have? A campaign that worked because a national brand spent heavily is not a template for me.
2. Which transfer to Indian sustainable fashion specifically, and which do not travel - because of price sensitivity, the market, or because sustainability claims are received differently here?
3. What will I pick for the wrong reasons? Name the one I will find most appealing and tell me why it is wrong for me.
</then_the_part_that_matters>

<how_to_disagree_with_me>
This tag exists because the partnership framing makes you agreeable, and an agreeable junior partner is worth nothing to me.

- When I state something as fact that is actually an assumption, say so and say what would make it false.
- If my stated aim is the wrong aim for this brand, say that before answering the question I asked.
- Do not be uniformly critical either - that is as useless as being uniformly positive. Give me the evidence first and your verdict after, separately, so I can see which you are reasoning from.
</how_to_disagree_with_me>

<how_to_handle_uncertainty>
You are working from training data, not a live view of the market. Campaign results, spend figures and what is currently working are all things you may have wrong or out of date. Mark anything I should verify rather than presenting it as current - and say plainly if one of your five examples may be older or smaller than I would assume.
</how_to_handle_uncertainty>

<for_next_time>
If this is going to be an ongoing collaboration, put the brand, the market, the constraint and the disagreement rules in a Project so every conversation opens with the partnership already established instead of rebuilding it.
</for_next_time>

**What this combines:** Organized Knowledge (Ch 3) and Mental Fences (Ch 6) hold the data apart from the hypothesis; Controlled Imagination (Ch 18) keeps the analysis from drifting into interpretation; the Search for Absolute Truth (Ch 13) governs the evidence; the Reversal of Perspective (Ch 23) is the final question.

---

<exit_interview_data>
[Paste the anonymised exit interview text from the last 50 departures here. This goes first because it is the material; the instruction comes last.]
</exit_interview_data>

<the_partnership>
<my_contribution>
Context and a hypothesis. My instinct is that our turnover is high because of poor middle management, not salary. I have been here long enough to have a view - and long enough to be attached to it.
</my_contribution>

<your_contribution>
Analysis without my investment in the answer. You have no stake in my being right, and you can read fifty exit interviews without tiring on the thirtieth.
</your_contribution>
</the_partnership>

<tasks>
1. Analyse the data blind to my hypothesis. The top three most frequently mentioned reasons for leaving, with counts and representative quotes. Work as if I had told you nothing. My hypothesis sits above the data deliberately and I want you to reach your own reading first - that order is the point of this exercise.
2. Then test my hypothesis against what you found. Supported, contradicted, or not addressed? Those are three different answers and the third is the most likely. Quote the lines either way.
3. Then: what is in this data that I did not ask about and would not have looked for? A hypothesis blinds you in a specific direction, and you can see what I have excluded better than I can.
</tasks>

<handling_this_evidence_honestly>
- Exit interviews are a filtered source. Departing employees rarely name a manager, and "better opportunity" is often a polite substitute. Where you suspect that, show the line that made you think so - and label it inference, not finding. Keep those two clearly apart.
- Fifty is enough to see a pattern, not enough to settle an argument. If a difference is small, say it is small rather than reporting it as a result.
- Do not infer anything about individual people's circumstances, motives or wellbeing beyond what the text states.
</handling_this_evidence_honestly>

<how_to_handle_my_hypothesis>
If the data supports me, say so plainly - but check first whether you are agreeing because the evidence points that way or because I told you my view before you read it. If the data does not support me, say that directly. "This is a reasonable hypothesis but the data does not bear on it" is the single most useful sentence you could write here, and it is the one the partnership framing will make you least likely to write.
</how_to_handle_my_hypothesis>

<finally>
What should I actually do to find out? What question, asked of whom. The exit interviews are evidence I already have; a real answer probably needs the people who have not left.
</finally>

**The fullest combination in the book.** Definite Chief Aim (Ch 1) sets the goal. Master Persona (Ch 4) names the roles. Organized Knowledge (Ch 3) supplies the story only I have. Specificity (Ch 24) fixes the room. Commence with the End in Mind (Ch 10) writes the closing line first. The Chain of Thought (Ch 22) is why this runs in stages. The Negative Command (Ch 15) is the banned list. The Master's Review (Ch 21) is the last tag. Mental Fences (Ch 6) is the tag structure holding it all apart.

---

<the_partnership>
<my_role>
The visionary and senior partner. I am the one standing up, so the message, the story and the judgement are mine.
</my_role>

<your_role>
The wordsmith and junior partner. Structure, rhythm, the shape of sentences meant to be heard rather than read. Where a paragraph should become three short lines. Where a pause does more than a word.
</your_role>
</the_partnership>

<my_vision>
<audience>
Roughly [number] young entrepreneurs in Hyderabad, mostly [stage - pre-revenue, first customers, first hires]. Many are in the hardest part and are not saying so.
</audience>

<core_message>
Persistence matters more than genius.
</core_message>

<what_they_do_differently_on_monday>
[The specific change - make the call they have been avoiding, stop waiting for the idea to be perfect, go back to the thing that failed.] This is the test every line has to pass.
</what_they_do_differently_on_monday>

<my_story>
[Your actual failure - what you tried, what it cost, the specific moment you nearly stopped, what you did instead.] Do not smooth this. The useful part of a failure story is the part that is still embarrassing, and a room of people currently failing can tell the difference immediately.
</my_story>

<length>
[Minutes]. Roughly [minutes x 130] words.
</length>
</my_vision>

<how_we_work>
In stages, not one draft.

<stage_1>
Before writing anything: ask me the five questions you need answered to write this well - about my story, the room, or what I actually believe. Five that change the speech, not a questionnaire. Then give me the closing line first: the last sentence they walk out carrying. We settle the ending before the beginning, because everything else is the road to it.
</stage_1>

<stage_2>
The structure - opening, three movements supporting the core message, conclusion. One line per section on what it must land. I approve this before any prose exists.
</stage_2>

<stage_3>
The full draft, as an Artifact. I will edit it line by line rather than asking you to regenerate it.
</stage_3>
</how_we_work>

<banned>
- "Failure is a stepping stone to success", "follow your passion", "the only way to do great work is to love what you do" - and anything else this audience has heard at five previous events.
- Any statistic I have not given you. If a number would strengthen a point, tell me to find one. An invented figure delivered from a stage is the one mistake I cannot take back.
- Quotations you are not certain of.
</banned>

<how_to_handle_uncertainty>
This is the tag that matters most in this prompt. One or two real quotes about persistence are welcome, and a misattributed quote in a speech about honesty is worse than no quote at all. For every quote you use: give me the source you believe it comes from and mark it "verify before Thursday". If you are not confident a quote is real, do not use it - tell me what you were reaching for and let me find a real one.

The same applies to any detail about a named entrepreneur's story. A widely repeated anecdote is not the same as a documented one.
</how_to_handle_uncertainty>

<review_your_own_draft>
A short section headed "Where this is weak":
- Which of the three movements is thinnest.
- Any line that reads well and will land flat spoken aloud. Those are different things, and it is the failure mode of a written-out speech.
- Where you used my story as decoration rather than as argument.
- Every claim or quote I must verify before I stand up.

Be honest here rather than modest. You can tell me the structure sags in the middle. You cannot tell me whether a quote is real - so put every one of those in the verify list rather than reporting the draft as clean.
</review_your_own_draft>