Coworker Friendly or Flirting? The 3-Signal Rule

Friendly. That's the default, and it holds until multiple signals stack against her personal baseline — over weeks, in ways that cost her something. One laugh, one arm touch, one warm goodbye is not information. The research is embarrassingly one-directional about which sex needs to hear this. And the fix isn't studying her harder — it's raising the bar the evidence has to clear, then living with whichever answer comes back.

TL;DR

• Verdict: friendly, until proven otherwise. Warmth at work is baseline behavior, not evidence.
• The test: score her behavior toward you against her behavior toward everyone else, never against a listicle.
• The bar: three or more deviations from her baseline, initiated by her, sustained over weeks.
• What counts: off-channel contact, one-on-one time she creates, held repeated eye contact, memory of small details.
• What doesn't: laughing, an arm touch, remembering your birthday, being nice on Slack.
• If it's a no or she reports to you: it's a no. Scroll to how to let it go — that section exists for a reason.

If you've spent two hours at a work party tracking someone's position in your peripheral vision, then fifteen minutes in the car replaying a "you too!" through every decoder you own — you're not confused, you're overloaded. The decoding problem feels like a data shortage. It's usually a bias problem, and the bias is on your side of the table.

So we're starting with the table you actually came for, not the psychology lecture.

Friendly vs flirting: what actually separates the two?

One principle does nearly all the work: judge her behavior toward you against her behavior toward everyone else, never against a generic list of signs. Warmth is a personality trait — and at work, partly a job requirement. Deviation from her own baseline is information. Behavior she shows everyone is just her.

Her baseline is how she treats colleagues she has zero romantic interest in. That's the control group, and a signal exists only as a difference from it. This is why "signs she likes you" listicles fail: they score the behavior and never score the baseline — and the work baseline is inflated by design. A smile at the office is the least informative smile she produces all day.

Behavior	Reads as friendly when...	Worth noticing only when...
Laughs at your jokes	She laughs generously with everyone; it's her social style	She laughs at yours specifically — including the weak ones — and nowhere else
Brings you a coffee	She's the one who does snack runs for the whole pod	You're the only recurring recipient, unprompted, more than once
Asks about your weekend	Monday small talk is workplace liturgy	She follows up Thursday on a detail you mentioned once
Touches your arm	She's expressive and tactile with friends of both sexes	Touch shows up only with you, across separate occasions
Long eye contact	Normal conversational attention; people look at people	Held noticeably longer with you than with others, repeatedly
Messages you	It's about work, on work channels, at work hours	She opens non-work threads, off-channel, on her own time
One-on-one time	Project structure puts you together	She creates it when nothing about the job requires it

Every entry in the right-hand column is a deviation — from her baseline, from what the job requires, from what the politeness script prescribes. That's the entire method. Not "did she laugh," but "does she laugh like that at Dave from finance." One honest limit: you can't see her full baseline — one context, a few hours a week, filtered through your own bias. Which is one more reason the friendly default deserves to outlive your patience with it.

Three gray-area cases, decided

Most real situations aren't in the table's clean columns. These three patterns come up constantly. They're composites, not case reports — the point is the reasoning, not the people.

Pattern 1: the 9 a.m. meme sender. She DMs you funny links most mornings on Slack, never anything personal, and has never texted your phone. Verdict: friendly. The channel is doing the talking. Slack is a zero-cost, fully deniable, work-sanctioned space — she can send you a meme with her entire team one alt-tab away. Deniability is free here, so nothing is being risked, so nothing is being signaled. Watch what happens if the memes ever migrate to SMS on a Saturday. Until then, you're her favorite audience, which is genuinely nice and nothing more.

Pattern 2: the intense project. Six weeks on a launch together: late pizza, inside jokes, she remembers your coffee order, the eye contact runs long. Then the project ships and it evaporates back to hallway-nod level. Verdict: friendly — and the fade proves it. Shared pressure manufactures closeness that feels exactly like chemistry from the inside. The org chart created the proximity; you didn't, and neither did she. The tell is what survives the deadline. If she's still creating one-on-one time in week three of the quiet period, now you have something.

