From people analytics to workforce intelligence: Why banking needs a "data lake" for skills

Julius Schelstraete
February 24, 2026
•
3 min read
Podcast cover: Stop benchmarking with peers, with Patrick Coolen and Frank Van Den Brink of ABN AMRO
Contents

In the world of European banking, the "social architecture" - the culture, the negotiations, and the headcount - has long been the primary focus of the human resources function. But as generative AI begins to reshape knowledge work, a new requirement is emerging. To survive this shift, banks must build a "technical architecture" for their people.

On a recent episode of the TechWolf podcast, Julius Schelstraete sat down with two architects of this movement: Frank van den Brink and Patrick Coolen. Having worked together at ABN AMRO, Frank as CHRO and Patrick as Head of People Analytics, they now advise global organizations through Kennedy Fitch.

Their message for the financial sector is clear: if you do not know your skills, you do not know your capacity to innovate. In a regulated industry, that isn't just an HR problem. It is a risk management failure.

The end of the "look at the neighbor" strategy

Historically, HR has been a function of benchmarks. Leaders often ask what their peers are doing before making a move. Frank van den Brink argues that this "social influence" muscle is precisely what holds banks back from true strategic workforce management.

"Buy what you need and deliver what is internally relevant," Frank says. "That is a far more useful muscle than looking for a benchmark."

The transition from people analytics (descriptive) to workforce intelligence (prescriptive) requires moving away from size, headcount, or FTE. In the AI era, two capable people providing strategic context are more valuable than a department of 100 that cannot.

Skills as a risk management asset

In banking, every major decision is filtered through the lens of risk and evidence. Yet, when it comes to the workforce, many organizations still rely on proxies like job titles or degrees rather than on what people can actually do.

Patrick Coolen defines strategic workforce management as a systematic, stepwise approach that starts with business strategy to understand what an organization needs to be good at.

"This is the product that helps you answer the question: is your workforce still fit for the future?" Patrick asks.

For a bank, "fit for the future" means understanding the gap between workforce supply and strategic demand. While HR has become better at taking a "photo" of today’s supply through analytics, the real struggle is making the demand visible. This requires a "data lake" of skills and tasks that allows leaders to see where human judgment is the edge and where AI can take the lead.

Beyond the "photo" of supply: Designing strategic demand

One of the greatest tensions in People Analytics is the imbalance between what we know about our people and what we know about our work. Patrick Coolen notes that HR is often excellent at taking a "photo" of the supply side, the current skills and demographics of the people already in the building.

The missing link is the demand side. Strategic workforce management fails when it stops at the photo. To be effective, the data must show what the organization needs to be good at over the next three to five years.

"You start with the business strategy," Patrick explains. "You look at what the organization needs to be good at, and then you see the gap."

For banking, this means identifying the specific capabilities required to navigate a turbulent AI era. It is not about filling seats. It is about identifying the delta between the skills you have today and the capabilities required by the strategy of tomorrow. Without this focus on demand, workforce planning remains a reactive exercise in headcount management rather than a proactive driver of innovation.

The CHRO as an anticipatory architect

The role of the CHRO is shifting from a jack of all trades to a strategic operator who manages the "human quotient" of the business.

The most successful leaders will be those who:

  1. Deduct complexity: Avoid over-engineered processes that do not solve business problems.
  2. Build a cockpit for decisions: Ensure the board has the best possible data to balance investment in technology with the development of people.
  3. Prioritize evidence over intuition: Use data to manage the "shop" of HR, being critical about whether recruitment or diversity practices are actually effective.

As Frank van den Brink puts it, the proof of value is created in the heat of the moment, not two years after a roadmap is drawn. For banking leaders, that moment is now.

Explore next:

Blog

Relevant sources

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

View all
View all
Cedric Vandamme of TechWolf presenting the data layer for the AI era of work on stage at Gartner HR Symposium/Xpo™ London 2026Gartner logo on the big screen at Gartner HR Symposium/Xpo™ 2026
Events
AI
Blogpost

Gartner HR Symposium/Xpo™ 2026: our takeaways from London and Orlando

Two Gartner HR Symposium/Xpo™ events, one on each side of the Atlantic, and the same message in both: time saved by AI only matters once the work itself is redesigned.
Giulia La Volpe, Senior Content Marketeer at TechWolf
Giulia La Volpe
Nov 1, 2026
Gartner HR Symposium/Xpo™ 2026: our takeaways from London and Orlando
A busy TechWolf booth 402 at UNLEASH World Paris 2026The UNLEASH swirl sculpture on the expo floor at UNLEASH World Paris 2026
Events
AI
Blogpost

HR's time to lead, and the data to do it: our UNLEASH Paris 2026 takeaways

Two days, 23 Wolves and one big theme: AI is ready to change how work gets done, as long as it runs on trusted data. Here's what we learned at UNLEASH World Paris 2026.
Giulia La Volpe, Senior Content Marketeer at TechWolf
Giulia La Volpe
Oct 26, 2026
HR's time to lead, and the data to do it: our UNLEASH Paris 2026 takeaways
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.