Why your skills directory belongs inside Microsoft Teams, not next to it

Walk into any organisation with more than fifty people and ask where the skills directory lives. You will get four different answers from four different people, and at least one of them will be wrong.

HR will point to a module in the HRIS that was set up during a 2021 implementation project and has been touched by twelve people since. Operations will mention a SharePoint list maintained by someone who left in March. The engineering manager has a Notion page. Learning and Development has a competency framework PDF that opens in a separate window and runs to forty-two pages. None of them know about each other. All of them are out of date.

This is not a tooling problem. There are plenty of fine skills-mapping tools on the market. It is a location problem. The skills directory lives somewhere people do not work, and so the information inside it ages out faster than the team can update it.

The first principle: skills mapping has to live where work happens

In 2026, for most knowledge-work organisations in the UK, "where work happens" means one of two places: an email inbox and Microsoft Teams. Email is where things end up; Teams is where they get done. Microsoft Work Trend research consistently shows information workers spending a significant share of the working day inside Teams. For some roles - operations leads, comms operators, project managers - it is the dominant tool of the day.

That is the floor on which any skills initiative either succeeds or quietly fails. If your team has to leave Teams to record a skill, look up a colleague, or check a competency, they will not do it. They will guess. They will message someone they already know. They will reach for the person they remember from the last project, not necessarily the person who is actually best for this one.

So the question is not "do we need a skills directory" - everyone needs one. The question is whether the directory is reachable from inside the four or five seconds of attention a manager has between meetings.

What "inside Microsoft Teams" actually means

Microsoft Teams is not one surface, it is four. Each one is a different opportunity to embed skills mapping into a workflow that was already going to happen.

1. The compose extension - "search without switching screens"

When you type a message in any Teams chat or channel, there is a small toolbar above the compose box. Most people use it for GIFs and stickers. Microsoft also lets third-party apps put a search there.

With SkillDrill installed, an operations lead can type into any chat:

@SkillDrill find python developer with NHS experience

Three matches appear as ranked cards inside the chat, with a green or grey availability dot, current location, and three actions: Message, Email, Call. The manager picks the right person and carries on with the original conversation.

No new tab. No login. No "where did I save that competency framework". The manager never broke focus.

2. The personal tab - "my skills, my growth"

Every Teams user has a personal app rail on the left. That is where the things they care about themselves live: their calendar, their files, their tasks. We add a SkillDrill tab there for each user.

What it shows is small and specific:

• What the system thinks they know, with a confidence score for each skill
• Two or three short prompts to refine those skills through a conversation - five minutes, not a one-hour interview
• Suggestions for catch-ups - "you have not spoken to your line manager in six weeks"
• Internal opportunities that match their stated growth direction

People update their skills on the way to lunch, on the train, in the gaps between meetings. Not because HR asked them to in an email, but because the prompts are small, useful, and live inside the app they already had open.

3. The channel tab - "this team's capability at a glance"

Pin a SkillDrill tab to a project channel or a department team, and the whole team can see what the team can do. Not as a list of names with five-star ratings - that has never been useful - but as a heat map of capabilities. Where are we strong, where are we thin, who is the second-best person for a given skill if the first is on leave.

For project managers, this is the difference between "I think we have someone who knows Power BI" and "we have three people, here they are, two are available this fortnight". For service managers, it is succession planning made visible: the gap between your one-person-deep skill and the second person who is two-thirds of the way to covering for them.

4. The bot and the proactive nudge - "the directory comes to you"

The least obvious surface is a Teams bot. Not a chatbot you talk to all day - nobody wants that - but a proactive messenger that nudges at the right moment.

Examples we see in production:

• "Sgt Jones is on shift today and has just renewed her firearms certification - the briefing notes flagged a related job at 16:00, do you want me to flag her name to the duty inspector?"
• "You have a recruitment panel on Thursday. Three internal candidates have applied. Would you like a skills summary card for each?"
• "Your team has not had a one-to-one captured in the system for 11 weeks. The system can prompt a five-minute catch-up this Friday - shall I schedule it?"

This is where skills mapping stops being a database and starts being an assistant. The system already knows what skills are present, who is available, who is overdue for a conversation, what opportunities are coming. Surfacing that proactively, in the place the manager already lives, turns a passive directory into an active workforce tool.

Why this works when a separate system does not

There is a specific reason a Teams-native approach succeeds where a separate HR module fails, and it is not a feature comparison. It is behavioural.

A separate system asks the user to remember it exists, log in to it, and then do something extra on top of their regular work. Three steps, each with a drop-off rate of forty per cent or worse. Multiply them and almost no-one finishes. The data inside the system is therefore stale, which makes managers distrust it, which makes them use the system even less. Six months in, the standalone tool is a graveyard.

A Teams-native approach removes the first two steps entirely. The user does not have to remember the app exists - it is in the rail. They do not have to log in - they are already logged in. They only have to do the third thing, which is the actual useful action, and even that is shaped to take less than thirty seconds.

This is the same logic that made Slack-native apps eat the integration market in the 2010s. It is not a new insight. The new part is that Microsoft Teams now has the same kind of extensibility surface - compose extensions, personal apps, tabs, bots, the message extensions API - and most skills-mapping vendors are still building standalone web apps.

What IT and information security actually need to hear

The other reason skills directories often live outside Teams is that someone in IT got nervous about a third-party app having access to staff data. That fear is reasonable. So here is what a sensibly-built Teams-native skills directory actually does and does not do.

What it does:

• Authenticate through your existing Entra ID (Azure AD) tenant. No new identity store. Single sign-on, conditional access, MFA - all your existing controls.
• Read user profile data through Microsoft Graph with the minimum permission scope you grant. If you only grant User.ReadBasic.All, that is all it gets.
• Store skills data in the UK, on AES-256-encrypted infrastructure, with a documented data processing addendum that maps directly to UK GDPR.
• Honour your retention policy - the system can be configured to forget after a defined period.

What it does not:

• Read message content. Skills data comes from short structured conversations, not from scraping chats.
• Train external models on your staff data.
• Make data available to anyone outside the tenant you install it in.

From an IT perspective, a Teams-native app installed through the Microsoft Teams Admin Centre is materially safer than a separate web application that requires its own user provisioning, its own credentials, and its own audit trail. The Teams app inherits the entire compliance posture you have already paid for.

So what does the buying decision actually look like

If you are weighing up a standalone skills platform against a Teams-native one, the right question to ask is not which has more features. It is this:

In six months, when no-one has updated their skills profile for three weeks, which of these two systems is going to recover the habit?

A separate system recovers by sending an email asking people to log in. That email will be ignored. A Teams-native system recovers by surfacing a thirty-second prompt at the moment a person is already in Teams - between meetings, in a one-to-one channel, while they are looking at their calendar. The recovery rate is incomparable.

The skills are on the workforce somewhere. They always have been. The only thing standing between you and using them is whether the directory lives where the work happens.

If you want to see what SkillDrill looks like inside a Teams tenant - the compose extension, the personal tab, the channel view, the bot nudges - book a fifteen-minute demo. We will show it inside a sandbox tenant and you can decide whether it is the missing layer between your HRIS and the work your team actually does.