Rethinking the “Business Analyst” Title

Kia ora koutou,

In @Hannah’s welcome post she alluded to something that’s also been on my mind for a while now, and I thought it might deserve its own kōrero here:

Do I want to keep calling myself a Business Analyst?

Does that title still reflect the mahi I want to do and where I want to be positioned?

Where I’m Coming From

My current workplace is being disestablished at the end of this year, due to changes brought in by the current government.

It’s bittersweet because I’ve really loved working here.

When I joined, the organisation was only two years old. I was the only BA positioned in corporate services, and I had a lot of freedom to design and embed systems, processes, and policies to help kaimahi deliver their best work.

One of the projects I’m most proud of was completely reworking our performance approach.

Designing a Culturally Responsive Performance System

Our organisation shares services with a larger entity, but our own board is much more progressive.

When they saw the highly structured, performance-based pay frameworks coming through, they pushed back.

They wanted a performance approach that was mana-enhancing and culturally responsive. Managers asked that Māori human resource management practices be considered, and we needed to make sure the system didn’t create barriers for Māori, Pacific, and whaikaha (disabled) kaimahi.

The whakataukī “the kūmara does not speak of its own sweetness” came up many times during discussions.

I started by researching a wide range of performance and compensation frameworks, and presented options to our managers and board.

We landed on separating performance from pay:

  • Salary increases were based on inflation, market conditions, and equity adjustments.
  • High performance was recognised through a separate programme – offering additional leave or other forms of recognition.
  • This fitted in alongside our existing values-based awards, and we made sure the high performance criteria were holistic and focused on broader contribution – not just visibility or output.
  • It was important to us that the criteria worked for all kinds of kaimahi – introverts, extroverts, frontline, back-office – and that recognition didn’t rely on being the loudest voice in the room.

Building the System (and Learning a Lot Along the Way)

We then needed to design the full performance cycle:

  • How often should check-ins happen?
  • What would meaningful reviews look like without traditional ratings?
  • How could we make sure the process served all stakeholders?

Off-the-shelf software options were too expensive and too rigid.

At the same time, our manual ‘paper’ system gave us no visibility, no tracking and no data for decisions like training needs.

So, I worked alongside managers, people and culture, cultural advisors, and kaimahi to prototype the first iteration:

  • Front-end: Microsoft Forms
  • Automation: Power Automate
  • Back-end: SharePoint Lists

It worked – but it had limitations.

I then built a case for developing a custom app. We brought on a developer, and I collaborated closely with them to design, test, and launch it.

I now own the app and manage it like a product, with continuous improvement after each cycle.

I also harvest data from the app to design our annual training approach – with full transparency to kaimahi that this would be a use of the information they provided.

What This Means for Me

This project ran the full spectrum – strategic, operational, technical.

I loved seeing it through from the very first conversations to a fully launched solution, and getting positive feedback that it genuinely made a difference.

So when I think about my title and career positioning, I realise:

I don’t want to be pigeonholed as “just gathering requirements” or “process mapping.”

I’m much more of an internal consultant. I like having my fingers in many pies.

My work spans project management, change management, a touch of DevOps, Product Manager, and learning and development – and I love it that way.

Closing Thoughts

It’s made me wonder if continuing to call myself a Business Analyst might undersell what I actually want to be doing.

I’d love to hear others’ whakaaro – have you found yourself asking the same question?

Ngā mihi nui,

Rhiannon

3 Likes

Okay two things:

  1. Very very cool mahi!! And very sad to see it disestablished.
  2. I have LOTS of thoughts on this topic! I’m going to loop back this evening with proper thoughts rather than just a “quick before I get stuck into work” ramble at you!

(but short answer is I’ve been very much on this journey!)

1 Like

That sounds like an amazing project - and just the sort of meaningful impact I think we should be having as ‘business analysts’!

Similarly my days look very diverse - ranging from requirements gathering, to acting as a project sponsor, to building a low code app, to architecting an orgs systems, to developing a performance management framework… All tasks that are either ‘traditional’ BA tasks, or ‘BA-adjacent’.

Reflecting about how I pitched my offerings I landed in the same place as you - that ‘business analyst’ as a title was underselling the full spectrum of what I did!

So I rebranded myself to ‘BeyondBA’ to break into a new definition!!

3 Likes

I really wanted to come back here and write a spiel but I realised I would be rehashing everything I’ve written about here. So I won’t!

But what I mulled today in between the meetings was that title and value are fundamentally different things. And sales is a different thing again. Unfortunately all three are involved in job hunting … so for the next role you’ll have to wrangle it.

But of those, the one that really matters is value. And from what you’ve written, your value comes from helping the people around you. How you listened. Provided clarity. Smoothed their processes. Bridged gaps. Helped them build new things. Found better ways of doing things. And did it transparently and with heart. :sparkling_heart:

The trick is finding somewhere – or someone – that will see that and enable that value irrelevant of the title on the role!

Yes, people who haven’t met you, may (unfortunately) pigeonhole you based on the BA title you’ve held. And those of us who stretch the boundaries of the role tend to find work through their network. But all my best bosses (and I’ve have a pretty amazing run of finding people who I’ve loved worked for) have been found through my network or a friend of a friend.

I hope you find an answer, or a working hypothesis at least!

[I should also say that I have found my own little rebrand and title change helpful because I’ve been able to reframe my value (which provides the kind of freedom you mentioned at your current org) so you’re also very welcome to adopt the name ha ha!]

2 Likes

@Hannah I feel like we have a lot in common. Everything is a system! Critical thinking and systems-level analysis are what drew me to this profession.

I’ve always enjoyed the parallels with science (my first love). Identifying a problem or opportunity, researching, forming a hypothesis, testing it, gathering insights, and then translating that knowledge into something usable and meaningful for the people who need it. That process of learning, adapting, and sharing is at the heart of how I work.

I often think of myself as a Pokémon going through ongoing evolutions. Each version connected to who I was before, but changed, grown, and better aligned with where I’m going.

I have immense love for the profession of business analysis. If everyone understood business analysis the way we do, the world would run a lot more smoothly! But lately I’ve felt drawn to broader, more varied work that ironically feels more connected to the roots of the profession:

  • Adam Smith’s transformation in the manufacture of pins
  • Frederick Winslow Taylor and Henry R. Towne treating management as a scientific discipline
  • Taiichi Ohno’s Toyota Production System
  • And of course, the authors of the Agile Manifesto

All systems thinkers, all change agents in their time.

After this exchange I’ve created a new albeit clunky tagline for Linkedin “Business Analyst | Applied Systems Thinker | Explorer of Organisational Ecosystems | Practitioner of Business Science | Crafting Insightful, Purposeful, and People-Led Solutions”

2 Likes