Leading the work.

Leading is its own craft, and it rests on the same spine as the rest of the guide: start from the need, keep the signal high, and own the problem out to its real edge — only now the “problem” includes the people and the schedule. What follows is the short version.

Know the people, not just the work.

The work has a shape; so does each person doing it. A lead who actually knows the people leads better, full stop. Learn what each engineer enjoys, where each one struggles, what excites a person, and what quietly drains one. Then grow people on purpose. The trick is to hand out tasks that push a little past what is comfortable while staying grounded in what is already known — far enough to learn, close enough to win.

Tailor the work to a person’s skills — and to the skills a person is reaching for — whenever the project allows it. People light up at a challenge that fits, and excited people do better work. Let engineers build things from scratch when it makes sense, too. There is a real pride in making something your own that a bolt-on or a half-reverse-engineering job never gives, and that pride shows up in the result.

One honest catch: to lead this way, you have to know the craft well enough to ask real questions and propose real solutions. This is principle three turned toward people — you do not need to have done every job, but you do need enough depth to see when someone is stuck, to ask the question that breaks the logjam, and to recognize good work when it lands.

Set the vision, then the marching orders.

A lead usually starts the same way an engineer does: with a project summary or a general idea of the solution. Share it. Take the feedback seriously, and hear the disagreements out — things go better when there is a common vision, and the people doing the work very often see what the lead missed. A few minutes of real listening buys an enormous amount of commitment.

And then, at the end of the day, you are in charge — and sometimes you can see something the room cannot yet. There is no prize for spending three weeks in meetings convincing everyone of a call you are already confident is right. Once the direction is sound, set the marching orders and go. Answer questions as they come, because questions are how good people commit, not a sign of trouble — but do not reopen the whole decision in every hallway. The balance is the craft: enough listening to earn a shared vision, enough decisiveness to keep the team moving.

Estimate honestly.

An estimate is a promise with a number on it, so make the number honest. Start by admitting that nobody is heads-down one hundred percent of the day.

For the shape of the work itself, here is a simple trick borrowed from Agile with a twist. List the tasks at a high level, give each one a complexity score from the Fibonacci ladder (1, 2, 3, 5, 8, 13…), and then let each task’s share of the total complexity stand in for its share of the effort. Now “this task is twenty-seven percent of the project” is a sentence you can say out loud, and progress is just the share of complexity that is finished.

Then there are deadlines. The most useful habit here is to refuse your own autopilot. If the thing you normally build in six months is wanted in one, do not reflexively quote six — ask honestly whether one is possible, and then tweak the design to make it possible: cut scope to the real need, change the approach, lean harder on the prototype. Often it genuinely can be done a different way. If it can, commit to it and hold the team to it. And set deadlines more often than once a week, because a task given a week tends to eat the whole week. Shorter checkpoints keep momentum honest and surface trouble while it is still small.

There’s a whole talk in here.

This page only teases the discipline — there is far more to say about hiring, feedback, conflict, career growth, and the long game of building a team that builds itself. The reason a slice of it lives in an engineering guide at all is simple: seeing the work through a lead’s eyes, even once, changes how an engineer reads the whole board. You start matching tasks to people instead of slots, you start naming the vision out loud, and you start estimating in a way you would be willing to sign.