Leadership and Team Management

01Purpose and scope

• This manual supports the course Leadership and Team Management. It is written for people who lead a small to mid-sized team, whether they hold a formal title such as team lead or manager, or they coordinate work across peers without direct reporting lines. It describes what the work looks like in practice: how goals get set, how work is assigned and checked, how feedback is given, how decisions are made, and how the health of the team is measured over time.
• The scope covers the daily and weekly rhythm of managing a team inside an organization. It does not cover executive strategy, board governance, or the detailed procedures of human resources departments. Where a decision involves hiring, dismissal, pay, discipline, or leave, the rules depend heavily on jurisdiction and on your employer's written policies, so this manual points you to those sources rather than replacing them. Anyone managing people in a regulated setting should follow the approved procedures and seek advice from qualified employment or human resources professionals before acting.

02Core principles

• Good team management rests on a few working principles that show up in almost every setting. The first is that the team's purpose must be clear enough that each person can explain, in their own words, what success looks like for the next month. If people have to guess, they fill the gap with their own assumptions, and those assumptions rarely line up.
• The second principle is that authority should match responsibility. A person asked to own a deliverable needs enough decision rights to finish it, and the manager needs to be clear about which decisions stay with the manager. Vague boundaries produce either bottlenecks, where everything waits for approval, or quiet overreach, where someone makes a call that later gets reversed.
• The third principle is that feedback is most useful when it is close in time to the work and specific about behavior. A comment about a missed handoff on Tuesday helps more than a general remark about communication during an annual review. The fourth is that managers set the conditions for the team to do its work, which includes protecting time, removing blockers, and keeping priorities stable enough that people can finish things.
• Finally, leadership is partly a matter of consistency. People watch whether the manager's actions match the stated priorities. When a manager says quality matters more than speed, then rewards the fastest delivery every time, the team learns what is really valued, regardless of the slogans on the wall.

03Planning and preparation

• Before a manager takes on a team, or before a new quarter or project cycle begins, it helps to gather the basic facts. List the team members and their current assignments, the recurring work the team must keep up, the open commitments made to other groups, and any known constraints such as budget limits, schedule dependencies, or required approvals. Ask each person what they are working on, what they think is going well, and what they find frustrating. Their answers often reveal capacity problems and hidden dependencies faster than any status report.
• Next, draft a short set of team goals. Keep it to three or four outcomes that could be checked at the end of a period. For a customer support team, that might be first response times within an agreed target, a backlog of open tickets reduced by a set amount, and a documented process for escalations. Share the draft, invite changes, and be honest about which goals are fixed and which are negotiable. A goal that the team had no part in shaping tends to get less commitment, though the manager still holds final responsibility for what gets pursued.
• Plan the operating rhythm early. Decide when the team meets as a group, when you meet one on one with each person, how status is shared, and where decisions get recorded. Many teams fail not because they lack talent but because nobody agreed on how information flows. Choose tools that the team will actually use. A shared task board, a simple document for decisions, and a regular written update are often enough. Adding more platforms rarely helps.
• Consider the trade-offs in your context. A small team in a single office can rely on informal conversation and quick corrections. A distributed team across time zones needs more written communication, clearer handoffs, and deliberate effort to build trust. A team working under contract or with external clients may have obligations that limit how freely priorities can change. Plan for the constraints you actually have, not the ideal you read about.

04Recommended workflow

1. 1
   : Confirm the goals and decision rights with your own manager or sponsor. Write down what the team is expected to deliver, what budget or headcount exists, and which decisions you can make without escalation. Get the answer in writing, even if it is a short email, because memories of these conversations drift quickly.
2. 2
   : Translate the goals into individual commitments. For each team member, agree on two or three outcomes for the next cycle, with a rough sense of effort and a named dependency on anyone outside the team. Avoid writing these as lists of tasks alone. Outcomes give people room to choose the method, which usually produces better results and more ownership.
