Stop 01 · Business Analysis FoundationsTopics · 9/9

Key Tools Overview (Documentation, Data, Process)

Part of the Business Analyst Roadmap

In short

Job posts list a dozen tools and it feels scary. Relax. BA tools fall into a few buckets, and if you know one tool in each bucket, you can pick up the rest in a week.

A preview of the toolkit this roadmap builds — documentation tools for requirements, data tools for analysis, and process modeling tools for mapping workflows visually.

The purple blob stands behind a kirana counter with a thick register and a calculator.

Think of it like this

The kirana owner's three tools

A kirana owner keeps a khata register for who owes what, a calculator for the day's totals, and a mental map of which shelf holds what. Records, numbers and layout. A BA's toolkit is the same three things, just digital.

Watch it happen

A BA's toolkit by job

BA toolkit
Documentation
Data
Process
Collaboration
Jira, Confluence
Excel, SQL
draw.io, Visio
Miro, Teams

1/5Group tools by the job they do. The brand matters less than knowing one tool per job well.

The big ideas

What you need to know

Documentation tools

Where requirements live. Jira for stories in Agile teams, Confluence or Docs for BRDs and meeting notes.

Data tools

Spreadsheets first, SQL second, a dashboard tool third. Most BA analysis never needs anything fancier.

Process tools

Diagramming tools for flowcharts and swimlanes. draw.io is free and works in the browser.

Concepts beat brands

If you can write a clear story in Jira, you can do it in Azure DevOps. Learn the idea, then the buttons.

Save yourself the pain

Common mistakes

Oops

Listing ten tools on your resume after watching one video each.

Do this instead

List the tools you've actually used on a project, and be ready to show the output.

Oops

Waiting for a paid licence before practising.

Do this instead

Google Sheets, Google Docs and draw.io cost nothing and cover most of what you need to learn.

Your mission

One tool per bucket

~30 min

Quick check

Your new team uses Azure DevOps but you only know Jira. What's the best way to think about it?

Go deeper

  1. 1Skim the table of contents of each remaining phase to see how the tools fit together.
  2. 2Learn that most real BAs use a mix of these tools depending on the project, not just one.
  3. 3Set a rough personal priority order — most beginners should focus on requirements skills first.

More topics at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge