Why everyone is talking about the 'Experience BA'

Nikitha Kocharla

Why everyone is talking about the 'Experience BA'

The global pandemic has changed the customer journey — it’s become more complex, and consumers have higher expectations. A business analyst (BA) plays a key role in understanding and executing on that journey.

An effective BA must bridge the gap between business stakeholders and technical teams, eliciting and capturing requirements from stakeholders and effectively communicating those requirements to the technical team. The BA plays an integral part in determining the best solution to achieve the defined business goals.

A BA wears the cap of a product owner and acts as the pseudo client for the development team, suggesting improvements and monitoring and directing them toward the business goals. They help ensure an outstanding customer experience and act as problem-solvers.

But the BA role is not just about understanding functional aspects; it also involves viewing the requirements from a technical standpoint. A BA is expected to have expertise in technologies like data analysis, automation, and SQL (a standard language for storing, manipulating, and retrieving data in databases).

BAs are also often the first point of contact with clients, hence they represent the organization. They’re partly responsible for helping to keep the client happy, marking the origin of the concept of an “Experience BA.”

How to Become an 'Experienced Business Analyst'

Early Engagement

BAs should be engaged in projects from the initial stages, giving them the opportunity to conduct a pre-analysis of the project’s purpose and get a complete understanding of what the client is looking for. This helps the BA develop metrics for process improvement and enables them to suggest solutions.

This also helps the BA become the subject matter expert, raising the right questions in the requirement phase to understand the requirements from the client's perspective and mapping them to their business processes. The BA can then proactively suggest alternatives in the development phase, deliver mature demonstrations and better evaluate results.

Client Interface

The BA should look for opportunities to interact with clients across the project life cycle to develop trust and establish a connection. This not only gives the project team a clear vision of the client's preferences and interests in critical areas, but it also helps in setting client expectations.

Critical Focus Areas

An “Experience BA” should identify the areas where the client is paying the closest attention. As per the 80:20 rule for software development, only 20% of features are used frequently, and 80% of features are used rarely (45% of those are never used). It is the BA’s responsibility to identify the 20% that is of utmost importance to the client.

User Acceptance

Keeping user experience as the goal of delivery, an “Experience BA” must conduct thorough user experience (UX) testing before the product is delivered to the client. They should check for intuitiveness, ease of navigation, and other factors to ensure that the solution surpasses client expectations.

Technical Skills & SQL

Technology is essential across all areas of business. Experience BAs are in a unique position, traditionally straddling both technology deployment and end-user analysis to enhance business value.

In the current market, SQL is a required skill set for experience BA, as they may need to draw entity-relationship (ER) diagrams, which consist of all the information on the entities and the relationship of the data and its flow.

Tips to Mastering the ‘Experience BA’ Role

A few simple yet effective processes can help you master the skills needed to be an ‘Experience BA’:

Keep the customer involved

BAs must have regular interaction with clients and keep them updated, giving them a sense of involvement and improving the customer relationship. This will not only help the customer know what the next milestone is but will also help them understand how it’s being achieved.

Modes of communication may include:

Scheduled calls: Bi-weekly, weekly or daily, per the client’s preference
Email: Daily status emails
Technical/business discussion: Whenever an issue needs to be addressed, the BA should schedule time with the client to explain the process. An experience BA is expected to have the knowledge to do this clearly and succinctly.
Planning dashboards: Give the client access to project dashboards (JIRA/SharePoint) and assign action points to involve them in the project.

Communicate the right way

Communication is key, whether it’s in written or verbal form, and it should be adapted to suit the preferences of stakeholders. BABOK identifies three categories of learners: