To build trust in a team, make commitments clear, give people the information and support to deliver, and deal honestly with missed promises. In a trade business, start where people depend on one another: the job handoff, the parts order, the schedule change, and the conversation about a problem.
Consider a familiar situation. A technician is told a replacement part will be ready before the next call. The counter team believes purchasing is handling it. Purchasing is waiting for approval. Everyone has worked hard, but nobody has confirmed who owns the next step. The technician arrives to find no part and no update.
This is an illustrative example, not a Blue Collar Smart client story. It shows a useful place to investigate when a team says, “We need better communication.” Before planning another team meeting, look at the promises people are relying on.
Make a promise specific enough to keep
“I'll take care of it” sounds reassuring. It leaves important questions unanswered. What will be done? By when? Who needs to hear the result? What happens if the plan changes?
Try replacing a vague commitment with a complete one: “I'll confirm the supplier's availability by 2 p.m. and update dispatch, even if the answer is that we're still waiting.” That person has promised an action they control. They have not promised an outcome that depends on an unconfirmed delivery.
Use four details when the work crosses from one person to another:
- Owner: the person responsible for the next action.
- Result: what the receiving person should expect.
- Time: when the result or next update is due.
- Exception: who gets told if the commitment cannot be met.
The point is not to document every conversation. Choose the handoffs where ambiguity creates repeated frustration. A clear promise gives both people something they can check without guessing what the other meant.
Check the handoff from the receiving side
A handoff is not complete simply because someone sent a message. Ask whether the next person has what they need to act.
Imagine a service manager assigning a revised job to a crew lead. The schedule contains the new address, but the customer has also changed the access arrangements. If that detail remains in the manager's text messages, the crew lead has the assignment without the context.
For a recurring handoff, ask the receiving colleague to explain the next step in their own words. This is a check on the handoff, not a test of the colleague. If the explanation differs from what you intended, correct the information before the job moves on.
Ask the people doing the work what they are repeatedly forced to chase. Their answers may point to something small enough to fix this week: a missing approval, an unclear priority, or an update that reaches the office but never reaches the field.
Make it useful to raise a problem early
Trust also concerns what someone expects will happen when they bring you uncomfortable information. If every early warning turns into a public argument, asking for “no surprises” is unlikely to be enough.
The CIPD's review of trust and psychological safety describes psychological safety as confidence in taking appropriate interpersonal risks at work, including asking questions and admitting mistakes. It is related to trust, but it is not permission to ignore standards.
When someone reports a problem, separate the immediate response from the later review. First establish what happened, who is affected, and what needs attention now. Then discuss the decisions, expectations, or support that need to change.
A practical opening is: “Thanks for telling me now. What do we know, and what do you need help deciding?” That response leaves room for accountability. It also gives the person a reason to bring the next problem forward while there is still time to act.
Invite input from people who do not usually speak first. A newer employee, a woman leading a crew, or a colleague working a different shift may see a gap that the usual voices have missed. Give the observation a fair hearing before defending the current process.
Repair a missed commitment with a concrete next step
In Hugh Hornsby's conversation with Darren Jacklin about integrity, Jacklin connects integrity to keeping one's word. He also describes proactively communicating and addressing the consequences when a commitment is broken. That distinction matters: a leader's responsibility continues after the deadline passes.
For the trades-team examples here, use a simple repair conversation:
- Name the commitment you missed, without making the other person reconstruct it.
- Acknowledge the effect on their work.
- Explain what you can reliably do next and when you will update them.
- Ask whether that next step addresses the immediate problem.
Suppose you promised to review an apprentice's progress on Friday and let it slide twice. “It's been a busy week” explains your circumstances but leaves the apprentice waiting. A more useful response is: “I missed our review again. You needed a decision about your next responsibility. Let's meet tomorrow at 8, and I'll arrange coverage so we can finish.”
The repair is only credible if the next commitment is kept. Make it small enough to honor. Do not try to regain confidence with a bigger promise you have not made room to deliver.
Apply the same standard to yourself
The Center for Creative Leadership's guidance on accountability emphasizes clear expectations, sufficient support, and consistent leadership behavior. It also calls on leaders to acknowledge their own mistakes and follow through.
Review your own part in the work before concluding that someone needs a better attitude. Did you change the priority without changing the deadline? Did you assign responsibility without access to the information? Did you approve an exception for a high performer while criticizing someone else for the same behavior?
Consistency does not require identical treatment in every circumstance. Experience and responsibility can justify different support or authority. Explain those differences clearly, and avoid making personal preference the hidden rule.
For people taking on leadership responsibilities, connect these habits to actual practice. In Hugh's conversation with Eric Himes about building a people-first business culture, the discussion connects personal development with the needs of the organization.
Try a ten-minute commitment review
At your next team check-in, choose one recurring handoff and review three recent examples. This is an editorial exercise to help you examine the work, not a validated trust score or a formal assessment.
For each example, ask: Was the owner clear? Did both people understand the expected result? Was an update given when the plan changed? What did the receiving person have to chase?
Agree on one adjustment and try it for the next week. Review whether the handoff required fewer follow-up questions and whether unresolved commitments stayed visible. Use what you learn to improve the process, not to rank people publicly. One smoother week is useful feedback, not proof that every trust problem is solved.
Start with a promise that belongs to you. Find one commitment a colleague is still waiting on, give them an honest update today, and complete the next step you agree to. Let your team see the standard in your own work.