Many young Business Analysts I have worked with have expressed disappointment in there being so many problems with their projects or at their client. In fact, I used to be like that myself. But after a little seasoning and maturing, I have come to see that problems are not the exception to be complained about. Rather, they are the reason for the Business Analyst in the first place. No problems [or potential problems], then no need for a BA.

A true BA learns to look for:

• The problems
• The root cause of the problems
• The solutions for the problems

It is easy for anyone to do the first bullet point – to find problems (and to complain about them).  But the BA with her professional commitment and problem-solving mindset has matured beyond trouble-shooter to problem-solver.

Understand that there is no disrespect for the trouble shooter who is supposed to operate in that capacity – like someone in QA.  But the BA has the greater responsibility to not only find the problem, but to also think about fixing it.  Though others like developers or architects or project managers might actually be the official party for solution delivery, the BA is proactive and drives the dialog or at least works to be ready to jump in at any time.