My Coworker Rejected Every Meeting Invite From Me
Priya rejected the first meeting invite eleven minutes after I sent it.
No message.
No suggested time.
Just:
Declined.
I assumed she was busy.
I sent another for Thursday.
Declined.
The following week, I tried Tuesday morning.
Declined.
Then Friday afternoon.
Declined.
By the fifth rejection, it no longer felt like scheduling.
It felt personal.
Priya and I worked on adjacent parts of the same operations project.
I managed vendor onboarding.
She owned internal workflow automation.
My team kept running into questions only she could answer.
Where should exceptions be logged?
Which approval step triggered finance?
Who owned failed integrations?
Every time I asked in chat, Priya answered eventually.
Sometimes two hours later.
Sometimes the next morning.
But every meeting invitation I sent came back declined.
I started noticing that she did accept other people’s meetings.
I saw her in conference rooms with finance.
I passed her talking with product at a whiteboard.
Her calendar was not empty.
It simply seemed closed to me.
After the sixth declined invite, I forwarded the notification to my friend Jordan in HR.
Am I imagining this?
Jordan replied:
Have you asked her?
I hated sensible questions.
The next morning, I saw her in the kitchen making tea.
I almost walked past.
Then I stopped.
“Can I ask you something awkward?”
Priya looked at me.
“Those are usually the interesting questions.”
“Why do you decline every meeting I send?”
She did not look surprised.
“Because your invites don’t have agendas.”
I waited for more.
There was no more.
“That’s it?”
“Mostly.”
I laughed because I thought she was joking.
She was not.
“You decline a meeting if there’s no agenda?”
“If I don’t know what decision needs a meeting, yes.”
“You could ask.”
“You could put it in the invite.”
That annoyed me.
“Most people don’t do that.”
“I know.”
“But you accept theirs.”
“Sometimes.”
“So why mine?”
Priya set down her mug.
“Do you want the honest answer?”
“I think I do.”
“Your meetings usually turn into live problem-solving for things I can answer in writing.”
That landed harder than I expected.
“That’s not fair.”
“Maybe not.”
“We’re collaborating.”
“Yes.”
“Then why make it difficult?”
Priya looked genuinely confused.
“I’m trying to make it easier.”
She explained her rule.
If a meeting invite did not include at least one of three things, she usually declined it:
A decision that needed to be made.
A question that could not be answered asynchronously.
Or a conflict that required multiple people in the room.
“What if someone just needs to talk something through?” I asked.
“Then they can say that.”
“In the invite?”
“Yes.”
“This feels intense.”
“So does having twenty-seven hours of meetings in a week.”
I stopped.
“Twenty-seven?”
“Before I started declining things.”
Priya told me that six months earlier, her calendar had become unmanageable.
She was spending entire days in conversations and doing her actual technical work at night.
Not because anyone forced her.
Because every invite looked reasonable on its own.
Fifteen minutes here.
Thirty minutes there.
A “quick sync.”
A “touch base.”
A “working session.”
By the end of the week, there was no uninterrupted time left to build anything.
So she made a rule.
Vague invite: decline.
Clear purpose: consider.
Pre-read included: much more likely to accept.
“I don’t understand why you never told me,” I said.
“I thought the decline was telling you.”
“It wasn’t.”
Priya paused.
“That’s fair.”
“A boundary that only makes sense to the person enforcing it can look like rejection to everyone else.”
That was the first thing she said that made me feel less defensive.
Because suddenly the problem belonged to both of us.
I had been sending empty invitations with titles like:
Vendor workflow sync.
Quick chat.
Onboarding questions.
Priya had been declining them without explanation.
I expected her to infer importance.
She expected me to infer the rule.
Neither of us was communicating.
I went back to my desk.
My next invite looked different.
Title: Decide ownership for failed vendor integrations.
Agenda: Choose between Operations and Automation as primary owner; review two exceptions.
Pre-read: three bullet points and one screenshot.
Requested time: twenty minutes.
Priya accepted in four minutes.
I stared at the notification.
Then I messaged her:
This is annoyingly effective.
She replied:
I know.
The meeting lasted fourteen minutes.
We made the decision.
No one screen-shared a document they had not opened before the call.
No one said, “While we’re all here…”
I left slightly offended by how much I liked it.
Over the next month, I changed how I scheduled meetings with everyone.
I stopped sending “quick sync” unless I could explain why synchronous time mattered.
I included the decision in the title when possible.
I sent documents before the meeting, not during it.
Something unexpected happened.
People declined more often.
And that was good.
Sometimes someone replied:
I can answer this here.
Or:
No meeting needed; I agree with option B.
Or:
Wrong person—ask finance.
My calendar got lighter.
So did theirs.
But Priya changed too.
One afternoon, she declined an invite from me and added:
I think this can be async. Send me the two questions and I’ll reply today.
I messaged back:
Look at you explaining the boundary.
She sent a thumbs-up.
Progress.
A few months later, our team adopted a simple meeting template.
The change exposed something else too. Some meetings had been compensating for unclear ownership. People invited six colleagues because no one knew who could decide. Others used meetings as a substitute for reading documents, so the first fifteen minutes were spent bringing everyone to the same starting point. Once we had to name the decision in advance, those habits became visible.
Not every meeting disappeared. One difficult vendor escalation still needed seven people in a room because legal, finance, operations, and product genuinely disagreed. But that meeting worked precisely because the conflict was clear before we joined. We did not waste time discovering why we were there. We spent the hour resolving it.
That helped me understand Priya’s rule differently. She was not protecting focus because conversation had no value. She was protecting enough space for conversation to be used where it actually had value.
Purpose.
Decision needed.
Required attendees.
Pre-read.
No one was forced to use it.
Most people did.
Not because Priya had won some ideological war against meetings.
Because clarity made saying yes or no easier.
That turned out to be the real benefit.
I had always thought collaboration meant being available.
Now I think it means being understandable.
Those are not the same thing.
Sometimes availability produces endless access.
Clarity produces better decisions.
Priya still declines a lot of meetings.
Including mine.
I no longer take it personally.
Most of the time.
Once, she declined an invite titled:
Quick sync about meeting process.
Her response was:
You’re testing me.
I was.
She still declined it.
Correctly.
Read more workplace stories or browse short stories for adults.
This is an original fictional story from Dastan.
Featured photo: Swello / Unsplash. Inline photos: Luke Southern and Austin Distel / Unsplash.
