VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Why Do I Find It Hard to Let Other People Do Things Their Way? | How to Hand Over Work Without Taking It Back

Students test and measure a small bridge in a collaborative STEM activity

It can be hard to let another person work their way when you feel responsible for the outcome, know one method well or have had to fix similar work before. Start by writing down what a good result must do. Then ask which steps genuinely need to follow a rule. If someone can meet the standard through another method, agree on when you will check the result and give them room to get there.

A clear handover names the outcome, deadline, limits and decisions the other person can make. “Please prepare the room by four. The exits must stay clear. You can choose how the tables are arranged within that requirement.” If an important condition changes, agree on how they will flag it. This gives you useful visibility and gives them a task they can actually own.

  • Describe the result and how you will know it works.
  • Name required steps and decisions that can be made independently.
  • Give the person the information, access and time they need.
  • Agree on an appropriate checkpoint before the work starts.
  • Intervene for a material problem and give acceptable differences room to stand.

eduKate Singapore · Mindset and character

Find the part you need

Choose where to start, or open the chapter list to read in order.

Chapters 1–8
  1. Why you want to take over
  2. Decide what you are actually handing over
  3. Choose a checkpoint that has a purpose
  4. What to do when their result is different
  5. Examples from home, school and work
  6. Use three categories when you disagree about the method
  7. How to hand over a job to somebody who is still learning
  8. When you share the result and nobody is the sole owner
Chapters 9–16
  1. A full example from a first handover to a better second one
  2. What to do when you are the person receiving too much supervision
  3. Review the handover after the result is used
  4. Practise on one task with a low cost of correction
  5. When you need to change the agreement during the work
  6. Give feedback without becoming the second owner
  7. Agree on a fallback before anyone needs it
  8. Frequently asked questions

Chapter 1 of 16

Why you want to take over

A different method can make a familiar task look uncertain

You always prepare a meeting pack in the same order. A colleague starts with the attendance list and adds the agenda later. From your side, it looks as though they have forgotten the agenda. From their side, they are waiting for the chair to confirm it. Ask when they expect to have a draft ready and what is still missing. The answer gives you more information than asking them to copy your order.

Notice which parts of your method genuinely protect the outcome. An approved source, a safety rule or a required review can matter. The order in which someone opens the files may be a preference. Explain the difference during the handover. If a process has to be followed, tell the person what it protects. Where more than one method works, evaluate the result against the shared requirement.

You may be carrying accountability without enough visibility

A person who must answer for an event may reasonably want to know whether a room has been booked. They do not need to choose every email sentence if someone else can handle the booking. Ask for one confirmation at the point when it matters. “Send me the confirmed room and access instructions by Wednesday.” That gives the organiser evidence while leaving the booking itself with the person who agreed to do it.

Gary Yukl and Ping Ping Fu examined delegation and consultation in manager–subordinate relationships. Their study found that delegation and consultation varied with factors connected to the subordinate and the relationship. That is one workplace setting. A useful lesson for everyday handovers is to check who knows the work, who can make decisions and what support the relationship allows. Saying “I should trust more” does not supply missing access or define responsibility.

A previous problem may be shaping your current reaction

Perhaps you once left a task with someone who missed a deadline and you learned to keep checking. The current person may have different experience, access and reliability. Ask what is similar and what is different. A previous failure may justify a clear checkpoint. It does not automatically mean you need to supervise every step today.

If the same risk remains, say so in practical terms. “Last time we only saw the missing material on the day. Could you show me the list on Wednesday so there is time to resolve any gaps?” This makes the reason for the check clear. The person can respond to a known risk rather than trying to guess when you will intervene.

Back to contents · Next chapter

Chapter 2 of 16

Decide what you are actually handing over

Separate doing the work from making decisions

A person can be asked to collect options while somebody else chooses. They can also be asked to choose within an agreed limit. Tell them which role they have. “Please find two options and send them by Tuesday. I’ll choose after the budget review” gives a different job from “Choose the option that fits the budget and tell the group.” If you change the authority later, explain why and how it affects the work.

  • Outcome. What should be usable at the end?
  • Requirements. Which conditions genuinely have to be met?
  • Decisions. What may the other person decide?
  • Resources. What information, access and support can they use?
  • Checkpoint. When should they update you or ask for a decision?

This agreement can be brief. A household task may need only one sentence. A shared project may need a written note. Choose enough detail to prevent the most likely misunderstanding. If the person cannot say what they own, the task may still be partly in your hands.

Give them the means to do the work

A student asked to format a group presentation needs the latest file and permission to edit it. A colleague asked to organise a review needs to know who should attend and how to reserve the room. A family member asked to collect a delivery needs the collection window and any required identification. Check that the person can act before you treat a delay as a sign they cannot handle the work.

