What does a Business Analyst do?

Something that I’ve actually been asked while pitching for work is “What does a Business Analyst actually do?”. While I won the work in that instance, I was never happy with the answer that I gave at the time. I managed to babble something out about how a BA was the bridge between IT and the business and while this is true, it hardly demonstrates what I could do to impact the bottom line of a project.

Since then I’ve relayed this story many times, only to discover that it wasn’t just my erstwhile interviewer that was unsure of what a Business Analyst actually does. Very often it’s not until a BA has delivered on a piece of work that the business that they are working for appreciates exactly what it was that the BA did for them, even then I suspect they would find it difficult to define exactly what it was that the BA did.

In a cold economic climate when IT budgets are being cut, it’s important that BAs answer the question of what we actually do, after all, our livelihoods depend on it! While our documentation skills and communication style will prove invaluable during the development phase of a project, when fingers are being pointed and vendors are demanding more cash, this will be no good to us if we haven’t won the business in the first place.

We have a very positive story to tell about what we do, but what exactly is it that we do?

Other IT professions don’t suffer from this sort of ambiguity, a project manager, for instance, has several very clear definitions of what they do, my favourite being:

A project manager has overall responsibility for the planning and successful execution of a project.

That’s it, it’s to the point and everyone knows exactly what to expect from a Project Manager and how they are going to benefit a project. On the other hand, we have the definition as stated by the International Institute of Business Analysis (The IIBA®) in version 2 of it’s Business Analyst Body of Knowledge®:

Business Analysts must analyze and synthesize information provided by a large number of people who interact with the business, such as customers, staff, IT professionals, and executives. The Business Analyst is responsible for eliciting the actual needs of stakeholders, not simply their expressed desires. In many cases, the Business Analyst will also work to facilitate communication between organizational units. In particular, Business Analysts often play a central role in aligning the needs of business units with the capabilities delivered by information technology, and may serve as a “translator” between those groups.

It does describe what we do, but it’s not quite as easy to digest as the definition of a Project Manager and you can see why there may be confusion about what the role actually entails. I can hear the business now, ‘Where is the value add?’. It’s a fair question, how does analysing and synthesizing all this information actually help an organisation to meet its goals?

To try to understand more about what Business Analyst actually does, I want to look at each phase of a typical project and examine what is required of a Business Analyst during the life cycle of a typical project:


The initiation phase is the period during which the business is feeling some kind of pain and is looking to alleviate the stress that this pain is causing, usually by implementing some form of technology or process based solution.

It’s the role of the BA to clearly identify the problem that the business is experiencing and to map out what a possible solution would look like.

This map is then used to create a business case which shows why a problem is being tackled, how much it will cost to resolve the problem and what benefits the organisation can expect to see once the problem has been resolved.

It is the business case which a Business Analyst will constantly refer back to as the need for changes occur during the course of a project, constantly checking to ensure that a change is in-line with the expected business benefits and to ensure that the business case is still relevant and that something still needs to be changed within the organisation.


The analysis phase is the period during which the Business Analyst defines the requirements in detail, stating clearly and unambiguously what the business needs in order to resolve its problem.

During this phase the BA will also work with the development team and, in particular, an Architect, to create the design and define exactly what the solution should look like.

Taken together the design and the requirements will guide the rest of the project, with the testers looking to ensure that the requirements have been met and the developers trying to deliver against the design. It’s the responsibility of the BA to ensure that the design meets the requirements and that the testers are testing the requirements.

During this early phase of the project the BA will expend a lot of energy ensuring that any possible changes that can be identified are identified, while they are easily, and often more importantly, inexpensively corrected. Once the initial requirements are documented they need to be tested to destruction by the BA to ensure that they will actually deliver a solution to the problems that the business are facing.


The development phase is possibly the most challenging phase for a BA. It’s quite normal after the pressure of the analysis phase to sit back a little, safe in the knowledge that both quality requirements and design have been delivered. However, it’s during this phase that a BA needs to step up their meetings with the development team, attending daily meetings and generally being the eyes and ears of the business, constantly looking for deviations in course that would otherwise go undetected.


The testing phase sees the Business Analyst back on firmer footing. There is a process to follow as the testing team go through the process of testing and identifying bugs and the BA can work with the business to set defect fix priorities.

Disputes between the business and development concerning what is and what is not an off spec defect will often be resolved by the BA using documentation created in earlier phases. The mere existence of this documentation is often enough for one side of the other to admit a mistake and for the issue to be resolved amicably.


The implementation phase is not the end for the Business Analyst. It’s the last chance for things to go awry and for goals to be missed.

It’s during this phase that a BA should be conscious of how users are using the system. Are they actually seeing the benefits envisaged in the business case? Do the training materials support the business case?

Looking at each of these phases in this way, a common theme of discovery, validation and verification appears throughout a project life cycle. Given the opportunity to answer the question again, I would define the role of a Business Analyst using the following statement which clearly shows what a Business Analyst adds to a project, a business or an organisation:

