Why "Table This" can create friction
People use familiar workplace shorthand because it feels efficient in the moment. The problem is that a familiar phrase can still leave the real ask, the real stakes, or the expected next step unstated.
That gap gets more expensive in Slack and email, where the reader cannot rely on tone or a quick follow-up question to fill in the missing context.
Clarity Score: 2.8/10
Clear scores workplace language across directness, specificity, tone safety, and async clarity. "Table This" lands here because:
- Directness: 2/10. It suggests movement or politeness, but not the exact ask the reader should respond to.
- Specificity: 2/10. "Table This" usually omits the deadline, trigger, or decision that would make it actionable.
- Tone Safety: 5/10. It sounds gentle on the surface, though the ambiguity can still create stress.
- Async Clarity: 2/10. In text, the softened wording leaves too much room for interpretation.
A clearer version of the same message
If you want to keep the intent but remove the guesswork, a stronger version looks like this:
Let's pause this until after the launch. I will bring it back in next Wednesday's planning meeting.
What people hear when you say "Table This"
It pauses the conversation without saying when the topic comes back, who owns it, or whether the pause is effectively a no.
A pause feels far less evasive when it has a date, a trigger, or a named owner attached to it.
3 Clearer Alternatives
Different situations call for different rewrites. These examples keep the original intent while making the message easier to understand on first read.
Direct
Best when: when you need to pause a topic
Let's pause this until after the launch. I will bring it back in next Wednesday's planning meeting.
It states the real ask instead of hinting around it.
Diplomatic
Best when: when you want to defer without sounding vague
I do not want to lose this, but I think we should revisit it after the launch when the current blockers are closed.
It stays courteous without leaving the other person to decode the message.
Async-Friendly
Best when: when you want a documented next step
Pausing this for now. I will reopen it in next Wednesday's planning meeting once the launch work is behind us.
It gives the reader a clean next step they can answer in-thread.
Before and After in Slack
The stronger version works better because the reader can see the request, the timing, and the expected response in one pass, even if the message is slightly longer.
Before:
Let's table this for now.
After:
Let's pause this until after the launch. I will bring it back in next Wednesday's planning meeting.
What changed
The rewrite keeps the polite intent but removes the uncertainty that makes the original phrase expensive to receive.
Common questions about "Table This"
What does "Table This" mean at work?
At work, "Table This" means to pause a topic and return to it later. In workplace English, it usually means stop discussing this for now, though the phrase is famously ambiguous across regions.
Why can "Table This" feel unclear at work?
It pauses the conversation without saying when the topic comes back, who owns it, or whether the pause is effectively a no.