Growing Your Leverage

Leverage is multiplying the people and systems around you. It is the seventh attribute, the one that sits near zero early and becomes the whole job at Lead and above. It is what separates a strong individual from a force multiplier: the same person who makes the whole team better, so the team keeps getting better whether or not that person is in the room.

This page is how you move yourself up one rung on it. It is a mirror, not a scorecard: find the row just above where you sit, and put your reps there. And unlike the other six spokes, near-zero is correct early: an intern’s leverage is their own growth, and that is right. This page is for when it is time to start climbing. The creed underneath it is Multiplier, Not Bottleneck.

Where you are now#

Find the line that matches the effect you actually have on the people around you.

Level	The tell
Intern	You are focused on your own growth, and that is right for now.
Junior	You help peers when asked.
Mid	You are the designated reviewer for newer folks.
Senior	You transfer patterns, not just answers, and you raise those around you.
Lead	You grow several engineers deliberately and platformize how the work gets done.

What moves you up#

Leverage climbs on one shift: from doing the work to making the work happen without you.

Multiply, don’t reduce. Before you act, ask whether it makes the team more capable or more dependent on you. Doing the hard task yourself reduces; teaching someone to do it multiplies. Fixing the one bug reduces; fixing the pattern multiplies. The reducing move is almost always faster today and more expensive every day after.
Transfer the pattern, not the answer. Handing someone the fix solves one bug. Handing them how you found it solves the next ten without you. Answers create dependency; patterns create capability.
Open capabilities, don’t hoard them. Being the only person who can do X is not job security, it is a liability you created. Teach the thing, write the playbook, grant the access. See Equipping People.
Push decisions down; do not be the gate. Every decision that has to climb to you and back is latency you added and judgment you did not grow in someone else. Set the guardrail, then let people decide inside it.

The habits that keep you stuck#

The reducing move feels responsible and is often faster in the moment, which is exactly why strong individuals get stuck here. Catch yourself in these:

Bad: you are the only one who understands the billing migration, so every question routes to you, every change waits for your review, and the work stops the week you are on leave.

Good: you wrote the migration up, walked two engineers through the tricky part, set a guardrail for the reversible changes, and the team ships them without you. You are missed for judgment on the hard calls, not for throughput on the routine ones.

The tells that you are reducing when you should be multiplying:

Grabbing the keyboard to fix it yourself because it is faster than teaching.
Context lives only in your head, so you are the single point of failure and the bottleneck at once.
Being the approval everyone waits on, rather than the person who made the approval unnecessary.
Delegating by dumping: handing off and walking away, which burns both the person and the work. You still own the outcome.

The reps that level it up#

Move a rung by taking on the next row’s multiplying before it feels comfortable, then close the gap with review:

Become the reviewer or mentor for someone newer, and in review transfer the pattern, not just the correction. The rep is teaching them to catch it next time.
Take one person’s growth as something you actually own. Not “help when asked”, own a specific gap of theirs closing. This is the Senior-to-Lead jump in miniature.
Find one thing that only you can do and remove yourself from it: document it, set a guardrail, or teach it, so the work does not stall when you are on a plane.
Fix the pattern instead of the instance once. Next time you fix a bug, ask what would stop the whole class of it, and do that instead.

The one question#

Run this one in real time, dozens of times a day: am I multiplying or reducing right now?

And the scoreboard for all of it: what happens when you step away? If the team slows to a crawl, you were a bottleneck. If it runs fine, you built capability. Aim to be missed for your judgment and direction, rarely for your throughput.