Leader Should Know Every Job Poorly

The "poorly" is load-bearing

The pattern sets a precise level for how much hands-on skill a leader should carry: enough to be useful, not enough to compete. It comes from George Bonaci, VP of Growth at Ramp, speaking on the 20VC podcast, who states the rule as "a good leader needs to know how to do everyone on their team's job, but poorly. And the poorly part is important."¹ The concept sits inside Ramp's broader management culture, which treats leadership fluency as something to be deliberately built rather than assumed.

Knowing each job a little gives a leader two things: the ability to step in when needed, and enough fluency to be, in Bonaci's phrase, "dangerous enough to ask the right questions." Knowing a job well, better than the person hired to do it, is presented as a red flag rather than a strength. As he puts it, "if they know how to do the job better than the people they've hired, then they didn't hire the right people."¹

The failure mode of over-competence

The stated consequences of a leader being too good at a subordinate's job are micromanagement and the low-leverage use of the leader's own time filling gaps that should not exist. The prescription therefore has two valid paths: learn enough of what the team does to do it poorly, or hire people who can do it better than you.¹ The ideal, in Bonaci's account, is both at once.

This resolves a real ambiguity about hands-on leaders. Rolling up one's sleeves to do individual-contributor work can be a strength or a symptom. The rule distinguishes them by intent: doing the work to step in or to ask a better question is healthy, while doing it because the hires cannot is a hiring failure wearing the costume of diligence. The "poorly" standard is what keeps hands-on leadership from becoming a permanent crutch.

Why it ties leadership to hiring

The pattern makes the quality of a leader's hiring legible through a single test: whether the team out-performs the leader at their own jobs. If they do, the hiring was good and the leader's job is to know just enough to direct and interrogate. If the leader is the best person in the room at every function, the org has been staffed below the leader rather than above.

That places it as the management-side complement of hiring for potential and for spikes: a leader hires people who will beat them at the spike, then leads by knowing enough to ask rather than enough to do. It pairs closely with Manage Through the Work, which holds that leadership happens through direct engagement with the substance of the work, and it sharpens the related caution against pure delegation captured in The Delegation Myth, which warns that walking away entirely lets quality slip.

The limits of the rule

Bonaci's own framing surfaces two tensions. "Know every job poorly" can shade into knowing too little to ask a good question at all, and the line between "dangerous enough to ask" and simply out of one's depth is a matter of judgment rather than a bright rule. In very deep-craft domains a leader may never be able to do the job even poorly, as with a non-engineer leading senior engineers.¹ In those cases the model leans entirely on the second path: hire people who are better than you and trust them, since the option of stepping in was never really available.