3. 3
   : Set up the operating rhythm and run the first cycle. Hold the team meeting at the agreed time, keep it short and focused on blockers and decisions, and use the one-on-one meetings for individual concerns, development, and feedback. In the first few weeks, watch for overloaded people, unclear ownership, and meetings that drift into problem solving that should happen elsewhere.
4. 4
   : Delegate with clear boundaries. When you hand off a task, state the outcome, the deadline, the level of decision authority, and how and when you expect updates. Ask the person to repeat back what they heard. Then stay available without hovering. Delegation fails most often when the manager gives the task but not the authority, or when the manager takes the work back at the first sign of difficulty.
5. 5
   : Give feedback as a routine practice. Describe the specific behavior you observed, explain its effect on the work or the team, and ask for the person's view. Separate the feedback about a single event from feedback about patterns. When a concern involves conduct, performance management, or possible legal issues, follow the documented procedure and involve human resources early instead of trying to handle it alone.
6. 6
   : Make decisions in the open where possible. For each significant decision, record the question, the options considered, the reasoning, the person who made the call, and the date of review. Use the record to explain the decision to people affected by it. When a decision was made without full input, say so and explain the reason, then revisit it if needed.
7. 7
   : Review the cycle and adjust. At the end of a period, compare outcomes with the agreed goals, discuss what helped and what got in the way, and decide what to change. Keep the review focused on the system and the work rather than on blaming individuals. Then carry the lessons into the next planning session so that the team's practices improve rather than repeat.

05Quality checks, risk controls and compliance

• Managers often treat quality as the output of other people's work, but a team lead also shapes quality through the standards they set and the checks they run. Define what acceptable work looks like before it is produced. For a software team, that might include code review requirements and a defined test process. For an operations team, it might include a sign-off step for changes that affect customers. Write these standards down and make sure the team knows who approves what.
• Risk controls in team management are mostly about preventing predictable failures. Key-person dependence is a common one: when only one person knows how a system works, that person's absence stops the work. Cross-training, shared documentation, and rotating responsibilities reduce this risk. Another common risk is burnout, which shows up as rising errors, withdrawal from meetings, or repeated requests for deadline extensions. Watch for these signals and adjust workloads before the situation becomes a crisis.
• Compliance requirements vary widely. Employment law governs hiring, pay, working hours, leave, accommodations, and termination in ways that differ by country, state, province, and sometimes by city. Safety rules apply in workplaces such as laboratories, construction sites, and manufacturing floors. Financial controls can govern how a team spends money or approves purchases. Data protection rules affect how customer or employee information is shared within the team. This manual cannot tell you what applies to your situation. Check the current authoritative source in your jurisdiction, follow your organization's policies, and involve the appropriate specialists when a decision carries legal or regulatory weight.
• Where a team is subject to professional or regulatory oversight, such as clinical staff, licensed financial advisers, or legal support teams, the rules of the profession take precedence over general management advice. Guidance in this manual does not replace qualified professional judgment, approved procedures, or any authorization required by your regulator or employer.

06Collaboration and documentation

• A team is a set of working relationships, and those relationships depend on shared understanding. Documentation supports that understanding. It does not need to be heavy. A running decision log, a current roles summary showing who owns which area, and a short handbook covering meeting norms and escalation paths will prevent many repeated conversations. Keep these documents where people can find them and review them at least once per cycle, because outdated documentation causes as much confusion as having none.
• Collaboration with other teams requires explicit agreements. When your team depends on another group for input, or another group depends on you, write down the request, the expected timing, the format, and the escalation path if the agreement is not met. Meet with counterparts periodically to catch problems early. Managers who only communicate with other groups when something goes wrong usually find that trust erodes faster than it can be rebuilt.
• Be deliberate about the team's shared conversations. Some topics are best handled in group meetings, such as changes in priorities that affect everyone. Others belong in private, such as performance concerns, personal circumstances, or compensation questions. Being clear about which forum fits which topic protects people and keeps group meetings productive. When information must be restricted for confidentiality or legal reasons, say so plainly rather than leaving people to speculate.
• Documentation also protects the manager. Notes from one-on-one meetings, written feedback, and records of agreed expectations are useful if a question arises later about performance, workload, or decisions. Keep these notes factual and dated in your own system, and store personnel records according to your organization's retention rules. Do not store sensitive personal information in general team channels.

