Five Ways a Product Owner Can Build Trust

For project teams to work together effectively, team members and stakeholders need trust. Each team member (product managers and owners, leaders, subject matter experts, and technical staff) have different roles and different interests.
As a product owner responsible for defining (and refining) the product backlog, you are expected to juggle a variety of issues including: choosing the most valuable work, meeting deadlines, controlling costs, incorporating bug fixes, addressing technical debt, ensuring quality, and communicating the changes to your users. If that trust breaks down, your product and process will, too. The result may be hidden agendas, rumors, gossip, no shows to standups, whining, or even subversive behavior.
Johann Rost, in his article “Political Reasons for Failed Software Projects,” [1] reported subversive behavior by team members, such as lying, withholding or delaying access to information, providing misleading or vague answers, and supplying poisonous ideas. Clearly, these projects are suffering from lack of trust.
Low trust levels can result in project churn, team turnover, low morale, and unhappy customers.
It doesn’t have to be that way.
As product owner, you have a lot of responsibility giving you the opportunity to build and sustain a healthy product development community. Reina and Reina [2] identified three types of trust needed in organizations that together influence a culture of trust.
Contractual trust: As you might expect, this kind of trust is based on having an unstated contract: “If you will look out for my best interests, I will look out for yours. If things change, we will renegotiate. Ultimately, we are jointly responsible for the team’s success.”
Communication trust: This kind of trust calls for honest and frequent communication. Team members tell the truth, admit their mistakes, maintain confidentiality, and seek and provide feedback. Their actions are consistent with their words and vice versa.
Competence trust: Finally, there must ultimately be respect for the team’s ability to get the job done. They promote mutual learning and development of everyone’s skills and knowledge.
Effective product ownership requires adherence to good practices. I have found the following five practical actions help build trust with your development team and business stakeholders:
One way to build trust is to collaboratively define a clear, crisp, and compelling product vision.
The vision is the why of the product, and communicates what needs to be built, who will use it, and how it’s different from what exists today. My September 2016 newsletter provides guidelines for creating a compelling product vision. [3]
Your vision statement builds contractual trust by establishing shared goals for business and technical people. If the team can’t agree on vision, you’re not ready to build the product.


