"Business Analyst"?
Feb. 25th, 2007 09:02 amA few weeks ago I found out from
renniekins that my long-term career goal is called "Business Analyst" at her company. That's been repeatedly independently confirmed, once again in comments to my latest LJ post. I expressed incredulity at the misnomer.
renniekins and I carefully described the job functions to each other, to make sure we were talking about the same thing. There could be no mistake. It couldn't have been more camouflaged against my notice than being named "Business Analyst".
Wikipedia's article on Business Analysis does not describe the same job. I hypothesize a reason for this situation. What if there are many businesspeople who are good at the things that article describes, who ended up getting shunted instead into the tasks I like (software mockups/demos, use-cases, interface specifications, and documentation)? What if that's why they keep the title of Business Analyst, because they'd rather be working with organizational structure, strategies for the enterprise environment, and shuffling money around, than translating between technical staff and end users?
I greatly prefer "Requirements Analysis", if I had to pick a necktie-sounding term. That article is far more recognizable. Compared to my previous career, in 2007 I've taken a huge step in that direction. Five to ten years from now I'd rather spend a larger percentage of time thinking about happy and productive end-users of a software package than thinking about employees and money, if I can help it.
And yes. I am good at it.
P.S. I like
netmouse's suggestion of the term Human Factors". I also like the Menlo Park article. My interest in alphabets, human languages, text-entry alternatives, measurement systems, spelling reform, game design, and software interfaces has been a long-standing manifestation of my fascination with cognitive ergonomics, before I knew the term.
Wikipedia's article on Business Analysis does not describe the same job. I hypothesize a reason for this situation. What if there are many businesspeople who are good at the things that article describes, who ended up getting shunted instead into the tasks I like (software mockups/demos, use-cases, interface specifications, and documentation)? What if that's why they keep the title of Business Analyst, because they'd rather be working with organizational structure, strategies for the enterprise environment, and shuffling money around, than translating between technical staff and end users?
I greatly prefer "Requirements Analysis", if I had to pick a necktie-sounding term. That article is far more recognizable. Compared to my previous career, in 2007 I've taken a huge step in that direction. Five to ten years from now I'd rather spend a larger percentage of time thinking about happy and productive end-users of a software package than thinking about employees and money, if I can help it.
And yes. I am good at it.
P.S. I like
no subject
Date: 2007-02-25 03:23 pm (UTC)Requirement analyze away!
no subject
Date: 2007-02-25 03:30 pm (UTC)no subject
Date: 2007-02-25 04:32 pm (UTC)Business Analyst, Human Factors Engineer, sometimes "Team Lead" is also the term for that work, and in some places it's part of the marketing department, which is weird.
no subject
Date: 2007-02-25 05:38 pm (UTC)See, to me, that would be someone who studies high tech cultures and whatnot. Or geek culture. But I could see how that would fit.
no subject
Date: 2007-02-26 12:00 am (UTC)If you're interested, I'll send you details. Assuming you take it the rest of the way, the entire bid price ($500) is yours, as is most of the credit.
no subject
Date: 2007-02-26 05:50 pm (UTC)