CORE COURSE / 078

Asking for Help Instead of Doing Everything Alone

Ask for specific help at the right time while keeping ownership of your responsibility.

What you will learn

  • Identify whether you need information, feedback, labor, or support.
  • Make a bounded request that is easy to understand.
  • Agree responsibilities and close the loop.

Name the kind of help missing

Being stuck does not always mean you need somebody to take over. You might need an explanation, access to a resource, feedback on a draft, a second pair of hands, or emotional encouragement. Identify the missing contribution before choosing whom to ask. A knowledgeable colleague may answer a technical question but be unable to provide an afternoon of practical labor. A friend may listen supportively without being qualified to advise on a specialized decision.

Try enough to describe the obstacle, but do not make suffering alone a prerequisite for asking. If a deadline or another person's work depends on the answer, early help may be more responsible than an extended private struggle. State what you have tried when it will help the other person understand the problem.

Make the request concrete and bounded

Include the context, the specific request, the time needed, and the deadline. 'Could you spend ten minutes checking whether these three instructions are clear to a beginner by Friday?' is easier to assess than 'Can you help with my project?' Provide the relevant material in an accessible form and avoid requiring the helper to reconstruct your whole history before understanding the question.

Make it possible to decline or suggest another time. A request is not clear consent to unlimited work. If you need a large contribution, say so rather than disguising it as a quick question. Respect confidentiality and permissions when sharing files; a helper does not automatically need access to every personal or organizational detail.

Agree what remains your responsibility

When somebody offers assistance, confirm who will do what and how the result will be used. For example, a colleague might explain a calculation while you complete and check the remaining entries. A family member might collect a parcel while you arrange the collection details. This prevents a vague request from turning into conflicting expectations about ownership.

If the help involves learning, ask for enough explanation to become more capable next time. You can watch a demonstration, repeat the process, and check your understanding. The immediate problem matters, but repeated dependence caused by never learning the procedure can create avoidable strain. Some ongoing assistance is entirely appropriate; independence is not the only valid goal.

Close the loop and adapt

Thank the person specifically and tell them what happened with their contribution. If their review helped you correct a confusing step, say which step and how it improved the result. Follow agreed deadlines and let them know promptly if circumstances change. A clear ending helps people understand that their effort was useful and that the request has not silently expanded.

If someone cannot help, separate their availability from your worth or the legitimacy of your need. Try another suitable person, a formal service, or a smaller request. When the same need keeps recurring, look for a durable arrangement such as training, shared documentation, or a regular division of responsibilities. Sustainable support is built through clear expectations rather than repeated last-minute rescue.

FICTIONAL PRACTICE CASE

A fictional everyday example

Malik, a fictional new bookshop employee, is confused by a stock-return form. He keeps guessing because he does not want to inconvenience a senior colleague. After two errors, he asks for a ten-minute demonstration using one example and brings the exact field he does not understand.

The colleague explains that field, watches Malik complete the next example, and points to the written instructions. Malik finishes the remaining forms and reports that the issue is resolved. His request saves rework and gives him a method he can reuse.

Put the lesson into practice

  1. Write the exact missing contribution.
  2. Choose someone whose role and knowledge fit the need.
  3. Draft a request with context, scope, timing, and room to decline.
  4. Agree ownership and report back after using the help.

Check your understanding

Which request is easiest to respond to responsibly?

Further reading

My notebook