Run Game Approaching

How to talk to someone you see every day (bus, gym, coffee shop)

6 min read

To talk to someone you see every day, nod hello for a few days, then add one short line about the shared place, then a question, then your name, and ask them out only after they've shown they enjoy chatting. The advantage is familiarity. The risk is that you'll keep seeing them, so the ask should be clear, easy to decline and followed by a graceful response either way.

You don't need to wait weeks. A common pace is nod to name in three or four visits, though there's no set number. What matters is that each step is small, and that you read the response before taking the next one.

Why the regular is a special case

Psychologists have a name for this: the familiar stranger. In 1972, Stanley Milgram described commuters who recognized people on the platform they'd never spoken to. In his train-station study, as summarized on Wikipedia, 89% of commuters recognized at least one person in photos taken on their platform, and the average person recognized 4.0 people they'd never spoken to against 1.5 they had talked with. Researchers who repeated the study in 2004 (Paulos and Goodman) found similar but somewhat lower numbers (77.8% and an average of 3.1). This is based on a summary, not the originals, and these were studies of commuters in particular places. Milgram attributed the pattern to information overload in cities: it's easier to recognize someone than to engage.

There's also the mere exposure effect. Robert Bornstein's 1989 review of 208 experiments found that repeated exposure tends to raise liking a little (r = 0.26), mostly for unfamiliar things shown briefly. The same sources note limits: exposure to someone you already dislike can raise dislike, and too much exposure can reduce it. So being a friendly, familiar face helps, but it isn't a guarantee, and a constant presence that feels like hovering can work against you.

The takeaway is modest. You probably have a head start over a stranger, because they already recognize you. They may also have noticed you looking, so keep your behavior low-key.

The small-talk ladder

A common approach, offered as advice rather than research, is to climb in steps over several visits. Each rung should be easy for them to ignore.

  1. A nod. Make eye contact, small smile, nod. Do this for a few days. That's it.
  2. A hello. "Morning." or "Hey." One word.
  3. A remark about the place. "Cold one today." "Crowded in here." "Looks like the 8:15 is late again." Nothing about them.
  4. A question. "Is that the new roast?" "Have you tried the other rack?" A question they can answer in one sentence.
  5. A name. "I'm Chris, by the way." They'll often reply with theirs.
  6. A callback. The next day: "Did the new roast work out?" Remembering a detail shows you listened.

You can skip steps or stay on one for a while. If they respond warmly (eye contact, a return question, a longer answer), move up. If they respond briefly, stay where you are or stop. How to make small talk has more lines for rungs 3 and 4.

Cues that say stop

If you see these, go back to a nod, or nothing. A person who doesn't want to talk isn't failing at anything.

What if you see them every day for a reason?

Context matters. If you see them on a bus, a train or in a gym, they may not be able to leave easily, and they may be on their own time. Talking to someone on public transport covers why to keep it lighter there, and talking to someone at the gym covers a setting where people are focused. If you're both at a workplace or school, the stakes are different: asking a coworker out covers policies, power differences and what a no means in that setting.

If the person is working, such as a barista, a server or a receptionist, they may feel they have to be friendly to you. Treat the first few chats as ordinary customer chat, and keep it out of the way of their work.

Is it friendly or flirty?

After a few exchanges, ask yourself what you actually know. Friendly people greet everyone. Friendly or flirting explains how to tell the difference. A few clues: they start the conversation, they ask about you, they stay when they could leave. None of them is proof. If you can't tell, that's useful information, and a low-pressure invitation is a good way to find out.

The ask

When the ladder has gone well, ask clearly. Vague asks tend to get vague answers. A few examples (advice, not rules):

Pick a time and a place if you can: "Saturday at 11 at the place by the station" is easier to answer than "sometime." We should hang out sometime covers why vague invitations get lost.

Ask once, in a spot where they're not stuck. Not when they're rushing to a bus, in the middle of a workout or while they're working. A good moment is when they're already chatting and have time.

Taking a quiet no

You may get a clear no, a "maybe sometime" that never turns into a plan, or silence. All of those mean no. A reasonable response:

That's all. Don't ask why, try again next week or ask a friend of theirs. Don't change your routine to avoid them either; you were friendly before and you can stay friendly. If you can't be around them without feeling awkward, change your routine for a while, and don't make them work around you.

If they seem uncomfortable even after that, give them more room. Switch to a different time, spot or bus, and keep distance. Our consent guide covers that.

If it's a yes, the usual rules of a first meeting apply: pick a public place, keep it short and let them set the pace.

What to do next

  1. Pick one person or just one place you pass every day. For three days, nod only.
  2. On day four, add one line about the place, not the person.
  3. Add one question about the next visit. Stop and go back a rung if you get short answers.
  4. When you know their name and they've started conversations, decide whether to ask. If you can't tell, invite a group instead.
  5. If you ask, name a day, time and place, and say it's fine if they say no.
  6. Write down each step and how they responded.

If you use Run Game, session notes work for tracking this, and you can log the ask as an approach whether it ends as Success or Rejected.

Sources