Data and BI
The product owner: more than just managing requirements
Delivering a solution is only part of what makes a technology project successful. That solution also needs to address the right problem, create value, and fit the client's reality. But who makes sure we're actually building the right thing?
When a dashboard request reveals a much bigger problem
It starts with a seemingly straightforward request: a client wants to build dashboards to better track their operations and make more informed decisions.
The goals seem clear, the desired metrics have been identified, and the team is ready to get to work.
But during the first few discussions, questions start to emerge. The data needed comes from several systems that don't communicate well with one another. Some calculations fail to account for important variables. And even though certain metrics seem well defined, their interpretation varies depending on who you ask.
We could choose to move forward anyway. After all, the original request was for dashboards, not a review of the client's processes or systems. But would we really be helping the client by building a solution on foundations we already know are shaky? That's when we decided to take a step back.
Before building the dashboards, we needed to understand the processes, trace how information flowed through the organization, and challenge some of the underlying assumptions. In other words, we needed to get back to the problem the client was actually trying to solve.
This experience reflects something we regularly encounter in our projects: what a client asks for doesn't always tell the whole story of what they need. And that's exactly where the product owner comes in.
Understand the problem before building the solution
A product owner (PO) helps clients turn their business objectives into practical solutions. Throughout a project, they help ensure that decisions remain aligned with the client's needs.
Their work starts long before writing requirements or building a backlog. They need to understand how the organization operates, what users are trying to accomplish, and the constraints they face.
Sometimes, that means questioning a requested feature, suggesting a different approach, or asking a question no one has taken the time to explore. In our dashboard example, producing reliable metrics meant first understanding how information was generated, transformed, and interpreted.
This is where the product owner's combination of business and technical expertise becomes especially valuable. In our practice, POs bring a strong understanding of business operations alongside solid technical knowledge.
We may not be the ones writing the code, but we understand enough about how solutions work to have meaningful conversations with technical teams, anticipate potential implications, and help clients make informed decisions.
A feature might seem essential but require considerable effort for relatively little value. On the other hand, a fairly simple change might address several needs at once.
The PO's role isn't to make every decision. It's to bring together the right information and expertise so that those decisions genuinely support the client's objectives.
Trust is built one decision at a time
As a project progresses, something interesting happens.
Meetings that initially focused on gathering requirements gradually turn into meaningful conversations about the product's direction.
The client stops asking only, "Can we build this feature?"
They also start asking, "What would you recommend?"
That shift marks an important evolution in the relationship. The product owner is no longer seen simply as the person documenting requests and coordinating with developers. They become a trusted partner who understands the organization well enough to contribute to important decisions.
We experienced this firsthand with a client we were supporting on several analytics initiatives. When they needed to temporarily replace someone responsible for managing their business intelligence requirements, they asked us to take on part of that responsibility.
Our role expanded beyond supporting product delivery. We were now involved in evaluating and prioritizing requests, and consulted before key decisions about how the solutions should evolve.
That trust didn't develop overnight. It came from building a deep understanding of the client's environment and, more importantly, from consistently recommending solutions that made sense for their reality.
Being a trusted partner sometimes means saying no.
It can mean explaining why a request may not be the best option, proposing an alternative, or helping the client distinguish between what's nice to have and what's truly needed.
A good product owner doesn't simply try to fulfill a request. They help ensure the client makes the right decision.
A role that thrives on collaboration
Of course, product owners don't work alone.
Let's return to our dashboard project. Once we had a clearer understanding of the processes and requirements, we still needed to design a solution that was reliable, intuitive, and adapted to its users.
That's where collaboration across different areas of expertise becomes essential.
Technical teams bring their knowledge of architecture and development possibilities. UX/UI designers focus on user journeys and experiences. The delivery director oversees areas such as planning, resources, budgets, and timelines.
The product owner brings a different but complementary perspective: business objectives, functional requirements, and the value the product is meant to deliver.
Consider a business application. A designer might propose an intuitive interface that allows users to submit a request. But before designing that interface, we need to understand what information should be collected, which business rules determine how the request is handled, and how it needs to move between the people involved.
These questions are part of understanding how the product needs to function, a central aspect of the PO's contribution.
Naturally, these responsibilities overlap during the design process. The PO contributes to discussions about user journeys and interfaces, while the designer challenges functional decisions based on user needs.
Similarly, when budget or timeline constraints require a shift in priorities, the delivery director works to keep the project realistic, while the PO helps identify the trade-offs that best preserve the product's value.
The goal is to bring complementary expertise together around the problem we're trying to solve, without adding unnecessary layers of management.
What if the real value becomes clear in the next project?
A few months after completing our dashboards, the same client comes back with a new initiative: this time, they want to develop an application.
The features are different, but much of what we learned during the first project is still relevant.
We already understand the main systems, some of the business rules, the organization's processes, and the challenges involved in working with its data.
Instead of starting discovery from scratch, we can focus on exploring the new requirements, anticipating dependencies, and identifying opportunities to reuse what already exists.
Even better, the different initiatives start building on one another.
In this particular case, the information generated by the new application could eventually feed future dashboards. Decisions made today about how the application is designed could directly influence the client's analytics capabilities tomorrow.
That's why, whenever possible, we aim to maintain continuity in the product owner's involvement across projects.
Development teams may change, and technologies may evolve. But keeping someone who understands the organization and its initiatives helps preserve a broader perspective that becomes more valuable over time.
Supported by proper documentation and knowledge sharing, this continuity makes it easier to connect projects and identify opportunities that might otherwise go unnoticed.
The value of a product owner extends beyond any single product. It grows with the understanding they develop of the client and their environment.
From delivering projects to becoming a growth partner
Our product owner practice initially developed around business intelligence and data-driven projects. Today, it also extends to business applications, automation, and other digital solutions.
The technologies may change, but one principle remains: before building a solution, we need to understand the problem and the processes behind it.
This is especially relevant in the age of artificial intelligence.
With tools evolving so quickly, it's tempting to introduce AI or automate tasks before taking the time to question how things are currently done.
But automating an inefficient process can simply make its problems happen faster. Even the most advanced technology can't compensate for inconsistent business rules, unreliable data, or poorly defined responsibilities.
Part of the product owner's role is to bring that perspective, regardless of the technology being considered.
And the ability to understand processes and recognize underlying problems creates opportunities to contribute in a much broader way.
Over time, we develop enough knowledge of our clients to identify opportunities for improvement beyond the projects originally planned.
A recurring technical issue, a manual task that takes up too much of several people's time, or a process that could be simplified. These are all situations where we can recommend improvements without waiting for the client to submit a formal request.
This mindset is what allows us to evolve from a solution provider into a genuine growth partner.
A partner who knows the organization well enough to recognize opportunities for improvement, anticipate emerging needs, and help shape how it works, beyond delivering the projects it asks for.
Product owners play an important role in this approach, working alongside other experts. Their proximity to users, understanding of business processes, and technical knowledge allow them to connect real-world challenges with potential solutions.
And those solutions don't always have to become major projects. Sometimes, a small adjustment can make a meaningful difference in how people work every day.
Being a growth partner isn't about constantly looking for the next project to sell. It's about continuously finding better ways to help clients achieve their goals.
At the end of the day, what makes a project successful?
Let's return to where we started.
A client wanted dashboards. By exploring their needs, we uncovered challenges that went far beyond data visualization. We took the time to understand those challenges, helped guide the necessary decisions, and developed a solution better suited to their reality.
Today, that knowledge continues to create value through new initiatives.
That experience captures how we see the product owner's role: someone who understands both business and technology, brings different teams together, and builds lasting relationships of trust with clients.
Ultimately, our goal goes beyond delivering what clients initially ask for. We want to understand their organizations well enough to help them build what they truly need, today and in the future.


Did this article start to give you some ideas? We’d love to work with you! Get in touch and let’s discover what we can do together.


.jpg)
