Why "As Discussed" 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: 4/10
Clear scores workplace language across directness, specificity, tone safety, and async clarity. "As Discussed" lands here because:
- Directness: 4/10. It suggests movement or politeness, but not the exact ask the reader should respond to.
- Specificity: 4/10. "As Discussed" usually omits the deadline, trigger, or decision that would make it actionable.
- Tone Safety: 4/10. It sounds gentle on the surface, though the ambiguity can still create stress.
- Async Clarity: 4/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:
Repeating the plan here: design will send the updated mock by Thursday, and product will review it Friday morning.
What people hear when you say "As Discussed"
It gestures at prior context without always restating the part the reader needs to act on now.
When the current ask matters, repeating the key sentence is usually clearer than pointing at the earlier conversation.
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 mean a recap
Repeating the plan here: design will send the updated mock by Thursday, and product will review it Friday morning.
It states the real ask instead of hinting around it.
Diplomatic
Best when: when you want a smoother reference
Sharing the agreed plan again here so it is easy to find: design sends the updated mock Thursday and product reviews it Friday morning.
It stays courteous without leaving the other person to decode the message.
Async-Friendly
Best when: when you want a quick thread update
Quick recap: design sends the updated mock Thursday, and product reviews it Friday morning.
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:
As discussed, design will send the updated mock Thursday.
After:
Repeating the plan here: design will send the updated mock Thursday, and product will review it Friday morning.
What changed
The rewrite keeps the polite intent but removes the uncertainty that makes the original phrase expensive to receive.
Common questions about "As Discussed"
What does "As Discussed" mean at work?
At work, "As Discussed" means as we already talked about. At work, it is usually meant as a recap marker, though it can sound clipped when it replaces the actual recap.
Why can "As Discussed" feel unclear at work?
It gestures at prior context without always restating the part the reader needs to act on now.