Tuesday, 06 January 2009 04:59

Ten Bad-Ass BA Techniques

Written by 
Rate this item
(0 votes)

Plus Four Fundamental Principles

Principle #1. Leave your ego at the door

  • You are a business analyst - you have a license to ask dumb questions; it is your responsibility and your job! So ask the dumb questions, admit you don't know, ask for input, show work at early stages, don't let your own ego-fears-pride get in the way of problem solving.
  • Put your team in the spot light, put yourself behind the curtain.

Principle #2. Authority is 20% given & 80% taken - take it!

  • Don't wait for permission, ask for forgiveness.
  • Manage those meetings!

Principle #3. Acknowledge people

Sometimes you have to push people or ask them to do more than is normal to expect. You can thank them for their help but over time, your thanks may develop a hollow tone. Take the time to recognize people's efforts in a way that means something to the individual; creative ways of saying "thank you" are remembered for a long time and create a positive impression and a good relationship.

  • Nominate them for an award
  • Send a message to their boss - what you needed, why the person's professional conduct and timely response saved your butt
  • Send a message to the person
    • A "thank you" card - there are many cyberspace sites that offer electronic cards
    • A simple email message acknowledging the person's effort
      Include a .jpg of a plate of tasty goodies like cookies, chocolates, or samosas

Principle #4. If you don't fail on occasion, you aren't trying hard enough

Progress and innovation come from holding on to the idea despite the inevitable series of failures. If the consequences of your taking initiative results in a backfire

  • Acknowledge verbally that you may have gone too far in your attempt to actively engage in moving the project along the path to success
  • Ask the person if there is a better way for you to accomplish your goal. Smile; deflect any barbs that might come your way.
  • Learn from the failure. Don't get defensive - nothing ventured, nothing gained!


The Ten Techniques

Remember, these are the "bad-ass" techniques. Use them with care, especially if you are risk-adverse.

Managing meetings

1. Use "roll call" to obtain explicit decisions. In meetings (telephone or in person), do not accept silence as a response! Instead of asking, "do we all agree?" instruct people to express their concerns with this prompt, "If you disagree, speak up now."

2. Provide a suggested agenda to focus activities at a standing meeting.

3. Use Actions-Decisions-Issues to record meetings.

Facilitating communication and understanding

4. Share bad news early

  • The sooner "management" or "leadership" knows there's a problem, the sooner they can start working on it. 
  • If you use the red-yellow-green flag paradigm: extend the paradigm, "Pale Yellow" means "warning, this could get worse"; "Orange" means "one step away from Red".

5. Did they read the document?
For documents that are in a draft form, include an unexpected phrase in a strategic location in the document, e.g., "300 Pink Elephants" - people will comment on it if they see it. Take care to remove the phrase before the document becomes a deliverable!

6. Treat requirements templates as guidelines

  • Provide all the information that is asked for, or explain why you can't.
  • Don't ignore the gaps, missing or unknowns, identify them!
  • Add the sections or references you think are missing

Conducting interviews

7. Send the list of topics you plan to cover in advance - no more than five general topics. If you have specific questions that will require research, provide those questions in advance.

8. Paraphrase as a way to keep a person talking without agreeing with what they are saying.

Establishing trust-based relationships

9.  Make a personal connection

  • Extend yourself beyond normal bounds to make a personal connection with the individual regardless of social group, ethnic background, and gender.
  • Ignore what you may have heard about an individual; do not allow another person's negative assessment of that individual to prejudice you - make your own assessment, based on how that individual conducts him/herself with you.

Managing requirements

10. Get the Success Criteria and Success Metrics

  • Offer outrageously low or high metrics for targets to elicit a more realistic expectation for "success"
  • Accept the "solution" with grace; but continue to ask questions. Play the fool until the requirement (need) has success criteria and a way to measure it.

Cecilie Hoffman is a Senior Principal IT Business Analyst with the Business Analysis Center of Excellence, Symantec Corporation. Cecilie's professional passion is to educate technical and business teams about the role of the business analyst, and to empower the business analysts themselves with tools, methods, strategies and confidence. Cecilie is a founding member of the Silicon Valley chapter of the IIBA. Her personal passion is cross-country motorcycle riding. She can be reached at This email address is being protected from spambots. You need JavaScript enabled to view it.

Read 5966 times Last modified on Tuesday, 27 March 2012 13:46

