The Product Owner in Malaysia: Balancing Stakeholder Demands with Backlog Prioritisation
The Product Owner (PO) role is fundamentally about maximizing the value of the product resulting from the work of the Development Team. In a typical Scrum environment, this means having final authority over the Product Backlog. However, in Malaysia’s corporate environment, which often features hierarchical decision-making and a preference for consensus among powerful local stakeholders, the PO’s authority can be easily challenged or diluted.
This tension transforms the PO from a tactical product manager into a strategic diplomat, demanding a unique approach to stakeholder management and backlog prioritization.
The Challenge of Authority and Consensus
In many traditional Malaysian organisations, especially those with high power distance, challenging a senior leader's request is culturally difficult. The Product Owner, who is tasked with saying 'no' or 'not now' to ideas that don't align with the highest value, can face significant resistance. This can lead to:
-
Backlog Bloat: Requests from powerful stakeholders are automatically added to the backlog, irrespective of their value or priority, turning the backlog into a "wish list" rather than a prioritized plan.
-
Shadow PMO: Informal decision-making by senior managers bypasses the PO, leading to unplanned work being pushed onto the Development Team.
-
Burnout: The PO spends more time mediating political disputes than focusing on product strategy and value delivery.
Strategies for Effective Backlog Management
To protect the backlog and assert their strategic role, a PO must employ tactical communication and value-driven transparency.
1. Prioritise by Transparent Value (Not Volume)
The PO must adopt an objective, transparent framework for prioritisation. This moves the discussion away from "whose idea is better" to "what delivers the most measurable value."
- Use the WSJF Model: Employing frameworks like Weighted Shortest Job First (WSJF) or a similar cost-of-delay calculation, which clearly assigns a numerical value to each feature. This objective data serves as a shield against purely political requests.
- Establish a Clear Definition of Value: Work with executive sponsors to agree on what "value" means before the project starts (e.g., market share, revenue generation, operational cost reduction). This consensus prevents goal-shifting midway through the project.
- Visualize the Backlog: Use digital tools (Jira, Trello) and physical boards to ensure the backlog is highly visible and strictly ordered. Any deviation from the order must be publicly explained and justified by the agreed-upon value metrics.
2. Mastering the Art of "Saying No" with Respect
In a culture that values harmony and deference, a direct "no" can be counterproductive. The PO must learn to deflect, defer, and reframe stakeholder requests.
Instead of Saying... | Try Saying... | Purpose |
|---|---|---|
"No, your request is low priority." | "That is an interesting feature. Based on our agreed value model, let’s see where it ranks against our top revenue-generating items." | Reframes the rejection based on objective criteria, not personal judgment. |
"We can't do that now, it'll delay the product." | "We can swap this feature in, but to maintain our target delivery date, we will have to remove X and Y. Which one delivers less value to our users?" | Forces the stakeholder to trade value and take ownership of the prioritisation decision. |
"I will add it to the bottom of the backlog." | "Let’s define the measurable user or business benefit of this request. Once we have the data, we can re-evaluate its placement in our next quarterly review." | Defers the decision and requires the stakeholder to do the work of justifying the value, buying the PO time. |
3. Formalise the Stakeholder Engagement Loop
To prevent powerful individuals from overriding the process, the PO must actively bring them into the Scrum events.
- Product Review: Use the Sprint Review as the primary, formal platform for showing incremental progress and discussing the backlog. When stakeholders see the product evolve and offer feedback in a controlled environment, they are less likely to demand disruptive changes outside of the forum.
- Dedicated Stakeholder Groups: Establish a small, formal Stakeholder Council (comprising key senior leaders). Meet with this group monthly to review high-level strategic changes to the top of the backlog. This satisfies the cultural need for senior consensus while keeping the day-to-day prioritization under the PO’s control.
By mastering strategic communication, embracing transparent, data-driven prioritisation, and formalising engagement with senior leaders, a Malaysian Product Owner can successfully navigate cultural complexities and focus the team on delivering maximum value.
