The one idea
An organisation is not a list of people. It is a set of flows — requests, approvals, dependencies and deadlines — and every person you meet sits somewhere on one of them.
Once you can see the flow, most confusing behaviour stops being confusing. The question "why is she asking me about this again?" almost always has the same answer: because someone is asking her.
Work travels through people in a fairly predictable order. Learn the order and you stop guessing who to talk to.
Every task has an owner, an approver, and people affected by it. Knowing which of those three you are for a given piece of work tells you what you are allowed to decide alone.
Organisations are accountability chains. Authority is delegated downward and answerability travels back upward, which is why information has to flow up before someone above you is asked a question they cannot answer.
The people, and what they actually want from you
Job titles tell you very little. What matters is what each person needs from you, and how often.
| Who | What they actually do | What they need from you |
|---|---|---|
| Your manager | Assigns your work, is answerable for its outcome | No surprises. Progress they can report upward. |
| Skip-level | Your manager's manager | Usually nothing directly. Do not route around your manager to reach them. |
| Your team | The people doing adjacent work | That you unblock them fast when they are waiting on you |
| Stakeholder | Anyone affected by the outcome, inside or outside your team | To be told early when something changes that affects them |
| Client | Pays for the work, external | Certainty. They tolerate bad news far better than silence. |
| Vendor | You pay them, external | Clear specifications and prompt decisions |
| HR | Employment matters — contracts, leave, conduct, disputes | Accuracy, and to be involved before a problem becomes formal |
| Finance | Money leaving and entering | Correct paperwork, on time, in their format |
| IT | Systems, access, hardware | Tickets, not personal messages. The ticket is how they prove workload. |
That last row is the one that catches new people. IT ignoring your direct message is not rudeness. Work that arrives outside the system is invisible to the system, and often genuinely cannot be prioritised.
How work actually flows
Five words describe almost everything that happens to a task.
Request. Someone asks for something. The request is often vague, because the person asking has a picture in their head they have not described.
Approval. Somebody has to say yes — to the spend, the design, the release, the leave. Approval is where work most often sits still. If something has stalled for days, ask who is being waited on. It is usually one named person.
Dependency. Your task needs something from someone else first. Dependencies are the main reason confident estimates go wrong, because you control your part and not theirs.
Deadline. A date somebody else has already promised to a third party. This is why deadlines feel arbitrary — you are usually seeing the last link of a chain of commitments.
Escalation. Raising something to a higher level because it is stuck or has grown beyond your authority. Escalation is a normal operating tool, not an act of aggression. Done late, it becomes one.
You are asked to prepare a supplier comparison by Thursday. You finish the analysis Tuesday, then wait on Finance for last year's spend figures. They reply Friday.
You missed Thursday. When asked, you say, "Finance took three days."
The reply you get is: "Why didn't you tell me on Wednesday? I could have called them."
The work was fine. The failure was that a dependency turned into a missed deadline without anyone above you knowing it was happening. A one-line message on Wednesday — "waiting on Finance for spend data, Thursday now looks tight" — would have ended the entire problem.
The vocabulary, only where it is useful
You do not need to memorise these. You need to not freeze when someone says one.
- KPI — key performance indicator. The specific number a person or team is measured on. Ask what your team's is; it explains most of their priorities.
- SLA — service level agreement. A promised response or delivery time, often contractual. "Four-hour SLA" means someone owes an answer in four hours.
- SOP — standard operating procedure. The written steps for a recurring task. If one exists, follow it exactly before improving it.
- Standup — a short daily meeting, often fifteen minutes. What you did, what you are doing, what is blocking you. The third part is the only one that matters, and it is the part beginners skip.
- Sprint — a fixed working period, commonly two weeks, with an agreed set of work. Things arriving mid-sprint usually have to displace something else.
- One-on-one — a recurring private meeting with your manager. It is yours, not theirs. Bring things to it.
The thing nobody says out loud
Your manager's job is partly to be able to answer for your work.
Someone above her will ask, without warning, "where are we on the supplier comparison?" She has to answer immediately, accurately, and without calling you first. If she cannot, she looks like she is not in control of her own team.
This single fact explains almost everything managers do that new employees find irritating. Status updates, the copy-me-in habit, the check-in you thought was unnecessary, the mild alarm when you go quiet for two days — none of it is distrust. It is her trying to stay able to answer.
Understand this and you become easy to manage, which is a larger career advantage than it sounds. The person who proactively says "no update yet, still on track, will confirm Thursday" is doing something most people never learn to do.
Your manager writes at 6pm: "Quick one — can you send me where you've got to on the onboarding deck? Skip-level review tomorrow morning."
The instinct is to panic, work late, and send something polished at midnight. The correct move is to reply within ten minutes with what genuinely exists:
"Sections 1–3 drafted, section 4 outlined but not written. Nothing on the data slide yet — I'm blocked on the numbers from Priya. Happy to send what exists tonight, or a cleaner version by 9am."
You have given her something to say in the room. That is what she asked for.
Mapping your organisation in your first fortnight
1 of 5Write down your manager and their manager. Names, and roughly what each is measured on. If you do not know what your manager is judged on, you do not know what she is worried about.
Try this
Your manager sends this on a Monday:
"Client's asking about the timeline for the migration. Can you look into it and get back to me?"
What has actually been requested, and what do you need to find out before replying?
Your challenge
Level 3 · IndependentDraw your own organisation on one page. Boxes for people, arrows for what flows between them — requests one way, approvals the other.
Mark three things: where work currently sits waiting, who you have never spoken to but depend on, and which single approval most often delays you.
You have succeeded when you can name the specific person who is the most common bottleneck for your work, and say what their normal turnaround time is. If you cannot, the map is not finished.
What people usually get wrong
- Treating the org chart as the real structure. The person who actually unblocks things is often three levels below the person whose title suggests it.
- Going around your manager to their manager. Even when you are right, it reads as a complaint about her and it will be remembered.
- Sending IT, Finance or HR a personal message instead of using their system. It feels friendlier and it is why nothing happens.
- Going quiet when blocked. Silence is read as progress, right up until the deadline, when it is read as failure.
- Assuming a deadline is arbitrary. It is usually someone else's promise. Ask what it is attached to and you will treat it differently.
- Waiting to be told who the stakeholders are. Nobody will tell you. Ask "who else is affected by this?" before you start.
How someone experienced does it
Experienced people manage upward without it looking like anything. They send the short update before it is requested, because they know an update that arrives unprompted is worth several that were chased.
They also learn the difference between the decision-maker and the influencer. The director signs off, but the operations lead's opinion is what the director asks for. Convincing the wrong one of those two is the most common way capable proposals die.
The deepest version of this skill is knowing what your manager will be asked this week, and making sure she already has the answer. Do that for six months and you will be given work that is well above your title, because you have made yourself the person who does not have to be chased.
Why the same job is completely different at a startup and a large company
The flows in this lesson exist everywhere, but their length varies enormously.
In a twenty-person company, request and approval are often the same conversation, and you may be talking to the founder in week one. Speed is high, process is thin, and the risk is that nothing is written down, so decisions get remade and nobody quite remembers what was agreed.
In a five-thousand-person company, a single approval may involve four people and a form, and your work may be three steps removed from any customer. The risk there is invisibility — doing good work nobody senior ever hears about.
Neither is better. But the behaviour that succeeds differs: in the small company, write things down; in the large one, make sure your work is attributable and your manager can describe it in one sentence.
Prove it
Produce the one-page map from the Challenge, and add one sentence at the bottom: the single approval or dependency that most often delays your work, and who owns it.
Bring that sentence to your next one-on-one. It is a genuinely useful thing to raise, and it demonstrates you are thinking about flow rather than tasks.
Keep learning this
Paste this into any AI assistant. It turns the assistant into a tutor that tests you instead of just answering you.
Act as an experienced practitioner who is good at teaching. I have just learned how organisations and reporting structures work for someone new to office work. Assume I am intelligent but relatively new to this — treat me as beginner level. Work through this in order, and wait for my reply at each step: 1. Ask me 5 questions that test whether I actually understood how organisations and reporting structures work for someone new to office work. Do not reveal the answers yet. 2. After I answer, tell me which parts I got right, which I got wrong, and which I only half-understand. Explain only what I misunderstood — do not re-teach what I already know. 3. Give me one practical challenge based on something I could genuinely encounter at work or in daily life. Do not solve it for me. 4. Evaluate my solution the way an experienced person would judge it, including what a professional would have done differently. 5. Tell me what to learn next, and why that comes next. 6. Give me trustworthy sources for deeper study — prefer official documentation, primary research or standards bodies over blogs and videos. Rules for you: no buzzwords. No motivational filler. Say "I'm not certain" when you are not certain, and tell me which parts of your answer I should verify myself. Clearly separate facts from your recommendations and your opinions.
Become independent at this
Use this when you want a path from where you are to actually good, with checkpoints you can test yourself against.
I want to become independently capable at reading how an organisation works and knowing who to ask — not permanently dependent on AI, tutorials or step-by-step guides. Design a progression for me with five stages: Beginner, Guided practice, Independent practice, Real-world application, Professional level. For each stage tell me: - what I must know - what I must be able to do without help - the mistakes people make at this stage - one practical challenge - one real project that would prove I reached this stage - one way I can test myself honestly Then tell me the signals that I am ready to move to the next stage, and the signals that I have skipped ahead too early. Keep the theory to the minimum I actually need. Focus on ability I can transfer to situations you and I have not discussed.