Spot the Hidden Assumption in a Coworker Claim

Sharp debates often argue conclusions while the premise sits unstated. Spotting the hidden assumption in a coworker claim turns volume into a checkable line. You still disagree. You just stop shadowboxing.

Use it beside forced trade-offs when options multiply: rank three options with a forced trade-off matrix.

Listen for Must, Always, and Only

Those words hide constraints. Write the claim in one sentence, then add because. If the because is missing, ask for it once. Skip stacking five follow-ups. One clear ask keeps the room calm.

Mute badge noise first so you can hear the claim, as in mute desktop badges until the next calendar break.

Separate Fact From Preference

Facts cite a source or a number. Preferences cite taste. Mixed claims blur both. Label each part before you argue. If preference drives the call, say so and move to criteria instead of fake certainty.

When research tabs bloom, timebox them: timebox curiosity with a hard stop desk timer.

Ask What Would Falsify It

A usable assumption names what would kill it. If nothing could, you are holding a belief, not a test. Write one falsifier on the whiteboard. That single line often ends circular talk.

Keep falsifiers boring and measurable. Drama invites defense.

Test the Assumption on a Small Slice

Pick a one-week check, a sample account, or a single funnel step. Large proofs delay learning. Small tests keep the claim honest without halting the project.

If the claim is strategic, force a trade-off axis so the assumption cannot win every column.

Capture the Premise in the Decision Note

Write: we chose X assuming Y. Store it where the work lives. Future disagreements should target Y, not vibes. Pair with a clear next physical action so the note leads to work: name the next physical action before you open Slack.

When seating and voices blur after a hard meeting, rebuild the map before you assign owners: sketch the room layout from memory after you leave.

Practice on Low-Stakes Claims First

Run the drill on lunch plans and tool picks before board decks. Muscle memory on small claims transfers. Keep tone curious. Premises feel personal when people feel attacked.

End the week by listing three assumptions you challenged. Patterns appear: cost, timeline, or user intent.

Practice naming assumptions in writing before meetings. Take a Slack claim, write Claim / Because / Falsifier, and send only if the because is missing. Written drills transfer into live rooms with less heat.

If the claim is about users, demand a sample size. Assumptions about everyone usually mean a loud few.

FAQ

Is this the same as playing devil advocate?
No. You surface the premise; you do not invent a rival thesis for sport.

What if people get defensive?
Ask for the because once, then offer your own assumption for critique.

How long should the interrupt take?
Under two minutes. Longer becomes a new meeting.

Can I do this in chat?
Yes. Quote the claim and ask for the missing because in one line.

What if the assumption is political?
Name it gently and decide whether the room can test it. Untestable politics need a different forum.

Do I need a template?
A sticky with Claim / Because / Falsifier is enough.