Project Leader Role Guide

The Project Leader keeps execution on track. They sit between the Owner's strategic decisions and the Collaborators doing the work: translating priorities into a clear backlog, removing blockers before they compound, and making sure the team knows what to work on next.

This is not a scrum master role. GoalPath handles most of what a scrum master does through the interface itself: ceremony structure, WIP monitoring, velocity tracking. The Project Leader's job is the coordination work the tool cannot do, which is mostly about people and judgment, not process mechanics.

This guide covers what Project Leaders contribute to the process. For the full permissions matrix, see User Roles & Permissions.

---

Responsibilities

Team coordination. The Project Leader monitors what the team is working on and intervenes when work is piling up in the wrong places. Too many items Started at once means flow is breaking down. Items sitting in Finished without being moved to Delivered means handoffs are stalling. The Project Leader spots these patterns and fixes them.

Technical input in planning. When a new milestone enters planning, the Project Leader contributes the technical perspective: what is actually involved, where the unknowns are, whether the proposed scope is realistic. This is a contribution to the session, not a facilitation role. Anyone on the team can walk through the planning stages in GoalPath.

Roadmap reordering. Project Leaders can reorder items and milestones. When the team has finished a batch of high-priority items and needs to know what comes next, the Project Leader ensures the roadmap reflects the current priority order.

Priority voting. Project Leaders vote in milestone prioritization voting, alongside Owners and Stakeholders. This reflects their role: they have enough business context to weigh in on priorities, not just estimate technical effort.

Unblocking individuals. When a Collaborator flags a blocker, the Project Leader acts on it: makes the call, routes it to the Owner, or finds the dependency that needs to move. A blocked item acknowledged but not resolved is still a blocked item.

---

Meeting Participation

GoalPath facilitates ceremonies. Any team member can click through the stages in a standup, planning session, or retrospective. The Project Leader's job in each ceremony is to contribute technical coordination, not to chair.

---

Daily Workflow

The Project Leader's day starts with the team's current state. What is in progress, what is blocked, and whether the work is flowing. Then they act on what they find before pulling their own work.

Check team WIP and highlights. Open the board or dashboard and review what the team has Started. If multiple people are working on many items at once, that is a signal to investigate. Check for Blocked and Question highlights. These are the items that will derail the week if left unattended.

Unblock team members. Blocked items need action, not acknowledgment. If a Collaborator is blocked on a dependency, the Project Leader makes the call or goes to the Owner to make it. If a Collaborator has raised a Question, answer it or route it to whoever can.

Review milestone health. GoalPath's forecast and health indicators show whether the current milestone is on track. A forecast that has slipped several weeks in a row is a pattern worth addressing before the alignment meeting, not during it.

Pull work. After handling coordination, the Project Leader works like a Collaborator: pick the highest-priority unstarted item and work on it.

---

Permissions

Project Leaders have all Collaborator permissions plus:

• Vote on milestone prioritization
• Reorder items and milestones on the roadmap

They cannot:

• Modify project settings
• Manage billing
• Invite or remove members

For the complete list, see the Permission Matrix.

---

When to Use This Role

The Project Leader role fits people who:

• Are responsible for how the team executes, not just for their own work items
• Have enough context to make priority calls and estimation judgments
• Are willing to coordinate teammates and unblock work as part of their regular responsibilities
• Need both execution access and some planning authority

Common fits: tech leads, senior developers coordinating a team, team leads who also write code.

One or two Project Leaders per project. More than two creates the same diffuse ownership problem as multiple Owners. If three people can reorder the backlog, nobody is accountable for what order it is in.

---

The Coordination Tax

Every Project Leader should be honest about the coordination tax. The time spent checking the board, unblocking teammates, and contributing to planning sessions is real time that does not go to implementation. That is the trade.

A Collaborator who gets promoted to Project Leader without capacity adjustment will underdeliver on both coordination and execution. Adjust the work expectation when someone takes on this role. A Project Leader who is also expected to carry the same implementation load as a Collaborator will fail at both.

---

How GoalPath Supports This Role

GoalPath reduces the administrative load that traditionally falls on a team lead or scrum master. Ceremonies are structured so any team member can run them, which means the Project Leader does not need to carry every standup or planning session personally. Milestone health signals surface automatically, so the Project Leader does not need to maintain a separate status spreadsheet. Voting is built into the alignment meeting, so priority conflicts get resolved in a structured way rather than in hallway conversations.

The Project Leader's real contribution is judgment and human coordination: reading the room, making calls when the data is ambiguous, and keeping individuals unblocked. GoalPath handles the rest.