Human-centred design starts with better questions

Most organisations say they care about their people.

Fewer can prove they understand them.

That is the gap human-centred design is built to close. Not with another platform. Not with another annual survey. Not with another leadership assumption dressed up as strategy.

With better questions.

Because if you are designing anything for employees — a learning experience, an onboarding journey, an AI adoption campaign, a benefits proposition, a culture intervention — you are designing for people whose lives, pressures, motivations and frustrations you may not fully understand.

And that matters.

At Freeformers, we talk a lot about moving beyond transactional HR. This is where that shift gets practical. Relational organisations do not design from the boardroom outwards. They design from the human reality inwards.

They ask.
They listen.
They learn.
Then they build.

That sounds obvious. It is not common enough.

You are not your user

If there is one principle to take from human-centred design, it is this:

You are not your user.

You may use the product. You may work in the organisation. You may care deeply about the experience you are creating. But that does not mean you understand how someone else experiences it.

In fact, your closeness can be the problem.

You care whether people use the learning platform. They care whether it helps them do their job.
You care whether the campaign lands. They care whether it is worth their attention.
You care whether the initiative succeeds. They care whether it makes their working life better.

That difference changes everything.

Too much employee experience work starts from what the business needs to deliver. Compliance. Policy. Mandatory training. Process. Reporting. Proof that something has been done.

Those things may matter. But they are only half the system.

The sweet spot sits between what the business needs and what people need. That is where the best work happens. The work that improves performance because it improves experience. The work that earns attention because it respects reality.

Less “we need employees to do this”.
More “what would make this useful enough for people to choose it?”

Surveys tell you what. Interviews help you understand why

Surveys have a place.

They can gather data quickly. They can show broad patterns. They can help you understand what is happening at scale.

But they often struggle with the most important question: why?

Why are people not using the new tool?
Why does onboarding feel overwhelming?
Why do people ignore internal comms?
Why does a learning experience fail to change behaviour?
Why do people say they are engaged but still leave?

A survey can tell you that something is happening. A conversation can help you understand what sits underneath it.

That distinction matters because most organisations already have more data than they know what to do with. The problem is not always a lack of information. It is a lack of meaning.

Quantitative data can show patterns. Qualitative insight gives those patterns context, texture and consequence.

Without that, action often falls into the “so what?” gap.

The dashboard says belonging is low.
The engagement score has dipped.
The LMS completion rate is poor.
The pulse survey says managers need support.

So what?

What should change? What should be designed differently? What is actually getting in the way?

That is where interviews earn their place.

Discovery is not a luxury. It is how you avoid expensive guesswork

Human-centred design has often been seen as slow, expensive and out of reach for employee experience teams.

That perception is understandable. Historically, deep discovery work could take months and cost tens of thousands. It was more common in customer experience, product development and big-budget transformation programmes than in HR or L&D.

But that is changing.

The methods are becoming more accessible. The tools are faster. AI can help with parts of the process. And, most importantly, organisations can start smaller.

You do not need the perfect research strategy before you speak to people.

You need a useful question, a sensible sample and the willingness to listen.

That might mean interviewing a dozen people before designing a new learning campaign. It might mean building three short user interviews into a monthly rhythm. It might mean asking new starters what they had to figure out for themselves in their first 90 days.

The point is to begin.

Not perfectly. Responsibly.

Because every initiative designed without user insight is still based on research.

It is just research made of assumptions.

The gold is in motivations and frustrations

Good interviews do not start by asking people what solution they want.

People are not always good at designing the answer for you. They are much better at describing their reality.

What do they love about their work?
What frustrates them?
What slows them down?
What do they ignore?
What do they trust?
What have they had to figure out the hard way?
Where do they feel confident?
Where do they feel exposed?

This is where the useful insight lives.

Motivation tells you what to connect to. Frustration tells you what to remove.

If someone is driven by problem solving, your change campaign needs to show how the change helps them solve better problems. If someone is motivated by recognition, your design needs to account for visibility and progression. If someone is overwhelmed by email, sending another beautifully crafted email may not be the answer.

That is the power of qualitative discovery.

It helps you stop designing for an imaginary employee and start designing for the actual conditions people are working in.

Focus groups are not always the shortcut people think they are

Focus groups can be useful, especially when testing something tangible.

But they are not always the best tool for discovery.

They take time to organise. They can be harder to facilitate well. And the biggest risk is groupthink.

In a group setting, confident voices can dominate. Quieter voices can disappear. People may soften their views, follow the mood of the room or avoid being the dissenting voice.

That does not make focus groups useless.

It just means they are not neutral.