07Measures and continuous improvement

• Measures help a manager see whether the team is delivering and whether its way of working is healthy. Choose a small number of indicators tied to the goals you agreed on. Output measures might include completed deliverables, cycle time from request to completion, or defect rates. Health measures might include the share of people who report clear priorities, attendance and response patterns in meetings, voluntary turnover, and the number of unresolved blockers older than a set period. Survey questions can supplement these, but interpret survey results cautiously, especially in small teams where individuals can be identified.
• Set a baseline before you change anything, so you can tell whether an intervention helped. A baseline does not need to be precise. A rough count of open requests and their average age over the last month is enough to start. Review the measures at the regular cycle review, and avoid using a single number to judge individuals. Metrics applied as individual performance targets tend to distort behavior, such as people avoiding hard tasks to protect their numbers.
• Continuous improvement works best when small changes are tested and reviewed. Pick one or two adjustments at a time, such as shortening the team meeting, adding a standing agenda item for blockers, or changing how handoffs are documented. Run the change for a defined period, gather the team's view, and decide whether to keep, modify, or drop it. Share what you learned with your own manager, since patterns across teams often point to organizational issues that a single team cannot solve.
• Trade-offs apply here too. Measures take time to collect, and in a team of three the overhead of a dashboard may exceed its value. In a large team, informal observation becomes unreliable and more structured data helps. The right level of measurement depends on the size, stability, and risk profile of the work.

08Common mistakes and how to prevent them

• One frequent mistake is taking on too much individual work. New managers often keep their old technical tasks because they feel useful and because they are familiar. The result is that the manager becomes the bottleneck and has little time for the team. Prevent this by listing your own tasks each month, identifying which ones could move to others, and treating coaching and unblocking as part of the job rather than an interruption.
• A second mistake is avoiding difficult conversations. Managers delay feedback about a missed standard or a conflict between team members, hoping it will resolve. Usually it does not, and the team notices the delay. Address concerns early, privately, and specifically. If the issue involves conduct or possible legal exposure, consult your human resources function before the conversation so you follow the required steps.
• A third mistake is changing priorities without explanation. When goals shift every week, people stop investing in any of them. If a change is necessary, explain the reason, name what is being dropped, and confirm the revised plan with the team. Keep a visible list of current priorities.
• Another common error is confusing activity with progress. A busy team may still be missing its outcomes. Return to the agreed goals regularly and ask what has actually changed for the customer, the business, or the people affected. Finally, many managers underestimate how much their own behavior sets the tone. Responding calmly to bad news, following through on commitments, and admitting mistakes teaches the team more than any policy statement.

09Practical checklist

• Confirm team goals and decision rights with your sponsor in writing.
• List current team members, assignments, recurring duties, and external commitments.
• Agree on individual outcomes for the next cycle with each team member.
• Set the team meeting schedule, one-on-one cadence, and where decisions are recorded.
• Define quality standards and who approves work before it is released.
• Identify key-person dependencies and plan cross-training for the highest risks.
• Check employment, safety, and data rules in your jurisdiction against current authoritative sources.
• Give specific, timely feedback and follow the documented process for conduct concerns.
• Record significant decisions with the reasoning and the person accountable.
• Choose two or three measures tied to goals and set a baseline before changing anything.
• Review outcomes and team health at the end of each cycle and agree on one or two changes.

★Learning sources

• Micro Degree: Leadership and Team Management
• Micro Degree: Business Intelligence Management
• Micro Degree: ESG Advisory Services
• Micro Degree: Executive Assistant Services