Technical accuracy alone doesn’t build trust

Project teams can forget that other people haven’t been living with the same information every day. What has become familiar to the team can be completely new to someone encountering the issue for the first time, and now only because it affects their property or community.

Presenting information accurately is part of the task but people still have to understand what it means in their circumstances. This is particularly important when building public trust in unfamiliar technologies or infrastructure, where technically sound information can sometimes leave people with more questions than answers.

On a past project we were involved in, we presented technical information in an overly complex format to our stakeholders. It led to misinterpretation and then mistrust. To rebuild that trust, we had to simplify the information and give stakeholders time to consider it before continuing the engagement. When we came back together with our stakeholders, they had a much clearer understanding of the expected change and could contribute more meaningfully to discussions.

A presentation, report or community meeting will rarely answer every question. Some questions only emerge once people have had time to reflect, speak with others or consider how the information affects them.

Give those questions somewhere to go. People should know how to return to the conversation, where to find supporting material and when they can expect a response. If an answer isn’t available, say so and follow up. Trying to fill every gap in the moment can introduce confusion and weaken confidence.

This is what continuous dialogue looks like in practice. People can test the information and add their perspective instead of simply receiving a completed position. The project team also benefits because stakeholder responses can reveal overlooked consequences, challenge assumptions or bring local knowledge into the decision.

Clear, transparent communication helps build community trust and gives people a stronger basis for informed engagement. Building community trust for Australia’s infrastructure future explores why communities need to understand how their input shapes longer-term outcomes.

Plain language can help people enter a technical conversation, but accessibility shouldn’t come at the expense of material context.

If supporting evidence disappears altogether, people may start wondering what has been left out. They then have to search for the information behind the summary before they can assess the message in front of them.

Keep the deeper evidence within reach. A short summary might introduce the issue, with supporting reports, assumptions and technical material available for people who want to examine it. Accessibility comes from helping audiences find the level of information they need, rather than deciding that everybody needs the same amount.

Access also depends on recognising the barriers that may prevent people from engaging. Reaching the hardly heard examines how project teams can involve people who can otherwise be overlooked in consultation processes.

When people can enter the conversation through clear language and follow the evidence as their questions develop, transparency becomes something they can experience for themselves.

Participation loses meaning if the project team only regards agreement as a useful response.

A stakeholder may question an assumption, describe an impact the project team hasn’t considered or introduce knowledge grounded in local experience. The value of that contribution lies in what it adds to the decision, not how closely it matches the project team’s original view.

This matters for infrastructure that communities may rarely think about until a failure or proposed change draws attention to it. New Zealand’s water infrastructure illustrates why greater visibility can support more informed participation in decisions about essential systems.

The aim isn’t unanimous agreement. People should have enough understanding and access to form an informed position. When they can question the evidence, contribute their perspective and see how the project team responds, communication becomes part of the decision process rather than a step that happens after the decision has already been shaped.

A stakeholder may challenge an assumption or bring a local perspective to the project that the team didn’t have. The value lies in what that response adds to the decision, rather than how closely it agrees with the original position.

This is critical for infrastructure that people rarely think about until something goes wrong. Greater public understanding can help communities engage with decisions about the infrastructure they rely on. New Zealand’s water infrastructure illustrates why visibility is important when the systems themselves are often overlooked.

The point is not that everyone should agree, but that everyone should have an informed view. Communication has done its job when people can use what they understand to take part in the decisions that follow.

Before asking stakeholders to respond to technical information:

• Consider their starting point. Give people enough context to understand how the information affects them.
• Allow time for reflection. Avoid pressing for an immediate response when the audience is encountering the issue for the first time.
• Keep the evidence accessible. Use clear language while providing a route to the assumptions, supporting material and deeper technical detail.
• Create a way back into the conversation. Explain where people can ask further questions and when they can expect a response.
• Treat challenge as a contribution. Stakeholders may question an assumption or add local knowledge that strengthens the decision.

Trust grows when people have the context, time and access they need to form an informed view. Good technical communication creates room for them to participate, including when their perspective differs from the project team’s.