High I and high C: the story and the spec, in the same document

The launch announcement draft has two layers now. The top layer is your high I's prose: confident, warm, a little grand in the way that works. The margin layer is your high C's comments: "source?", "we support 14 integrations, not 'dozens'", "legal will not approve 'guaranteed'", eleven of them, each one correct.

The I opened the doc this morning, read the margins, and closed it again. The C is waiting for replies that are not coming. The launch is in six days and the draft has not moved since Tuesday.

Both of them made the document better. So why does the document feel worse to both of them?

Why this keeps happening

What is happening: The I writes for resonance and treats precision as polish for later. The C reads for accuracy and treats every overstatement as a liability shipping under the company's name. In a shared doc, the I hears nitpicking and the C sees negligence, and the work stalls between them.

How it feels: You need both layers and you know it. But every shared deliverable arrives late and slightly bruised, and you have started writing the contested sentences yourself, which scales nowhere.

Why it should not be this way: Resonance and accuracy are sequential, not opposed. The story gets drafted at full volume first, then verified, and both people need to know which phase the document is in.

Five questions for your next working session

1. Which phase is this document in right now, and who owns the current phase?
2. Which three claims in this draft actually need verification, and which are voice?
3. What did the other person save you from in the last launch, specifically?
4. What is the agreed vocabulary for the gray areas: which superlatives are allowed, which are banned?
5. Where is the deadline for each phase, and what happens to unresolved comments at the cutoff?

Coaching script

Install the phase protocol before the next launch, with both in the room.

• Name both contributions as load-bearing: the I’s voice gets it read, the C’s accuracy keeps it standing. Neither is the polish.
• Phase the document: full-volume draft first with comments off, verification pass second with every comment resolved or escalated, voice pass last.
• Pre-agree the vocabulary: which claims need a source, which superlatives are banned, what legal words are off the table. Most margin wars are the same five words every time.

Conflict repair script

For the silent standoff: closed doc, unanswered comments, launch approaching.

• Name the standoff without blame: "The draft has not moved in three days. That is the protocol failing, not either of you."
• Resolve the open comments live in one sitting, you in the room, each comment answered with a change, a source, or a ruling.
• Then set the phase protocol for next time, and put the phase label at the top of every future draft.

A plan you can start this week

1. Phase the document. Volume first, verification second, voice last. Comments off in phase one. The label at the top of the doc says which phase it is in.
2. Pre-agree the vocabulary. The same five words start most of the wars. Settle them once: what needs a source, what is banned, what legal owns.
3. Resolve, never ignore. Every C comment ends in a change, a source, or an explicit ruling. Ignored comments are how the C stops protecting you.

What happens if you wait

Unmanaged, the I starts routing copy around the C, and the first overstated claim ships unverified. The correction that follows costs more credibility than any margin war ever did.

Or the C wins, every draft flattens to defensible beige, and you wonder why launches stopped landing.

What you'll see in Team Mode

Department Dynamics turns this page from a read into a tool you put in front of both groups this week. Two teams, plotted on the pace and focus axes, with the working agreement written for both sides.

See Team Mode

Frequently asked

How do high I and high C personalities collaborate on content?

Phase the work. The I drafts at full volume with comments off, the C runs a verification pass where every flag gets resolved, and the I does the final voice pass. Both layers survive; the war does not.

Why does a high I avoid a high C’s feedback?

Volume. Eleven accurate margin comments read as one message: this is not good. Batch the feedback into a single phase with a clear endpoint, and the same comments become a service instead of a verdict.

What strengths do an I and C pair share?

Together they make the rarest thing in marketing: copy that is exciting and true. The I supplies reach, the C supplies durability. Every claim survives scrutiny and people still want to read it.

How do you know an I and a C pair is failing?

The doc has stopped moving. The I has closed it, the C is waiting, and neither will say so out loud. The standoff is the failure mode; the doc just becomes its evidence.

Should an I and a C own a launch together?

Yes, and they will produce the best launch you ship that year if you phase the document. Resist the urge to split them across two workstreams. The friction is the feature, with structure.

What if the C will not stop commenting?

They are not over-commenting. The doc is not in the verification phase. Either label the phase explicitly at the top of the doc, or move the doc into verification and let every comment get resolved.

Can the I and C roles trade across launches?

Yes, and you should. Letting the C draft and the I verify once a year teaches each one what the other is paying for. It rarely changes the eventual split, and it always changes the respect.