1. The User Isn't a Box on a Process Map 

For years, I'd been mapping customer journeys and business processes, building a strong understanding of customer needs. What I've been reminded of is the value of complementing that understanding with direct insight from users themselves. 

Working alongside User Research has deepened the way I think about user needs. Observing research sessions, listening to feedback and hearing people's real experiences brings an additional layer of context and understanding. 

It's very easy to make assumptions. We all do it. The reality is that users don't always behave in the way we expect them to. When user research is brought into the mix, rather than simply documenting what a user does, the conversation shifts from focusing on processes and systems to understanding what people are trying to achieve and where they encounter challenges. That's often where the most valuable insights emerge. 

In one piece of work, we initially focused on streamlining a process step. User research later revealed that the real issue wasn't the process itself but users being unsure what information they needed before starting. Once we understood that, the solution changed completely. 

2. Understanding the "Why" Matters More Than Capturing the "What" 

One of the biggest lessons I've taken from this experience is the importance of not stopping at the requirement. Stakeholders are generally very good at telling you what they want. The real skill is understanding why they want it. This experience has reinforced the value of exploring outcomes before discussing solutions. 

More than once, I've seen teams focus on improving a process step, only to discover the real issue wasn't the process itself but confusion, uncertainty or a lack of confidence among the people using it. Once we understood that, the conversation shifted from "how do we improve this process?" to "how do we make this easier for people to navigate?" 

Focusing on the underlying need often opens up new possibilities. Sometimes the best outcome isn't delivering the requested solution at all. It's solving the actual problem. 

3. Evidence Is More Powerful Than Opinion 

Something that has been consistently reinforced for me is the importance of challenging assumptions, even in experienced teams. 

Throughout my career, I've taken part in many workshops exploring what users might want or how they were likely to behave. That's why I've come to value working closely with User Research and UCD colleagues. They bring real user experiences into the conversation and help move discussions beyond "I think" and "we believe". 

As Business Analysts, we're often balancing different perspectives from across an organisation. Evidence provides a common reference point. It helps shift discussions away from assumptions and towards shared understanding. 

One question I find myself asking more often now is: 

"What evidence do we have?" 

Not because I doubt people's expertise, but because the best decisions are usually made when experience is combined with insight from the people using the service. 

As BAs, we spend a lot of time helping teams make decisions. The stronger the evidence, the stronger those decisions tend to be. 

4. If People Can't See the Complexity, They Can't Fix It 

I've always been a fan of visualisation. I've never found a better way of creating shared understanding than getting people around a process map, journey map or service blueprint. Complexity becomes much easier to tackle when people can see it. 

One thing I've consistently noticed in large transformation programmes is that teams often hold different versions of the truth. Operations see one thing, Policy sees another and Digital teams see something else. Nobody is wrong. They're simply looking at the same challenge from different perspectives. This is where visual techniques are invaluable. 

Some of my go-to BA tools still include: 

• Current-state process mapping 

• Future-state process mapping 

• Context diagrams 

• Service blueprints 

• Stakeholder maps 

• Decision logs 

None of these techniques are particularly new or revolutionary, but they remain some of the most effective tools in a BA's toolkit. When everyone can see the same picture, conversations become more productive, decisions become clearer and alignment comes much more easily. 

5. The Real Value of a BA Is Creating Alignment 

If you'd asked me 15 years ago what made a good BA, I would have emphasised requirements. Today, I'd place equal emphasis on alignment. 

The further I've progressed in my career, the more I've realised that a BA's value often comes from connecting people and perspectives. Policy specialists, operational colleagues, developers, architects, designers, delivery managers and senior leaders all bring different insights. None of them have the complete picture on their own. 

The BA sits at the centre of that complexity, translating, facilitating and helping people build a shared understanding. 

One technique I use regularly is documenting decisions and assumptions, not just requirements. It provides traceability, reduces misunderstandings and helps teams understand how and why choices were made. 

People don't have to agree on everything, but they do need a shared understanding of the problem they're trying to solve. In my experience, that's often where the biggest breakthroughs happen.