A Business Analyst is responsible for knowing what the goal of a project is, how to achieve it, managing any changes to the goal and ensuring that all deliverables are aligned with the goal.

In essence, a Business Analyst is a navigator, responsible for reaching the end destination, in our case that destination is the successful resolution of a business problem. The BA always knows what the end destination is, how to get there and is capable of handling course adjustments as they arise.

In the future, when pitching for work, I’ll be better prepared to answer the question and will have a great story to tell.

I hope you found this article useful. If you have a definition of what a BA does, then please feel free to let me know by leaving a comment below.

, , , , , , , , , , , , , , , , , , ,

104 Responses to “What does a Business Analyst do?”

  1. Daisy Says:

    This article is very good, and it tells us the detailing work process of a BA. But I also agree that there is a bridge between IT and business for them, especially on the more and more complex business problems, and a script called esProc can help narrow such bridge, which could let the BA do some analyzing work by themselves with simple script instead of complicated modeling.


  2. Mukesh Says:

    Its really a good and informative article.


  3. Shashank Says:

    simple and subtle briefing….thanks


  4. Karthik Says:

    Great work on a succinct explanation of the role of a BA.
    This helped me on my application to apply for a Step Up BA role in the last minute!
    Well done.


  5. jane Says:

    very great definition thanks j


  6. Basheer Says:

    The brief actually explains the skill of an Analyst; Clear, concise and unambiguous. The role of Analyst in different phases of the project is really useful.

    Many thanks.


  7. Hari Raghu Says:

    Very clear and concise. A very modern definition


  8. Navjyotsing Rajput Says:

    That is fabulous… it is helping a lot


  9. Shaun G. Says:

    Hi, I enjoyed the read and description as an aspiring BA who is currently enrolled in college. Just throwing this out there, but would it be possible to do a brief interview with the writer for my English class? The goal would be to obtain further personal knowledge on the career which interest us. Please email me if this would be possible.

    Thank you.


  10. Priyanka Says:

    Very nice article.


  11. Samuel james Says:

    This defination is concise and clear


  12. Vivian Wied Says:

    Great description – Especially like the breakout of responsibilities by phases of the development cycle. Thanks for sharing.


  13. GN Says:

    An interesting article, but through observations and discussions with IT personnel regarding IT-BA-Client discussions, some BA personnel often have no input, take no notes and are unable to integrate with IT personnel, leaving the latter sometimes wondering their actual purposes, other than implementing new complicated and troublesome systems over existing ones rather than simplifying or streamlining workflow. Are those BA lost in the ambiguity of their roles or are there ways to improve and strengthen their roles to reduce confusion?


  14. Faraz Says:

    Very informative and good article.

    Thank you.


  15. Daisy Says:

    Good article, the discription is quite clear. But I have a few questions.does BA only means the analyst of BI project? Can a business professional who uaually analyze the sales and marketing data also call as a BA?


    • Michael Gill Says:

      Daisy, I would characterize that role as a Data Analyst.


    • Daniela Says:

      I am having an interview for a position as a Customer Business Analyst. Would that be similar to what you have explained, but focusing on being a liaison in between the customer and company (factory/sales)?
      I am bit confused since I am a student applying for this Internship and on the web there is very little information.
      I would appreciate your response.


  16. ankush Says:

    A very well written article with clear definition of what a BA does. Helped me a lot to understand the basic JD of a BA. Thnx for sharing.


  17. krishnaraj Says:

    superb explanation…every BA should read ..this gives the feel as if i worked as a BA in a Concern.


  18. Michael Gill Says:

    A good article, thanks. The IIBA description is inadequate, and you have put some meat around it. But when you’re in the elevator or sitting across the table from a senior manager and you have 20 seconds, we need a description of only 2 sentences.
    That will take further work.
    Nevertheless, I would suggest considering that an experienced BA must also bring business knowledge (industry and company) to the table, being a valuable advisor to the business.
    I like to think of the process of making a building, the roles of Foreman and architect. A PM is the foreman of the project, coordinating the different skilled workers, arguing about budget and schedule, and the BA is the architect that has consulted with the buyer, provided advise as they designed a solution. He insures that the result is what was designed and in the end (User acceptance testing) ensures that the client is satisfied.


  19. Jaydaher Says:

    Well done. I believe a business analyst main role is to know how to deal with data in hand, provided by the IT depatment. To deal with statistics reports that help the business perform better in the future. Im a programmer and an MBA student, and i have an interview for a BA position next week, wish me luck.


  20. Melvin Says:

    Well explained and relates to my work quite well.


  21. Tin Says:

    Thank you very much for publishing this article. This will really help me a lot for my job interview later. 🙂


  22. Ramu Says:

    Good Information for those who wants to take BA as a carrier.


  23. Michael Says:

    Good article. I would like to see an article explaining the distinction between a Business Analyst and a Systems Analyst. I believe there is a distinction and it is my experience that very many people who bill themselves as Business Analysts are in fact Systems Analysts.


  24. Ben Says:

    I liked the article, this website also has a lot of relevant information about business analyst training.


  25. Ben Says:

    I liked the content, the site above is good for BA Training.


  26. Richard Swarbrick CAPM, PMP Says:

    Enjoyed the article. To the point and delivers great insight.


  27. Scott Rowe Says:

    Couldn’t we just parrot the definition of the PM and say “The BA has the overall responsibility for gathering and communicating the requirements of a project.” If a company doesn’t think that is every bit as important, it deserves to fail, and you don’t want to work for them. Problem solved.


  28. Kirk Says:

    Very informative article. Thank you so much.


  29. Farid Abboud Says:

    Great article. Many thanks for breaking it down to all the SDLC stages.


  30. AstroPackaging Says:

    Great Post! To run a business efficiently it is necessary to make right strategy and analysis before start up the business. Hard work and right decision make people and their business.


  31. Angelo Says:

    Well done sir! You might have just helped many people get through some tough interview questions, as basic as it may seem


  32. Alan Jones Says:

    Shapes the project and acts as a go between from technical to client. Acts as product owner and should ultimately have the full holistic product knowledge.


  33. Sofia Says:

    Useful information which is really worth reading. Perfect analysis is required before starting any business.


  34. F.Parekh Says:

    Excellent explanation of the BA role and responsibilities.

    F. Parekh


  35. Andrew Hinge Says:

    A very good definition although it can encompass other areas.

    My view is :

    1:to analyse a situation.
    2:to ellicit a desired result.
    3:look for solutions to that ‘Desired Result’.
    4:build and manage that solution.
    Of course this is only the ‘Headlines’ of a BA’s role, there are many sub-facets underlying this/my description of a BA’s role.

    Hope this compliments your description.


  36. Sean Says:

    Great article

    Lack of clarity in specs, is my one bug bear.

    I would like examples included in the specs. Not many analysts do this, but it makes things clear- and helps reduce ambiguity.



  37. Ed Goldstraw Says:

    I didn’t like all arse-licking comments – they added nothing.

    The problem for the BA is that historically the issues that a BA tackles were resolved twenty years ago by the Project Manager. I had many roles where I was called the PM but spent most of my time doing activities that we would now associate with a BA.

    I also don’t like the term System Architect. Is this a technical role? Lie a DBA before a system is implemented?) or somebody who is going to take a BAs work and arrive at a solution for the software design?

    MY view is simple:

    A BA has to have to the knowledge and ability to analyse a position, understand the problems AND arrive a solution. That is they are the designer.

    The PM allocates resources (including keeping the BAs under control).

    If you take the view that a BA is merely an analyst then it means that all that the BA has learnt has to be re-learnt by the “Solution Architect”. In a large project the senior BA may have such a title but they are just that – a Senior BA.

    One of our clients took a very strong view on the whole subject – the PM was subordinate to the BA. I am inclined to agree – if you are constructing a building who should be in charge – the designer or the builder?


  38. Azim Says:

    thanks for the great article. You have beautifully communicated with simplicity the gist of a BA role for the good of all… I have only one thing to add to your definition of BA which is communication!!!


  39. business analysis training Says:

    Business analysts play a major role in moving an organization towards productivity and profitability while attaining the financial goals and objectives as well. He needs to understanding the business – to define the problem in statistical terms and, after the analysis, to summarize and suggest solutions which the business can implement.


  40. Malathi Says:

    Very Informative article.


  41. Linda Says:

    Thank you so much for this information. I’m going to inquire about a posting in my company and this data is awesome.


  42. ksi johnson Says:

    Many people will surely appreciate and i got more learn some points from your article. thank you so much.


  43. William14 Says:

    Hi, do you allow guest posting on businessanalyst.com ? 🙂 Let me know on my e-mail



  1. Top Business Analyst Websites and Blogs to Follow | Nihad Bassis - September 4, 2014

    […] 4. Business Analyst.com – You don’t see frequent posts on this one, but when you do, the posts are thought-provoking. I particularly like the post on what a business analyst does. I’ve seen many articles written on this topic, but this one clearly stands out. […]

  2. thecribb.com » Business Analyst resource guide - March 22, 2015

    […] Business Analyst.com- You don’t see frequent posts on this one, but when you do, the posts are thought-provoking. I particularly like the post on what a business analyst does. I’ve seen many articles written on this topic, but this one clearly stands out. […]

  3. Compendium of BA Resources | MPMO BA Blog - December 3, 2015

    […] “What do Business Analysts Do” is an excellent article which states what a BA does, and it’s even broken down by project phase. If you look far down in the article, I like the short description of what a BA does that the author offers: “A Business Analyst is responsible for knowing what the goal of a project is, how to achieve it, managing any changes to the goal and ensuring that all deliverables are aligned with the goal.” […]

  4. What Does A Business Analyst Do, Exactly? | BaSimplified - December 4, 2015

    […] think that Business Analyst.com have got the essence of an answer in their article titled ‘What Does A Business Analyst Actually Do? They have made a good attempt at breaking down where a Business Analyst can add value at different […]

Leave a Reply