The Evolving Landscape: Business Analysis, Product Ownership, and the Path Ahead

Maddenz
Thu, 05 Jun 2025 12:18:38 +0000
Career advice

The following is a collection of thoughts that’ve managed to put down that seem to be orbiting around a central theme - I apologise if they seem a bit disconnected - but now that you’ve been properly warned…

The world of technology and business is constantly shifting, and with it, the roles that drive innovation and delivery. For those of us in business analysis (BA), it’s an exciting, sometimes dizzying, time. We’re seeing an evolution in how our core skills are applied, particularly in relation to product ownership and the broader product ownership landscape.

The Shifting Sands of the Business Analyst Role
Two decades ago, starting out as a Business Analyst, the role felt incredibly attractive precisely because it was less rigidly defined. It was more about performing duties as directed, encompassing a wonderfully diverse range of responsibilities and activities spread across the entire project lifecycle. You might find yourself doing a bit of everything – from detailed analysis to some project coordination or even basic testing. Today, however, while undeniably more structured and focused around established standards and refined processes, that shift might not appeal to the same crowd who were drawn to the variety and broader scope that characterized the role when I began my career.

The Rise of Product Ownership and Product Ownership Analysis
With the surge of agile frameworks, the “Product Owner” role has become central. This role often focuses on defining the vision for a product, prioritizing features, and maximizing its value. They are the voice of the customer and the business, guiding the development team.
“Product Ownership Analysis” (POA) is emerging as a critical discipline within this space. It’s where deep analytical skills are applied to truly understand the product’s market, user needs, and strategic fit, often using techniques familiar to BAs to ensure the product delivers intended value. This is where the lines start to blur – and beautifully so.

Product Owner: A Natural Progression or a Distinct Path?
A common question that arises is: Is “Product Owner” a natural career path for a Business Analyst? While distinct, the roles share significant common ground. Product Owners often possess a broader strategic scope, encompassing market analysis, competitive positioning, and the full product lifecycle.
However, the core competencies of a seasoned Business Analyst—strategic advisory, stakeholder engagement, understanding business goals, and translating needs into solutions—are incredibly valuable in a product ownership context. Many BAs, myself included, have spent years in strategic advisory roles, contributing to systemic improvements and aligning business needs with technology solutions, which are foundational skills for product ownership.

So is it Collaboration or Combination? Thoughts?
I’ve been contemplating whether the crucial conclusion is that these roles are not mutually exclusive and are, in fact, often better when working together.

BAs strengthen Product Ownership: A strong BA can provide the deep dive into requirements, process, and system intricacies that empowers a Product Owner to make more informed decisions and articulate clearer needs to development teams. We can “unpack” the detailed implications of a product feature, ensuring feasibility and alignment.

Product Owners provide context for BAs: A clear product vision from a Product Owner gives the BA the necessary strategic context to perform their detailed analysis, ensuring their work contributes directly to overarching product goals.

Shared Goal: Ultimately, both roles are focused on delivering value. Whether it’s through ensuring SME-friendly procurement pathways or leading infrastructure delivery, the objective is the same: effective solutions that meet real needs.
In essence, my current view is that Product Owners fundamentally need BA-type resources to help them define what to build and to provide the detailed analysis required to truly develop their product strategy. This leads me to wonder: can/should/will the Business Analyst role remain the same both inside a traditional project environment and outside, in the continuous delivery world of “Product”-land?
But I’m genuinely interested in hearing your thoughts. What’s your view on the current state of business analysis? What is your view on how product ownership may fit or align with that?Do you see the career path for a Business Analyst not including the Product Owner role? I’d love to hear your opinions (I know at least one of you has one… ) and experiences on this evolving landscape in the comments below!

9 posts - 4 participants