Pattern 3: the almost-signal. She texts your personal phone at 10 p.m. — but about a client fire. She lingers after standup — but she lingers after standup with everyone. She asks about your weekend on Thursday — the same Thursday she asks three others. Verdict: friendly, and this is the one that hurts. Each item is one honest step from a real signal, which is why your brain keeps rounding up. Score each behavior against the baseline separately; three near-misses do not add up to one hit. Rounding up three times is exactly the error the next section explains.

Which coworker signals actually carry information?

The signals worth weighting share three properties: she initiates, it costs her something, and it repeats. Warmth, laughter, politeness, one party-adjacent arm touch — none of it clears that bar. What does:

1. Off-channel initiation. She starts non-work conversations in non-work spaces — texting your phone, not your Teams — on her own time. This costs her deniability, which is exactly why it carries signal.
2. Engineered proximity. One-on-one time the org chart doesn't explain, created by her, more than once.
3. Held, repeated eye contact. Not a glance. In Kellerman's 1989 experiment, two minutes of mutual gaze between strangers measurably raised reported attraction. Gaze is potent — which is why adults ration it, and why someone repeatedly spending it on you is spending something real.
4. Asymmetric memory. She retains and resurfaces small details of your life, unprompted, weeks later.

The rule this article stands behind: three or more of these, initiated by her, sustained across weeks — before you're allowed to move the needle off "friendly." Notice how much higher that bar sits than wherever your gut just put it. That gap is the calibration.

A full stack still isn't certainty — it's a probability shift. It earns you no green light; at most, the standing to make one respectful, easily-declinable move outside work. Which is the part most articles refuse to spell out.

Why does the bar have to sit that high?

Because male perception reliably over-reads warmth, and the office punishes that error harder than any other setting.

The cleanest demonstration is Abbey's 1982 experiment. A man and a woman talked for five minutes while another man and woman observed; everyone then rated the interaction. Both the male participant and the male observer rated the woman as more seductive and more promiscuous than either woman rated the same five minutes. Same room, same behavior, two different movies. Haselton and Buss later named the mechanism: error management theory — when two errors carry lopsided costs, perception drifts toward the cheaper one. Ancestrally, a missed opportunity cost more than an awkward false alarm, so the male read skews positive the way a smoke alarm skews jumpy.

Biased doesn't mean always wrong — coworkers do fall for each other. It means your unaided read overstates the odds in a known direction, so the bar has to sit above where your gut wants it.

And the modern office inverts the old cost matrix. A false positive here — acting on interest that isn't there, with someone who shares your Slack channels and your manager — costs vastly more than a false negative, and she pays first. Your alarm was calibrated for a different building. (For the other half of the correction — what actually registers with women in the first place — see what women actually find attractive.)

What should you do at work — and what should you never do?

At work, behave as if the answer is "friendly" even while your private model updates. Not because your read must be wrong — because the office is the one environment where testing it isn't yours to do cheaply. She can't freely exit the interaction the way she could at a bar. Her politeness is load-bearing: team dynamics, reputation, reviews. Every ambiguous move you make is something she has to manage at her job.

So the never-list, in order of importance:

• Never run tests. Escalating touch, loaded jokes, engineered late nights to see how she reacts — that machinery outsources the cost of your uncertainty onto her, and it's exactly what makes workplaces worse for women.
• Never leverage structure. If saying no is expensive for her — you're senior to her, you control something she needs, she's cornered at a work event — the question is disqualified before it's asked. That's not a technicality; consent that can't be freely refused isn't consent. The dignified version: you don't ask, you don't hint, and you don't make her manage your feelings by going cold or over-warm either. If the reporting line genuinely ends someday — a reorg, one of you moves teams — the situation changes and the normal rules apply. If it doesn't, you treat it as a great colleague you happen to have found attractive, which is a thing adults survive constantly. The next section is how.
• Never renegotiate a no. "I'm so busy right now!" is a no. It does not get appealed at the holiday party.