Ask if they want an example or a short demonstration. If they know the task better than you do, ask which information would help instead. The point is to make the assignment workable. A demonstration can show the requirement without making your preferred method mandatory.

Back to contents · Previous chapter · Next chapter

Chapter 3 of 16

Choose a checkpoint that has a purpose

Check while there is still time to act

If a group is creating an unfamiliar display, review one sample before they make all the copies. If a colleague is booking an event, check when the venue needs a final decision. If somebody is trying a familiar task independently, a final confirmation may be enough. Put the check where it can change the outcome. A daily question about a task with no daily milestone may create little information.

Tell the person what you will review. “At the draft stage I’ll check whether the figures match the source. You can choose the layout.” A check that changes its criteria each time can feel like a hidden veto. Agree on the review early and add a requirement later only when a genuine new fact makes it necessary.

Agree which problems need an immediate message

Identify what would interrupt the arrangement. The budget might change, an essential person may be unavailable or a required safety condition may fail. Ask the person to flag those issues early. Leave ordinary choices with them. “Tell me if the date moves or we cannot get the equipment. You can resolve changes to the order yourself.” Both people now know when help is expected.

If there is no time to recover from an error, choose a smaller handover or closer review. A low-risk task can give someone practice. A sensitive task may require permission or a trained person. Giving room to choose includes respecting legitimate limits on who can do the work.

Back to contents · Previous chapter · Next chapter

Chapter 4 of 16

What to do when their result is different

Check against the agreed standard

A colleague organises the report differently from you. The recommendation is clear, the figures are correct and the required sources are present. If your order was a preference, let the new order stand. You can mention a possible improvement where it helps, while recognising that the person has met the job. If readers consistently miss an important detail, use that evidence in the review.

If the result misses a requirement, identify it. “The total must include the late entries. Could you add them and check against the approved list?” Give the person a chance to fix it when time permits. Redoing the whole task may solve one deadline and leave the learning gap unchanged. If you have to take over to protect a deadline or prevent harm, explain which decision you are taking back and what the person still owns.

Notice when you are changing the task after seeing it

You asked for a summary and expected the same headings you use. The other person wrote a short table. If the table meets the purpose, acknowledge that. If a particular format is necessary because another team imports it, say so and give the specification. Be honest when the requirement was omitted. A good review distinguishes a missed instruction from an instruction you had never given.

Back to contents · Previous chapter · Next chapter

Chapter 5 of 16

Examples from home, school and work

A family member takes over groceries

Leena always buys groceries and makes the list in a particular order. Another family member offers to take over. Leena identifies the items needed for a planned meal, which ingredients have restrictions and the time the shopping should be done. The other person chooses the route and the order of the list. When they bring home a different brand that meets the requirement, Leena can leave the choice with them.

If the person returns without a required item, discuss what happened. Maybe it was unavailable and they did not know which substitution was safe. Agree when to call and what to leave out. That repair gives them more information for next time. It is more useful than deciding they must always shop in the same way.

A pupil lets a partner design their own slide

Maya likes using a particular layout. Her partner uses a different one for the second part of the presentation. They compare it with the assignment. The text is readable and the example supports the claim. The difference can stand. They agree on a common title size and the order in which they will speak. This gives the presentation consistency where it affects the audience.

If the slide exceeds the time limit or leaves out a required source, ask for that change specifically. The partner can make the fix and keep the design. A group can share standards without giving one member ownership of everybody’s method.

A manager stops reopening a finished task

Arun delegates a weekly update and reads every version before it goes out. The person responsible keeps waiting for comments. They agree to use a checklist for required facts and send the update independently when those facts are confirmed. Arun asks to be told if any source is missing or the schedule changes. He can review the process at the end of the month.

If a problem appears, they identify whether it comes from missing information, a skill gap or an unclear checklist. They can adjust that part. The arrangement works when both know what can be done independently and what needs review.

Back to contents · Previous chapter · Next chapter

Chapter 6 of 16

Use three categories when you disagree about the method

Requirements protect an outcome

A requirement could be an approved source for figures, a safe way to handle equipment or a document format another person’s system needs. If a method is required, explain the reason and where the person can check it. “Use the current template because the office reads the fields automatically” gives a clearer standard than “Do it like mine.” The other person can follow a real condition while making choices in other parts.

Check whether you are in a position to set the requirement. A teacher can explain assignment rules. A team member may need to agree a shared style rather than imposing one. A household can discuss what is necessary for a shared space. When authority is unclear, settle who gets to decide before treating your preference as a rule someone has broken.

