“I wish the team would show more ownership.” Before saying this in a staff meeting, ask what you want someone to do differently. Notice an unfinished task? Raise a concern before it becomes urgent? Keep a promise made to a patient? Each calls for a different conversation. The word “ownership” can hide those differences and leave staff guessing which part of their work has disappointed you.

A more useful request names the responsibility, the authority to act and the support available. Staff can care deeply about their work without sharing the owner's financial position, decision-making power or personal ambitions. Your task is to make responsible work possible and recognisable, then address specific problems when they arise.

Turn the complaint into an observable expectation

Start with one recent administrative task that did not go as expected. Describe what was left undone without assigning a motive. “The handover did not identify who would answer the enquiry” gives you something to examine. “Nobody cares about this practice” does not tell anyone what to change.

Write down what a satisfactory result would have looked like. Include where the result should be recorded, who needs to know and what the employee should do if the task cannot be completed. Check whether those expectations were already understood. If you are introducing them now, explain the change instead of treating an unwritten preference as a rule that everyone should have known.

Invite the person who does the work to describe the task from their side. Ask what information was available, what else was happening and where they were unsure. This does not excuse every omission. It gives you a basis for distinguishing an unclear instruction, a workload conflict, a learning need and a decision that needs direct feedback.

Respect the difference between employment and ownership

A practice owner and an employee hold different responsibilities and make different decisions. That difference does not mean employees have nothing at stake: their income, time, professional development and working relationships matter. It does mean that asking them to feel exactly as the owner does is a poor substitute for agreeing what the role requires.

Be especially careful when “ownership” quietly expands to mean constant availability, absorbing every staffing gap or accepting responsibility without the power to make decisions. State the additional work plainly. Discuss who can do it, what must change elsewhere and what support is available. Enthusiasm cannot create time that the schedule does not contain.

The useful goal is professional commitment expressed through actions. An employee may work carefully, help colleagues and raise concerns while having no wish to make the practice the centre of their identity. You can expect agreed standards and thoughtful communication without requiring a display of personal devotion.

Check whether the expected behaviour is workable

When a procedure is not followed, examine both the procedure and the behaviour. Can the person find the current instruction? Is the reason for it clear? Do they have the information, access and time to use it? Does another instruction point in a different direction? These questions make a performance conversation more specific; they do not establish in advance that either the employee or the system is at fault.

Try walking through the task together using fictional information. Watch for the point where a judgement is needed but no authority has been assigned. A reception team member might know an enquiry needs a response yet have no way to confirm who will handle it. Telling that person to “be proactive” leaves the unresolved decision in place.

Define what the employee may decide, what needs a manager's agreement and what must go to a clinical colleague. Provide a way to raise an unresolved issue. Clear limits are part of responsibility: staff should not invent clinical advice or make promises outside their role to demonstrate initiative.

Make respect, recognition and development concrete

Instead of demanding an owner's attitude, consider what would make this a practice people feel proud to work in. In daily practice, begin with ordinary commitments: listen to a concern, explain a decision that affects the person's work and follow through on support you have offered. A special gesture cannot substitute for reliable answers to recurring problems.

Recognition is more useful when it names an action and its value. “You noticed that the response had no named owner and asked us to assign one” tells the team which behaviour you appreciate. Keep the acknowledgement accurate. Do not attach a claim about increased revenue, patient loyalty or fewer complaints unless you have evidence for that result.

Ask how the person prefers their work to be acknowledged; public praise is not everyone's preference. Also notice the less visible work: careful handovers, preparing a colleague to take over and flagging a limitation early. If praise goes only to the person who stays late to rescue a problem, examine whether your recognition is overlooking the work that kept another task on track.

For development, agree on one task the person wants or needs to learn, the help available and the opportunity to practise. Keep pay and role expectations explicit rather than using appreciation as a replacement for those conversations. Promise advancement or a change in compensation only when the decision is made and the practice can honour it.

Give initiative a clear route and a real response

If you invite ideas, explain what happens after someone offers one. Identify who will consider the suggestion, what information is needed and when the employee can expect an update. A response may be “we can try this”, “we need to check this first” or “we cannot take this on now”. Each is more useful than repeated encouragement with no decision.

Where a small administrative trial is appropriate, agree on its scope before starting. Name who can approve the change, who will carry it out and how the team will judge whether it is usable. Schedule the work within the team's available capacity. An invitation to improve a process should not silently become another duty with no time or support.

Make it possible to report a problem with the trial, including a reason to stop. A suggestion is not a pledge that the idea will work. The owner remains responsible for the decisions and resources they control, even when a member of staff has proposed the change.

A hypothetical handover: replace a slogan with an agreement

Imagine an administrative enquiry passed between two shifts without a named person to handle the next step. This is an illustrative situation, not a reported patient case or a claim about results. The owner's first reaction is, “Someone should have taken ownership.” A more useful review asks where the responsibility was expected to change hands.

The team could agree on a simple handover rule: record the enquiry in the approved internal system, identify the next responsible colleague and confirm that the colleague has accepted it. If that person is unavailable, use a named backup or ask the manager to resolve the assignment. The handover should contain only information needed for the task, with no patient details copied into a general staff discussion.

Test that proposal with a fictional enquiry before adopting it. Check whether the next person can find the information, whether a backup is actually available and who will notice if the task remains unassigned. If the process adds more work than the shift can absorb, revisit the arrangement instead of asking staff to compensate through extra enthusiasm.

Decide separately how the patient will be kept informed, using the contact method they have agreed to. Do not promise a response time that nobody has confirmed, or turn an unanswered question into pressure to book. The patient may want information, time to think, a later appointment or no further contact. The administrative agreement must leave room for that choice.

Review one expectation and one management promise

At the next team check-in, bring two questions. First, was the agreement clear enough to carry out, and what happened when the team used it? Second, did management provide the support it promised? Looking at both prevents a discussion of responsibility from applying only to employees.

Keep the review small: one expectation, one obstacle, one decision and one person responsible for the follow-up. Recognise the work that met the agreed standard. Where there is a gap, discuss the action, its context and the next step without turning the conversation into a judgement about loyalty.

The team's affection for the practice does not need a score. Start by replacing one demand for ownership with a specific agreement that the team can explain and use. Clear responsibilities, credible support and honest recognition give you a practical way to discuss commitment without asking people to become someone they are not.