Role
HR business partner
What do you not know about a team until the manager comes to you with a problem? Usually everything that could have been seen earlier - turnover building up, headcount that never closes, absences that form a pattern.
Intro call
Four questions we would start with
What do you not know about a team until the manager comes to you?
An HR business partner is meant to advise, and usually finds out last. The conversation starts when the problem is already a fact rather than a tendency.
Whose desk does a question about turnover in a given department end up on?
Usually yours - and it starts with assembling the number from several summaries instead of with a conversation about what it means.
What remains of your knowledge about the teams when you change roles?
The history of conversations, of what was agreed and of what has already been tried in which department - usually nothing. Your successor starts from zero with the same people.
Who notices first that something in a team is starting to go wrong?
If it is the manager, you will find out when they consider it a problem. If it is nobody, you will find out at the resignations.
We take over assembling the picture, you keep the conversation
Collecting data about teams, catching signals and preparing material for the conversation can be taken off the desk. The conversation itself, reading the situation and advising stay with the HR business partner.
- We measure teams, not people - with one caveat. - In a team of a few people, "aggregated" data is data about a particular person, and pretending otherwise would be dishonest. That is why below an agreed team size the picture simply does not appear. Turnover, headcount, the shape of absence in a team - yes. Ratings and rankings of individuals - no.
- A signal is material for a conversation, not a diagnosis. - Rising turnover in a department may mean a problem with the manager or a new company that opened next door. A person tells the difference.
- The history of what was agreed stays. - What has already been tried in that department and with what result - so that the next conversation does not start from the same idea.
Scope
What can be taken off an HR business partner
Eighteen example tasks. Each one has a human approval point. Below is a selection, and the scope we fit to your process.
The picture of a team before a conversation
- A summary of the department: headcount, turnover, tenure, the shape of the roles
- What has changed in the team since the last conversation
- The history of what was agreed with the manager and how far it was delivered
- Open vacancies in the department
- Absence at team level (interpretation: the HR business partner)
Signals from the organisation
- Rising turnover in a department against its own history (reading of the cause: the HR business partner)
- Teams with roles unfilled for a long time
- Departments with no development conversations in the recent period
- Engagement survey results at team level
- Signals from exit interviews grouped by theme
Preparing difficult conversations
- Material for a conversation about organisational change
- The development paths available in particular roles
- Data for a conversation about pay at team level
- The history of similar situations in other departments (conclusions: the HR business partner)
Headcount planning and recommendations
- A headcount plan against the department's business plans
- Pointing out critical roles with no cover prepared
- The competences available in the team against what is needed (not at individual level)
- Material for an organisational review for the board (conclusions: the HR business partner)
A day's work
Today
- Before a conversation with a manager you assemble the picture of the department from several summaries
- You learn about problems when the manager comes to you
- You remember what was agreed in previous conversations, or you do not
- You answer a question about turnover half a day later
- You collect exit interviews, but nobody puts them together
- When the HR business partner changes, the department starts the relationship from zero
With AI assistance
- The picture of the department is waiting, assembled, with the history since the last conversation
- Rising turnover arrives as a signal rather than as a surprise
- What was agreed and how far it was delivered are recorded
- You have the numbers about a team during the conversation, not after it
- The lessons from exit interviews add up to themes
- Your successor takes over the department with its history, not with a list of names
- Grounded in facts
the conversation with a manager starts from facts
the picture of the team is ready before the meeting
- Early signals
the response comes at the tendency, not at the resignations
changes in a team are monitored against its own history
- Time with managers
more conversations, less preparing for them
assembling the picture stops taking half a day
- Continuity of knowledge about teams
a change of HR business partner does not reset the relationship with the department
the history of what was agreed is recorded outside one person's head
We start with the picture of a team, not with signals.
- Step 1
We assemble the picture of one department
By hand, for one team. That single page shows how much work goes today into something an HR business partner should always have at hand.
- Step 2
A team page for every department
The picture assembled automatically. No signals - first the picture alone, so the HR business partner and the managers build trust in it.
- Step 3
Signals at team level
One, the least ambiguous - usually turnover. Every false alarm we fix or switch off.
- Step 4
The history of agreements and headcount planning
A register of conversations and succession plans. Last, because it needs the trust built in the earlier steps.
Common questions
Questions that come up at the first meeting
Does the HR business partner become less needed?
This role exists so that somebody talks to managers - and today half of its time goes on assembling summaries before those conversations. When the material arrives ready, there are more conversations and they are better prepared. That is exactly the direction the role was meant to go in from the start, and rarely reaches.
Does this fall under the AI Act?
Here care is needed. Systems supporting decisions about hiring, promotion and termination are a high-risk use. Working on data aggregated to team level does not belong to that category - and that is exactly why the line is drawn where it is.
Still have a question that is not here? Book a call
Next step
When did you last learn about a problem in a team before a resignation?
We will show you what an HR business partner's work looks like when the picture of the team assembles itself and the conversation with a manager starts from facts.