Preferences can be discussed and traded

You may prefer a room arranged one way because it is easier for you to find things. The other person may have a different preference that works for them. If you both need to use the room, agree the parts that need consistency, such as where shared items belong. Leave separate work areas open to different choices where practical. A shared preference can become an agreement, provided both people know what they are agreeing to.

Say why a preference matters and see whether there is another way to meet the underlying need. “I like the labels facing out because I need to find the supplies quickly” may lead the other person to propose a readable list. Test whether it works. You may keep your own method when you do the work and accept another when someone else does it.

Personal habits can stay personal

Some steps feel essential simply because you have always done them. You may answer messages before opening the main file. Someone else may work on the file first and answer messages later. If the response deadlines and the result are sound, the order may be theirs to choose. Notice when your discomfort comes from seeing the difference rather than from evidence of a problem.

A useful exercise is to name the last time the different method caused a material consequence. If you can identify one, build a check around it. If you cannot, give the other method a trial. You can evaluate what happens at the agreed checkpoint instead of trying to make the work look familiar during every step.

Back to contents · Previous chapter · Next chapter

Chapter 7 of 16

How to hand over a job to somebody who is still learning

Make the first assignment small enough to support

A person learning to run an event may be ready to confirm one room and send one announcement. They may need a more experienced person to handle a larger booking or resolve an access issue. Give them a defined part and explain what they can decide. A smaller handover can make the learning visible. It also limits the cost of an error while you learn how much support they need.

When you give a demonstration, show which parts are flexible. “I do the title first because it helps me organise the material. You can start with the examples.” This avoids teaching a habit as though it were a rule. If the person asks why a step matters, explain the consequence. They are more likely to recognise when a similar situation calls for the same check.

Let feedback lead to another attempt

After a first attempt, name one thing that worked and one requirement to address. If a student wrote a readable slide with a missing source, ask them to add the source and check the next slide independently. If you quietly replace the whole slide, they may never learn which part needed attention. A brief second attempt can help them see how their own method can meet the standard.

If a deadline prevents another attempt now, decide what you will review afterward. You can protect the immediate outcome and give the person a chance to understand the fix later. A handover may need to become smaller next time if the current responsibility was beyond their access or experience. Change the assignment based on what happened rather than making a general judgment about the person.

Back to contents · Previous chapter · Next chapter

Chapter 8 of 16

When you share the result and nobody is the sole owner

Agree how choices will be made

Two family members share a kitchen. One is quicker to start reorganising things. The other discovers their supplies have moved. They can agree which shelves are shared, how often supplies will be replaced and what each person can arrange independently. A conversation about ownership may matter more than a conversation about who is tidier. Once the boundaries are clear, both can choose methods within them.

In a project, shared ownership can include a rule for edits. One person can change their own draft, suggest changes to someone else’s section and ask the whole group before altering the order. If a deadline is close, agree who has final authority and how the decision will be communicated. This helps people understand what is still theirs to do.

Decide what to do if the agreement is missed

If one person does not send the promised update, ask what happened and what the group still needs. The issue may be unclear timing, missing access or a real failure to follow through. State which part needs a remedy. “We need confirmation before the room can be used. Please send it by two, or tell us who can check it.” This keeps the group from taking back every responsibility because one checkpoint failed.

If a pattern continues after a fair handover, adjust the arrangement. You may need to change the owner, give support or choose a different deadline. Explain the reason. A person deserves to know whether the change is due to a capacity limit, a process requirement or repeated missed commitments. A clear account is easier to learn from than a general withdrawal of trust.

Back to contents · Previous chapter · Next chapter

Chapter 9 of 16

A full example from a first handover to a better second one

Maya usually prepares signs for a club event. She asks Dev to do it this time and initially sends him an old file with “Use this as a guide.” Dev keeps the required room numbers and changes the layout. Maya dislikes the layout and begins editing every sign. Then she checks what the event actually needs. Visitors must be able to read the directions, the final room list must match and the signs must be ready by Friday.

They agree to check a sample at the distance a visitor will read it. The sign is easy to read, but one arrow points the wrong way. Dev corrects the arrow and uses the same check for the rest. Maya leaves the layout. At the next event, she sends the current room list, the reading-distance requirement and the approval time. Dev has enough information to own the work. Maya keeps visibility where it matters.

Now change one detail. Suppose the signs must use a required accessibility format or be printed by a supplier with specific dimensions. Maya needs to provide that condition before the work starts. If she forgot, she should acknowledge it and help arrange a realistic revision. A format can become a true requirement when it affects who can use the result. The responsibility for communicating it is part of the handover.

Back to contents · Previous chapter · Next chapter

