Who’d’ve Thunk This!?

So the COO asks to speak to me the other day.  Fast forwarding, I was being moved out of my current role — the one I’ve been in for years, the one I’ve spent the last decade of my career doing — to the development team as a business analyst.

Huh?  What?  Me?

After taking a few days to let the shock wear off and see the decision from a logical point of view, fast forwarding through the gruesome turmoil of emotions and gauntlet that my mind went through, I see how this is an opportunity that I should embrace.

Maybe a year ago, I presented an idea to the COO of a new role the company needed.  See, we have several different departments, all with their individuals processes.  And since each process is created in a silo, there’s no way of knowing if there’s an overlap or gap between all the processes where something is falling through the cracks.  We needed someone who would meet with each department, understand each department’s processes, what they want to accomplish, how these processes work with other department’s processes — and how they don’t — and most importantly, how to reconcile them so that all the processes put together form one unified, coordinated, efficient and effective company process that keeps everyone on the same sheet of music.

Well, that’s my new role.  Lead Business Analyst, they’re calling it.  My first To Do is figure out what’s a business analyst.

A business analyst (BA) is someone who analyzes an organization or business domain (real or hypothetical) and documents its business or processes or systems, assessing the business model or its integration with technology.

The International Institute of Business Analysis (IIBA) describes the role as “a liaison among stakeholders in order to understand the structure, policies, and operations of an organization, and to recommend solutions that enable the organization to achieve its goals.”

Interesting.  In my now former role, I was already doing that, to an extent.  Only I didn’t have the pay grade to compel other departments to change their processes.  The goal was always to get all of us talking in the same language, but I didn’t know how to say that in their language.

Now, that’s my job.

I have a long way to go to be where I want to be to say I know what I’m doing.  Speaking of language, there’s a bunch of new words I’ll have to learn to be able to really communicate with the rest of the IT team.  Sprint.  Scrum.  Use Case.  Instance.  One day in and already I’m Googling four words?

Anyway, as I always do when there’s a significant change in life, I’ve created this blog to capture this journey.  It’s more for me to take notes, save ideas, and more than likely, express some frustrations, but also to be able to look back at today and remember where I was when I started this journey.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s