Corporate slang lives in a strange register. It's English, kind of. The words mean things, kind of. Most of them started as serious language and got hollowed out by overuse until they're now just structural connectors — verbal stickers that show you know how meetings work.
Here's a working translation guide. Use these to decode meetings, write emails that sound like you've been around, or roll your eyes with more precision.
The classics
Synergy
Two things that, when combined, supposedly produce more value than either alone. In practice, used to justify any merger, partnership, or org change. Useful only as a tone marker — if someone says it earnestly, you're in a deck.
Circle back
Return to a topic later. Specifically: defer it without committing to a follow-up time. "Let's circle back on this" usually means "we are not going to talk about this again unless you bring it up." See also: park it, take it offline, follow up async.
Blue-sky
Hypothetical or aspirational. "A blue-sky version of this" = "a version where we ignore most of the constraints." Useful in early planning, dangerous in shipping conversations.
Boil the ocean
Try to do something so big it can't actually be done. "We don't want to boil the ocean" = "let's pick a smaller scope." Always used as a warning, never as an aspiration.
Move the needle
Have measurable impact. "This won't move the needle" = "it won't change our metrics enough to matter." A cousin of impact, drive growth, juice the numbers.
Reach out
Contact someone. Specifically: contact them in a way that's slightly more proactive than email. "Reach out to legal" = "go email or Slack legal." Has effectively replaced the word contact in most office English.
The Agile/SaaS layer
Standup
A daily 15-minute meeting where each person says what they did yesterday, what they'll do today, and what's blocking them. The name comes from doing it standing up to keep it short. In practice almost nobody stands up anymore.
Sprint
A two-week (sometimes one-week or three-week) cycle of work in Agile/Scrum methodology. "We'll get to that next sprint" = "in 2–4 weeks, maybe."
Retro / retrospective
A meeting at the end of a sprint to discuss what went well, what didn't, and what to change. Often deteriorates into venting; well-run, can be the best meeting on the calendar.
Backlog
The prioritized list of things to do. "It's in the backlog" = "we acknowledge this exists and have not committed to doing it." A graveyard for inconvenient feature requests.
Story / ticket / issue
A unit of work tracked in a system like Jira or Linear. Story implies user-facing functionality; ticket is generic; issue usually means a bug. The distinction is enforced by tribal habit, not consistent rules.
Velocity
How much work a team finishes per sprint, measured in story points. Heavily contested as a metric — using it as a target tends to corrupt the estimates. "Increasing velocity" usually means "making points smaller."
MVP (Minimum Viable Product)
The smallest version of a product that can be released. In practice, what counts as "viable" is hugely negotiated. See also v1, scrappy version, cut v1.
The strategy layer
North star
The single metric or goal that orients everything else. "Our north star is daily active users" = "we judge most decisions by whether they grow DAU." Useful when real, dangerous when nominal.
Runway
How long the company can keep operating at current burn rate before running out of money. "We have 18 months of runway" is a common startup phrase that means "in 18 months we either need revenue or another fundraise."
Burn rate
How much money the company loses each month. "Burning $400k a month" = "spending $400k more than we make per month."
Headwinds / tailwinds
Adverse and favorable conditions, respectively. "There are some headwinds in Q3" = "things are getting harder for a reason we'll list." The metaphor is so dead that nobody notices.
Pivot
Change the company's direction in a major way. Originally a technical Lean Startup term meaning a deliberate strategic shift; now used loosely for any change of plan.
The HR layer
Restructure
Layoffs, plus or minus a reorganization. "We're restructuring the org" = "people are being laid off."
Right-sizing
Layoffs, framed as a correction to a previous over-hiring. "We need to right-size the team" = "we hired too many people; some are losing their jobs." Older equivalent: downsizing.
Performance plan / PIP
Performance Improvement Plan. Officially: a structured set of goals to help an underperforming employee improve. Informally: a near-certain path to dismissal. "Putting someone on a PIP" rarely ends with the employee staying.
Headcount
Number of employees. Used as a unit of resource: "we don't have headcount for that" = "we can't hire someone for it." Also: "open headcount" = an approved unfilled role.
Aligned
In agreement, especially after a discussion. "Are we aligned on this?" = "do we all agree, or are you about to disagree and slow this down?" The word does most of its work as a closing move.
The signals layer
A few words and phrases that tell you something specific about who's talking:
- "Bandwidth" as a synonym for time/capacity — common at tech companies, almost unheard of in most other industries.
- "Take this offline" — said in a meeting, means "let's stop discussing this here." Always followed by it never being discussed again.
- "Per my last email" — passive-aggressive escalation in writing. Never neutral.
- "Quick sync" — a meeting that will not be quick.
- "Walking the dog" / "taking the dog for a walk" — the polite excuse some managers use to step out of an awkward call.
How to actually survive your first standup
You don't have to use these words. You do have to recognize them. Most of corporate slang is structural — it tells you what a meeting is doing, not what's actually being said. Once you can hear "circle back" and translate it to "we're not deciding this today," meetings get a lot more navigable.
For more in this lane, browse the corporate category on Slangora.