Chapter 10 of 16

What to do when you are the person receiving too much supervision

Ask which decisions are yours and what evidence the other person needs. “I can send a sample by Wednesday. After you confirm the headings, can I finish the rest without sending each page?” This gives them a way to see the work and makes your independence explicit. If they need to approve more because of a real requirement, ask which step matters and why.

If they change the criteria every time, record what was agreed and ask for the current standard. “I used the format we confirmed on Tuesday. Should I follow this new one for future copies?” If the work is repeatedly reopened without a reason, discuss what the review is meant to protect. You may need a clearer agreement or help from the person who owns the process. Making the job visible can protect both of you.

Back to contents · Previous chapter · Next chapter

Chapter 11 of 16

Review the handover after the result is used

Ask the person who received the work whether it served its purpose. Did they find the required information? Did an important deadline hold? Did the other person have what they needed? These answers tell you more than whether the method matched your usual order. If the result worked, recognise the method that produced it. You may find a useful idea you can borrow.

Then ask the person doing the work where they needed more information and where they could have used more room. Adjust one part for the next handover. Perhaps the first sample was helpful and the daily messages were unnecessary. Perhaps the deadline was clear and the authority to contact someone was missing. A short review can make the next handover more dependable without keeping both people tied to the same work.

Back to contents · Previous chapter · Next chapter

Chapter 12 of 16

Practise on one task with a low cost of correction

Choose a task somebody can realistically own. Write the result, the requirements and one checkpoint. During the work, notice when you want to intervene. Ask whether the issue threatens a requirement or looks different from your method. If it only looks different, wait for the checkpoint. If a genuine condition has changed, explain the new fact and decide together what needs to change.

Afterward, write what you learned about the result and the other person’s method. You may discover that they needed a resource you forgot to share. You may find that their approach worked better than expected. You may also find that this task needs closer review. The aim is to match oversight to the work, with enough room for another person to make meaningful choices.

Back to contents · Previous chapter · Next chapter

Chapter 13 of 16

When you need to change the agreement during the work

A genuine new fact may justify changing the task. The room may become unavailable, an approval rule may change or another person may need a different handover time. State the new fact, explain which part it affects and ask what adjustment is possible. “The supplier moved the collection time to noon. Can you still handle the booking, or should we move that part to another person?” This changes the task openly without treating the earlier plan as a mistake.

If you simply saw a method you would not use, wait for the agreed check. Ask whether it still meets the standard. If you raise a preference, explain that it is a preference and give the person room to disagree. A reliable handover allows both people to tell a real change from a late attempt to regain control.

Back to contents · Previous chapter · Next chapter

Chapter 14 of 16

Give feedback without becoming the second owner

You can point out a problem without directing every action required to fix it. Name the result you need. “The sign should be readable from the entrance.” Ask what the person wants to try. They may adjust the size, position or wording. If one solution affects a requirement, explain it. Otherwise let them choose and evaluate whether the result works.

When the person has resolved the issue, close the review. “That meets the requirement. Please send the final version.” This gives them a clear point when they can proceed. Reopening an approved result for a series of preferences can make ownership hard to use. If a genuine issue comes to light later, explain what changed and why it matters.

Back to contents · Previous chapter · Next chapter

Chapter 15 of 16

Agree on a fallback before anyone needs it

A backup can make a handover easier to leave alone. “If you cannot confirm the room by Thursday, tell me and I’ll ask the venue team” gives both people a specific trigger. The other person can continue until the trigger occurs. You know when you will be needed. If the task goes well, the fallback can stay unused.

For a small household or school job, the fallback may simply be another time or a person to ask. For a larger responsibility, check that the backup has the authority, access and time they would need. A name alone may give false confidence. The useful fallback covers the actual problem and leaves ordinary work with the person who owns it.

Tell the person when the fallback stops being available so they can plan around it.

Back to contents · Previous chapter · Next chapter

Chapter 16 of 16

Frequently asked questions

Is it controlling to care how work is done?

Some methods matter because of safety, accessibility, rules or dependencies. Explain those requirements. Check which steps are preferences and give the other person room to choose there.

How can I stop checking every step?

Pick a checkpoint that can reveal a material problem in time to fix it. Agree what the other person will share and which changes they should flag earlier.

What if the person is inexperienced?

Give them a task that fits their experience, the necessary information and an example if useful. Agree when to review a first attempt. Adjust the level of support as they show what they can do.

What if I can do it faster?

You may be faster at a familiar task. Check whether this instance genuinely requires you to do it and whether another person needs room to learn or own the work. A short handover can make future tasks easier to share.

Back to contents · Previous chapter · Sources and next reading

Sources and next reading