Business Management Terms & Vocabulary: 23 Terms Managers Should Know

Direct report

Someone who reports directly to you—not a skip-level, dotted line, or the wider organization.

Why it matters: Managers need a precise word for “my team” when headcount, coaching, and performance conversations start to blur.

In a management conversation: “I have six direct reports; the rest of the function reports through them.”

Skip-level

A conversation or relationship two layers apart—usually a manager and someone who reports to their direct report.

Why it matters: Skip-levels help a manager hear what is happening without turning every issue into an override of the line manager.

In a management conversation: “I’ll do skip-levels this month to hear how the new onboarding process feels.”

One-on-one

A regular private meeting between a manager and a direct report, used for coaching, priorities, and unblocking work.

Why it matters: If one-on-ones slip, coaching and risk usually slip with them—problems show up later in delivery or attrition.

In a management conversation: “Bring the launch risk to the one-on-one; don’t wait for the team meeting.”

Span of control

How many people report directly to one manager.

Why it matters: A span that is too wide usually shows up as weaker coaching, slower decisions, and missed one-on-ones—not as a staffing line item.

In a management conversation: “Her span of control increased from five to nine direct reports.”

Headcount

The number of people employed on a team or in a company.

Why it matters: Headcount is how managers talk about capacity, hiring, and cost—often before anyone mentions names.

In a management conversation: “Our engineering headcount grew from 30 to 38 this year.”

FTE

Full-time equivalent: a way to count staffing as fractions of a full-time role, including part-time and shared people.

Why it matters: Managers use FTE when headcount and actual hours available are not the same thing.

In a management conversation: “We have six people on the roster, but only 4.5 FTE after the shared-role split.”

Succession planning

Preparing who can step into a critical role if someone leaves, is promoted, or is out for a long stretch.

Why it matters: Without a successor, a manager is one resignation away from an operational emergency.

In a management conversation: “We have no succession plan for the only person who can ship payroll.”

Capacity planning

Matching planned work to the people and time actually available, including existing commitments.

Why it matters: Without it, managers accept every request and the team discovers the overload in missed dates.

In a management conversation: “Capacity planning says we can take the migration or the new feature—not both this quarter.”

Ownership

Who is expected to drive the work forward and keep it moving when it gets stuck.

Why it matters: A project can have many contributors and still stall if nobody has ownership.

In a management conversation: “Priya has ownership of the launch checklist end to end.”

Accountability

Who answers for the outcome—success or failure—even when others contributed.

Why it matters: Accountability names the person who cannot reasonably say “that wasn’t my job” when the result misses.

In a management conversation: “Engineering contributed, but marketing is accountable for campaign results.”

Delegation

Assigning work and decision space to someone else while staying accountable for the outcome.

Why it matters: Managers who cannot delegate become the bottleneck; managers who dump work without context create rework.

In a management conversation: “I’m delegating the vendor review, but I still own the final call.”

Decision rights

Who is authorized to decide what—and who only advises, executes, or needs to be informed.

Why it matters: Unclear decision rights create slow meetings, surprise reversals, and work that gets redone.

In a management conversation: “Product has decision rights on scope; finance has decision rights on discounting.”

RACI

A simple map of roles on a piece of work: Responsible, Accountable, Consulted, and Informed.

Why it matters: Managers use it when several teams are involved and “we’re all on this” has become a delay.

In a management conversation: “Let’s put a RACI on the launch: Priya is accountable; design is consulted, not a second owner.”

Escalation

Moving a stuck issue to the person who has the authority or context to unblock it.

Why it matters: Late escalation looks like poor judgment; early, specific escalation looks like control of the work.

In a management conversation: “Escalate if legal has not responded by Thursday; do not wait until launch week.”

Stakeholder management

Identifying the people who inherit a decision, then keeping them informed and involved enough to avoid surprises.

Why it matters: Managers get blindsided when they treat stakeholders as optional reviewers instead of people who live with the result.

In a management conversation: “Stakeholder management here means briefing support before the pricing change, not after customers call.”

Alignment

Shared understanding of the goal, the constraints, and what “good” looks like.

Why it matters: Busy teams can still waste a quarter if they are not aligned on the actual priority.

In a management conversation: “We are busy, but we are not aligned on whether this quarter is for growth or reliability.”

Performance review

A formal look at someone’s work over a period—what they delivered, how they worked, and what comes next.

Why it matters: Reviews only help if the criteria were clear earlier. A surprise review is usually a failed year of feedback.

In a management conversation: “Nothing in this performance review should be new; we already covered it in one-on-ones.”

Calibration

A conversation among managers to align ratings, standards, and evidence so similar work is judged similarly.

Why it matters: Without calibration, “exceeds expectations” means whatever each manager happens to mean.

In a management conversation: “In calibration, we compare evidence—not who advocates most loudly for their team.”

Psychological safety

A climate where people can ask questions, admit mistakes, and disagree without being punished or embarrassed.

Why it matters: Teams without it hide problems until they are expensive. Managers hear good news and late bad news.

In a management conversation: “Psychological safety means people can say the launch is not ready without it becoming a loyalty test.”

KPI

A key performance indicator: a metric chosen to show whether an important result is actually happening.

Why it matters: Managers get lost in dashboards; a KPI is the few numbers they are willing to manage to.

In a management conversation: “Our KPI for the support team is first-response time, not ticket volume.”

OKR

Objectives and key results: a qualitative goal plus a few measurable outcomes that show whether the team hit it.

Why it matters: Managers use OKRs to keep a quarter focused when the backlog is full of useful-but-not-decisive work.

In a management conversation: “The objective is faster first response; the key result is 90% of tickets answered within four hours.”

Leading indicator

An early signal that helps you see a later people or delivery outcome forming.

Why it matters: If you only watch end results, you find out too late to coach, hire, or change the plan.

In a management conversation: “One-on-one skip rates are a leading indicator for engagement risk.”

Attrition

How many people leave over a period, often watched as a team-health signal.

Why it matters: Managers need to discuss leaving rates without treating every departure as a surprise or a personal failure.

In a management conversation: “Attrition on the night shift is disrupting coverage.”