Read a sample: 1. The Project Lead’s Real Job
Maya knew the assignment mattered because her director mentioned it twice in the same conversation.
“We need a better way to onboard new business customers,” he said. “Can you lead that project?”
Maya was a capable operations specialist. She understood the complaints that prompted the request: customers sometimes received incomplete instructions, internal teams repeated the same questions, and account managers had trouble telling where an onboarding stood. She had ideas about what could improve.
Then she looked at the people whose help she would need. Customer Support handled early questions. Product maintained the tools customers used. Sales made promises during handoff. Operations managed much of the process. Each group had its own manager, deadlines, and definition of urgent.
Maya could schedule a meeting with all of them. She could not assign their work in the same way their managers could. She did not yet know what her director meant by “better,” what the project was expected to deliver, or who could settle a disagreement if the teams wanted different things.
That gap is where the project lead’s real job begins.
Leading a cross-functional project is not primarily about persuading everyone to follow you. It is about making the work understandable enough that the right people can make useful decisions and keep their agreements. You bring purpose, boundaries, commitments, dependencies, and emerging problems into the open. You help people see what is needed from them and what their choices mean for others.
You do not need to become everyone’s manager. You do need to become a reliable coordinator of the work.
Maya’s project is hypothetical, but the pressures around it will be familiar throughout this book. We will return to her team as the assignment becomes more specific, contributors make commitments, dependencies emerge, and priorities compete. For now, her first challenge is to understand the role she has been asked to play.
A manager is generally responsible for an employee’s ongoing work relationship: setting expectations within the organization’s structure, discussing performance, supporting development, and participating in decisions about priorities and capacity. The exact responsibilities vary by workplace, but the manager has a continuing relationship with the person beyond any one project.
A project lead has a different focus. The lead coordinates a defined piece of work toward an intended result. That can involve clarifying what must be delivered, bringing contributors together, tracking decisions, identifying obstacles, and communicating changes. The relationship is centered on the project, even when it lasts for a substantial period.
The distinction matters because a project request can sound like a management instruction when it is not one.
“Please have the revised onboarding guide ready by Friday” may sound straightforward. But if Maya has not discussed the work with the person preparing the guide, checked the effort involved, or understood what that person’s manager has already prioritized, she has stated a desired date—not secured a commitment.
A more useful opening would be:
> “We may need a revised onboarding guide as part of this project. Could we look at what that would involve, what you already have underway, and when you might realistically be able to work on it?”
This does not mean the contributor alone must decide every priority. It means Maya starts with the person who understands the work and then involves the appropriate manager if capacity or competing priorities need a decision.
That distinction also protects the contributor. A colleague should not have to choose silently between satisfying Maya and meeting an existing obligation to their manager. When those obligations conflict, the conflict belongs in a conversation with the people who can resolve it.
Project leads sometimes worry that asking about capacity makes them look hesitant. In practice, pretending capacity is unlimited produces a more fragile plan. A clear request, an honest answer, and a visible trade-off give the project a better foundation than an apparently confident deadline that nobody has agreed to meet.
You may have more authority than you think in some areas and less than you assume in others. Your sponsor might expect you to run meetings, recommend a plan, or decide how to organize a working session. That does not necessarily mean you can change a team’s priorities, approve spending, or settle a dispute about the final deliverable.
The title “project lead” does not answer those questions by itself. Your organization may give the role broad decision rights or very narrow ones. Ask rather than guess.
Early in the assignment, Maya can ask her director:
> “Which decisions would you like me to make, which should I bring to you, and who should be involved if this work conflicts with a team’s existing priorities?”
The answer may not cover every situation. That is fine. The conversation establishes a starting point and makes it easier to recognize when a new decision falls outside it.
Consider three different issues in the onboarding project. Maya can probably propose an agenda for a discovery meeting and adjust it based on the participants’ input. If the team disagrees about whether the project includes changing customer-facing software, the sponsor may need to clarify the intended scope with input from Product. If a Product specialist cannot support both onboarding work and an existing release, the relevant managers may need to decide the priority.
These are not failures of leadership. They are different kinds of decisions with different owners.
A common mistake is to treat every unresolved issue as…