The Community Blog for Business Analysts

HSantanam
HSantanam

BA Careers - Is industry experience more important than Analytical skill?

 

Business Analysts often delve into business requirements, gathering, understanding and documenting business processes and functions. An analytical mind and detailed information gathering are considered to be essential; one wonders though, if industry experience is a must for good business analysis skills. After all, if you knew well the ins and outs of the industry you were in, that’s good, right? The answer is probably, but not always. Why is that?

 

 

Business analysts, like developers and solution architects, are trained to think logically and focus on specific issues at hand. Once in a while, though, they need to step back, and like a painter evaluating and assessing his painting-in-progress, assess their progress on the task at hand and be prepared to explain it to a wider audience in plain talk. That, in my opinion, is an essential skill of the modern analyst.

 

First, industry experience means less time is wasted knowing the industry environment – the general models the business follows, what regulatory and competitive arena it is part of and some common terminology. Secondly, business process flows are easier to understand, say, if one was documenting business process flows for a financial transaction, if that person had already worked in a financial services firm in a financial transaction environment (e.g., Front office, where the deals were made, or the middle office, where financial and regulatory processes were checked or filtered, and the back office, where the transactions were processed and settled – and where exceptions were followed up for closure).
That of course, brings up an interesting question – if a business analyst goes into an unfamiliar environment, how much time should be spent learning the business environment? Wouldn’t that leave less time for focusing on the essentials of requirements, elicitations and documentation? And how valuable would all that be, anyway? After all, time is money – and with workloads being what they these days, such knowledge, while good for a progressive and open mind, would be quite expensive indeed, wouldn’t it?
The answer is that depending on the timeframe, it would be beneficial to get the most important work done first, which would mean skipping the overview on the business. In a limited time frame, a “bullet-point” information dissemination method (summary) might work. Asking questions in the right environment is healthy, but learning important concepts on one’s own time is a better idea. After all, stakeholders have limited time available even for requirements – they might not have the patience for an extended basics class. On the other hand, workflows and the reasoning behind them should be questioned to extract the maximum value for optimization and better business.
What about the times when it might be beneficial to hire a business analyst who is sharp and curious, but not industry-knowledgeable? When the existing patterns are so constricted and “inside the box” that a fresh perspective is needed, hiring analysts without a lot of presumptions and insider’s knowledge is actually a good idea.
I worked in a firm once where I was asked to interview, evaluate and recommend IT candidates (mostly developers, some analysts). At the end of the face-to-face interview, I would ask the candidate to solve a problem on pen and paper. The rules were clear – no writing code, simply writing out the solutions – a diagram was acceptable as long as it wasn’t too complex. Additionally, the answer had to be limited to 1 page and be completed in about 30 minutes. I was amazed at how the smartest candidates failed this written “test” – it was actually quite simple, for it did not require deep industry knowledge and did not put the candidate on the spot by testing coding knowledge. I simply wanted to know how the candidate thought about solving problems and whether he/she was able to put it on paper. I often got several pages of answers, written code and requests for extending the time available, though all the requirements for the written test were explained before hand. Needless to say, these candidates were not hired.
 
This entry was published on Dec 06, 2010 / HSantanam. Posted in Project Management, Analytical and Problem Solving Skills, Soft Skills, Career as a Business Systems Analyst, Roles and Responsibilities. Bookmark the Permalink or E-mail it to a friend.
Like this article:
  3 members liked this article

Related Articles

COMMENTS

posted on Thursday, December 9, 2010 8:25 AM
To respond to the question posed in your title, No, no and no - industry experience without the capabilities and skills that make a good BA can never be more important. However I would agree - up to a point - with the case you make for industry experience being highly useful. The downside though is that it can make you lazy: you "know" the context so well that you don't always take the trouble to go out and ask questions.
I certainly agree with the latter part of your post, that an attitude of curiosity and openness, coupled with the appropriate skill set obviously, will ready an analyst to walk into an unknown domain and add value.
HSantanam posted on Friday, December 10, 2010 11:33 AM
Pat - Thanks for your input. I guess industry knowledge, while useful, is not great in and of itself. It can definitely lead to a "know-it-all" attitude and outdated assumptions.
Aleksandr posted on Monday, December 13, 2010 6:23 AM
Too brief and abstract, no any in-depth info. Skip it.
zjjia posted on Saturday, December 18, 2010 9:27 PM
i totally agree. in China, i can't find a good BA job position. They only care about the industry knowledge. I have nothing to say with them. I just graduated from the uni for 1 yera, during the 1 year, I finished 1 big project.

However, I always think in this way. We have the detail knowledge of BABOK, we can spend time learing new industry then design new solution. The problem is the time. Yes this is correct.

I told others, I am not a ba, im a designer, just like designing flat or hotel or anyother architecuture. I have the concept and knowledge to design everything logically, what i need is the chance to do it.

I dont think one ba new to 1 industry works worse than one traditional worker in that industry if let him to do ba tasks.

Im sad that i have to choose to be 1 CRM consultant. BA is greater than consultant, no matter SAP consultant or other consultant. Consultant's tasks depend on BA's initial development of the application. e.g. BA designs the SAP, then so many SAP consultant use it to work. In china, they r in high salary, but they are still module consultant, not like a BA who is solution consultant. If you put one SAP consultant into 1 new industry, it will not work better than 1 ba new to it. I think so.
Putcha posted on Wednesday, February 16, 2011 4:17 AM
If you want an improvement or innovation or break-through in a Business Process or Product or a System. A team of Business Analyst, Requirements Engineer, Domain specialist,System Analyst, Developers need to be formed.

The role of a BA is to find the requirements from the end users, the current practices, new expectations etc. For this there are many industry independent methods and tools (some simple and some sophisticated). It is the experience with these tools that make a BA valuable. In any case Domain Specialists are there to give Industry specific inputs.

So, a well trained BA with a portfolio of methods and tools + case studies would be very valuable. The speed of progress can be taken care of by planning and coordination.

I provide B A Training and Consulting over the Skype and WebEx + email. Let's work on a Trial Case of BA free of consulting fee. putchavn@yahoo.com
Only registered users may post comments.


Blog Information

» What is the Community Blog and what are the Benefits of Contributing?

» Review our Blog Posting Guidelines.

» I am looking for the original Modern Analyst blog posts.



Copyright 2006-2019 by Modern Analyst Media LLC