Team Appic looking for people

Team Competency Matrix

Frederik Heins, Engineering Manager - Sep 21, 2022

How to find your next team member?

Recently, we were looking for a new team member. In order to find out what skills we were missing and to create a job posting, we used a tool called Team Competency Matrix. In short: a Team Competency Matrix shows you which skills are present and which are currently lacking in a team.

How does that work?

We did a workshop with the whole team (developers, UI/UX designer, product owner as well as our agile coach). The session was split into 2 parts. In the first part, we would gather all the skills needed in our daily work and in the second part, we would map our team’s skills to the required skills.

Step 1: Gather required skills

This was done similarly to a brainstorming session. We would use Mural as a digital whiteboard and everyone wrote down all the skills that are required during our daily work. This part was really insightful. It provided a good overview of the status quo and was also really valuable to reflect on what we are actually doing during the day.

The skills collected contained items like:

  • PHP
  • Unit / Integration Testing
  • API Design
  • Graphql
  • User Journeys
  • Splunk
  • Code Reviews
  • Frontend Tests
  • Docker

The collection was a lot bigger, so in the next step we had to group those skills as a preparation for step 2.

Step 2: Creating the Team Competency Matrix

The collected skills from part 1 were added to a google sheets table.

skill table

Everyone would self-assess how well they know a certain skill using the following criteria:

  • green (1): I can teach that
  • yellow (2): I can do that
  • red (3): no clue

skill table colored

Using that result, we could count the green team members for each skill and easily determine the required skills for our job posting. But keep in mind: some skills require more people, other skills require fewer people. In a typical development team, it’s probably fine if 1 or 2 people take care of user journeys; but there should be more people who write code.

Key learnings

Using the Team Competency Matrix was not hard and didn’t take much time. We spent like 90 minutes doing it. It was very valuable to get everyone on the same page where we were as a team and what gaps we had. We realized during the workshop that it is crucial to be very clear on what the colors (or numbers) mean. We made the mistake of switching from numbers to colors which caused confusion. I highly recommend using numbers and having the background colors adjust automatically based on the number.

Additionally, self-assessing your skills is always a good exercise in order to find areas where you want to further develop yourself and grow in your position.

In the end we were able to craft a well-matching job description for our team and actually already found our next team member!

Our offices

Remote. Distributed. Together.

Work from home or any of our offices. Our team is 100% remote and will stay this way. You need a stable internet connection and your laptop. Currently our way of work supports the central European timezone +/-2h.

Treppendorf

Our Thomann headquarters. Just a few minutes’ drive outside of Bamberg. Come by to visit our shop or meet with colleagues outside of tech & data.

Berlin

Our thomann.io office in the heart of Berlin. Easily reachable at Rosenthaler Platz. Perfect for workshops and team building.

Erlangen

Our thomann.io office in Nuremberg's metropolitan area. Just a few minutes by foot from Erlangen station. Nice, quiet location to do some deep work.

Our thomann.io Blog

Nov 10, 2022 - Markus Melber

The right amount of spice makes our solutions tasty

The right amount of spice makes our solutions tasty

Sep 21, 2022 - Frederik Heins

Team Competency Matrix

Finding your next team member by mapping your team’s skills and visualizing what is currently lacking.

Jul 13, 2022 - Oliver Dolgener

Are you Appic enough to join us?

Developing the most appic Thomann App while hunting for 5-star reviews and perfect burndown charts!

Jun 30, 2022 - Heiko Terfloth

A day at the BK-nusprig drive-in

Bad jokes, burgers, and developers... Did someone call us?

May 13, 2022 - Ralph Cibis

Thomann.io goes Cyberpunk

We went fully cyberpunk! Our branding community's last side and heart project.

Jan 3, 2022 - David Beuchert

DIY software: Why it's the one and only way to do it and everyone else is wrong

My provoking approach wooing for more in-house development.

Dec 8, 2021 - Nadine

Going fully responsive

Why we redesigned our shop - and why purple's the new blue.

Oct 18, 2021 - Julia Manger

Open Space 2021

Summer 2021 - Home office, lockdown, a fourth wave and: huh?! An Open Space!

Aug 6, 2021 - Stefan Stammler

Bits, Beats, Ops-Team

Someone needs to bring our shop online. This is our mission.

Jul 7, 2021 - Ralph Cibis

Hello, Webteam

We are the Thomann Web Team. We create thomann.de and the Thomann App.

Jan 27, 2021 - Nadine

What Kan Kanban do

The idea behind moving cards - with a crispy epilogue.

Sep 7, 2020 - Francesco

Guitars to Oslo or: The Art of Offering the Right Shipping Methods

Our developer Francesco provides you with behind the scenes insights

Jul 14, 2020 - Thomas Tischner

How Thomann is mastering the move to Kubernetes

Our Sysadmin Thomas tells you from his day-to-day work

Nov 4, 2019 - Domi

Thomann Dev Camp 2k19

This year under the Slogan "ready for our collective take-off".

Severe case of I-wanna-work-with-you?

...or any questions for us? Give Anne a call!

Welcome to Treppendorf, welcome to Thomann Music

We're inspiring and enabling people to speak music, everywhere. 24/7.