Comments  

 
0 # Brian Chugg 2009-01-06 11:50
I think I'm a Bad-Ass BA (-: Great Article. Have used the "300 Pink Elephant" approach and it does work.
Reply | Reply with quote | Quote
 
 
0 # Rebecca Burgess 2009-01-06 13:53
Great guideline article. Could be used to direct discussions in BA forums. A couple of observations: Asking the dumb questions and risking failure are absolutely critical. If you're a BA and you find yourself in a group or company that doesn't subscribe to those principles, it's time to refresh the resume. Rememb er that there are two types of success criteria - the short term "project" success criteria (how do we know when we are done/have delivered) and the long term "run rate" success criteria (how do we verify that the process is still working or the product is being produced with the same level of quality). Get both.
Reply | Reply with quote | Quote
 
 
0 # Ian Frazer 2009-01-06 18:55
New professional designation: "B-a BA". I qualify. The digging for information is sometimes like digging in taffy but must be done. One aspect is that sometimes -their- ego(s) take a beating as you get the questions answered and create consensus.
Reply | Reply with quote | Quote
 
 
0 # Wesley Grisdale 2009-01-06 23:00
Fantastic - very few 'text books' cover this approach and only experience will provide such an education. The ego point is probably the most important in todays environment which is full of them! I manage a BA team for a large retailer and look forward to sharing this!
Reply | Reply with quote | Quote
 
 
0 # Paul Mulvey 2009-01-07 03:19
Will the Business Analysis A-Team now have a BA Baracus? I pity the fool that doesn't recognize this!
Reply | Reply with quote | Quote
 
 
0 # Jon Borden 2009-01-07 10:15
Excellent list of tips for the BA. In addition to critical thinking, and technical analysis skills, the ability to ask the right questions and effectively draw out and document business decisions from the business is critical to the success of the BA. The of 4 principles and 10 techniques in this article are great examples of how a BA can do that. The only point I would add is... ...ACTUA L cookies, chocolates, and samosas are much more effective as a thank you, than the ".jpeg" versions. :) Some of these techniques are that "not so common, common sense".
Reply | Reply with quote | Quote
 
 
0 # vasuramanujam 2009-01-07 19:09
Great observations. I did occasionally had to play the 'bad cop' angle to ensure everyone was on same page w.r.t requirements. I especially liked your "principle #4".
Reply | Reply with quote | Quote
 
 
0 # Keith Privette 2009-01-08 06:18
Great article thank you for writing out these techniques. One thing I would like to add is that this might not be for everyone and not everyone can be a BA. If you find these techniques uncomfortable and your title is a BA you may want to reconsider the title the company has knighted you with. This article also dispells the notion that "well anyone can be a BA"....its like saying "anyone can be an Accountant". There are soft and hard skills that just can never be taught....you either have it or you dont. The ones that fake it and dont get it tarnish the rep.
Reply | Reply with quote | Quote
 
 
0 # Arvind 2009-01-08 20:48
This article is really an enlihtening one about various aspects of being a BA.
Reply | Reply with quote | Quote
 
 
0 # Howard 2009-01-12 08:24
Excellent article on the subtleties of being and effective BA. I would also offer the "Do No Harm" attitude; being someone who can be confided in without it coming back to bit them. This has been invaluable in understanding the obtacle/opposit ion and general lack of cooperation along with unvoiced concerns regarding the success of a project.
Reply | Reply with quote | Quote
 
 
0 # Pat Ferdinandi 2009-01-13 06:38
I would move the building a relationship higher on the list. Building individual relationships is key to success for the current project and future. If you have a personal relationship with each business member, you are a trusted advisor. You will hear about scope creep or change in direction faster if you have a relationship with the business community. You will be a trusted advisor to the IT community. You will be the successful bridge between the two. It only happens when you have a relationship.
Reply | Reply with quote | Quote
 
 
0 # Cecilie Hoffman 2009-01-15 18:31
All, thank you very very much for the great comments. Cecilie
Reply | Reply with quote | Quote
 
 
0 # Joseph Medica 2009-01-29 11:57
Cecile, this was very good material. Thanks doing sucha great job of putting into words the practices I've followed for years - I've never been able to manage it. One thing I would note - this list looks much like a similar list I was given years agon on how to be an effective PM! Joe
Reply | Reply with quote | Quote
 
 
0 # Cecilie Hoffman 2009-02-02 05:57
Joe, I agree that all the practices could apply to PMs. The more responsibility the BA takes on, the greater the need for the BA to apply sound project management techniques to the work of business analysis! Cecilie
Reply | Reply with quote | Quote
 
 
0 # Aaron Gothelf 2009-02-05 13:50
Cecile, Great article! I've been a Business Analyst and a Project Manager for many years; if the project is small enough, I find myself doing both. One thing that I learned is: Be honest. Do not hide the truth (even if it's bad). People (stakeholders) want to know what's happening and what is (and is not) going to happen. They all hate finding out after the fact. Managing expectation is the name of the game! Aaron Gothelf New Jersey
Reply | Reply with quote | Quote
 
 
0 # Lucia Dupard 2009-02-10 12:44
"Put your team in the spot light, put yourself behind the curtain." This has saved me a lot of time and grief. As a generalist BA this mindset has afforded me to work on many projecs without being a specialist and has allowed me to truly insert myself as a bridge between stakeholders and developers. Great article!
Reply | Reply with quote | Quote
 
 
0 # Cecilie Hoffman 2009-02-10 15:33
Dear Ihdupard, yes, exactly! The trouble with becoming a specialist is that you get pigeon-holed, and over time you may find yourself perceived as an "application analyst". Your wonderful cross-functiona l communication and strategic negotiation skills will not see the light of day. Generalist BAs need to work hard to stay generalists; strategic hiding behind the curtain so that the spotlight is on the specialists (and deservedly so!) will save your day.
Reply | Reply with quote | Quote
 

Add comment