“She is good at organising things” may sound like a reason to give someone another job. It is not yet an assignment plan. Which part of the work has she done well, under what conditions, and does she want to do more of it? What will come off her existing list? Those questions turn a general impression into a decision the practice can examine.

A useful approach to staff strengths starts with work people have demonstrated, the work they want to develop and the support available. It also looks beyond the individual: when one person's duties change, someone else may receive the remaining tasks. The aim is a workable allocation across the team, without turning a strength into a permanent label or an unlimited supply of extra capacity.

1. Describe the work before choosing the person

Start with a small set of duties suitable for reassignment. Break broad labels such as “administration” into activities with visible requirements: gathering proposed meeting items, checking that an agenda contains the necessary details, or updating the list of agreed actions. Different parts of the same job may call for different experience, time and support.

For each activity, describe what a usable result looks like, when it is needed, who relies on it and what must be checked. Include less visible work such as clarifying an incomplete request, correcting a draft and helping a colleague. Counting only the final output can leave the preparatory and review work out of the allocation.

Identify duties whose standards or staffing arrangements cannot be loosened for this exercise. Required safety procedures, information handling and essential coverage remain in place. A preference for other work does not remove an essential responsibility, and enthusiasm does not establish competence or authorisation. This article concerns the allocation of suitable administrative work; it does not set clinical staffing requirements.

2. Use observations as a starting point, then ask the employee

Replace a broad judgement with an example that can be discussed. “You arranged the agenda so that each item had a purpose and a named presenter” describes a contribution. “You are our detail person” turns it into an identity. Ask what helped: previous practice, a clear template, uninterrupted time, support from someone else or a part of the work the employee particularly enjoyed.

Look at the conditions as well as the result. A person who completed a task accurately with guidance has shown something useful, but not necessarily readiness to handle every variation alone. Someone who has had fewer opportunities may have less visible evidence, not less potential. Avoid comparing speed without checking the complexity, interruptions and assistance involved.

Ask what the employee would like to repeat, learn or change. “Which part of that work would you like more practice with?” can be more useful than asking for a list of personal strengths. Invite correction of your observations. An employee may enjoy the planning part while finding the follow-up difficult, or perform a task well while preferring not to make it their main duty.

Keep the record modest: the activity observed, the conditions, the result, the employee's view and what remains uncertain. Do not treat learning quickly, volunteering or looking pleased as a test that reveals an enduring talent. A personality label or assessment score cannot replace a discussion of this particular assignment. Discuss relevant needs privately without requiring unrelated personal disclosures.

3. Compare the whole allocation, including the work left behind

Before moving a task, put the current and proposed arrangements beside each other. Who performs each activity now? Who would perform it next? What time, preparation and review does that require? Who covers absence? A change is incomplete if the attractive work has a new owner but the remaining routine work has none.

Ask who gains a learning opportunity and who loses one. Giving every complex task to the colleague who already does it well can leave others without a way to practise. Equally, rotating everyone through every task is not automatically the right answer. Decide which skills need shared coverage and where supported development or deeper experience is useful for the actual team.

Make the basis for allocation understandable without publishing personal rankings. The work may require specific experience, access, available time or a learning arrangement. Those reasons are different from declaring one employee naturally suited to people and another suited only to paperwork. Review whether familiar staff repeatedly receive opportunities while quieter or newer colleagues are overlooked.

Routine and less popular duties still need a fair, feasible arrangement. Name the person, time and support rather than leaving the work with whoever is least likely to object. Appreciation can recognise a contribution, but it does not provide cover or remove an excessive workload. If the proposed allocation does not fit, reduce its scope or resolve the capacity problem before starting.

4. Agree a limited change with room for development

Choose one manageable adjustment and write down the reason for trying it. Agree the work being added, removed or shared, the standard required, available time, support and a review date. A fixed percentage of someone's duties is not necessary. The size of the change should follow the work and the team's capacity.

Clarify whether the person is taking on a task they already know or learning a new one. Provide the instruction, practice and review that the actual gap requires. A strength in one activity does not cancel a need for training in another. Nor does a difficulty justify closing off development before examining unclear instructions, missing access or insufficient time.

Check the proposed arrangement with everyone whose workload changes. Explain what is settled and what can still be adjusted. The employee's view is essential information for the decision, while the manager remains responsible for arranging workable coverage and resolving competing requirements. Do not describe an imposed extra duty as a development opportunity without discussing its practical consequences.

Agree a route for raising a problem before the review date. Staff should be able to report an unmanageable load, a missing prerequisite or a duty they are not ready to perform. A short trial should not become permanent merely because nobody complained. State what would prompt a pause, a narrower scope or a return to the previous arrangement, while keeping essential work covered.

5. Rehearse a task swap with a fictional meeting example

Imagine a fictional practice reviewing the preparation of an internal administrative meeting. The exercise contains no real staff assessments, patient records or reported results. One activity is gathering proposed agenda items and clarifying incomplete submissions. Another is assembling those items into a draft agenda for the manager to check. Approval and decisions about the meeting remain with the manager.

In this scenario, a colleague currently gathering items has shown an interest in learning agenda preparation and has organised a sample well with guidance. The colleague currently assembling the agenda would like more experience clarifying requests. These are assumptions for the exercise, not personality profiles. Both need to understand the requirements of the proposed work.

The manager explores a swap rather than adding a second task to each person's list. They check how much work each activity involves, including following up on missing details and revising the draft. They also check whether the proposed timing conflicts with existing duties. The swap is not assumed to be equal merely because each colleague receives one activity.

Before starting, the colleagues practise with invented administrative topics. One checks what a proposed item needs; the other prepares the draft using the agreed format. They identify where instructions or support are missing. Each receives access only to the information needed for the work. Sensitive individual matters use their appropriate existing route rather than becoming general agenda content.

The manager agrees time for guidance and review, and arranges a trained backup. Both colleagues retain an opportunity to practise the other activity where it supports coverage or their development. The aim is not to make one person the permanent organiser and the other the permanent conversationalist. The proposed allocation remains open to review.

When rehearsing the review, consider more than one possible result. The agenda may meet its requirements while one colleague needs more time than the plan allowed. Or the work may be manageable but depend on guidance that the manager has not provided reliably. In either case, examine the actual condition and revise the arrangement. Do not turn a short exercise into a conclusion about either person's overall ability.

6. Review quality, workload and opportunity together

Compare the work with the standard agreed before the change. Look at completeness, necessary corrections, unresolved items and the support used. Ask both colleagues about workload and what they learned. Include effects on the rest of the team: an arrangement may appear manageable for the main participants because someone else has absorbed interruptions or unfinished work.

Separate evidence from interpretation. An item awaiting a manager's answer is not the same as an employee overlooking it. Extra time spent learning is not automatically poor performance. Equally, an interest in a task does not mean the work meets its requirements. Describe the specific gap, provide appropriate support and decide what can safely continue within the person's role.

The next decision may be to continue, adjust the split, provide more practice or stop the trial. Record the reason and the next review, with only the people who need the information. Share the operational arrangement with the team; keep individual development discussions appropriately private. Offer specific feedback in a way the employee is comfortable with, without ranking colleagues in public.

For a first assignment review, bring a simple page showing the duties, current allocation, observed evidence, employee preferences, proposed changes, capacity, backup and review point. Check that essential work remains covered and that development is not reserved for the same people. No assignment should reward pressure on patients to book or accept treatment; affordability, time to consider, declining and rescheduling remain legitimate choices. A strength is a reason to explore useful work with someone, not a verdict about everything they can or should do.