The assumption worth examining
Consider a hypothetical owner who hires experienced tradespeople. The owner expects professional arrivals, clear customer communication, and complete handoffs because everyone knows the trade. When the work becomes inconsistent, the first explanation is that the team does not care enough.
Before accepting that explanation, ask a narrower question: what did the owner actually explain? Technical skill and a shared job title do not tell you whether people understand the same standards for communication, preparation, or follow-through. Treat that gap as something to investigate rather than a verdict on anyone’s character.
Replace the adjective with an agreement
Choose one word you use often: professional, reliable, accountable, or respectful. Write what someone would do if they were demonstrating it in one specific situation. For a handoff, reliability might mean naming what is complete, what is still open, and who owns the next decision.
Then provide a non-example. A message saying “all set” without mentioning an unresolved issue does not meet that particular agreement. The point is not to script every conversation. It is to remove a preventable disagreement about what was expected.
Which expectation are you asking people to meet without first making it visible?
Build the conditions, not just the demand
Ask what makes the behavior possible. Does the person have the information, time, authority, and appropriate channel to complete the handoff? Is the expectation compatible with safety requirements and existing policy? An agreement that cannot realistically be followed needs more than a motivational reminder.
Make your own part visible. If you expect complete handoffs, provide them when you delegate. If you need to change a deadline, explain the change and its effect on the next person. Do not quietly exempt yourself from a standard and then treat the exception as another person’s attitude problem.
Practice a response before the next problem
Prepare a simple conversation: “We agreed to include the open items. This handoff did not include them, and the next person had to stop and ask. What context am I missing?” Listen before deciding whether the next step is clarification, support, a revised agreement, or an appropriate response under your policies.
This is not a rule to avoid accountability. It is a way to make accountability about an observable agreement rather than an argument over labels. Keep confidential matters in the proper channels and do not use a public team discussion to single someone out.
Start with one routine
For the next 30 days, choose one recurring moment rather than announcing an entire culture transformation. Explain the agreement, demonstrate it yourself, provide the necessary support, and set a review date. Record an actual example before the change so you have something concrete to revisit.
At the review, ask what happened, what became clearer, and what extra burden the change created. Keep, adapt, or stop the practice based on those observations. A stronger working agreement is a useful outcome even when it does not produce a dramatic story.
Choose one expectation and turn it into a visible behavior, practical support, and a review conversation.
Open From values to visible behavior