# Should I wait for certainty before making a move with my ex?

> By Benny Lichtenwalner, breakup coach and author of "How to Get Your Ex Back".
> Canonical: https://bennylichtenwalner.com/answers/should-i-wait-for-certainty-before-making-a-move-with-my-ex/

**Short answer:** No. Uncertainty isn't a reason to wait, it's the normal condition for any move that matters. You don't get clarity by thinking harder, you get it by making the move and reading the response. Check it against the Five Rules first, keep it low-investment, then act and calibrate from what comes back.

# Should I Wait for Certainty Before Making a Move With My Ex?

No. Uncertainty about how something will land is never a good reason to wait. It's proof the move actually matters. You don't resolve that uncertainty by running it through your head one more time. You resolve it by making the move and reading what comes back.

Benny Lichtenwalner, breakup coach and author of *How to Get Your Ex Back*, sees this freeze constantly: a text, a question, an invitation, something low-stakes and completely reasonable, and the client stalls out asking what it means if it goes wrong. Nothing you haven't acted on yet can answer that question. The move is the only way to get real data instead of a guess.

## What Separates Stalling From Genuine Caution?

| Situation | Genuine caution | Stalling disguised as caution |
|---|---|---|
| The move would break one of the Five Rules | Don't send it. That's a real reason | — |
| You're still in no-contact | Hold the line, this isn't the moment to act | — |
| A low-stakes text, question, or invite is available and clean | — | Waiting for certainty about how it'll land |
| You're not sure of the exact wording | — | Hedging it into something vague to reduce risk |
| Your nervous system is triggered right now | Wait until you're regulated, then act | — |

## What Do I Actually Do Instead of Waiting?

1. **Identify the one concrete move.** Strip the situation down to the actual thing you're deciding on: a text, a question, an invitation, a reply.

2. **Check it against the Five Rules.** If it's clean, the deliberation after this point is just fear, not strategy.

3. **Send it. Keep it simple.** Don't over-engineer the message to compensate for how uncertain you feel. A low-investment version works better than an elaborate one.

4. **Read the actual response, not your prediction of it.** Their reaction is real information. Your guess about their reaction isn't.

5. **If the wording is the real hang-up**, default to the version that keeps more optionality rather than the one that commits harder. That's a reasonable adjustment. Not sending anything at all isn't.

## What Should I Avoid?

Don't pre-interpret how they'll probably respond as a reason not to act. You don't have that data yet, and a guess isn't a fact.

Don't hedge the message itself. "I think maybe..." or "not sure if this is weird but..." signals the exact anxiety you're trying not to broadcast.

Don't attach heavy personal disclosure to a move that's supposed to be light. Save emotional content for a different moment; mixing the two undercuts both.

Don't treat a flat or low-effort response as proof you shouldn't have acted. It's data either way, and data is what you were missing.

## What Does This Look Like in Practice?

Two situations that show up constantly, combined here because the freeze looks identical both times. One client sat on a simple invitation for a week, convinced that asking too early would "use up" her shot, until the window for the actual plan closed on its own. The uncertainty she was protecting herself from never resolved. It just got replaced by a different kind of regret.

Another client drafted and redrafted a single text for days, adding qualifiers each time to make it feel safer, until the message barely said anything at all. Sending the plain, two-line version he'd written on day one got a warmer response than any of the hedged versions would have. The information he needed was always on the other side of sending it, not inside more thinking.