If you want honest, personal, contextual insight, one-to-one interviews often give you a cleaner route in. They create more space for nuance. They let you follow the thread. They make it easier to notice what someone says, what they hesitate over, and what they reveal when they feel safe enough to keep talking.

Better insight often comes from depth, not volume.

How many interviews is enough?

There is no magic number.

It depends on the question you are exploring, the diversity of your audience and the variables that matter.

If you are designing for one relatively consistent group, you may need fewer interviews. If you are designing for people across different roles, locations, seniority levels or working environments, you need to hear from enough people in each meaningful group to spot patterns.

As a practical starting point, aim for enough interviews to hear repeated themes without simply hearing the same thing again and again.

You are not trying to interview everyone.

You are trying to understand enough of the real human context to make better design decisions.

That distinction is important. Qualitative research is not about mass participation. It is about meaningful representation.

Be careful who you ask

The easiest people to interview are rarely the only people you need to hear from.

If you only speak to the enthusiastic users, the people nearest to you, the people who always volunteer, or the people already bought into the work, you will get a partial picture.

Useful, perhaps. Complete, no.

The richest insight often comes from the frustrated users. The sceptics. The people who dropped out. The people who never open the emails. The people who quietly work around the system because the official process does not help them.

That does not mean chasing perfect academic rigour.

It means being honest about bias and making better choices where you can.

Sometimes, starting with whoever will talk to you is better than doing nothing. But do not confuse convenience with truth.

Better questions create better answers

Interview design matters.

A poor question can flatten insight before it has a chance to appear.

Avoid leading questions.
Avoid asking two things at once.
Avoid asking people to predict hypothetical behaviour.
Avoid loading the question with so much context that people simply tell you what they think you want to hear.

Instead, ask people to describe real moments.

Not “what would make you feel like you belong?”
Try “tell me about a time you felt like you belonged at work.”

Not “would you use this platform if we made it easier?”
Try “talk me through the last time you needed help with this task.”

Not “do you think our onboarding is effective?”
Try “what did you have to figure out for yourself after onboarding?”

The best questions open a door. Then the interviewer has to be human enough, curious enough and disciplined enough to follow what comes through it.

That means listening properly. Not just waiting for your next question.

Interviews are conversations, not scripts

A good interview guide is not a checklist to be obeyed at all costs.

It is a map.

The conversation may move. It should. People will answer three questions at once. They will say something unexpected. They will reveal a frustration you had not thought to ask about. They will casually mention the thing that turns out to matter most.

Follow that.

Mark what has already been answered. Change the order. Ask for examples. Dig into vague words. Notice emotional energy. Stay neutral, but stay interested.

This is one of the reasons interviews are so powerful. They allow the researcher to respond to meaning as it appears.

A survey cannot do that.

A form cannot say, “Tell me more about that.”

A dashboard cannot notice when someone laughs before describing something painful.

Human-centred design needs that kind of attention.

Build insight into the rhythm of work

The real opportunity is not just running better discovery projects.

It is making insight part of how the people function works.

Imagine an HR or L&D team where user interviews happen every month. Not as a huge transformation exercise. Not as an emergency response when engagement drops. As a normal part of designing work well.

Over time, those conversations become an insight bank.

A living source of employee reality.

What are people struggling with in their first 90 days?
What motivates high performers?
What makes managers feel unsupported?
What do people ignore?
What do people trust?
Where are systems helping, and where are they quietly creating friction?

That kind of insight can serve the whole people function, not just one project team.

Because employees do not experience HR in neat functional silos. They experience work as a whole.

So our insight should be connected too.

Small changes can create meaningful impact

One of the most encouraging truths about human-centred design is that the answer is not always expensive.

Sometimes the insight points to a major redesign.

Sometimes it points to a tiny change that removes a daily irritation.

A meeting setting.
A clearer message.
A trusted sender.
A better handover.
A simple checklist.
A different timing.
A more human explanation of why something matters.

Not every employee experience problem needs a platform.

Not every culture challenge needs a programme.

Sometimes people have already told you what would help. You just have to ask properly, listen carefully and act with enough humility to change the thing.

Stop assuming. Start discovering.

Human-centred design is not about making HR softer.

It is about making it sharper.

Sharper because it is grounded in real evidence.
Sharper because it connects human need to business value.
Sharper because it reduces wasted effort.
Sharper because it designs for behaviour, not intention.

This is how people teams move from reactive delivery to relational impact.

Not by guessing harder.

By getting closer to the truth.

The organisations that will build better employee experiences are not the ones with the biggest dashboards or the loudest claims about being people-first.

They are the ones brave enough to ask better questions.

And careful enough to listen to the answers.