Komatelate

You know that gut-punch feeling.

When the email lands at 4:58 PM on Friday. The one saying the deadline moved. Or the family news you should’ve heard days ago.

It’s not just inconvenient. It’s exhausting. And it happens all the time.

I call it Komatelate. Not a typo. A real habit.

The reflex to wait until the last second to say what matters.

We do it at work. We do it with friends. We even do it with ourselves.

It’s not laziness. It’s not incompetence. It’s a pattern (and) it’s fixable.

I’ve watched this play out in dozens of teams. Seen how one delayed message derails a whole week.

This isn’t about blame. It’s about breaking the cycle.

In the next few minutes, I’ll show you why Komatelate sticks (and) exactly how to stop it. No theory. Just steps that work.

Why We “Comatelate”: It’s Not Laziness (It’s) Fear

I delay hard conversations. You do too. We call it procrastination.

But it’s not about time management.

It’s about fear of conflict. I’ve sat on feedback for days—weeks (because) I imagined the other person’s face falling. Their defensiveness.

The silence after I spoke. That fear feels real. It stops me cold.

And it’s not irrational. Conflict hurts. Especially when you care.

A calm room. A clear head. Spoiler: that moment never comes.

Perfectionism is another trap. I wait for the “right” words. The perfect moment.

The email stays in draft. The call goes unmade. The thing piles up.

Then there’s optimism bias. I tell myself the problem will fade. That someone else will fix it.

That the deadline won’t really matter. It’s magical thinking. And it fails every time.

(Yes, even in 2024.)

Here’s a real example: a manager puts off performance feedback for three months. She tells herself, “I’ll wait until after the big project.”

Then the project ends. Then vacation hits.

Then she’s “too busy.”

Meanwhile, the employee keeps making the same mistake. Trust erodes. Resentment builds.

No one wins.

This isn’t weakness. It’s wiring. Our brains default to short-term relief (even) when it costs us long-term clarity.

Komatelate names this pattern. Not as a diagnosis. Not as a label.

As a mirror.

You don’t need more discipline.

You need better tools for the discomfort.

Start small. Say the hard thing in 30 seconds. Send the message before you reread it.

Watch what happens.

Most people expect explosion. What they get is relief. And maybe (just) maybe (a) real conversation.

The Ripple Effect: When Silence Becomes Sabotage

I’ve watched it happen. A simple delay in saying “this is delayed” turns into a full-blown trust collapse.

You know that sinking feeling when you don’t hear back? That’s not just awkward. It’s corrosive.

When someone Komatelate a hard truth. Like a missed deadline or a scope change. They aren’t buying time.

They’re burning goodwill.

Colleagues start checking Slack twice as often. They rework things you already approved. They stop asking questions because they assume you’ll reply eventually (not) now.

That’s how respect disappears. Not with shouting. With silence.

Missed deadlines pile up. Then quality drops. Then someone else does the same task, unaware it’s already done.

I tracked one project where three people rebuilt the same dashboard. Because no one knew the first version was live. That’s not efficiency.

That’s waste.

And the anxiety? Real. The person delaying feels it every time they glance at the unread message.

The person waiting feels it every time their calendar fills with last-minute fire drills.

It’s like ignoring a small leak under the sink. You tell yourself it’s fine. But mold spreads.

Pipes weaken. One day the floor gives way.

I covered this topic over in Why Komatelate Is Important for a Pregnant Woman.

You think a two-day delay doesn’t matter? Try explaining that to the client who just canceled.

Trust isn’t built in big moments. It’s kept (or) lost. In the tiny gaps between what you say and when you say it.

Say it early. Say it clearly. Say it even if it’s ugly.

Because the cost of waiting isn’t just time. It’s credibility. It’s calm.

It’s your team’s ability to plan.

And once that’s gone? Good luck getting it back.

The “Communicate Early” System: Acknowledge, Frame, Initiate

I used to wait. Too long. For feedback.

For hard news. For anything that felt messy.

Then I built the AFI system. Acknowledge, Frame, Initiate. It’s not clever. It’s just what works.

Step one is Acknowledge. You feel it in your gut before your brain catches up. That tightness.

The mental loop. The email draft you delete three times.

Name it. Out loud if you’re alone. “I’m avoiding this conversation.” Not “I’m nervous.” Not “It’s complicated.” Just: I’m avoiding it.

That separation matters. The feeling isn’t the action. You can feel awful and still send the message.

Step two is Frame. No jargon. No softening.

Just clarity and respect.

Try: “I have an update on X that I want to share early so we can plan for it.”

Or: “I want to discuss something that might be difficult. When is a good time for you?”

Both signal intent without drama. Both give the other person agency. (And yes, I’ve used both.

They work.)

Step three is Initiate. Set a hard deadline. I use 24 hours.

Why komatelate is important for a pregnant woman (same) principle applies. Delaying hard conversations around health, timing, or support doesn’t make them easier. It just shrinks your options.

If I acknowledge the need, I act within one day.

Not “when I’m ready.” Not “after I draft it perfectly.” Within 24 hours. Even if it’s voice note, even if it’s five sentences.

An imperfect, early conversation beats a polished one that arrives too late. Every time.

I’ve seen projects stall because someone waited to “get all the facts.”

They didn’t. They got silence instead.

You don’t need full clarity to start. You just need to start.

So next time you feel that pause?

Say it out loud: Acknowledge.

Then: Frame.

Then: Initiate.

What to Do When You’re the Victim of a ‘Comatelate’

I’ve been on the receiving end of a Komatelate. It stings. Not because the info is wrong (but) because it’s late.

And late changes everything.

So what do you do? You don’t fire off an angry reply. You don’t sigh loudly and mutter about “basic professionalism.” (Though I’ve done both.

Regretted it.)

Say this instead: “Thank you for letting me know. In the future, getting this earlier would help me a lot. What can we do to make that happen?”

That’s not passive.

It’s direct. It puts the fix in the shared space (not) on their head or yours.

If it comes Monday, the timeline shifts.”

Set boundaries before the next project starts. Not as a warning. As a normal part of scoping. “If we agree on a Friday deadline for input, I’ll build in time to review and adjust.

Blame solves nothing. Process fixes do. Ask yourself: Is this a one-off, or a pattern I keep absorbing?

If it’s a pattern? Stop absorbing it. That’s not being difficult.

That’s being functional.

Stop Letting Komatelate Run Your Life

I’ve seen it a hundred times. That email you didn’t reply to. The meeting invite you ignored.

The text you read and scrolled past.

That’s not laziness. That’s Komatelate. And it’s slowly wrecking your focus, your reputation, your peace.

You don’t need to become a communication guru. You don’t need more apps or reminders or “hacks”.

You need one thing: a repeatable way to step into any conversation (even) the awkward ones (without) freezing.

That’s why the Acknowledge, Frame, Initiate system works. It’s not theory. It’s what I use when my own inbox hits 83 unread.

It’s how I stop avoiding the hard calls.

You don’t have to fix everything today.

Just pick one conversation you’ve been dodging this week.

Then do only the Frame step. Write down one opening sentence. Not three.

Not a script. Just one clear line that says what the conversation is about. And why it matters.

That’s your start.

No setup. No prep. No overthinking.

You already know which conversation it is.

So go write that sentence.

Now.