In context

Gen Z Slang at Work: Slack and Email Context

I have moderated enough internet arguments to know this: most communication blowups are not about the slang itself. They happen because someone misses the tone the slang is carrying.

In many teams I have seen, Gen Z slang shows up in Slack first (fast, casual, reaction-heavy), then sometimes trickles into email (more formal, but still human). Your goal is not to become fluent overnight. It’s to answer three questions quickly:

  • Is this friendly (rapport, hype, humor)?
  • Is this urgent (time pressure, escalation, risk)?
  • Is this inappropriate (too personal, too blunt, not workplace-safe)?

If you want a broader approach to decoding unfamiliar phrases, my go-to is our guide on working out unfamiliar internet slang. Below, I am focusing specifically on Slack and email context.

A group of coworkers in a modern office gathered around a laptop, one person typing while others read a Slack conversation on screen

Start with the platform

Slack: shorthand, reactions, and low-stakes vibe checks

Slack messages are often written like texts. That means slang can function as punctuation. A “lol” might not mean laughing; it might mean softening a critique. A “bet” might mean “confirmed.”

In Slack, look for these context clues:

  • Speed: short messages, rapid replies, “quick q” intros.
  • Audience: DM vs channel vs thread. Public channels push people toward safer, more performative humor (memes, light teasing, quick reactions).
  • Reactions: emoji reactions are tone indicators. Lots of reactions usually means social bonding, not crisis.
  • Threading: some teams move urgent topics into threads to keep steps organized; other teams keep urgency in-channel with clear @mentions. Either way, urgency tends to show up as direct asks, owners, and next steps.

Email: fewer slang terms, higher stakes

Email slang tends to be more intentional. If someone uses “yikes” or “this is wild” in an email, they are usually trying to communicate emotion without going full rant.

In email, context clues shift to:

  • Subject line: “Quick question” is rarely quick. “Action required” usually means it.
  • Structure: bullets, dates, owners, and deadlines are urgency markers.
  • Formality mismatch: heavy slang in a formal chain can signal closeness, frustration, or just one person refusing to code-switch. Consider the sender, the relationship, and who else is on the thread.

The three-bucket test

Bucket 1: Friendly slang

Friendly slang is often used to keep things light, reduce friction, or build camaraderie. It pairs well with thanks, humor, and collaborative language.

Common signals:

  • Compliments: “ate,” “slayed,” “goes hard” (and more niche ones like “absolute cinema”)
  • Agreement: “bet,” “say less,” “facts”
  • Softeners: “lol,” “lmao” (often used like a nervous laugh), “lowkey”

How to respond: Mirror the warmth, not necessarily the slang. You can be friendly without cosplay.

  • Instead of: “slay”
  • Try: “Nice work on this, thank you” or “This looks great. Approved.”

Bucket 2: Urgent slang

Some slang can be a flare. It signals “pay attention” even if the words are casual.

Common signals:

  • “This is not it” (something is wrong or unacceptable)
  • “We are cooked” / “it is cooked” (situation is going badly, often with humor but real concern)
  • “Yikes” (error spotted, possible reputational risk)
  • “Can you lock in?” (focus up, deliver now, stop multitasking)

How to respond: Translate it into operations. Ask for specifics, timeline, and owner.

  • “Got it. What is the impact and what do you need from me, by when?”
  • “Thanks for flagging. Can you point me to the exact doc/link and the expected fix?”

Bucket 3: Inappropriate slang

This is less about “Gen Z words” and more about workplace boundaries. Slang becomes inappropriate when it introduces sexual content, insults, or overly intimate commentary, or when it is likely to be misread across cultures and seniority levels.

Watch for:

  • Direct insults disguised as jokes: “cringe,” “corny,” “embarrassing” aimed at a person, not a situation
  • Sexual or body-focused terms, even if someone thinks they are being funny
  • Dogpiling language: slang that invites others to mock someone in a channel

How to respond: Keep it calm and professional. If needed, move the conversation to a private channel and refocus on work.

Slack examples

Here are a few real-world patterns I have seen across gaming and pop-culture communities that now show up at work, too.

“Bet”

  • Friendly: “Can you send that deck by 3?” “Bet.” (Meaning: yes, confirmed.)
  • Edge case: If it comes after pushback, it can carry a tiny bit of bite. Read the prior message.

“Lowkey” / “highkey”

  • Friendly hedge: “Lowkey this feature is my favorite.”
  • Soft critique: “Lowkey I do not think this timeline is realistic.” (Meaning: I think it is unrealistic, but I am saying it gently.)

“I am dead” / “I am crying”

  • Friendly: Reaction to something funny. Usually paired with laughing emoji or a GIF.
  • Usually not literal: In workplace Slack it is typically hyperbole. Still, if there is any sign someone is in real distress or talking about self-harm, pause the jokes and treat it seriously. Check in privately and follow your workplace policy.

“It is giving …”

  • Friendly vibe description: “This landing page is giving premium.”
  • Potentially sharp: “This email is giving passive-aggressive.” That is a tone critique, and it can escalate quickly.
A coworker seated at a desk typing a message on a laptop with Slack open, office background slightly blurred

Email examples

“Yikes” in an email chain

In Slack, “yikes” can be playful. In email, it can signal discomfort, concern, or a desire to put a reaction on record. It can also still be light if you have an easy rapport, so read it in context.

What to do: Respond with clarity and accountability.

  • “Agreed this is not ideal. Here is what happened, what we changed, and the new ETA.”

