What is the accent of Business Analysis?
Just like me, business analysis also carries a sound that reveals its origin. This communication accent should not limit its scope.
Originally posted on The Brazilian BA website. A Portuguese version is also available on the Gigante Consultoria website.
I have consistently strived to improve my English in presentations, conferences, meetings, and classes. However, despite my intense dedication, my Brazilian accent persists. I was born and raised in Brazil, and Portuguese is my native language. Anyone listening to me speak English immediately recognizes that I come from a different background. Similarly, business analysis carries its distinct roots.
The Origin of Business Analysis
Originating from the Information Technology (IT) environment, specifically software development, business analysis evolved from the challenges faced by software experts: creating something of quality through a structured process. This necessity gave rise to software engineering, incorporating principles from traditional engineering into the software realm.
As time progressed, it became apparent that understanding the real needs of users was one of the most complex aspects of software development. Requirements engineering emerged as a specialization, addressing these needs in a more structured manner by eliciting, analyzing, documenting, and managing requirements.
Although these disciplines significantly propelled software development, it became clear that software development lacked a clearer definition of what the business expected as outcomes. Developing software is just one part of something more complex: business development. The shift from technology to business focus led to the emergence of business analysis.
Recommended by LinkedIn
Blend of Accents in Business Analysis
In addition to techniques and concepts from software and requirements engineering, business analysis incorporated knowledge from various areas such as process reengineering, management, finance, and marketing. However, the IT accent still resonates strongly in the language we use to present business analysis.
This IT accent can, in some situations, hinder the understanding of business analysis for professionals from other areas, limiting its application to the software engineering domain from which it originated. This should be avoided.
Care for Those with an Accent
In my case, I am not ashamed to be Brazilian, and I understand that my accent is part of the characteristics that form my personality. That’s why I present myself internationally as The Brazilian BA. Still, I always take care to speak in a way that can be understood by anyone, avoiding my accent becoming a barrier to communication.
Similarly, we should be concerned with presenting business analysis in a way that is understood by everyone, preventing the IT accent from becoming a communication barrier.
Communication for a Broader Audience
Fortunately, business analysis is much more diverse and plural than I am, able to draw contributions from authors, speakers, and enthusiasts from various backgrounds. The collective contribution to the development of this discipline will make it broader and more comprehensive, fulfilling its original mission of providing better business outcomes for organizations.
As a discipline, business analysis is still very young. The International Institute of Business Analysis (IIBA) has just celebrated its 20th anniversary. Our language can be adjusted to welcome more professionals, allowing them to benefit from the practices we use. Let’s join forces to build a more diverse and global business analysis capable of transcending borders and positively transforming organizations.
I equip individuals, teams, and companies to do better business analysis, enabling them to deliver business outcomes.
1yGreat article, Fabricio Laguna and a subtle reminder that business analysis is about the business first, its needs, stakeholders and value before solution (technology). And by the way, I love listening to your voice *winks* sounds like music in my ears 😀
Project Manager | ex.EY | Vipassana Practitioner | #BAPM #IMeanBusiness
1yThat’s a great point, Fabricio! When learned business analysis I’ve come through numerous IT artefacts as techniques, documents, meetings. And, having non-IT BA experience I can state that most of these artefacts don’t match the needs of business. I’ve found that focusing on business part is more important than on technology. It shapes the latter in a way that makes business effective and not the other way around. It all starts with processes being too time consuming in manual mode, or initiative on new strategy coming out, or changes in legislation. And definitely BA’s need business specific native speakers that have financial, marketing, engineering, sales, physics, etc. accent to meet the needs. I’ve personally found that BA with finance background is a gold in my region that is tremendously hard to find. A word about an accent, it makes one’s speech unique as far as one can express their thoughts in a manner that target audience understand. There is a signature in it, not a limitation. And yours is a good one.
Brilliant article explaining differences of the different roles with a nice metaphor. I’m often asked a similar question. What is the difference between requirements engineering end business analysis. I often explain it by the main goal of the both organizations IIBA and IREB. A business analyst has the goal to optimize the outcome of business and focusing on business opportunities and outcomes that might be supported by IT solutions. A requirements engineer has the goal to provide a perfectly fitting IT solution to e.g. support business processes but also many other areas like solutions for autonomously driving vehicles. Both roles for sure have certain overlaps in tasks, responsibilities. They also share similar skills, as both have to work with people understand their real needs in order to be able to find the best solution - in business or IT. This was perfectly covered by your article in an easy way that can be understood by everyone. Thanks 🙏 Fabricio
President Value University | Swiss Association for Value | CEO Mark BA Company | Value Designer Professional | Créateur de la méthode Qualigramme (AFNOR, 2000)
1ySure BA has IT accent to much… and many client don’t understand what that’s mean… that the reason why BA could not cross boundary of IT and can’t become more strategic. May be if you integrate value analysis #valuedesign in your speech you have some hope to become more than a requirement manager.