How to Run an Online Workshop to Co-Create Your Team's Skill Matrix
- Вячеслав Сидячкин
- Oct 27, 2025
- 7 min read
As a manager, you’ve probably been there. You sit down with a blank spreadsheet, ready to build the "master skill matrix." You list the skills you think are important. You present it to the team in a Zoom call.
And you get… polite nods. Muted mics. And a flurry of private eye-roll emojis on Slack.
Why? Because a skill matrix created in a vacuum is just one person's opinion. It’s a top-down decree, not a ground-maded map. If you want a skills map that's actually useful, you need to co-create it. Facilitating a team workshop isn't just a "nice" thing to do; it’s the most effective way to build a fair, accurate, and living tool for growth.

Why a Skill Matrix Workshop? The Value of Co-Creation
A collaborative workshop isn't a meeting; it's a force multiplier.
You Get a Map That's Actually Accurate: The collective brainpower of your team will always be more accurate than a manager's best guess.
You Get Genuine Buy-In: People support what they help create. When the team builds the matrix, they will own it, use it, and keep it updated.
You Build a Shared Language: The process forces your team to agree on what "good" actually looks like, creating a new level of clarity.
You Foster a Culture of Transparency: The process itself sends a powerful message: we are building a transparent and fair system for growth, together.
A Step-by-Step Guide to a Killer Online Workshop
This guide uses a powerful facilitation technique called 1-2-4-All to ensure every voice is heard.
Step 0: The Prep Work
Define the Goal: Be crystal clear. "Our goal today is to create V1 of our team's skill matrix to achieve transparency in understanding our skills and to create a clear path for growth for the team and each of its members."
Set Up Your Digital Tools: Prepare a board in Miro or Mural. Make sure you're comfortable with creating breakout rooms in Zoom or Teams.
Don't start from scratch. Use AgileHR's AI-powered import to scan your team’s CVs/ JDs and generate a comprehensive first version of your skill matrix in about a minute. This isn't a final draft; it's a powerful, data-driven starting point that saves you an enormous amount of time.
Step 1: The Kickoff - Frame the "Why" (10 Minutes)
Set the stage. This is not a test. This is a collaborative session to build a tool for our collective growth. Explain how this workshop directly leads to transparency in skills and a clear path for growth. Briefly explain the 1-2-4-All process so everyone knows what to expect.
Step 2: Co-Create Your Skill Taxonomy with 1-2-4-All (25 Minutes)
The central question for this exercise is: "Based on our business goals and product roadmap, what skills are we using now or will we need in the future?"
Silent Self-Reflection (5 mins): Everyone individually and silently adds skills to their personal space on the digital whiteboard using virtual sticky notes.
Pairs in Breakout Rooms (5 mins): In breakout rooms of two, pairs discuss, cluster and refine their lists.
👉Pro tip: Teams can use AgileHR's batch upload here to instantly generate a mini-taxonomy from their own CVs, bringing a data-driven list to their discussion.
Merge pairs into groups of four to consolidate lists and cluster skills into logical groups (e.g., Frontend, Databases, Cloud).
👉Pro tip: While clustering, decide together whether a skill group should be narrow or broad:
Narrow group = very specific focus, usually tied to one tool or framework (e.g., React, PostgreSQL, Terraform). Helps identify deep expertise.
Broad group = higher-level category that combines related skills (e.g., Frontend Development, Databases, Cloud Infrastructure). Helps spot gaps across domains.
The balance matters: too narrow, and the matrix becomes cluttered; too broad, and it loses practical value.
All. Share Back (5 mins): Bring everyone back to the main room. A spokesperson from each group briefly shares their main clusters and any surprising insights. The facilitator drags and drops the clusters on the main whiteboard area to create a unified list.Congratulations, you now have your skill taxonomy.
Step 3: Define Proficiency Levels in Expert Groups (30 Minutes)
A generic “Expert” label is useless. You need concrete, shared definitions.
Form Around Clusters: Ask people to group themselves around the main clusters of skills by specialty (e.g., frontend developers, database engineers, cloud/DevOps). Each cluster becomes an expert group.
Define Levels: Within each group, participants create clear names and descriptions for proficiency levels (e.g., 1–10 or Beginner → Intermediate → Advanced → Expert/Teacher). Define what someone at that level can actually do in practice.
Align With the Whole Team (5 mins): Each expert group shares back their draft levels to the full team. The goal is alignment, consistency, and a shared understanding across clusters.
Use AgileHR to Accelerate: All of this can be drafted or even generated directly in AgileHR, which can prefill suggested levels and descriptions that teams can then refine together. Agree that if an expert group identifies an important skill that isn’t yet in AgileHR, responsible person will add it. This ensures the matrix reflects reality, not just the starting template.
Step 4: Co-Creating the Assessment Pact with "Min Specs" (20 Minutes)
The skill matrix is the "what." Now, you need to agree on the "how." A fair process is just as important as an accurate matrix. Instead of a manager reading a list of rules, you will co-create them together.
The Technique: We'll use a Liberating Structure called "Min Specs". The goal is to quickly generate a short list of essential "Dos and Don'ts" that will guide your behavior during the assessment. The question is: What are the simple 'Dos and Don'ts' that will make our upcoming skill assessment fair, safe, and genuinely useful?"
The Steps:
Silent Self-Reflection (2 mins): Everyone individually and silently writes down their "Dos" and "Don'ts" on virtual sticky notes on your digital whiteboard. (e.g., "Do: Assessment only based on Done work" "Don't: Rate people based on one bad day").
Pairs in Breakout Rooms (2 mins): In pairs, share your rules. Consolidate individual lists, and expand them to be as complete as possible.
Pairs in Breakout Rooms (5 mins): Test all the items in groups on their lists against the challenge. Can the purpose still be achieved without this item? If so, remove the item
Harvest with the Whole Group (5 mins): Bring everyone back to the main room. Go around, and have each pair share their critical rules. Consolidate together to the shortest list possible.
By the end of this rapid cycle, you will have a short, powerful list of principles co-created by the entire team. This is your Assessment Pact.
Step 5: Build and Prioritize in Real Time (15 Minutes)
Now that you have your shared skill taxonomy, it’s time to make it live and relevant.
Break into Teams: Move into breakout groups based on real teams.
Dot Voting: Ask each team to use dot voting on the main taxonomy to identify the skills that are definitely needed for their team's specific work or they will need them in the future?
Step 6: Ending the Meeting: The Final Next Steps (5 Minutes)
Now you can end the workshop with a powerful sense of accomplishment and a clear, co-owned path forward.
Wrap it up with a summary and a call to action:
"Excellent work, everyone. We’ve not only built a shared map of our skills but also a shared agreement on how we'll navigate it. The next step is the asynchronous self- and team-assessment—guided by the principles we just created—which you'll receive an invitation for shortly."

At this point, the main goal of the workshop is achieved: the team has co-created a shared skill matrix with clear definitions and priorities.
The following actions can be completed offline (async, at each person’s pace).
The AgileHR Way: Everything Flows
The digital whiteboard is great for collaboration; AgileHR makes it stick. They’re not rivals, they complement each other in one continuous workflow.
Kickoff (Before):AI-import in AgileHR generates a data-driven matrix from CVs or Jib descriptions. Open it directly in AgileHR to start.
Co-create (During):Facilitate discussion on the whiteboard while experts add/adjust skills and levels in AgileHR in real time. Every change is reflected immediately—one source of truth.
Finish Without Handoffs (After): When the workshop ends, the matrix already lives in AgileHR: clean, digitized, and ready. Next step is an Assessment.
Get started today with AgileHR and build your matrix together, in real time.
External & Internal Links
Internal Links:
(link-to-internal-article-on-skills-matrix) with anchor text: skill matrix.
(link-to-internal-article-on-skill-based-assessment) with anchor text: detailed, confidential assessment.
(link-to-internal-article-on-understanding-assessment-scores) with anchor text: proficiency levels.
(link-to-internal-article-on-skills-matrix-in-1-minute) with anchor text: generate an 80% complete skills list from CVs.
External Links:
Liberating Structures - "1-2-4-All" (The official source for the facilitation technique).
Liberating Structures — “Min Specs” (The official source for the facilitation technique).
Miro (An example of a popular digital whiteboard tool perfect for such workshops).
Gamestorming by Dave Gray (A classic resource for collaborative workshop ideas).
FAQ Section
(H2) Frequently Asked Questions
How long should this online workshop be?
Aim for 120 minutes. This gives you enough time for breakouts and discussion without causing Zoom fatigue. If you use AgileHR to pre-populate the matrix, you can often get it done in a very focused 60 minutes.
What if the team gets stuck debating the definition of a skill?
That's a feature, not a bug! That debate is incredibly valuable because it builds a shared understanding. As a facilitator, your job is to timebox the discussion. Say, "This is a great conversation. Let's spend 5 more minutes on it and then make a 'good enough for now' decision." Decide by Fist-to-Five. If we’re not at ‘3’, [Name] owns an async tighten-up, due in 48h, and we lock it offline.
What if people inflate their skills during the initial assessment?
It can happen, but it's less likely in a group setting where definitions are co-created and visible for all. Remind everyone that the goal is accuracy for development, not a competition. The follow-up assessment in AgileHR, which includes peer (experts) and manager input, also helps to create a more balanced and honest final result.


Comments