Tag: ai

Step 1: Establish Safety & Intent

Before touching any tools, address the “Who” and “Why”.

• The Intent: Frame the matrix as a tool to “reveal the system to itself,” not a performance review.
• The Agreement: Use a Designing the Team Alliance (DTA) session to establish how the team will handle being vulnerable about what they don’t know.
• Actionable Script: “This matrix is our collective map for survival and technical excellence. It ensures we ship high-quality products without burning out individuals”.

Step 2: Map Critical Skills

Create the grid structure in a physical or digital workspace.

• Vertical Axis (First Column): List the specific technical skills and domain knowledge required to deliver the current product or upcoming MVP.
• Horizontal Axis (First Row): List the names of all active team members.

Step 3: Self-Assess with the 1-2-3 Scale

Ask each team member to honestly rate their proficiency for every skill row. Use this specific pragmatic scale:

• 1 — I want to learn: I have little to no knowledge but am ready for growth.
• 2 — I can do it: I can complete tasks independently or with minimal support.
• 3 — I can teach it: I am an expert who can mentor and guide others.

Step 4: Identify Single Points of Failure (SPOFs)

Analyze the completed grid to find business risks.

• The Red Flags: Look for rows where only one person is a Level 3 and everyone else is a Level 1.
• The Impact: Explain that these gaps are the root cause of reoccurring quality issues and Sprint bottlenecks.

Step 5: Design the Cross-Training Schedule

Don’t leave learning to chance. Integrate it into the Sprint Backlog.

• Pairing Rotations: For every critical gap identified, assign a “Level 3” mentor to pair with a “Level 1” learner for the upcoming Sprint.
• Working Agreements: Formulate an agreement on technical excellence: “We agree to never work alone on tasks in our SPOF rows”.

Step 6: Protect Capacity & Update “Ready”

Bake learning into the team’s “Rules of the Game”.

• The 10% Rule: Explicitly allocate 10% of the team’s capacity to learning activities. Do not plan for 100% feature work if you have Level 1 gaps.
• Definition of Ready (DoR): Update the team’s DoR to include a requirement that complex stories must have a Primary (Expert) and Secondary (Learner) assigned before entering the Sprint.

Summary: From Frustration to Action

By following these steps, you transform a vague feeling of being “stuck” into a data-driven strategy. You are no longer guessing; you are building a Team Learning Network that ensures the team—not just individuals—is capable of shipping high-quality products.