"BA level-up" - Ep 02: Technical Skills for BAs: Understanding Systems to Collaborate Effectively with Developers
- Tuan Anh
- 1 day ago
- 4 min read
Continuing our journey of self-improvement—after clearing up the career roadmap and overcoming mindset bottlenecks—today, I want to dissect a topic that makes many Business Analysts (especially those from non-IT backgrounds) feel intimidated: Technical Skills for BA.
Have you ever sat in a meeting with the Dev Team and felt like they were speaking an alien language? They discuss APIs, Frontend, Backend, Databases, Microservices... while you just nod along and mindlessly jot down keywords?
The biggest mistake a BA can make is thinking: "I handle the business; technology is the Developer's job."
True, you don't need to write code yourself. But if you don't understand the system, you will forever remain a "Secretary BA"—someone who mechanically relays messages. A true BA (what I call a "BA Architect") needs a solid technical foundation to assess if a proposed solution is feasible, understand its impact on other modules, and most importantly: to earn respect from the Dev Team.
Below is a comprehensive Technical Skills Map to help you "break the ice" and collaborate effectively with the technical team.
---------------
PART 1: SYSTEM THINKING - THE ROOT OF EVERYTHING
Before learning specific tools, you need to learn to view the product through the lens of a System.
This skill helps you understand how technological components interact to create value for the user. When a client requests a new feature, your reflex shouldn't be to draw the interface immediately. Instead, analyze:
Where does this data come from? (Database)
Where is the logic processed? (Backend)
How is it displayed to the user? (Frontend)
Does it need to fetch info from third parties? (API/Integration)
Pro-tip: Always ask "How does this work under the hood?" instead of just caring about the surface
---------------
PART 2: THE BASIC IT FRAMEWORK - A COMMON LANGUAGE WITH DEVS
To "speak the same language" as Developers, you need to master these foundational concepts:
Frontend & Backend: The Separation of Display and Processing
Frontend: Everything the user sees and interacts with (HTML, CSS, JavaScript, Mobile Apps). You need to understand UI/UX principles and the limitations of each platform (Web vs. Mobile).
Backend: The "brain" that processes logic, calculations, and data management (Java, Python, .NET...). When writing User Stories, clearly distinguish between interface changes and processing logic changes..
Database: The Information Warehouse
A system cannot function without data. A BA needs to understand Relational Databases (RDBMS)—where data is organized into tables connected by keys (Primary Key - PK and Foreign Key - FK).
Pro-tip: Don't just stop at knowing data exists. Learn about ERD (Entity Relationship Diagram) to understand how Entity A relates to Entity B (1-1, 1-n, or n-n).
API & Communication Protocols: The System's Nervous System
In this era, rarely does a system stand alone. API (Application Programming Interface) is the "contract" that allows systems to talk to each other.
Understand that APIs work on a Request - Response mechanism.
Grasp basic methods: GET (retrieve data), POST (create new), PUT/PATCH (update), DELETE (remove).
Learn to use tools like Postman to "test" APIs. This helps you validate requirements faster without waiting for the Devs to finish the UI.
---------------
PART 3: SQL - THE BA'S ULTIMATE WEAPON
If I had to choose the single most important technical skill for a BA to stand their ground, it would be SQL (Structured Query Language).
Why do BAs need SQL?
Requirement Validation: When a client says "The system is buggy, the data is wrong," you can query it yourself to check instead of waiting for a Dev.
Impact Analysis: Before changing logic, use SQL to see how much legacy data will be affected.
Data Storytelling: Use actual data to persuade Stakeholders instead of relying on gut feelings.
SQL Roadmap for BAs:
Data Definition Language (DDL): Understand how table structures are created (CREATE, ALTER, DROP).
Data Manipulation Language (DML): This is what you'll use most. Master SELECT, INSERT, UPDATE, DELETE.
Advanced SQL: Learn to connect tables (JOIN), group data (GROUP BY), and use calculation functions (SUM, AVG, COUNT).
Tip: Start with SQLite. It's simple, requires no complex configuration, and is perfect for learning the fundamentals.
---------------
PART 4: INFRASTRUCTURE & TRENDS
A Senior BA or Technical BA needs a broader view of infrastructure:
Server & Cloud (Azure, AWS): Understanding how tech products operate on the cloud helps you consult on system stability and scalability.
Microservices Architecture: Instead of one giant block (Monolithic), systems are now divided into small services. The skill of modeling interactions between services (Sequence Interaction) is incredibly valuable.
AI & Automation: Don't view AI as a rival. Learn to use AI as an "assistant" to draft documents, summarize meetings, or even help write complex SQL queries.
---------------
PART 5: TWO-WAY COLLABORATION TACTICS TO EARN RESPECT
Your technical skills only truly shine when converted into effective communication.
Communicate with Logic
When working with Devs, ditch vague phrases like "I want it to look fancy." Instead:
Use precise, detailed language.
Provide full Acceptance Criteria (AC) in Gherkin format (Given/When/Then) so Devs know exactly the input conditions and expected output. At the very least, clearly state the Context, Input, and Expected Output.
Use visual diagrams like Activity Diagrams or Sequence Diagrams instead of writing lengthy text.
Become a "Quality Gate" for Technical Results
Don't trust 100% when a Dev says "It's done." Use your technical knowledge to validate. Check if the solution affects other modules (Impact Analysis) and if the data in the Database matches what's displayed on the Interface.
---------------
TECHNICAL SKILL FOR BA: MINDSET IS THE KEY
Remember, the goal of a BA learning technical skills is NOT to argue with Devs about whose code is more optimal. The goal is to:
Understand the nature of the system to propose the "right" and "precise" solutions.
Narrow the gap between Business Needs and Technical Feasibility.
Build trust and reliability—the glue that holds the project team together.
Building a system isn't hard. Building the right thing that people actually use, and ensuring the system runs smoothly—that is the hard part.
---------
Related Posts in this Series:
Comments