Congratulations! You have been asked to act as the lead Business Analyst (LBA) on an important project. It is more than likely someone recognizes the good work that you have done in the past and their hope is that your past success can be replicated with multiple Business Analysts on this new initiative. Like any new experience, you may have some anxiety or nervousness regarding this new role. It is important to you that what happens turns out to be a future success story and not an experience that stays in the closet.
Here are some tips for success as a new lead Business Analyst from someone who has gone through the experience. I have also had the fortune (or misfortune) to observe many colleagues who have succeeded in this role and some who have crashed and burned.
1) Understand the Role
Spend time upfront figuring out the role of the lead Business Analyst in the context of the work effort that you are about to join.
- Do not make assumptions on expectations or the outcome expected. While the function is becoming more common, there is no universally accepted definition for the lead Business Analyst role. Some experts view the lead Business Analyst as a formal role inheriting many project management-type responsibilities while others view the lead Business Analyst as an informal way of steering people in a common direction. There is no consensus.
- Work with the manager who assigned you to this role (Project Manager or Business Analyst Manager) to understand their expectations, their interpretation of the role. Ask the question “What is your definition of success for this role?”
- Provide input about your views on how you can provide value as the lead.
- Capture the outcome of the meeting of the minds to provide a reference point that you can subsequently use to ensure you are on track.
What I have observed in practice is that many people accept the lead BA role on a project and skip this step because they feel they are a natural leader, that they inherently understand what is needed, or that the expectations (in their mind) are obvious. They subsequently bump into reality when results do not happen the way they or their manager expected. Combat this possibility by understanding the role upfront.
2) Set Team Expectations Upfront
Spend upfront time with assigned Business Analysis resources on the team to reach a common understanding of roles and responsibilities.
- Recognize that Business Analysts have an independent streak and often are used to steering their own ship.
- Avoid describing a responsibility with the words “participate” or “contribute”; such ambiguity invariably leads to future conversations.
- Recognize that team members have different experiences and viewpoints on what tasks and deliverables are necessary to be successful. This is a dialogue, not a monolog.
- Capture the shared understanding of a team discussion to provide a reference point to keep the team in harmony going forward.
Setting team expectations of the relative role of the different members of the team is a practice that seems to be very much in its infancy from an adoption perspective. On the positive side, the practice of using Business Analysis plans on large projects seems to be growing which lends itself to this task.
3) Communicate Openly and Transparently
Take guidance from our Agile brethren by communicating openly and transparently. There is no mystery here; good leaders are good communicators.
- Motivate and inspire people through clear communication.
- Build trust through direct and open communication; do not be afraid to share difficult messages. Do not be afraid of the difficult conversation.
- Do not treat information as currency, to be controlled and dispensed as it fits your needs; banish the phrase “need to know”.
- Communicate information from top to bottom as well as bottom to top.
- Communication should be continuous; err on the side of over-communicating; people do not always hear, understand or make a connection when they hear a message the first time.
- Remember your actions communicate a message; the message that you communicate verbally and the actions you follow should be in accord.
If you fail to communicate properly, you can poison the atmosphere between you and your colleagues, as well as the morale of the project team. Communication is paramount to your success as a new lead Business Analyst.
4) Lead by Example
Show what you expect by taking the lead by example approach. Taking the role as a lead Business Analyst should not preclude being an active participant in the project.
- Make it easier for people to follow you by piloting the approach for Business Analysis that was agreed on during upfront planning.
- Set the standard for excellence by your actions; be the role model and do not dabble in mediocrity
- Build trust by sharing your experience in the trenches and how you adjust from the initial gameplan
- Don’t be afraid to ask for help; illustrate that no one has all the answers and that we rely on each other for success
In my experience, successful lead Business Analysts are the ones that engage directly and share in the accountability for the deliverables. The lead Business Analyst who is preoccupied with status reports and attending management meetings is often viewed as too remote to understand the real issues being faced by the Business Analyst in the trenches.
5) Accept when you are wrong
Accept that as a lead Business Analyst you will not be perfect. You will not get everything right at first and will make mistakes along the way. Your success on this project is dependent on how you handle mistakes and failures.
- Opening acknowledge mistakes in leadership that impact the team and the outcome of the project
- Take ownership of the mistake
- Keep calm; handle failures with grace and humility
- Move forward by reflecting on the challenge and identifying lessons learned
A significant component of leadership is related to your ability to influence. Accepting when you are wrong illustrates your humanity and builds trust in the team.
6) Know when to keep Silent
Avoid the temptation, as a new lead, to micromanage contributors on the team. Know when to keep silent. Setting guidelines by communicating expected outcome is acceptable. Paying excessive attention to how a resource does their job is counterproductive and leads to conflict.
- Treat Business Analysts as professionals and give them the benefit of the doubt when you contemplate stepping in to provide direction
- Do not undermine the authority and credibility of a Business Analyst during elicitation sessions by intervening to steer the outcome into what you expect; use offline time to guide, coach, and mentor resources.
- Talk to your team about how they want you to provide direction and how you would like to be kept apprised of their progress.
- Do not overreact when things do not go the way you expected; reflect on whether your expectations were realistic and how your guidance could be improved.
- Remember that individuals will feel disempowered and not trusted to complete their work completely when they encounter excessive involvement by their supervisor or leader.
Knowing when to keep silent and when to intervene is not always straightforward for the new lead Business Analyst. If in doubt, reflect on your need for control weighing it against the need to develop and grow the team.
7) Apply Servant Leadership
View your role on the project from the lens of a servant leader. Put your team first and yourself second.
- Listen first and practice empathy. Acknowledge the perspectives of other before asserting your viewpoint
- Understand the obstacles faced by the Business Analysts when facing their deadlines.
- Distinguish between obstacles they can solve on their own and the ones that need assistance; provide the support needed by removing those obstacles
- Use persuasion and influence to set direction; resist dictating a process
- Champion the success of the contributors; act as a cheerleader by applauding victories and witnessing people doing good things.
- Look beyond the delivery of documents as a measurement of success. Look at the professional growth of your team members as an equal victory.
Applying servant leadership is more than knowing when the keep silent and avoiding micromanagement. It means being vocal and active while serving the needs of the team.
No matter your background, age, or experience, we all share something in common—a desire to be successful. As noted in the beginning, being a lead Business Analyst for the first time can lead to anxiety and nervously. Following the seven tips listed are an effective start towards meeting that success. These tips are based on the patterns that I have observed in my career as an experienced Business Analyst but are certainly not conclusive. What has your experience been? What advice would you provide? Cheers to your success and future learnings.
Author: Michael Roy, Business Analysis Professional / Requirements Leader
Michael is a solutions-focused Business Analysis professional with extensive experience leading change initiatives at a tactical and strategic level.