Start with the work: why Colt chose TechWolf to build its skills foundation

Mathieu De Baets, TechWolf
Mathieu De Baets
September 30, 2026
•
3 min read
TechWolf and Colt logos on a dark background
Contents

Skills programs fail at the foundation

It's very hard to kick off a skills transformation journey with a messy job architecture. If roles are too broad, too generic, or out of date, every skill profile built on them inherits the error. Career paths point to roles that don't reflect the work, and workforce plans count the wrong things.

Colt, the global network and connectivity provider, saw the symptoms before it saw the cause. Leaders never said the job architecture was broken. They said they couldn't see career paths, couldn't plan future skills at scale, and that recruitment took too long in some areas.

Earlier attempts had tackled those symptoms one at a time: a skills initiative, then a rethink of grades, then a career development project. Each one made sense on its own. Together they never held, because nothing connected them.

"Where we failed in the past is trying to do piecemeal elements of skills, or rethinking our grades, or looking at career development. The bit that brought this all together for us was our job architecture."
Jonathan Jacobsen, VP Reward at Colt Technologies

Demand side first

There are two ways to build a picture of skills. Supply-side approaches start with people: CVs, profiles and candidate data. They tell you what your workforce has. Demand-side approaches start with the work: the roles, the tasks and what each one requires. They tell you what the organization needs.

Both matter, but the order matters more. Workforce planning, internal mobility and career paths are all questions about demand. Start with supply and you end up mapping people's skills onto job titles that were never designed to carry them.

Most skills vendors are born as recruitment solutions, where supply comes first because the business is finding candidates. Colt ran a full RFP, and that distinction ruled out a large part of the market.

"So many of them have come from a recruitment background. Their technology is built on the assumption that you're going to start with supply. We wanted to start on the demand side."
Jonathan Jacobsen, VP Reward at Colt Technologies

Job architecture is the connecting layer

A job architecture is more than an org chart with titles. It defines the distinct roles in an organization, the levels within them and what each one involves. Grades and pay attach to it. Skills and proficiencies attach to it. Career paths are routes through it. Fix any of these separately, and they drift apart again.

That makes the job architecture the natural place to start an end-to-end skills program, and it is why Colt came to TechWolf with a structural problem rather than a shopping list. The redesign was not in the original scope, but it shaped the decision.

"It wasn't what we originally signed up for, but it absolutely helped us believe that TechWolf was the right partner to look at this more holistically."
Jonathan Jacobsen, VP Reward at Colt Technologies

Phase one: redesign without the usual cost

Colt's existing architecture was a couple of years old, had taken significant effort to build, and was too generic in places to carry skills reliably. The usual fix is to buy an off-the-shelf architecture and tailor it by hand.

Colt had no appetite for that. A generic catalog would have meant months of stakeholder interviews, line-by-line data reviews and validation rounds to make it fit, and the team had already lived through one heavy manual build. It wanted a structure that started from its own work, not someone else's template.

TechWolf's Job Architecture Redesign Agent analyzed the work behind Colt's existing roles, proposed a structure of distinct roles, and drafted a job description for each one. Colt's core team reviewed and changed the structure, and Talent Acquisition, who use job descriptions more than anyone, validated the descriptions. The judgment stayed with Colt; the manual effort did not.

"It's allowed us to get there requiring less manual intervention, less of us having to go out and talk to the business and pick through lines and lines of data. It's taken less manpower on our side."
John Ambrose, Director of Talent, Learning and Performance at Colt Technologies

The structure and job descriptions for HR are validated. For the other functions, the structure is reviewed and the job descriptions are being loaded, so skills can follow directly.

From project to operating model

The real test of a job architecture is not the day it goes live. It is whether it keeps up as the work changes, and with AI reshaping tasks inside almost every role, the work is changing faster than any refresh cycle.

Colt is already planning for that. It wants a job architecture center of excellence that reviews the market regularly and uses the Agent to model role redesigns before making decisions, with TechWolf supporting the handover. Skills, proficiency, career paths and workforce planning then all build on one structure that stays current.

That is the difference between a skills project and a skills foundation.

See the Job Architecture Redesign Agent live at SAP Connect, Las Vegas, 5 to 7 October.
Book a meeting
No items found.

Blog

Relevant sources

From guides to whitepapers, we’ve got everything you need to master job-to-skill profiles.

View all
View all
TechWolf and Colt logos on a dark backgroundTechWolf and Colt logos on a dark background
Job Architecture
Skills Intelligence
Blogpost

Start with the work: why Colt chose TechWolf to build its skills foundation

Colt's past skills efforts stalled because they were piecemeal. It chose TechWolf for a demand-first, end-to-end approach, starting with a Job Architecture Redesign that took far less manual effort.
Mathieu De Baets, TechWolf
Mathieu De Baets
Sep 30, 2026
Start with the work: why Colt chose TechWolf to build its skills foundation
Job Architecture
SAP Partnership
Blogpost

Weeks, not months: how Chiesi rebuilt the foundation for its workforce transformation

Chiesi, the global pharmaceutical group, had job titles and a grading structure but no job architecture detailed enough to build on. With TechWolf's Job Architecture Redesign Agent it rebuilt the architecture from the work people actually do, wrote a new job description for every job, and went live in SAP Job Profile Builder in a matter of weeks.
Mathieu De Baets, TechWolf
Mathieu De Baets
Sep 24, 2026
Weeks, not months: how Chiesi rebuilt the foundation for its workforce transformation
Skills Intelligence
Strategic Workforce Planning
Article

Getting skills right: Why demand and supply must always be on

Skills only create value when demand and supply are connected, and kept connected. Renée Smith (WTW) and Daniel Torrens (TechWolf) on why one-off taxonomies age the moment they ship, and what continuous skills intelligence changes for workforce planning, mobility and pay.
Renée Smith & Daniel Torrens
Sep 21, 2026
Getting skills right: Why demand and supply must always be on

Using AI while interviewing at Techwolf

At TechWolf, we see generative AI as part of the modern toolkit — and we expect candidates to treat it that way too. We love it when people use AI to take their thinking to the next level, rather than to replace it.You are welcome to use tools like ChatGPT, Claude, or others during our interview process, especially in take-home assignments or technical exercises. We encourage you to bring your full toolkit — and that includes AI — as long as it reflects your own thinking, decisions and creativity.We don’t see AI as replacing your skills. Instead, we’re interested in how you use it: to brainstorm ideas, speed up iteration, validate your thinking, or unlock new ways of approaching a challenge. Great candidates show judgment in when to rely on AI, how to adapt its output, and where to go beyond it.

What we’re looking for:

Our interviews are designed to understand how you think, solve problems, and express ideas. Using AI in a way that amplifies those things — not masks them — is encouraged.

What to avoid:

We ask that you don’t submit AI-generated work without review, or present answers that you can’t fully explain. We’re not testing the model — we’re getting to know you, your skills, and your potential. If there are cases where we don’t want you to use AI for something, we’ll tell you ahead of the interview being booked.In short: use AI as you would on the job — as a smart assistant, not a stand-in.

Example: Programming with AI

In a coding challenge, you’re welcome to use generative AI to support your workflow — just like you might in a real development environment. For instance, you might use AI to quickly generate boilerplate code, look up syntax, or get a first-pass solution that you then adapt and debug collaboratively. What we’re interested in is your ability to reason through trade-offs, communicate clearly, think about complexity and iterate effectively — not whether you memorized the syntax perfectly. If using AI helps you stay in flow and focus on higher-level problem-solving, we consider that a strength. There could be some challenges where we won’t allow you to use AI - in that case we’ll tell you in advance, and will tell you why.