Margin codes that survive a hostile meeting
Hostile is a strong word. Most strategy meetings are merely impatient. Someone asks whether a technical journal “supports” a launch claim, and the reader who loved the paper three days ago cannot find the sentence that mattered.
We teach a four-code margin system that fits most technical articles:
- M — methods concern (design, sampling, measurement)
- C — claim leap (conclusion stronger than data)
- X — conflict with another source already in the packet
- Q — open question that would change the decision if answered
Write the code in the margin and three to six words of substance. Do not write “interesting.” Interesting evaporates under fluorescent lights.
In the Journal & Strategy Lab we collect codes on a shared board before anyone drafts strategy language. The board looks messy. That mess is the point: strategy refinement starts from visible friction, not from a polished abstract paraphrase.
If you practise alone, set a timer for twenty minutes of silent coding before you allow yourself to summarise. Summaries without codes are how overconfident briefs are born.