If — and only if — the signals have genuinely stacked, no reporting line runs in either direction, and a genuinely social context exists: one clear, specific, low-pressure invitation she can decline with zero professional residue. "Coffee Saturday?" is the entire move. Her answer, at any level of vagueness, is final. Anyone selling you a longer playbook is selling you risk and billing it to her.

When one error is catastrophic and the other is survivable, you don't need certainty. You need a default. Friendly is the default.

Signs it is just friendly, and how to let it go

Half the people who search this question aren't hoping for a green light. They want permission to stop running the loop. Here it is, plainly: if you've been watching for weeks and the stack never formed, it's friendly — and you're allowed to close the file.

The clearest signs there's nothing there:

• Everything happens on work rails. Work channels, work hours, work topics, work-created proximity. Nothing has ever cost her anything.
• Her warmth is uniform. She's like this with Dave from finance, the new hire, the vendor rep. You're inside the circle, not at the center of it.
• You're always the initiator. Rewind the last ten interactions and count who started them. If the honest number is nine or ten, that's the whole answer.
• The moments never move. Months in, it's still the same friendly plateau — no context has ever shifted, nothing has ever escalated on her side.
• She mentions a partner, or a life you're clearly not in. Which is information, not an obstacle.

Then the harder part — the letting go, which is behavioral, not emotional:

1. Say the verdict once, to yourself, in plain words. "She's friendly. That's all it is." Ambiguity is what keeps the loop spinning; a stated verdict starves it.
2. Stop collecting. No re-reading messages for subtext, no timing your kitchen trips, no narrating updates to friends. The replaying keeps the feeling alive far more than the feeling does.
3. Don't punish her for your read. Going cold, getting short, quietly withdrawing — she'll notice, she won't know why, and she'll have to manage it at her job. She did nothing wrong by being nice. Stay the same colleague you were.
4. Don't confess to clear the air. A declaration she can't freely decline isn't honesty, it's a transfer of your discomfort onto her. Silence is the more generous option here.
5. Change where the energy goes. The feeling doesn't dissolve on command, but it does starve. What kills it fastest is having somewhere else to look — contexts where interest can be expressed cleanly and answered honestly, which the office is not. If approaching outside work is the actual bottleneck, how to start a conversation on a dating app is a low-stakes place to start.

It usually fades in weeks once you stop feeding it. And if this is the third coworker in two years, the pattern isn't about them — it's that work is the only place you're meeting anyone. That's a fixable input, and it's a much better problem than the one you opened this page with.

If you want the other half of the picture — how you actually land on people before you've said a word — our free first-impression test gives you that read in about a minute. It won't tell you what she thinks. It will tell you what you're working with everywhere else.

The bottom line

"Coworker: friendly or flirting?" is a well-formed question pointed at the wrong side of the interaction.

The evidence says your instrument over-reads — put men and women in front of the same five minutes and the men see more intent, reliably. So default to friendly. Score deviations from her baseline, not behaviors from a listicle. Require the stack — initiated by her, costly to her, repeated across weeks — before you update. At work, keep the friendly assumption in your behavior even while the model updates privately: misreads there are asymmetric, and she pays first.

And if the stack never forms, that's not a loss — it's a closed file and a week of your attention back. Take the friendly answer, keep the good colleague, and spend the next conversation talking instead of decoding.

---

Studies referenced: Abbey, A. (1982). Sex differences in attributions for friendly behavior: Do males misperceive females' friendliness? Journal of Personality and Social Psychology, 42(5), 830-838. Haselton, M. G., & Buss, D. M. (2000). Error management theory: A new perspective on biases in cross-sex mind reading. Journal of Personality and Social Psychology, 78(1), 81-91. Kellerman, Lewis & Laird (1989), Journal of Research in Personality, 23(2), 145-161.