Message with Metadata
Label certainty and intent before others interpret your message
- Difficulty
- Starter
- Time to result
- ~days to results
- Steps
- 4
- Confidence
- 98%
Message with Metadata adds a compact status layer to ordinary communication. First deliver the substantive claim or recommendation. Then label how sure you are and why: perhaps it is backed by a checked fact, a historical example, data, or only a guesstimate. Finally state the purpose of the exchange, such as requesting feedback, asking for a decision, or sharing an FYI. This separates content from confidence and intent, giving the recipient the context needed to interpret the message correctly. It also makes strong disagreement healthier because people can challenge the evidence or uncertainty without treating every statement as a fixed position. The mechanism is simple enough for meetings, messages, and documents, and it reduces conflict caused by mismatched expectations about what each person thought the exchange meant.
Origin
Mustafa Suleyman describes this as a basic communication practice he often asks teams to use when exchanging strong opinions, evidence, guesstimates, feedback requests, and FYIs.
Core principles
- 01A claim and its confidence level are separate information
- 02Evidence should determine how strongly a message is delivered
- 03The recipient needs to know what response the sender expects
- 04Explicit uncertainty prevents avoidable conflict
How to run it
- 1
Deliver the core message
State the claim, recommendation, or update directly so the recipient can identify the substance before interpreting its status.
Pro tip Keep the status label separate from the core sentence so neither gets buried.
Watch out Do not use metadata to soften a message until its meaning disappears.
- 2
Label certainty
Say whether you are highly confident, uncertain, or offering a guesstimate. Match the confidence to the evidence you actually possess.
Pro tip Use plain phrases such as 'I'm really sure' or 'I'm really not sure.'
Watch out Confidence is not evidence; name the basis separately.
- 3
Attach the evidence status
Reference the fact, data, historical example, or empirical case behind the message. If none exists, explicitly call the statement a guesstimate.
Pro tip A clear guesstimate is more useful than an unsupported claim dressed as certainty.
Watch out Do not imply that a reference proves more than it actually supports.
- 4
Name the expected response
Tell the recipient whether the message is an FYI, a request for feedback, a recommendation, or a call for action.
Pro tip End with one explicit response mode when ambiguity would create work.
Watch out Do not ask for feedback when the decision has already been made.
In the wild
A product lead writes: 'I think this launch can move forward next week. I'm moderately sure because the critical tests pass, but the support-volume estimate is a guesstimate. I'm looking for feedback from operations before deciding.' The team can now challenge the weak input without reopening settled technical work.
→ The discussion focuses on the uncertain support assumption and reaches a decision faster.
Common mistakes
Presenting a guesstimate as fact
Unlabeled uncertainty makes recipients over-trust a claim and creates conflict when assumptions surface later.
Leaving the response implicit
Recipients may act on an FYI or ignore a request because they do not know what the sender expects.
Is it for you?
Best for
It is best for collaborative teams exchanging recommendations, estimates, decisions, and early ideas under uncertainty.
Not ideal for
It is not ideal for trivial messages where confidence, evidence, and expected response are already obvious.
From the transcript
“deliver your message with metadata.”
“They need to be explicitly named as a gueststimate.”
“letting each other know like what the status of our exchange is helps to kind of often I see conflicts arise from a mis expectation…”
From the episode
Mustafa Suleyman: Harnessing AI to Transform Work, Business, and Innovation
Mustafa Suleyman