Skip to content
Interface language: English
Imperium / Signal

Ask for help before an uncertainty becomes a whole project

Explain where a task is stuck, what kind of help you need and who will continue the work after an answer.

Article language: English

Fine white strands cross a wooden piece with gold-coloured teeth on a workbench.
In this article

“Have you got a minute?” The person asked does have a minute. Twenty minutes later, they also have an open file, a new responsibility and a vague feeling that they have just taken over somebody else's task. The person asking only wanted to understand one customer comment. Help arrived without a request for a handover, complete with delivery.

Suppose an employee of a fictional workshop-booking company is stuck while moving a participant to another group. They understand an ordinary date change. They do not know whether a note in the correspondence concerns one participant or the whole booking. No mistake has occurred yet. There is an uncertainty on which the next action depends.

They can guess, hand the whole case to a more experienced person or ask for a particular kind of help. The third choice requires them to describe where their understanding stops. A short account should let the other person respond without reconstructing the entire booking from the beginning.

Locate the uncertainty in the task

A useful request shows the goal, where work stopped and the kind of answer needed. In our example, the employee says: “I want to move one person. But the customer's message uses the plural. I don't know whether to clarify the number of participants or whether there is an earlier confirmation I haven't found.” The recipient can recognise the problem before opening the entire booking history.

“I don't know how to do it” covers many more possibilities. It may concern operating the software, the meaning of the request, permission to make a change or missing data. Each leads to different help. Name the distinction you can already see, even if you do not know how to resolve it. That can be useful work completed before asking.

Add what you have checked, but do not account for every minute of effort. “I checked the confirmation and the transfer instructions; both concern one person” gives a basis for continuing. “I've been sitting with this all morning” shows the cost, but does not help choose a source or specialist. You do not have to prove you have suffered to deserve an answer.

Be careful with material sent alongside the question. The recipient should get the part needed to understand the case and access to the right context in the agreed place. Pasting an entire correspondence thread into a random channel can make the work harder and widen its audience. Access rules remain part of how an organisation works, even when someone wants to help quickly.

Do you want a pointer, shared reasoning or a handover?

These three requests have different effects. A pointer can direct someone to the right instructions or name a missing piece of information. Shared reasoning means examining part of the task with someone who can help choose the next move. Taking over changes who performs the work. That change should not happen merely because the expert reached for the mouse faster.

Komissarouk and Nadler's 2014 study distinguishes asking in order to learn how to solve a problem from asking another person to solve it. We use that distinction here without assigning psychological traits to employees on the basis of one message. Both forms can occur in actual cooperation.

For the booking, the employee might ask: “Help me decide what to clarify with the customer; I'll continue handling the case myself.” That differs from “Please take over this booking because I don't have access to the necessary system today.” In the second case, the handover may be justified by how work is organised. There is no reason to call it a failure of independence when the conditions for doing the task have actually changed.

The person helping should check the scope too. “I can show you where to check the earlier confirmation, but I cannot decide the number of people on the customer's behalf” keeps the limit of their knowledge clear. If they propose taking over, they should name why and what they will hand back. Otherwise a request for an explanation can quietly become a new division of duties.

Research by Liu and colleagues on different forms of asking for help at work included a field study and three experiments using scenarios. The authors analysed different relationships between these forms and assessments of competence and job performance. It does not justify a company rule saying “never ask someone to take over”. It shows why the kind of help should be recognised instead of counting all questions as the same behaviour.

The right person is not always the nearest one

The colleague who is most available may know the software but not the agreement with the customer. The customer contact may know the history but lack permission to make the change. A manager may decide on an organisational exception but still not know what the recipient wanted. The question should reach the expertise needed at that point in the task.

In the fictional company, the employee first checks whether the uncertainty concerns the transfer instructions or the customer's intention. If the instructions clearly describe one person and the doubt lies in the message, the next move may be to clarify the request. An internal vote among the most experienced colleagues will not reveal the sender's intention.

If you do not know who can help, first ask for the right person. That is a smaller request than sending the entire case to a broad group. It can also expose a missing organisational arrangement. If nobody can identify the owner of an important decision, the company has a problem beyond one employee's ability to ask questions.

The five Signal articles linked below are in Polish.

When a company depends on one person, every difficulty may end up with the same expert. The Article about dependence on one person (in Polish) explores this risk. Encouraging everyone else to be more independent will not fix that. Check what only this person knows, what only they may approve and what others could learn. Those are three different reasons for returning to the same desk.

Aeneia conceptual photography

