The Community Blog for Business Analysts


Is it just me, or do I really dislike BA work?

I was lucky enough for awhile to do very technical systems analyst work.  Now I am only given what I suppose are traditional BA assignments.  I find the work boring, tedious, uninspiring, and most of all I feel unappreciated and undervalued.  I feel like a glorified secretary - I take notes and write up requirements or meeting minutes, send them out or meet again, and everyone dumps on the work I've done.  There is no way I can know what people want if they don't tell me, and I don't think my job is to put my own thoughts into things.  I am discouraged greatly that all I seem to be doing is writing things down other people say, then they get to revise it and make me do it over again.  I never get the satisfaction of doing something well and having it be "done" - someone is always adding or revising.

What can I do to understand if this is just me, or is this the true life of being a BA?

This entry was published on Jan 06, 2015 / DMLeVoir. Posted in Roles and Responsibilities. Bookmark the Permalink or E-mail it to a friend.
Like this article:
  8 members liked this article

Related Articles


Karin posted on Wednesday, January 14, 2015 10:13 AM
I think putting your own thoughts into things is a very important part of being a Business Analyst. Also, I don't think our role is to write down things people say. You need to understand the business needs, then gleen the business requirements from that and make sure that developers and testers have sufficient context to understand the requirements. Some of the work can be tedious, but I find it highly satisfying if there is a business issue to fully understand that issue and to translate that into requirements which everyone then agrees with (hopefully :-) ).
You can't know what people need if they don't tell you what their challenges are, so the most important thing is to get those stakeholders to open up to you and let you know what pain points they face and what they are looking for in terms of Success Criteria. When you know these things, you can start articulating business requirements and validate those with your stakeholders. Requirement elicitation should be a two way conversation in my view.
Only registered users may post comments.

Modern Analyst Blog Latests

As we start a new year many of us will take the time to reflect on our accomplishments from 2012 and plan our goals for 2013. We can set small or large goals. goals that will be accomplished quickly or could take several years. For 2013, I think Business Analysts should look to go beyond our traditional boundaries and set audacious goals. Merriam-...
Recently, I was asked by the IIBA to present a talk at one of their chapter meetings. I am reprinting here my response to that invitation in the hope that it will begin a conversation with fellow EEPs and BAs about an area of great concern to the profession. Hi xx …. Regarding the IIBA talk, there is another issue that I am considering. It's p...
Continuing the ABC series for Business Analysts, Howard Podeswa created the next installment titled "BA ABCs: “C” is for Class Diagram" as an article rather than a blog post. You can find the article here: BA ABCs: “C” is for Class Diagram Here are the previous two posts: BA ABCs: “A” is for Activity Diagram BA ABCs: “B” is for BPMN


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-2024 by Modern Analyst Media LLC