Influence Without Authority

## Leadership is a scope claim, not a personality trait When a hiring manager listens to a leadership story, they are not scoring enthusiasm. They are placing the story on a ladder and asking whether it sits at the level the role is open at. The most portable version of that ladder has **three columns — task, project, multiple teams** — and the whole craft here is knowing what evidence each column demands. | Column | What you owned | What a hiring manager listens for | Typical horizon | |---|---|---|---| | Task | One piece of work | Execution quality, judgment inside a defined boundary, unblocking yourself | The current piece of work | | Project | An outcome inside 1 team | Sequencing, decisions taken without being told, coordination with named counterparts, carried to done | About 6 months | | Multiple teams | A change in how 2-3 teams (or an org) operate | Something you supplied that others adopted, and which outlived your involvement | About 18 months | ### The three axes underneath the columns The columns are shorthand for three things that move together: 1. **Reach** — how many people changed what they do. One person (you) is the task column. One team is the project column. Two or three teams, or an org, is the third. 2. **Autonomy** — how much of the direction you set. In the task column the goal was handed to you. In the project column you chose the sequence and the tradeoffs. In the third column you chose the problem. 3. **Horizon** — how far ahead the work is planned. A 6-month plan for one team's outcome reads as project scope; an 18-month plan whose consumers are other teams reads as multi-team scope. A story can be excellent on execution and still sit in the first column. That is not a failure — it is a calibration fact, and the whole point of knowing the ladder is to stop guessing. ### The same work told at three widths Take one infrastructure world — a group standardising how services are deployed — and watch one candidate's material sit in each column depending on what the evidence actually supports. - **Task column.** *'The nightly build kept failing on a flaky step. I found the cause, fixed it, and wrote up the failure signature so the next person would recognise it.'* Real work, clean judgment, boundary set by someone else. - **Project column.** *'I owned moving my team's services onto the shared deployment pipeline. I sequenced it so the riskiest service went last, negotiated the freeze windows with the team's tech lead, ran a rollback drill before the first cutover, and had it done inside the 6-month plan I proposed.'* Now there is direction-setting and coordination inside 1 team. - **Multiple-teams column.** *'I wrote the migration playbook and the compatibility layer that let a team move without rewriting call sites. Two other groups used it without me being in the room. Three teams now share the pipeline, and I own the 18-month capacity plan we defend it with.'* The evidence is adoption by people you do not manage, and survival after you stopped pushing. Notice what changes between the second and third bullets: not effort, not difficulty, not hours. What changes is that **someone else's behaviour changed because of something you supplied**, and that it kept working when you left the room. ### Why titles are the wrong ladder Rung names, and where a company draws its lines, vary a great deal — the same title can mean one team's outcomes at one employer and multi-team influence at another, and many companies publish an internal ladder that does not match anyone else's. Because of that, saying *'I operated at staff level'* transfers nothing. Describing reach, autonomy and horizon transfers everywhere, because the hiring manager can map it onto whatever ladder they actually use. ### What the ladder is for, practically Before a loop, take each story you plan to tell and write the column it honestly sits in, plus the one line of evidence that puts it there. You will usually find you have more first-column material than you thought and fewer third-column examples than you hoped. That is the useful discovery: it tells you which stories to lead with, which to keep as backup, and where you are genuinely thin — long before a hiring manager finds the same gap by asking one probing follow-up.