“This is wild”

This usually communicates disbelief or frustration without stating it outright.

What to do: Do not match the emotion. Pull it into specifics.

  • “I hear you. To confirm, the issue is X and the decision point is Y. I can deliver options by end of day.”

“Respectfully,”

Not Gen Z slang exactly, but it behaves like internet tone markers: it can mean “I am about to disagree strongly.”

What to do: Keep your reply neutral and solution-focused. Avoid escalating language.

Workplace mini-dictionary

Meanings shift by team culture, but these are common “in the wild” interpretations. Treat them as probable, not permanent.

TermUsually meansWorkplace-safe?Best response style
betyes, agreed, confirmedUsuallyConfirm details if needed
say lessI understand, I will do itUsually“Thanks, appreciate it”
lowkeykind of, quietly, softeningYesAcknowledge and clarify
highkeyvery, openlyYesMatch clarity
yikesthat is bad, risky, uncomfortableDependsMove to specifics, fix plan
cookedin trouble, not recoverable (often joking)DependsAsk impact, mitigate
lock infocus and deliver nowUsuallyConfirm priority and deadline
ate / ate thatdid an amazing jobDependsSay thanks, accept praise
cringeawkward or embarrassingRiskyRedirect tone, focus on work
it is giving…it has the vibe of…UsuallyAsk what they want changed

Quick note on “Depends”: It usually means “fine in a friendly peer context, risky in a tense thread, formal chain, or mixed-seniority room.”

For more general definitions and internet usage notes, browse the Slang Dictionary guide.

Power dynamics examples

Manager to direct report

  • Their message: “Can you lock in on the bug triage today?”
  • You reply: “Yes. I will prioritize triage until 3 pm, then send a status update with what is fixed and what is blocked.”

Direct report to manager

  • Their message: “Lowkey worried we are cooked on the deadline.”
  • You reply: “Thanks for saying it. What is the biggest blocker right now, and what would make the deadline realistic?”

Peer to peer

  • Their message: “Bet. I can take first pass.”
  • You reply: “Perfect. Thanks. Want me to QA and merge, or do you want to?”

Cross-cultural clarity

If you work with ESL teammates or cross-cultural teams, slang can land like idioms: confusing, overly indirect, or accidentally sharp. Sarcasm also does not travel well. When stakes are high, plain language is not “stiff.” It is kind.

  • Swap “we are cooked” for “we are at risk of missing the deadline because X.”
  • Swap “this is not it” for “this does not meet the requirement because Y.”
  • If you do use slang, add the operational meaning right after it: “Yikes, the link is broken. Can you update it before 2 pm?”

When not to mirror slang

I love a little linguistic bonding, but workplace power dynamics are real. Here are moments where mirroring slang can land weird:

  • You are delivering negative feedback: “this is not it” can sound dismissive. Use clear, respectful language instead.
  • You are writing to leadership or clients: even harmless slang can read unpolished.
  • You are not sure what it means: do not guess with terms that could be insulting or sexual.
  • The slang is doing emotional labor: “lol” after bad news can be a coping mechanism. You do not need to copy it.

Ask what it means

If you need clarification, you can ask in a way that respects the person and keeps momentum.

Good clarification lines

  • “Quick check: when you say ‘cooked,’ do you mean the deadline is at risk or the approach is blocked?”
  • “When you say ‘lock in,’ what is the top priority you want me focused on today?”
  • “Just to make sure I am reading the tone right, is this more of a heads up or do you need action right now?”

What to avoid

  • “What does that even mean?” (sounds dismissive)
  • “Stop using slang.” (makes it about identity, not clarity)
  • Replying with the same slang if you are uncertain (risk of misuse)

When to hop on a call

If tone keeps getting misread, or you see conflict signals piling up, text is no longer your friend. Move to a faster, richer channel.

  • If a thread is looping: “Want to do a 10-minute huddle to align on the decision?”
  • If you see heat rising: “I might be misreading tone over text. Can we talk live for a minute and get on the same page?”
  • If it is sensitive: take it out of the channel and into a private 1:1 or your normal escalation path.

Red flags for conflict

Sometimes people use “internet voice” to mask irritation. Look for these patterns:

  • Public call-outs: slang plus @mention in a channel, especially if it assigns blame.
  • Stacked tone markers: “lol” + “yikes” + “…” can mean “I am not happy.”
  • Short, clipped replies: “bet.” by itself after disagreement can mean compliance, not enthusiasm.
  • Receipts culture: pasting quotes, screenshots, or message excerpts to prove a point.

If you see these, treat it like any other workplace tension: move to private, clarify facts, agree on next steps.

FAQ

Is Gen Z slang unprofessional?

Not automatically. In many teams it functions like friendliness, humor, or efficiency. It becomes unprofessional when it replaces clarity, excludes people, or crosses boundaries.

What if I think a term is rude?

Assume misunderstanding first, especially across generations or cultures. Ask for intent and specifics. If it is clearly a dig at a person, treat it like any other inappropriate workplace comment.

Should managers use the slang their team uses?

Managers can adopt a little of the team’s casual tone, but they do not need to mirror every phrase. The safest lane is: warm, direct, clear. Let slang be optional, not required.

How do I decode something totally new?

Use surrounding clues: who it is addressed to, whether it appears after a mistake, whether it comes with a request, and what the next message does. Then use our step-by-step guide: Work Out Unfamiliar Internet Slang.

Latest entries