When an expert is the right recipient, prepare the question so they can assess a particular part. The Guide to giving feedback on a specialist’s work (in Polish) also distinguishes an observation from a proposed solution. You do not need to know their whole field to describe your own difficulty clearly. You do need to leave room for them to correct an assumption.

Urgency comes from the effect of waiting

“Urgent” does not say what will happen without an answer. In our example, a participant is waiting for confirmation of their group before a workshop begins. That differs from organising a booking for next month. State the event and the point after which a missing decision will change the work. The recipient can then weigh the request consciously against their own commitments.

Not every uncertainty should interrupt someone else's task immediately. If postponing this part does not block the remaining work, you can do another part and agree when to return to the question. If the next action would depend on an unconfirmed assumption, do not pretend to make progress. Reasonable independence includes recognising when to stop, not only the ability to keep clicking.

An organisation should establish a route for a genuinely urgent question. A message in a channel nobody is watching does not become an escalation just because it has an exclamation mark. Is someone on duty? Must receipt be confirmed? What happens if no answer arrives? The details depend on the service and need to be known before a difficult case.

Consider the cost of interrupting a team’s work alongside the cost of waiting. The Article on interruptions (in Polish) examines that trade-off. A ban on questions may reduce notifications while concealing uncertain decisions. Automatically calling an expert for every case, by contrast, takes time away from teaching others. A message count alone cannot determine that balance.

A short answer should leave room to return

Suppose the customer contact replies: “Check Monday's message; the customer separated the booking then.” The employee finds it, but it concerns a different workshop. They should not treat the pointer as confirmation just because it came from an experienced person. They return with a specific point: “I found that message, but it shows a different date. Did you mean another agreement?”

This continues the help rather than starting a new question from zero. It shows the action taken and why the answer did not close the case. The person helping can correct their pointer without reconstructing the whole thread. The person asking remains involved in the reasoning instead of waiting for a complete result from someone else.

Once the issue is resolved, confirm the next action. “First I'll clarify the number of people with the customer; until then I won't change the group” shows how the help was used. A formal record is not necessary. One sentence is enough for the other person to notice whether their advice was understood as intended. If the task is handed over, also agree who continues the contact.

If an actual error comes to light, the response needed changes. A clear report including the event and its effect is useful; the Guide to reporting errors (in Polish) discusses what to include. A question before an action and a report after an event should not be put in the same category. Otherwise the company will treat every request for clarification as proof that someone has already broken something.

When the answer does not arrive before the deadline

Return to the employee handling workshops. Suppose the customer contact is absent and the customer expects confirmation today. Sending the same question to five more people will not give the employee certainty. They can, however, tell the person leading customer service which decision is missing and what needs to be communicated to the customer. From the customer's side, waiting for clarification should not look like a completed change.

If the company has an agreed approach for when no answer arrives, apply it to this case. If it does not, the appropriate person should decide about further contact or pausing the action. The person asking should not invent a new rule merely because their working day is ending. That is the difference between performing a task within one's role and making a decision outside it.

When the customer contact returns, close the request too. A short note such as “The customer clarified the scope; I no longer need a decision” prevents unnecessary reconstruction of the case. If the question was passed to someone else, say so. Help has a beginning and an end. Without that closure, several people can remain busy with the same uncertainty long after it was resolved.

A recurring question may reveal a needed change

If several people ask about the same distinction, check the common source. Perhaps the instructions describe only the ordinary case while the offer lets customers order other variants. Perhaps a field in the tool has changed. Or perhaps the organisation never agreed who confirms an exception. A series of questions does not always mean employees have failed to read the material.

Useful cases can be discussed when the purpose is to learn together from work being done. The Article on communities of practice (in Polish) explains this way of sharing experience. That does not mean turning the group into a mandatory help desk for every booking. An immediate answer needs an identified recipient; a later shared conversation can draw something useful from the case for others.

For questions about an AI output, keep the input, draft answer and point of doubt in the approved workflow. “The model answered badly” may be too broad. It may have identified the wrong record, added information that was absent or used an old source. Each diagnosis calls for a different check, and an expert should not have to guess which occurred.

At Aeneia Audit, a particular use of AI can be traced and the sources, checking rules and human involvement identified. An example of an unresolved question helps show where the current process needs clarification. The company remains responsible for assigning work and ensuring the availability of people who provide support.

For your next request, try naming the kind of help expected before sending the entire case. The recipient can decline to take over while still offering a useful pointer. They may also conclude that their direct action really is needed. In both situations, cooperation starts with a shared understanding of the request, not with who reaches the keyboard first.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear