What Tools Do Business Analysts Use?
Business analysts commonly use a mix of documentation tools (Confluence, Word), process mapping tools (Visio, Lucidchart), tracking tools (Jira, Azure DevOps), and basic data tools (SQL, Excel). No single tool defines the role — what matters more is knowing how and when to use each one for the task at hand.
Quick facts
- Most BA roles require some combination of documentation, process mapping, and tracking tools, though the specific tools vary by company.
- Basic SQL skills are increasingly expected, even in non-technical BA roles, for direct data analysis.
- This connects to Core Skills Required for a Business Analyst.
Common business analyst tools by category
| Category | Common tools | What they're used for |
|---|---|---|
| Documentation | Confluence, Microsoft Word, Google Docs | Writing and sharing BRDs, functional requirements, and meeting notes |
| Process mapping | Microsoft Visio, Lucidchart, Miro | Creating flowcharts, swimlane diagrams, and process maps |
| Requirements/task tracking | Jira, Azure DevOps, Trello | Managing backlogs, tracking requirements status, linking work to epics and stories |
| Data analysis | SQL, Microsoft Excel, Tableau/Power BI | Querying data, analyzing trends, building reports for stakeholders |
| Wireframing/prototyping | Figma, Balsamiq | Creating low-fidelity mockups to clarify requirements visually |
| Collaboration/workshops | Miro, Mural, Zoom | Running remote requirements gathering workshops and stakeholder sessions |
Why tool proficiency matters, but isn't the whole picture
Tool familiarity makes a BA more immediately productive at a new company, since most organizations already have established tooling in place. But tools are ultimately just a means of executing core BA skills — requirements gathering, process analysis, and clear communication — rather than a substitute for them. A BA who's highly skilled with Visio but weak at actually eliciting accurate requirements will produce clear, well-formatted diagrams of the wrong process.
How to build tool proficiency without formal training
Most BA tools have low barriers to entry — Confluence and Jira are widely used enough that free trials or company access during a role provide plenty of hands-on practice. Visio and Lucidchart both offer free or low-cost tiers sufficient for building real process-mapping familiarity. For SQL, many free online courses cover the basic querying skills (SELECT, WHERE, JOIN) that cover the majority of what a BA typically needs for requirements-related data analysis, without requiring a deep technical background.
A worked example of tools used across a single project
A business analyst working on a new customer onboarding process might: run a requirements gathering workshop in Miro with distributed stakeholders, document the current-state process in Visio, write the resulting BRD in Confluence, break requirements into trackable items in Jira, and query onboarding completion data in SQL to validate assumptions about where customers currently drop off. Each tool serves a distinct purpose within the same overall analysis.
Common mistakes with business analyst tools
- Treating tool expertise as a substitute for core BA skills, producing well-formatted documentation of inaccurate or incomplete requirements.
- Learning a tool in isolation without a real project context, which tends to produce shallower familiarity than hands-on use during actual analysis work.
- Assuming every company uses the same toolset. Tool preferences vary significantly by company — being adaptable and quick to learn a new tool matters more than deep expertise in one specific product.
- Ignoring basic data literacy (like SQL), missing an increasingly valuable skill for BAs who want to validate requirements and recommendations with real data.
FAQ
Do all business analysts need to know SQL? Not universally required, but increasingly valuable — even basic query skills let a BA independently validate assumptions with real data rather than relying entirely on someone else to pull it.
Is Jira required for business analyst work? Not specifically Jira, but familiarity with some backlog/requirements tracking tool (Jira, Azure DevOps, or similar) is common in most modern BA roles, especially those working alongside agile development teams.
What's the difference between Visio and Lucidchart? Both are process mapping and diagramming tools with similar core functionality — Visio is a Microsoft product often used in enterprises already invested in the Microsoft ecosystem, while Lucidchart is cloud-based and often preferred for its collaboration features.
Can I become a business analyst without knowing any of these tools first? Yes — most of these tools have a relatively short learning curve, and many BAs learn them on the job; what matters more for entering the field is the underlying analytical and communication skill, with tool proficiency developing alongside real project experience.