My daughter is home from Dunedin for the mid-semester break, and the weeks before she arrives always do the same thing. Time compresses. I make plans, try to cram in more work than the calendar allows, and then spend the first few days just finding our rhythm again.

She is studying biomedical science. I work in the people space. On the surface we operate from completely different disciplines, and yet my youngest watched us talking one evening this week and said, in exasperation, that it was like watching the same person have a conversation with themselves.

We laughed (maybe laugh-cried-snorted just a little… we seem to get the giggles quite frequently). But it made me think.

What we share is not subject knowledge. It is something closer to how we approach a problem, the instinct to ask a different question, to look for what is underneath the obvious answer, to stay curious when the easier move is to reach for certainty. That crossing of domains, when it happens easily, is not accidental. It requires a particular kind of preparation that has very little to do with what either of us knows about our subject.

I have been thinking about that in the context of the work I see delivery teams doing.

A few weeks ago I had dinner with a retired civil engineer. Brilliant man, the kind of intelligence that fills a room without trying. At some point in the conversation I said that talking plainly is not dumbing down. It took some convincing. He couldn't put his finger on why, but somewhere in his career the two ideas had become entangled. Simplifying the language had come to feel like simplifying the thinking. That assumption quietly undermines community trust on projects where the technical work is genuinely excellent.

I told him about a young water engineer I had met on a site visit, who lit up when I asked him to explain what the plant did to a class of twelve year olds, and delivered an explanation that was vivid, precise, and completely accessible. It had been inside him all along, it just needed a different question to bring it out.

Here is what I keep coming back to. When pressure rises in a community engagement, technically trained people reach for what they know best. They explain more. They defend their position. They become more technical, or they withdraw, or they try to regain control of a conversation that has stopped feeling safe. Stakeholders experience those behaviours long before they process the words.

The preparation that precedes those moments is usually key messages and a presentation.

That is a design problem, not a personal failing. These are people who care deeply about the work. They are standing in front of communities at the highest-pressure moments of a project with deep subject knowledge and very little preparation for what a room under pressure actually requires of them.

Reading a room, interrupting an automatic response, finding the language that builds rather than breaks trust under pressure are learnable skills. They sit alongside technical expertise without diminishing it. They are also the skills that determine whether a project keeps its social licence when the conversation gets hard.

It is a learnable skill that we need to build into our delivery teams.

That is exactly what the Conditions for Trust Network is designed to do. It is a peer advisory membership for communications and engagement practitioners who work alongside technical delivery teams, people who want to understand their own response under pressure, build a practical framework for difficult conversations, and develop the kind of judgement that holds when the room stops being friendly.

The founding cohort opens on 11 August. There are 25 places. If this is the work you are trying to get better at, I would love to have you in the room.

You can find out more and register your interest here at Conditions for Trust Network, or replying to this email.