UPI Study › Courses › Project Management › Free lessons › Lesson 8.3 Free with a free account
Managing Team Roles and Work Distribution
Project Management · Chapter 8: Driving Project ExecutionSection 8.3 · lesson 46 of 7315 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Project Management.
Lesson complete
Earn the 3 college credits for Project Management
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Defining and Tracking Milestones in Active Projects →← Time Management: Techniques and Scheduling During ExecutionNext lesson: Defining and Tracking Milestones in Active Projects →
In this lesson
Delegating, balancing workload and clarifying ownership while work is under way.
- Delegate work by passing the task, authority, expected result and deadline
- Scan a RACI chart for gaps and overlaps in ownership
- Calculate load ratios and redistribute work toward people with capacity
- Distinguish role ambiguity from overload and choose the matching fix
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (2,170 words). Read along, or search it.
Opening Case
One Person Drowning, Two Waiting
One person is drowning, and two are waiting. What would you change: the people, or the way work is handed out? Priya is the project manager at Willowbrook Community Clinics, a made-up clinic network, and her team is moving patient records into a new scheduling system. In week five she counts the urgent tasks. Tobias, the data specialist, holds nine of the eleven. He's also the only person allowed to decide whether a record's fields were mapped correctly, so every urgent question lands on his desk. Meanwhile Nia and Owen, two records clerks who work remotely, have finished their own work, and are waiting for direction.
Work Distribution
Workload Links Roles to Reality
Nia works from home, two time zones away. Her queue has been empty since Tuesday, and nobody has noticed. Roles on paper said who does what. Work distribution is the day-to-day practice of deciding who takes each piece of work, and when. During execution it's a continuing job, because paper assignments meet three kinds of change. Estimates meet reality: a two-day task needs five. People's availability moves, through illness, leave, or other demands. And the work itself changes, as defects and new requests arrive. The measure that links a role to reality is workload: the work a person is actually carrying, compared with the time they have.
Delegation
Four Things Pass Across at Handover
Fixing this starts with delegation: handing someone responsibility for a piece of work, with the authority to do it, while you stay answerable for the result. Four things pass across: the task with its boundaries, the authority, meaning the decisions and resources they may use, the expected result, and the deadline. A weak handover says: take care of the user guide. A sound one says: write the ten-page staff guide for the new scheduling screens. Choose the layout, and ask Marcus for screen images. It's finished when Elena can follow it end to end without asking a question. A draft is due on the twelfth, and the final on the nineteenth. Either person can check the second version. Nobody can check the first.
Delegator's Role
Avoiding Micromanagement and Dumping
What does the person delegating keep? Accountability for the outcome, decisions outside the authority granted, like changes to scope, and the duty to notice trouble. Micromanagement is controlling how a task is done in detail, and checking far more often than its risk justifies. You avoid it by agreeing the follow-up at the handover: denser checkpoints for risky or unfamiliar work, sparser ones for routine work by an experienced person. Agree what the owner reports without being asked, like any risk to the deadline. Then review results and ask questions, rather than redoing the work. The opposite failure is dumping: passing work on without the authority, clarity or support to finish it. On the day, delegating and dumping can look identical. The difference shows later: a dumped task arrives vague, and the person who dumped it can't be found until the deadline passes.
Responsibility Chart
Scanning RACI for Gaps and Overlaps
Next, who owns each task. The responsibility chart, or RACI, records it. For assignment, two marks matter: R, the role that does the work, and A, the role that answers for it. A usable row has at least one R and exactly one A. One person may hold both, which is common on small tasks. Scan the R and A marks, row by row, for two faults. A gap is a task with no owner: no A, or an A with no R. With an A and no R, someone answers for work that nobody was asked to do. An overlap is a task with two owners: two A marks, or two R marks when nobody has said which part belongs to whom. Take a website refresh. Testing pages on phones has no A, and two Rs with no stated split: a gap and an overlap at once. Approving final wording has two As. And the staff user guide has an A but no R, so nobody has been asked to write it. Each fix is one small decision: name one accountable role, remove the second A, assign a writer. A fault found at assignment costs one conversation; found at the deadline, it costs a deliverable.
Quick Check
One Person Marked Both A and R
Quick check. Consider a new task: post the clinic opening notice. Marcus is marked both A and R, and no one else is marked. What does the scan find? Pause, and decide. No fault. The row has exactly one A and at least one R, and one person holding both is common on small tasks. It isn't an overlap, because both marks sit with the same person, and it isn't a gap, because the work has an owner.
Load Ratio
Rebalancing Tobias's Thirty-Six Hours
An owner for every task doesn't mean the owners can carry them. Capacity is the hours a person can really give the project in a period, after meetings, other duties and leave. The load ratio is assigned hours divided by available hours. One point zero means every available hour is spoken for. Above one is overload. Just under one is a warning too, because it leaves nothing for rework or illness. Priya's team sets a caution point at point nine. These are made-up figures. This week, Tobias has 36 hours assigned against 30 available: a ratio of one point two. Nia is at point seven five, Owen at point eight, and Elena at point seven. The team as a whole has 92 hours against 104, about point eight eight. So the team has room, and one person has none. It's a distribution problem, not a total-effort problem, so hiring or cutting scope would be the wrong cure. Priya moves ten of Tobias's hours: four to Nia, three to Owen, three to Elena, each piece matched to skills they already hold. Now Tobias is at point eight seven, Owen at point nine, and Elena at point eight five. Nia, at point nine two, sits just above the caution point, so she's watched. The total hasn't changed: still ninety-two hours. And since a ratio is a snapshot, the balance is reviewed every week.
Assignment Methods
Fixed Assignment, Work Queues and Boards
How should work be handed out? Three arrangements are common. In fixed assignment, the lead decides in advance who does each task. It suits specialist work with strict dependencies, but the lead becomes a bottleneck, and Monday's plan is stale by Thursday. In a work queue, ready tasks sit in one ordered list, and people pull the next item. It's fast for small, similar tasks, but hard items can age while easy ones get picked. On a board, each task is a card in a column, like queue, in progress, review and done, carrying its owner's name, and moving right as the work advances. Boards usually add a work-in-progress limit: a cap on cards in a column, so people finish work before starting more. A full column means: finish or review, don't start. A board shows the state of the work, not the capacity of the people. So it doesn't replace the load ratio.
Two Views
Lead Assigns or People Pull
Who should decide who does what? One position says the lead should assign: the lead sees the whole project, matches skills, and makes sure unattractive work gets done. The other says people should pull work: they know their own capacity and skills best, waiting for assignment slows things down, and autonomy sustains motivation. Whether pulled work really gets left undone more often is a factual question, and no study settles it. How much say people should have over their own work is a question of values. Many teams combine the two: the lead assigns specialist or sensitive work, and the team pulls the rest. That's a common practice, not a verdict.
Performance Management
Expectations, Feedback and Underperformance
Assignments also need performance management, and that's only possible if an expectation was set: the result, the standard, and the timing a person is to meet. Some apparent performance problems are really expectation problems. So the first question is whether the expectation was clear. Feedback compares someone's work with the expectation. It works when it's timely, specific, and about the work. Eleven records in Tuesday's index are filed under the wrong heading: that can be acted on. You need to be more careful can't, and it sounds like a judgment. Underperformance, a sustained gap between results delivered and results expected, is handled early and privately. In week one it's a conversation. In month four, it's a dispute. Describe what was expected and what happened, ask for their account, and look for causes in order: an unclear expectation, overload, a missing skill or tool, and only then effort. Agree what will change and when it'll be reviewed. If it moves toward formal procedures, human resources applies, and where employment law is involved, consult counsel.
Recognition
Recognition Versus Reward
Recognition acknowledges a contribution: a specific thank-you, a mention to the sponsor, a written note, a chance to present, or a stretch assignment. The strongest recognition says what was done, why it mattered, and who benefited. A plain good job carries little. Reward is different: a tangible benefit under the organization's rules, like pay, promotion or leave. Anyone can recognize a colleague, at once, for free. A reward often isn't the lead's to give. So don't promise a reward that isn't yours, and don't use recognition as a substitute for a fair workload. One risk: recognizing only visible effort, like late-night messages. Quiet work, like documentation, a risk removed early, or a careful test, leaves little to see, and remote members get overlooked. The habit that corrects it is to recognize against the results and standard agreed at delegation, not against who looked busy.
Virtual Teams
Replacing the Signals of a Shared Office
Back to Nia at home. A virtual team works in different places, often different time zones, and loses the casual signals of a shared office. Nobody could see that she was idle. Four practices replace those signals. Agreed working hours, with an overlap window when everyone can be reached and decisions get made. A written handover: what was done, what's under way, what's blocked, what's waiting for a decision, and where the files are. Shared task visibility, like the board, so everyone sees what's being done and what's waiting. And checking understanding. Over distance, silence doesn't mean agreement. Ask the person to restate the task and the deadline, and confirm it in writing.
Diagnosis
Role Ambiguity Versus Overload
Two faults keep assignments from staying true. Role ambiguity is not knowing what you're responsible for, what authority you hold, or what result is expected. Its signs: tasks done twice or not at all, repeated whose-job-is-this questions, people seeking approval for routine decisions, and rework. Overload's signs are late work, more errors, work outside agreed hours, withdrawal, and a pile of tasks waiting on one person. One busy week is a peak. Overload is a pattern. The first move is to ask: what are you working on, in priority order? What are you waiting for, and from whom? Who decides this, and have they said so? If the answers disagree between people, it's ambiguity: repeat the RACI scan. If they show too much work for the hours, it's load: repeat the load comparison. Redistribute toward people with room. If the whole team is full, take scope or dates to the change process. And fix ambiguity with a decision right: explicit permission to make a stated kind of decision, without asking anyone.
Quick Check
Three Weeks of Missed Deadlines
Quick check. For three weeks, a records clerk has missed deadlines, mislabeled files, and answered messages at midnight. Her duties and authority are written down clearly. Which fault is this? Pause, and decide. Overload. Late work, errors and hours outside the agreed day, lasting weeks, make a pattern and not a peak. It isn't role ambiguity, because her duties and authority are clear. The fix is to compare her hours with her capacity, and move work toward people with room.
Case Resolved
Moving the Decision With the Work
Back to Priya, Tobias, and the pile of urgent tasks. People or process? Priya sees that moving tasks alone would fail: they'd come straight back to Tobias for approval. So she does two things. First, she moves four of his urgent tasks, the ones needing records knowledge more than data skills, to Nia and Owen, each with a handover note from Tobias. Second, she moves the decision with them. Within the agreed mapping guide, Nia and Owen may approve a mapping themselves. Only cases outside the guide go to Tobias. All urgent work goes onto a shared board, with a limit of three cards in progress per person. The trade-off is a slower first week, while Tobias writes handovers, and a risk that mappings approved without him are less consistent. He checks a sample of them each Friday. The overload eases because the work moved, and the decision moved with it. And the remote clerks stop waiting, because the board shows them what's ready.
Key Takeaways
Delegate, Scan, Balance and Decide
To recap: delegate the task, the authority, the expected result and the deadline, and keep the accountability. Scan the responsibility chart for gaps and overlaps: every row needs one A and at least one R. Compare assigned hours with available hours, and move work toward people with room before anyone breaks. And when one person is a bottleneck, move the decision right along with the work.
About Project Management at UPI Study
Project Management (Business 230) is a self-paced online course of 73 video lessons in 12 chapters, from starting and defining a project to planning, budgets, scheduling tools, proposals, contracts, execution, monitoring, closure, teams and certification. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Business courses Every course with PRO →
Why take it here
Why students take Project Management with UPI Study
Where the credit goes
Universities that work with NCCRS
Project Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Managing Team Roles and Work Distribution
What is the difference between recognition and reward on a project team?
How do you calculate a team member's load ratio?
What is the difference between delegating and dumping work?
How can you tell role ambiguity from overload on a project team?
About the Project Management course
How many college credits is Project Management?
How much does Project Management cost and what is included?
Which universities accept UPI Study credits?
How long does Project Management take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Project Management.
73 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →