You rarely need a dramatic moment to understand whether someone is likely to build with you.
It is usually hidden in the tiny stuff.
A two-second pause before answering.
Whether they ask a question back.
How quickly they turn an idea into a concrete next step.
Whether they remember something you said three conversations ago.
Whether they say “we should do this” and then actually do something about it.
These are micro-signals.
They are not mind-reading. They are not proof of someone's intentions. But when you observe enough of them over time, they can help you estimate something incredibly useful:
How much probability should I assign to this person actually moving with me?
And once you have that estimate, you can pre-plan your route.
The problem with judging people from big signals
Most people look for obvious signals.
“Are they excited?”
“Did they say yes?”
“Did they compliment the idea?”
“Did they say they want to work together?”
The problem is that big signals are cheap.
Almost anyone can say:
“Sounds amazing.”
The more valuable information is often hidden inside what happens after that sentence.
Do they open the document?
Do they make the introduction?
Do they send the data?
Do they show up?
Do they suggest a better version?
Do they take ownership without being chased?
The difference between interest and movement is enormous.
Someone can be genuinely excited about you and still be a terrible person to build with.
Micro-signals are probability updates
Think of collaboration less like a yes/no decision and more like a probability curve.
You start with uncertainty.
Maybe there is a 30% chance this person will actually build with you.
Then you observe something.
They respond with a specific idea.
Your estimate moves to 40%.
They independently complete a small task.
Maybe 55%.
They introduce you to someone useful without being asked.
65%.
They miss two agreed deadlines without communicating.
The probability drops.
This is basically Bayesian thinking applied to human behavior—not because people are mathematical objects, but because every new piece of evidence should update your expectations.
The mistake is treating one signal as destiny.
The better approach is:
Look for repeated behavioral evidence.
The Five-Second Signals
Some of the strongest signals take almost no time to observe.
1. The specificity signal
You say:
“We could build something around this.”
They respond:
“Yeah, maybe.”
Low information.
Another person responds:
“If we target X users first, we could test it with Y workflow.”
High information.
Specificity usually indicates that someone's brain has already started simulating the project.
They are no longer merely reacting to your idea.
They are mentally building inside it.
2. The question signal
Pay attention to what someone asks after you explain an idea.
There is a massive difference between:
“How much would this make?”
and:
“What would we need to prove first?”
The second question reveals something deeper.
They are moving from evaluation to construction.
Questions expose where someone's attention naturally goes.
Some people immediately look for risks.
Some look for status.
Some look for money.
Some look for technical feasibility.
Some look for the next move.
None is automatically good or bad.
But it tells you what kind of route they are likely to take.
3. The friction signal
Watch what happens when the first obstacle appears.
This is one of the highest-value signals.
When everything is exciting, almost everyone looks motivated.
Then reality arrives.
The API doesn't work.
The customer doesn't respond.
The prototype breaks.
The meeting gets postponed.
The original assumption was wrong.
Now observe.
Does the person disappear?
Complain?
Wait for you to fix it?
Or say:
“Okay. That path is blocked. What's another way?”
That response tells you far more than their original enthusiasm.
People reveal their collaboration quality under friction.
The "Next Action" Signal
One of my favorite signals is extremely simple:
Does the conversation naturally produce a next action?
Compare:
Conversation A
“Yeah, this could be really interesting.”
“Definitely.”
“We should do something.”
“Absolutely.”
Nothing happens.
Versus:
Conversation B
“Let's test this.”
“Okay. I'll build the first version.”
“I'll find three users.”
“Let's check again Thursday.”
Now there is movement.
The second conversation contains coordination.
Coordination is expensive.
When someone commits time, reputation, effort, money, or social capital, you learn much more about their actual willingness to build.
Words describe intention.
Actions reveal commitment.
The Tiny Delay That Matters
Sometimes the signal isn't what someone says.
It's the transition between receiving information and responding.
Someone hears your idea.
There is a pause.
Then:
“Wait. If that's true, couldn't we also...?”
That pause can be interesting.
Their brain may be processing rather than performing.
But don't over-romanticize it.
A pause doesn't automatically mean intelligence, interest, or commitment.
The useful signal is what follows.
Pause + deeper question = interesting.
Pause + avoidance = different signal.
The same micro-behavior can mean different things depending on context.
That's why individual signals are weak.
Signal clusters are powerful.
Build a Signal Stack
Instead of asking:
“Does this person like me?”
ask:
“What evidence do I have about how this person behaves when building?”
You can create a simple signal stack.
| Signal | What it may indicate |
|---|---|
| Asks specific questions | Cognitive engagement |
| Remembers details | Attention |
| Suggests next steps | Initiative |
| Completes small tasks | Reliability |
| Handles friction calmly | Resilience |
| Introduces useful people | Social investment |
| Challenges assumptions | Intellectual engagement |
| Takes ownership | High collaboration potential |
| Repeatedly delays | Low execution reliability |
| Requires constant prompting | Low autonomous momentum |
None of these should be treated as proof.
They are probability modifiers.
That's the important distinction.
Don't Confuse Chemistry With Compatibility
This is where people get burned.
You can have incredible conversations with someone and still be terrible collaborators.
Chemistry creates excitement.
Compatibility creates output.
Someone may understand your ideas instantly but hate ambiguity.
Someone else may disagree with you constantly but consistently turn messy ideas into working systems.
Which person is more valuable?
Depends on the mission.
The real question isn't:
“Do we vibe?”
It's:
“Does the way this person naturally operate fit the kind of thing we're trying to build?”
Pre-Planning Your Route
Once you start observing these signals, something interesting happens.
You stop planning around ideal behavior.
You start planning around observed behavior.
Suppose someone is brilliant but slow to respond.
Don't complain about it every week.
Design around it.
Give them decisions that don't require immediate responses.
Suppose someone is extremely fast but frequently changes direction.
Don't give them the entire roadmap.
Give them short feedback loops.
Suppose someone is highly reliable but doesn't initiate.
Give them clearly owned responsibilities.
Suppose someone is excellent at introductions but weak at execution.
Use them where their network matters.
This is the real advantage of reading micro-signals:
You stop trying to change people and start designing the route around the people you actually have.
The Strongest Signal: What Happens Without You
There is one signal that deserves special attention.
What happens when you stop pushing?
If you disappear for three days, does anything move?
Does the person follow up?
Does the project continue?
Does someone else take ownership?
Or does everything freeze?
This is brutally informative.
Because constant prompting creates artificial momentum.
You may think:
“We're building together.”
But perhaps the reality is:
“I'm building, and they're responding.”
Those are completely different situations.
The Anti-Signal
Sometimes the most useful information is negative.
You propose a small experiment.
They repeatedly say yes.
Nothing happens.
You follow up.
Another yes.
Still nothing.
At some point, stop collecting explanations and start collecting data.
The reason might be:
- They're busy.
- They're uncertain.
- They're polite.
- They're distracted.
- They don't prioritize it.
- They like you but don't like the project.
- They like the project but don't want to build it.
- They simply aren't reliable.
You don't actually need to know which explanation is true to make a planning decision.
You only need to know:
“Can I safely build my route assuming this person will execute?”
If the answer is no, route accordingly.
Micro-Signals Should Change Your Route, Not Your Respect
This is important.
Reading signals isn't about labeling people as:
good / bad
or
useful / useless.
People have different capacities at different times.
Someone can be a fantastic friend and a terrible cofounder.
Someone can be a brilliant engineer and a terrible manager.
Someone can be incredibly creative but unreliable with deadlines.
Someone can be slow but extremely dependable.
The goal isn't to judge their human value.
The goal is to understand operational fit.
That's a much cleaner question.
The Micro-Signal Advantage
The biggest advantage isn't predicting people perfectly.
You can't.
The advantage is reducing expensive surprises.
If you notice early that someone:
- doesn't initiate,
- avoids ownership,
- struggles with ambiguity,
- needs constant prompting,
- or disappears under pressure,
you don't need to wait six months to discover it.
You can change the route now.
Likewise, if someone consistently:
- turns ideas into experiments,
- keeps promises,
- asks sharp questions,
- handles uncertainty,
- creates momentum,
- and takes responsibility,
you can increase the amount of the journey you trust them with.
That's the real power of micro-signals.
Not prediction.
Calibration.
The Rule
Don't ask:
“Can I trust this person?”
Ask smaller questions.
“Can I trust them with this specific thing?”
Then observe.
Can they handle a small commitment?
Can they handle ambiguity?
Can they handle disagreement?
Can they handle pressure?
Can they handle ownership?
Trust doesn't have to be a giant leap.
You can build it incrementally.
Small signal → small bet → observed outcome → updated belief → bigger or smaller bet.
That's how you build a route through uncertainty.
Final Thought
People tell you who they are in dramatic moments.
But they also tell you who they are in thousands of tiny moments that nobody thinks are important.
The speed of a reply.
The quality of a question.
The follow-through after an exciting conversation.
The reaction to a broken plan.
The willingness to take the next step.
The behavior when nobody is watching.
These moments are easy to ignore because each one seems insignificant.
But stacked together, they form a map.
And once you have the map, you don't have to guess the entire journey.
You simply decide:
“Given what I've observed so far, what's the smartest next step?”
That's what micro-signals are really good for.
Not predicting people.
Pre-planning your route through uncertainty.
Top comments (0)