T04: Empower Team | Domain 1

📖 Lý thuyết / Theory

🇺🇸 English

Empowerment means giving team members the authority, resources, and information to make decisions within their area of responsibility. It's different from delegation:

Delegation: Assigning tasks while PM retains authority and accountability
Empowerment: Transferring decision-making authority to team members; they own the outcome

In Agile: Self-organizing teams are empowered to decide HOW they work. PM/SM does not prescribe technical approaches — the team decides. This increases intrinsic motivation and improves quality.

Reference: PMI — Empowering Project Teams

🇻🇳 Tiếng Việt

Trao quyền nghĩa là cho thành viên team quyền hạn, nguồn lực và thông tin để ra quyết định trong phạm vi trách nhiệm của họ. Khác với ủy quyền:

Ủy quyền: Giao nhiệm vụ trong khi PM vẫn giữ thẩm quyền và trách nhiệm
Trao quyền: Chuyển giao thẩm quyền ra quyết định cho thành viên team; họ sở hữu kết quả

Trong Agile: Self-organizing teams được trao quyền quyết định HOW họ làm việc. PM/SM không prescribe cách tiếp cận kỹ thuật — team tự quyết định.

🔑 Điều kiện để Trao quyền thành công

Điều kiện	Mô tả	Ví dụ
Clear boundaries	Team biết rõ phạm vi quyền hạn của họ là gì	"Team tự quyết công nghệ, nhưng architecture change cần review với Tech Lead"
Sufficient information	Team có đủ thông tin để ra quyết định tốt	Product goals, constraints, stakeholder expectations được share đầy đủ
Adequate skills	Team đủ năng lực để đảm nhận trách nhiệm	Training + experience phù hợp với decision level
Psychological safety	Team không sợ bị phạt khi mắc lỗi trong quá trình trao quyền	PM/EM normalize mistakes as learning, not blame
PM support	PM sẵn sàng hỗ trợ, không micromanage nhưng không abandon	Available for guidance when asked, check-in without hovering

🎯

Exam Tips — Empower

Câu hỏi về Agile: team tự quyết định cách làm việc — PM/SM facilitate, không dictate
Nếu PM đang "làm thay team" hoặc "quyết định thay team" → thường là đáp án SAI
Trao quyền ≠ bỏ rơi team. PM vẫn available và hỗ trợ khi cần
Stakeholder empowerment: cung cấp đủ thông tin để stakeholders tham gia và ra quyết định có hiểu biết

💼 Thực chiến / Scenario

🏢

FinTech Company X — Team Autonomy in Technology Decisions

Tình huống: Team Project Alpha đang refactor legacy DOP codebase. EM muốn chọn framework cho team. Team muốn tự quyết định.

PMI way — Empower: EM chia sẻ constraints (performance requirements, team learning curve budget, timeline), sau đó để team research và present 2-3 options với tradeoffs. Team vote, document decision trong ADR. EM support bằng cách approve budget cho learning resources.

Kết quả: Team có ownership cao hơn với quyết định. Commitment tốt hơn. EM tập trung vào strategic work thay vì technical micromanagement.

✏️ Practice Questions

Question 1

In an agile project, the project manager notices that team members always wait for approval before making technical decisions. What should the PM do?

A. Approve decisions faster to reduce wait time
B. Establish clear decision-making authority boundaries and encourage the team to make decisions within their scope
C. Create a formal decision approval matrix requiring all decisions to go through PM
D. Assign a team lead to make all technical decisions

✅ Answer: B — The PM should empower the team by clarifying what decisions they can make autonomously. This aligns with servant leadership and self-organizing team principles. Option A doesn't fix the dependency. Option C increases bureaucracy. Option D just moves the bottleneck from PM to team lead.

Question 2

A senior developer consistently asks the PM for approval before making any technical architecture decisions, even for minor components. What should the PM do?

A. Continue approving decisions — PM oversight ensures quality
B. Delegate decision authority clearly and explicitly, define the scope of their autonomy
C. Assign a more experienced PM mentor
D. Document all decisions the developer makes and review weekly

✅ Answer: B — A senior developer seeking approval for minor decisions signals that empowerment boundaries are unclear. The PM should explicitly define what the developer can decide independently (e.g., component-level architecture) vs. what requires review (system-level changes). Option A perpetuates the bottleneck and is the opposite of empowerment. Option C doesn't address the root cause. Option D adds overhead without solving the approval dependency.

Question 3

Which condition is MOST important for successful empowerment?

A. Team members have high seniority
B. The PM has clear visibility into all decisions
C. Team members have the skills, information, and authority needed for the decision
D. The team is co-located

✅ Answer: C — Empowerment fails when any one of three elements is missing: skills (competence to make the decision), information (context and constraints to decide well), or authority (explicit permission to act). Seniority (A) is a proxy for skills but isn't sufficient alone. PM visibility (B) is about control, not empowerment. Co-location (D) is irrelevant — remote teams can be fully empowered.

🔧 Delegation Matrix — Decision Authority

Delegation Matrix — Decision Authority

🤖 AI Tools for PMs

🤖

How AI Augments This Process

AI helps PMs design delegation frameworks, create RACI matrices, and generate empowerment plans that match authority levels to team members' readiness.

Sample Claude Prompts

RACI matrix generation I need to create a RACI matrix for a project/workstream. Project/process: [name and brief description] Key activities or deliverables (list 5-10): 1. [Activity] 2. [Activity] ... Roles involved: [PM, Tech Lead, Dev, QA, Product Owner, Sponsor, etc.] Generate a RACI matrix where: R = Responsible (does the work) A = Accountable (signs off — only ONE per row) C = Consulted (gives input) I = Informed (kept in the loop) Highlight any rows with: multiple A's, no R, or over-consulted roles (too many C's = bottleneck). Suggest adjustments to streamline decision-making.

Delegation decision framework I want to delegate [task/decision/responsibility] to [team member / role]. Current state: Their competence for this task: [1-4 scale] Their motivation/confidence: [1-4 scale] My risk tolerance: [low/medium/high — what's the cost if they fail?] Deadline pressure: [urgent / flexible] Help me: 1. Decide whether to delegate fully, partially, or not yet 2. Define the boundaries of their authority (what they can decide vs. must escalate) 3. Design a support plan (check-ins, resources, escalation path) 4. Draft the delegation conversation — how I'll frame it to motivate and empower

Team empowerment health check I want to assess how empowered my team feels. Here's what I observe: - Decision-making: [do they make decisions or always ask me?] - Initiative: [do they proactively solve problems?] - Psychological safety: [do they speak up, challenge, experiment?] - Ownership: [do they take accountability or blame others?] Team context: [remote/co-located, Agile/waterfall, team tenure] Diagnose the team's empowerment level and give me: 1. 3 specific behaviors that are blocking empowerment (mine or theirs) 2. 5 micro-changes I can make this sprint to increase autonomy 3. One structural change worth considering (e.g., decision rights, ceremonies)

Jira / Confluence Template

Confluence — Delegation Authority Matrix

Empower Team Members and Stakeholders