Blocker

The team is dependent on leadership to make decisions.

Solution

Transfer decision making power from leadership to the team.

Power Swap Workshop — Give the Team Decision Power

At this stage, our goal is simple: shift decision-making from leaders to the team, so they can own the decisions they are responsible for.

This helps the team move faster, reduces bottlenecks, and builds confidence.

We use two sources to guide this process:

  • Decision Authority Workshop (Stage 1: Foundation — Leadership)
    Shows decisions the team currently can’t make (🟡).

  • Roles & Responsibilities Builder
    Shows who currently owns which decisions.

The Power Swap Workshop is run when decisions are still too dependent on Product Owners, Leaders, or Scrum Masters.

It helps the team clearly understand:

  • Which decisions they can own

  • Which decisions must remain with leadership

  • Which decisions they should avoid

Tip: There’s no one-size-fits-all.

Only shift decision authority where it makes sense for the team’s skills, context, and goals.

Who Should Attend

  • Core team members (developers, testers, designers)

  • Product Owner

  • Scrum Master / Agile Coach

  • Team-aligned leaders or managers (optional but encouraged)

Step-by-Step

  1. Review the Map
    Look at the 3-circle output from the Decision Authority Workshop and the Roles & Responsibilities builder to see current decision ownership.

  2. Spot Opportunities
    Examine 🟡 “Can’t make” decisions. Ask:

    • Can the team realistically take ownership?

    • Do they have the skills and context?

  3. Shift the Power
    Move decisions from 🟡 to 🔵. Be explicit: “We now own this.”

  4. Document the Shift
    Update the Roles & Responsibilities builder to reflect the new decision ownership.

  5. Check Escalation Paths
    Ensure escalation paths remain clear, fast, and practical. Adjust as needed.

  6. Repeat Regularly
    Run this workshop every 3–6 months, or when team members, leaders, or scope changes.

Outcome

The team gains clarity and control, reducing dependency on leaders and Scrum Masters, while maintaining safe, well-defined escalation paths.

Tip: This can be done in a Retrospective.

Leaders step back, teams step up.

Let us make that shift.