Chain of Command & Org Structure

The chain of command is simply who reports to whom. Each level is accountable to the one above and responsible for the one below. Knowing it tells you who to ask, who decides, and how far a decision has to travel. It’s the invisible map underneath every “let me check with my manager” — and once you can read it, you stop guessing about where to take a question.

An org chart is just this chain drawn on paper. Read it top to bottom: authority and strategy flow down, while information and requests flow up. The higher a box sits, the broader its scope and the fewer day-to-day details it touches.

## The common levels, top to bottom

Titles vary between companies, but most organisations stack roughly like this:

• CEO and C-suite — set strategy and own company-wide outcomes (covered in Module 1).
• VP / Head of — owns a whole function or large business area (e.g. “VP of Engineering”). They translate company strategy into goals for hundreds of people.
• Director — runs a department or several teams; turns the VP’s goals into concrete plans and headcount.
• Manager — your day-to-day boss, responsible for a single team’s output, priorities, and growth. This is the person you talk to most.
• Individual contributor (IC) — does the hands-on work and reports to a manager. That’s likely where you sit, and it is not a lesser place to be — most of the actual work of any company happens here.

Don’t read seniority off a title alone. A “Director” at a 50-person startup and a “Director” at a 50,000-person bank can have wildly different scope. Reporting lines tell you more than the word on the badge.

Two kinds of lines show up on real org charts. A solid line is your true reporting line — the manager who sets your goals and reviews your performance. A dotted line means you also coordinate with someone else (say, a project lead in another team) without formally reporting to them. Knowing which is which prevents you from treating a dotted-line request as an order from your boss.

Skip-levels: handle with care

Going straight to someone two or more levels up — a skip-level — isn’t forbidden, but do it sparingly and transparently. Surprising your manager by raising something with their boss first is the fastest way to lose trust. The norm: raise things with your manager, and escalate only when that path is genuinely stuck (next module).

There’s a healthy version and an unhealthy version. The healthy one is the skip-level meeting: many senior leaders deliberately schedule time with people two levels down to hear unfiltered feedback. If your manager’s manager invites you to chat, that’s normal and good — go.

The unhealthy version is going around your manager to win an argument or get a faster “yes.” Picture this: you disagree with a deadline, so you ping the director directly. The director, not knowing the full context, overrules your manager. Your manager now looks undermined in front of their boss, trust evaporates, and your next ten requests get scrutinised. The work might have been right — but the route poisoned it.

A simple test before you skip a level: have you actually raised it with your manager first, and given them a fair chance to act? If yes, and you’re still stuck, escalation (Module 4) is the structured, respectful way up. If no, start with your manager.

Spot it: chain moves

Read each situation and decide whether it’s the right move on the org chart, then tap a card to flip it and check your answer.

Sort the org levels

Drag each title into the level it belongs to on a standard org chart — or tap an item, then tap a bucket. Hit Check placement when you’re done.

How to use it

When you need something, find the lowest level that can actually decide it, and start there — usually your manager. Travel the chain one step at a time; most questions never need to climb past two rungs. Before a big meeting, glance at the org chart so you know who in the room owns the decision and who’s just informed. And when you do need to go higher, loop your manager in first so no one is surprised.

Why it matters

The chain of command isn’t bureaucracy for its own sake — it keeps decisions, accountability, and information flowing predictably. Respecting it makes you easy to work with and gets your requests answered faster. Ignoring it, even with good intentions, burns the trust you’ll need later. Read the chart, route through it, and you’ll navigate any organisation with far less friction.