Is it a Business Analyst’s Role to take meeting minutes? | Yes or No
Should a Business Analyst be responsible to take minutes in project meetings?
There is a lot of debate about whether a Business Analyst should be taking minutes as part of their Business Analyst role on a project or whether it is simply not in their job description as a professional business analyst. This article outlines some of the different perspectives on this sticky topic and also concludes with how this particular task should be treated by Business Analysts.
Let’s start this article by being very clear that taking minutes is not part of the Business Analysts role in any formal way. However, there are many different considerations and arguments to be had around this topic and we outline some of the mainstream arguments here.
Argument #1: Taking minutes is part of the Business Analysis Task.
Historically the Business Analyst’s role was not very clearly defined and was often viewed as a generic project resource role where the individual was seen to document the requirements and pretty much get involved in any other project related tasks. This also meant that the Business Analyst was often the one that was responsible to take minutes in meetings as part of their every day role on the project. Project Managers have traditionally not really been made aware of the specific job description of the role of the Business Analyst and have over the years simply made assumptions about this role in the context of being a general project resource they could assign any project task to. This is not any fault of the Project Manager because the profession of Business Analysis is reasonably new within the industry.
This does however explain why a lot of Project Managers today are still operating within the framework of thinking that it is in fact part of the Business Analysts job to take minutes in project meetings. Needless to say, this misunderstanding and incorrect delegation of this task to the Business Analyst is causing a lot of Business Analysts to feel undermined in their professional roles as Business Analysts.
Argument #2: The Business Analyst ends up doing the minutes informally every time because they are available and do lots of documentation as part of their role anyway (besides, who else will do it if not them?).
There is often the situation that the project team ends up assigning the role of taking minutes to the Business Analyst in an indirect and less formal way. It just happens that the Business Analyst is invited to a lot of the Project Management meetings and asked to take actions or minutes while the project manager is running the session. In some cases it makes sense for the Business Analyst to be part of the meeting from a Business Analysis perspective and therefore helping out with the minutes is perfectly okay, but then it happens often that the Business Analyst didn’t really have to be in the meeting and is only invited in order for them to take the minutes (because there is no other “logical” person in the team to do it). This is clearly inappropriate and a misjudgment of how to apply the Business Analyst within the project.
This type of situation can be caused by a variety of things and in many cases it is a combination of the Business Analyst being good nature’d and happy to help out (at least initially), the Project Manager not really being aware that it is not part of the Business Analysts role (sometimes the Business Analyst not knowing it is not part of their role) and a habit that is then created during the early stages of the project.
This scenario makes it harder to manage the Project Manager’s expectations without damaging the relationship between the Business Analyst and the Project Manager when the Business Analyst starts to feel that they are being asked to do something that it really not part of their role. Catch this misunderstanding around responsibilities as early as possible to avoid creating an uncomfortable relationship in future.
Argument #3: We all know it is not the Business Analysts role to take minutes, but they (have to) do it anyway.
There are some projects that acknowledge that it is not the Business Analysts role to take the minutes but because the projects are often under resourced it ends up happening that the Business Analyst is asked to step in to help out with taking the minutes regardless. Projects where this task is managed in a way where the Business Analyst is acknowledged as doing the project a favour, it is much easier for the Business Analyst to manage this additional responsibility and be accepting of it. However, this scenario can unfortunately easily become a situation where the Business Analyst feels taken for granted and their professional role undermined.
Firstly, it is important to keep in mind that the Business Analyst will in most cases be more than willing to help to take the minutes in a meeting providing that they are approached in a way which addresses the following:
- Acknowledgement that the task of minute taking is not part of their role as a Business Analyst
- They are not singled out to always have to be the one that has to take the minutes for the project, but that this task is shared among team members if there is no project analyst assigned to the project
What a Business Analyst should do to manage expectations with minute taking
Many Business Analysts will just take on this task and not say anything. This is not a great idea because it sets the wrong expectation around the whole profession of Business Analysis. If you are simply accepting the role of minute taker in every scenario of your project, you will be creating the expectation among your peers that minute taking is in fact a formal part of the Business Analyst’s role. It is like asking an Accountant to sort out a legal problem. You know the Accountant will say to you that you need to contact a legal representative to help you to ensure you get the best results. They may offer to help you with contact details or general personal opinions (in order to be helpful) but they will not take on the task without saying anything to correct the misaligned task request. So as a Business Analyst you should say that you are willing to help out this one time (for example), but perhaps the project should appoint a project analyst to assist with the task of minute taking in the future. Or suggest the project team shares the responsibility around the team to ensure that you don’t create this false expectation that minute taking is part of a Business Analysts role.
Being a team player is different
Another reason why a Business Analyst should find a way to point out that minute taking is not a formal part of their role is to prevent setting an expectation that you as the Business Analyst don’t really want to set in the first place. Of course it is part of being a great team player to help out with tasks that is not necessarily always part of your job description but there is a fine balance to be had between setting the wrong expectations about your role (and all other Business Analysts roles as a result) as a Business Analyst and being a good team player. It is in fact your responsibility to manage this common issue pro-actively to ensure that all stakeholders learn what the Business Analyst role includes and doesn’t include. Your project team will respect your professionalism and pride in your profession and there are plenty of other ways to demonstrate that you are a great team player.
Finally, to conclude a controversial topic, it is important to emphasize the fact that Business Analysis as a profession is in a stage of development and formal formulation in the industry (and making fantastic progress at that) and to help this profession be seen as a defined and specific profession all Business Analysts must respect the boundaries of their roles. Learn to gently educate your peers and project managers about what it means to be a Business Analyst whilst remaining a great team member to have on a project team.