Chapter 6 Summary
Chapter Summary
Introduction
Chapter 6 focused on one of the most important foundations of successful delegation: authority and accountability. Delegation is not simply giving work to another person. It also requires giving the person enough authority, decision rights, support, and accountability structure to complete the work successfully.
A common mistake in delegation is assigning responsibility without giving enough power. Another mistake is giving authority without clear boundaries. Both situations can create confusion, delay, frustration, and risk. Effective delegation requires balance. The delegated person should know what they own, what they can decide, what needs approval, when to escalate, and how progress will be reviewed.
This chapter explained that authority and accountability must work together. Authority allows people to act. Accountability ensures that people follow through responsibly. When these two are aligned properly, delegation becomes fair, practical, and empowering.
The central message of Chapter 6 is: Delegation becomes effective when responsibility, authority, decision rights, accountability, and review mechanisms are clearly aligned.
Chapter 6 Overview
Chapter 6 was divided into five key learning sections:
- 6.1 Responsibility vs Authority: Explained the difference between what a person is expected to deliver and what they are allowed to do in order to deliver it.
- 6.2 Levels of Delegated Authority: Explained different levels of authority, from informing to full ownership with review.
- 6.3 Avoiding Responsibility Without Power: Explained why leaders should not give people responsibility without access, authority, resources, visibility, or escalation support.
- 6.4 Accountability Without Micromanagement: Explained how leaders can maintain accountability through clear outcomes, checkpoints, progress visibility, and trust-based follow-up.
- 6.5 Delegation and Decision Rights: Explained how to define what the delegated person can decide, what they should recommend, and what requires approval.
Together, these sections provide a practical framework for giving responsibility in a way that is clear, fair, empowering, and controlled.
Summary of Section 6.1: Responsibility vs Authority
Section 6.1 explained the difference between responsibility and authority. Responsibility means what the person is expected to deliver. Authority means what the person is allowed to do in order to deliver that result.
For example, if a person is responsible for updating an action tracker, they may also need authority to contact action owners, request updates, update status, and escalate missing information. Without authority, the person may be responsible in name only.
Key Difference
| Responsibility | Authority |
|---|---|
| Defines what must be delivered. | Defines what actions and decisions are allowed. |
| Focuses on task, result, ownership, and outcome. | Focuses on access, decision rights, permission, and influence. |
| Example: “Prepare the weekly report.” | Example: “You can contact module owners directly for updates.” |
This section also explained that responsibility without authority creates frustration, while authority without responsibility creates risk. The goal is to align both.
Key lesson: A delegated person should not be expected to own a result unless they also have enough authority to influence that result.
Summary of Section 6.2: Levels of Delegated Authority
Section 6.2 explained that authority does not have to be all or nothing. A leader can give authority in levels based on the task risk, person readiness, experience level, and development goal.
This section introduced five levels of delegated authority:
| Level | Authority Type | Meaning | Best Used For |
|---|---|---|---|
| Level 1 | Informing | The person collects and shares information. | Beginners or low-risk information gathering. |
| Level 2 | Recommending | The person analyzes and suggests options. | Developing analytical thinking and judgment. |
| Level 3 | Deciding with Approval | The person proposes a decision, but the leader approves before action. | Moderate-risk tasks or developmental decision-making. |
| Level 4 | Deciding Within Limits | The person can decide independently within agreed boundaries. | Competent and reliable team members. |
| Level 5 | Full Ownership with Review | The person owns the process or outcome with periodic review. | Experts, process owners, or leadership development. |
The section explained that leaders should increase authority gradually as people demonstrate capability, reliability, and judgment.
Key lesson: Delegation becomes safer and more empowering when leaders choose the right authority level and communicate it clearly.
Summary of Section 6.3: Avoiding Responsibility Without Power
Section 6.3 explained one of the most common delegation failures: giving someone responsibility without giving them enough power. Responsibility without power means expecting a person to deliver an outcome without giving them the authority, access, resources, visibility, time, or escalation support needed to succeed.
This situation is unfair because the person is accountable for results they may not be able to influence. For example, a person may be asked to collect updates from different owners, but if they are not introduced as the coordinator or allowed to contact owners directly, they may struggle to complete the task.
Power in Delegation Includes:
- Information power: Access to required information, data, documents, or trackers.
- Decision power: Authority to make certain decisions within boundaries.
- Communication power: Permission to contact people needed for the task.
- Resource power: Access to tools, templates, systems, or support.
- Escalation power: Permission to raise blockers when progress is stuck.
- Role visibility power: Others know the person has been assigned the responsibility.
- Time power: Enough time and priority space to complete the task.
The section also introduced the POWER Delegation Model: Provide access, Offer authority, Widen visibility, Enable escalation, and Review support.
Key lesson: Delegation becomes fair and effective when leaders give people not only responsibility for outcomes, but also the power, access, authority, and support needed to achieve those outcomes.
Summary of Section 6.4: Accountability Without Micromanagement
Section 6.4 explained how leaders can keep people accountable without controlling every small step. Accountability without micromanagement means staying connected to the outcome while giving the person enough freedom to manage the work.
This section explained that micromanagement often happens when leaders are anxious, expectations are unclear, review points are missing, or trust is weak. Micromanagement may feel safe in the short term, but it damages ownership, confidence, initiative, and problem-solving in the long term.
Healthy Accountability Includes:
- Clear outcomes and success criteria.
- Defined decision rights and boundaries.
- Planned checkpoints instead of random checking.
- Progress visibility through trackers, updates, or reviews.
- Escalation rules for blockers and risks.
- Coaching questions instead of controlling instructions.
- Autonomy between agreed review points.
This section introduced the TRUST Framework: Target outcome, Review rhythm, Update method, Support and escalation, and Trust autonomy.
Key lesson: Delegation becomes stronger when leaders stay connected to the outcome while giving people enough freedom, trust, and space to own the work.
Summary of Section 6.5: Delegation and Decision Rights
Section 6.5 explained that delegation becomes clearer when decision rights are defined. Decision rights tell the delegated person what they can decide independently, what they should recommend, and what must be approved before action.
If decision rights are unclear, the person may either ask for approval too often or make decisions beyond their authority. Both situations create problems. Clear decision rights help people act confidently while protecting important decisions through approval boundaries.
Three Categories of Decision Rights
| Category | Meaning | Example |
|---|---|---|
| Can Decide | The person can decide independently within agreed limits. | “You can decide the internal follow-up order.” |
| Should Recommend | The person should analyze and suggest, but not finalize. | “Please recommend which risk should be escalated first.” |
| Must Get Approval | The person must check with the leader before acting. | “Do not send external communication without approval.” |
This section also introduced the RIGHTS Model: Responsibility, Independent decisions, Guided recommendations, Hard approval boundaries, Triggers for escalation, and Support and review.
Key lesson: Delegation becomes more powerful when people clearly understand what they can decide, what they should recommend, and what must be approved before action.
Chapter 6 Key Concepts
The following are the most important concepts from Chapter 6:
- Responsibility means what a person is expected to deliver.
- Authority means what a person is allowed to do to deliver the result.
- Responsibility and authority must be aligned.
- Responsibility without authority creates frustration and dependency.
- Authority without accountability creates risk and confusion.
- Delegated authority can be given in levels.
- Authority should match task risk and person readiness.
- Responsibility without power is unfair and ineffective.
- Power includes access, resources, visibility, decision rights, escalation, and time.
- Accountability should not become micromanagement.
- Planned checkpoints are better than random checking.
- Progress visibility helps leaders stay informed without controlling every step.
- Decision rights should be clearly defined before work begins.
- Decision rights should be divided into can decide, should recommend, and must get approval.
- Authority and decision rights should expand as trust and capability grow.
Important Comparison: Weak Delegation vs Strong Delegation
| Weak Delegation | Strong Delegation |
|---|---|
| Gives responsibility without authority. | Aligns responsibility with authority. |
| Uses vague language such as “own this.” | Defines what ownership actually means. |
| Requires approval for every small decision. | Gives decision rights within safe boundaries. |
| Does not provide access or resources. | Provides information, tools, templates, and support. |
| Does not inform stakeholders about delegated ownership. | Makes the delegated person’s role visible to stakeholders. |
| Checks randomly and frequently. | Uses planned checkpoints and progress visibility. |
| Micromanages the method. | Focuses on the outcome and boundaries. |
| Does not define escalation rules. | Defines when and how blockers should be escalated. |
| Blames people for delays caused by missing authority. | Checks whether the person had enough power to succeed. |
Authority and Accountability Checklist
Use the following checklist before delegating a task to ensure responsibility, authority, and accountability are aligned.
| No. | Checklist Question | Yes / No / Needs Action |
|---|---|---|
| 1 | Is the responsibility clearly defined? | |
| 2 | Is the expected outcome clear? | |
| 3 | Does the person have access to required information? | |
| 4 | Does the person have access to required tools, documents, or systems? | |
| 5 | Can the person contact required stakeholders directly? | |
| 6 | Have stakeholders been informed about the person’s role? | |
| 7 | Are decision rights clearly defined? | |
| 8 | Are approval boundaries clearly defined? | |
| 9 | Are escalation rules clear? | |
| 10 | Are review points planned? | |
| 11 | Is progress visibility agreed? | |
| 12 | Does the person have enough time and capacity? | |
| 13 | Is the monitoring level appropriate to risk and readiness? | |
| 14 | Does the person know what to do if blocked? | |
| 15 | Is accountability fair based on the authority provided? |
Responsibility-Power Alignment Worksheet
This worksheet helps leaders check whether a delegated responsibility has enough supporting power.
| Delegation Area | Your Answer |
|---|---|
| What responsibility am I delegating? | |
| What result should the person deliver? | |
| What information does the person need? | |
| What resources or tools are needed? | |
| Who must the person coordinate with? | |
| What authority should the person have? | |
| What decisions can the person make independently? | |
| What decisions should the person recommend? | |
| What decisions require approval? | |
| When should the person escalate? | |
| How will progress be visible? | |
| When will review happen? |
Decision Rights Review Table
Use this table to clarify decision rights before delegation begins.
| Decision Area | Can Decide Independently | Should Recommend | Must Get Approval |
|---|---|---|---|
| Communication | |||
| Timeline | |||
| Format / Quality | |||
| Risk / Escalation | |||
| Stakeholder Updates | |||
| Closing / Finalizing Work |
Sample Complete Delegation Statement for Chapter 6
The following statement combines authority, accountability, power alignment, checkpoints, escalation, and decision rights.
“I would like you to take responsibility for maintaining the weekly action tracker. Your responsibility is to collect updates from action owners, update the tracker, highlight delayed items, and prepare a short summary before Friday’s review.
You can contact action owners directly and update status based on confirmed responses. You can decide the order of items in the tracker to make it easier to review. Please do not close any action unless the owner confirms completion, and do not change due dates without checking with me.
I will inform the team that you are coordinating the tracker. If any owner does not respond after two follow-ups, escalate it to me by Wednesday evening. To keep progress visible without micromanagement, let us review the tracker together for the first two weeks. After that, if everything is working smoothly, you can manage it more independently.”
Why This Statement Works
- It clearly defines responsibility.
- It gives the person communication authority.
- It gives decision rights within boundaries.
- It clarifies what needs approval.
- It provides stakeholder visibility.
- It defines escalation rules.
- It sets review points without micromanagement.
- It allows authority to expand as trust grows.
Chapter 6 Practice Questions
Use the following questions for revision, classroom discussion, or self-study.
Short Answer Questions
- What is the difference between responsibility and authority?
- Why must authority match responsibility?
- What is responsibility without power?
- Name five types of power needed in delegation.
- What are the five levels of delegated authority?
- What is accountability without micromanagement?
- Why are planned checkpoints better than random checking?
- What are decision rights?
- What is the difference between “can decide” and “must get approval”?
- Why should decision rights expand gradually?
Long Answer Questions
- Explain the relationship between responsibility, authority, and accountability in delegation.
- Discuss the five levels of delegated authority with examples.
- Explain responsibility without power and describe how leaders can avoid it.
- Describe how leaders can maintain accountability without micromanaging.
- Explain the importance of decision rights in delegation and provide examples.
Scenario-Based Question
A leader asks a team member to own the weekly project update. The team member is expected to collect updates from multiple people and prepare a report. However, the leader does not give access to the tracker, does not inform others that the team member is coordinating, and does not define what decisions the person can make. The report is delayed. What went wrong, and how should the leader correct the delegation?
Suggested Answer Direction: The leader created responsibility without power. The team member was responsible for the report but lacked access, role visibility, decision rights, and escalation support. The leader should provide access to the tracker, inform stakeholders, define decision rights, clarify approval boundaries, and set escalation rules.
Reflection Questions
- Do I clearly define authority when I delegate responsibility?
- Have I ever given responsibility without enough power?
- Do I provide access, resources, and stakeholder visibility before expecting ownership?
- Do I use planned checkpoints or random checking?
- Do I sometimes micromanage because I am anxious about results?
- Do I define what people can decide independently?
- Do I clearly explain what requires approval?
- Do I expand decision rights as people grow?
- How can I create accountability without reducing autonomy?
- What delegated task should I review using the Chapter 6 checklist?
Chapter 6 Final Summary
Chapter 6 explained that authority and accountability are essential for effective delegation. Delegation is not only about assigning a task. It is about creating the right conditions for the person to own the task successfully.
We learned that responsibility defines what the person is expected to deliver, while authority defines what the person is allowed to do. These two must be aligned. If responsibility is given without authority, the person may feel powerless. If authority is given without accountability, decisions may become risky or unclear.
We also learned that authority can be given in levels. A person may start by informing, then recommending, then deciding with approval, then deciding independently within limits, and eventually owning the work with review. This gradual growth helps people build confidence and judgment.
The chapter also emphasized avoiding responsibility without power. Leaders must provide access, resources, role visibility, decision rights, time, and escalation support. Without these, accountability becomes unfair.
Accountability without micromanagement was another major theme. Leaders should stay connected to outcomes through clear expectations, planned checkpoints, progress visibility, and escalation rules. They should avoid controlling every small step.
Finally, the chapter explained decision rights. The delegated person should know what they can decide, what they should recommend, and what must be approved. Clear decision rights reduce confusion and help build true ownership.
The main message of Chapter 6 is: Delegation succeeds when responsibility is supported by authority, decision rights, accountability, visibility, and trust-based review.
Preparation for Chapter 7
In Chapter 7, we will move from authority and accountability to monitoring delegated work without micromanaging. Once authority and decision rights are clear, the next question is: How should leaders track progress and support execution without taking over?
Chapter 7 will discuss:
- Monitoring vs micromanaging
- Creating effective checkpoints
- Progress tracking methods
- Status updates and dashboards
- Coaching during execution
- Handling delays and blockers
- When leaders should intervene
- How to maintain trust while tracking progress
Before moving to Chapter 7, learners should complete the authority and accountability checklist and identify one delegated task where responsibility, authority, and decision rights need better alignment.