Stop 01 · Business Analysis FoundationsTopics · 1/9

What Business Analysts Actually Do

In short

A shop owner says 'I want an app'. A developer asks 'which screens?'. Nobody understands each other. The business analyst is the person who gets both sides agreeing on the same thing.

BAs bridge the gap between business needs and technical or process solutions — understanding a problem deeply enough to translate it into requirements someone else can actually act on.

The purple blob measures a kurta on a dress form and writes the numbers in a notebook.

Think of it like this

Like the tailor with the notebook

You tell the tailor you want 'a nice kurta for Diwali'. The tailor asks about fit, fabric and the date, writes exact measurements in a notebook, and the karigar stitches from that notebook without ever meeting you. A BA is that tailor.

Watch it happen

From a vague wish to a clear requirement

Ops head

Dev team

Fewer complaints, please

1/6The business starts with a wish, not a requirement. Nobody can build 'fewer complaints'.

The big ideas

What you need to know

Find the real problem

People ask for solutions ('add a button'). A BA digs for the problem behind the request before anyone writes code.

Turn it into requirements

Requirements are clear statements of what the solution must do. They are written so builders and testers read them the same way.

Keep everyone agreeing

Business, tech and operations want different things. The BA helps them settle on one shared version and writes it down.

Check it actually worked

After launch, the BA checks if the original problem got smaller. Shipping a feature is not the same as solving the problem.

Save yourself the pain

Common mistakes

Oops

Thinking a BA just takes notes in meetings and types them up.

Do this instead

A BA questions, challenges and shapes what gets built. The notes are only the output of that thinking.

Oops

Writing down exactly what the stakeholder asked for, word for word.

Do this instead

Ask 'what problem will this solve?' first. The stated request is often not the best fix for the real need.

Oops

Believing you need to code to be a good BA.

Do this instead

Coding helps in IT BA roles, but the core skills are asking good questions, clear writing and logical thinking.

Your mission

Find the problem behind a request

~20 min

Quick check

A manager says 'We need a new dashboard'. What should a good BA do first?

Go deeper

1Read 2-3 'day in the life of a business analyst' posts from different industries.
2List the last 5 process or system changes a company you know probably needed a BA for.
3Notice how much of the job is asking the right questions, not just writing documents.