home

BA's need a BA'd attitude

Analysis: There seems to be one thing that can't be taught and that is the analytical attitude. Maybe this is the wrong name - perhaps willingness is a better term, or professionalism - don't know.

But without an analytical attitude you are going to struggle. That attitude can be summed up as
"Trust nothing, believe no-one, prove everything".

"Trust nothing" = things aren't always what they seem. Don't assume because a report is headed "profit report" that it is reporting profit. Define what profit is to that organisation, examine the input to the report, the process it goes through to calculate profit and prove that it is what it says it is.

"believe no-one" = just because a Director or subject matter expert tells you something is so does not make it true. Get it corroborated. Validate it against other information. Prove the correctness to your satisfaction.

And this applies to Business Analysis and our methods as well! Just because some BA guru tells you something does not make it true if it is only based only on the status of that guru.

"prove everything" = "trust nothing" + "believe no-one" + build your conclusions based on facts that have been proved.

This attitude cannot be learnt - it has to be part of the character of the individual.

The analytical attitude: good for all kinds of investigative work such as business analysis, crime investigations, scientific discovery - anywhere in fact that new information needs to be uncovered.

Is there one true method or approach for doing this? No. There are hundreds of valid approaches. But if you don't have the attitude you will be following the method without knowing why (why would you trust the method - you don't trust anything!).

The attitude is one thing, the skillset that maximises on the attitude is another and there are any number of training courses out there (check out my business analyst training offering).

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

You go, Guy!

Nicely said.

People lie

People lie deliberately, they lie inadvertently. Lie is a tough word. Sometimes it's just wishful thinking. 

Challenge everything - politely.

Peter

www.princelite.co.uk 

Comment responses

Cdeturk: many thanks!

 

Merrickp: totally agree with your point: I didn't use the word 'lie' for that very reason. I don't know (and from a professional point of view) don't care whether they are lying, misunderstanding, wishful-thinking, speculating, hoping, dreaming - I just care whether it is correct in the context of the project. Thanks for your clarification on that.

 

www.smart-ba.com

Exactly!!!

Years ago I was in sales and had the best analytical thinking course I've seen. It taught us to discover hidden needs. What a customer said they wanted may be the result of inaccurate analysis on their part and it was up to the "sales consultant" to get to the root of the problem before they could make a recommendation.

Often there is a tendency for analysts to rush to a solution without understanding the WHOLE problem and all its perspectives. The very skill set that an analyst brings to the table is to examine the problem thoroughly, even the small details that customers deem insignificant or irrelavent or were not aware of. Discovering these and assessing them is what analysis is all about.

How true

Thanks for the comment Millieac: its an interesting point that analysis of sales needs is (just) another analysis of needs. Now you have pointed it out, it is surprising how little that is done for significant purchases of (say) a car. 

I guess things are a little more fluid in a car sales scenario but if you were selling (say) telephony networks then there is no rational reason not be as rigorous in the analysis of needs as in analysis of change requirements...?

www.smart-ba.com

That's why we do not always see eye-to-eye with developers

Developers want to get things done. Analysts try to prevent the incorrect thing being done. Opposite attitudes.

And it's not just software, these attitudes should apply to just about any industry.

Leslie.

BA's Need a BA'd Attitude

Yes - it's similar to parenting a teenager. :-)

Assumptions vs corroboration

Assumptions are just that. They conclude a standpoint from information that is exposed. Corroboration on the other hand is checked, cross-checked and verified from multiple sources to ensure the findings concur with each type of analysis being undertaken.

Again, your "Prove everything" is the only sure way to document findings upon which decisions, direct-setting and structure decisions depend

re "Assumptions vs corroboration

Johnnyv,

Many thanks for your comment.

I agree with the distinction you are making. In the real world, how much corroboration do you do? I ask because I tend to only corroborate once (i.e from the originator of the statement/requirement and the people/group that sign it off). Your comment made me wonder if that is sufficient - and then I thought "how would I know when sufficient corroboration has been done" - and then I though perhaps you might have a view on that...?

Regards,

Guy

www.smart-ba.com

Somewhat agree

man, you guys are tough!!!   I think the points being made are accurate, but the comments make us sound like we are the sleezy private investigator.  Collaboration is key in our roles to understand the true business need or opportunity so the right solution is delivered.  I take the approach of trust.  When you build strong relationships with stakeholders and team members, there is a level of trust that allows the team to challenge each other so the focus is on the right solution.

Post new comment

*
*
The content of this field is kept private and will not be shown publicly.

*

© 2007 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group