Business analysis is often seen as a technical skill. The business analyst builds process and data models, writes precise requirements, makes requirements traceable, estimates the effort involved, and so on. These are what we refer to as hard skills. But a business analyst has another set of responsibilities. The business analyst needs to be able to uncover what it is that stakeholders actually need, and not just what they say they need; to see the big picture when people are talking details. This requires quite different skills: knowing what questions to ask, dealing with vagueness, listening and providing feedback, knowing how to recognise and respond to the behaviour of individuals. This article discusses why successful business analysts combine hard and soft skills.
Wants and Needs
When a business stakeholder says “I want [something]”, it might be a real, quantifiable need that is relevant to the business. In many cases it is not. People ask for fragments of functionality that relate to their own part of the work, or perpetuate the way things are done now. Or they ask for a solution but don’t fully understand (or know) the need. Sometimes they neglect to mention something because they assume that everyone else knows the things that they themselves know.
Those badly stated wants – the gloop – must be understood, translated into the real needs, and transmitted to developers, solution architects, business architects and suppliers. These people need concrete – the precise and relevant requirements. The needs of a business come from many sources.
Some of them come from the conscious understanding of stakeholders that an improvement needs to be made to help them do their work. There might also be unconscious needs, “It’s never worked in the past so there’s no point in asking for it. We’ll just continue to work around it.”
Another set of needs are those that the stakeholders might not even dream of because they don’t know that a technology exists and has become available and affordable. For example, stakeholders at a rail company did not ask for train drivers to have on-demand scheduling; they believed that the technology was too expensive. However, when the train drivers’ needs were correctly understood, it became apparent that hand-held tablets and some OTS software would be an effective solution to communicating their schedules to the drivers.
Improving Hard Skills
There are established techniques – hard skills – for defining scope, modelling process, data, and dynamics, writing requirements and business rules. These techniques package the knowledge into an understandable form. Most of these techniques involve building a model, Naturally, you use a notation that you are comfortable with, and is known and understood by colleagues.
However, instead of taking the same hard skill every time, it pays to think differently, and to experiment with alternatives for stating a problem or its solution. Some suggested ways of becoming aware of other techniques are:
These ways of improving hard skills suggest you look outwards, and find new ideas in new places. Anything but doing things because that’s the way you have always done it.
Improving Soft Skills
People who are responsible for analytical thinking – Product Owners, Business Analysts, Systems Analysts, Systems Architects, and so on, usually have some training (the amount and depth varies enormously) and awareness of their hard skills. But the same is not true for their soft skills. We ask people what they need. However, the answers we get vary considerably depending on the feelings, attitude, assumptions, mood, personality, experience, and the confidence of the people we are asking. We can’t press a button and have everyone behave the way we want them to.
Instead of a button, we have soft skills that can make us aware of the differences between people, and help us figure out the most appropriate communication strategy for them.
Some ideas for improving your soft skills:
Borrowing from other Disciplines
You don’t have to start from scratch; you can learn a lot more about soft skills by exploring other professions.
Gillian Tett trained as a cultural anthropologist and spent years living with and studying the culture and customs of village communities in Tibet and the Soviet Union. When Tett changed her career to that of a financial journalist, she realised that she could apply a lot of the insights from studying the village communities to understanding modern organisational behaviour. In the Tibetan village, she observed how people became trapped in their own social group, their team or pocket of knowledge. That of course made communication with other groups more difficult. She recognised this parallel behaviour within organisations, and how it led to “silo thinking”, which in turn reduced ability to communicate. You can learn much more from Gillian Tett’s book The Silo Effect.
There are other disciplines worth exploring for ideas for improving soft skills. Family Therapy focuses on how family groups work (or don’t work) and many of the ideas are applicable to helping a group of stakeholders work together. Psychology and sociology are packed with ideas for improving your ability to communicate and to help others make connections. These subjects are usually aimed at other topics, but are equally applicable to business analysis. Borrowing from other disciplines also improves your hard skills. If you come across an architectural diagram, or a marketing survey with an innovative structure, then why not adapt the idea. Being on the lookout for new skills, often in unlikely places, will enhance your ability to turn vague, gloopy, open-ended stuff into concrete business needs.