You are given a task and do not know where to start. You could look for instructions, try your own approach, or ask an experienced colleague. Ask too soon and you may interrupt someone unnecessarily. Try to handle everything alone and you could lose an entire morning, only to discover that you were missing one piece of information.
Problem-solving is not just about finding the right answer. It also means choosing the best way to get there. Sometimes a small independent test is the right move; at other times, you need to ask a question, verify a condition, or have a brief consultation. The key is not whether you are independent enough, but what is stopping you from taking a sensible next step.
First, distinguish a problem from an unclear brief
Imagine being asked to “prepare a better results overview.” You could start building a spreadsheet, testing charts, and collecting data. But “better” can mean different things to different people. Perhaps the overview should be shorter, more accurate, or make decisions easier.
In that situation, you do not yet have a technical problem to solve. You are missing a definition of the expected result. Trying to solve the task before getting one could lead to work that has to be redone.
Before looking for a method, complete these three sentences: “The result should be…”, “It will be finished when…”, and “I do not yet know…”. If you cannot complete the first two, asking the person who assigned the task to clarify it may be more useful than trying another approach.
Identify what kind of support you are missing
“I’m stuck” can describe several different situations, and each calls for a different response. You may be missing a fact, a skill, a broader perspective, or the authority to make a decision. If you do not distinguish between these gaps, you could ask the wrong person or spend time learning something you do not actually need.
| What you are missing | How to recognise it | A useful first step |
|---|---|---|
| Information | You know what you want to do but do not know a fact or rule | Find a reliable source or verify the information |
| A skill | You understand the goal but do not know how to carry out the necessary steps | Try a small example or ask someone to demonstrate |
| Perspective | You have several workable options but cannot judge their likely effects | Consult people affected by the outcome |
| Authority | You can suggest a solution, but the decision is not yours to make | Ask the responsible person for approval or a decision |
| A clear goal | It is not clear what successful completion means | Clarify the brief and expected result |
A complex problem may involve more than one of these gaps. Start with the one that is blocking the others. For example, learning a new tool is unlikely to help if nobody has confirmed that it should be used at all.
Try things yourself when they are safe to undo
Trying your own approach makes sense when it is quick, low-cost, and has limited consequences. You could test a document format on a copy, practise a new workflow with sample data, or create a simple draft without affecting anyone else.
It is different when a mistake could change live data, put privacy at risk, cause financial loss, or disrupt other people’s work. Experimenting is not a good way to prove your independence in those situations. The more serious and difficult a consequence is to reverse, the sooner you should check the approach.
Before you try anything, ask yourself: “What would happen if I got this wrong?” and “Could I safely undo the result?” If you do not know, that does not automatically mean you should stop. It means you should first understand the risks or limit your test to a safe part of the task.
Set a reasonable limit on how long you search alone
An open-ended plan to “keep trying until I figure it out” may work for a simple task, but it can consume a lot of time when the problem is more complicated. Before you begin, decide what you need to find out and when you will assess whether your approach is making progress.
A practical rule might be: “For the next twenty minutes, I’ll check the input data and test one solution on a copy. If I still cannot identify the cause, I’ll ask for a consultation.” Twenty minutes is not a universal limit. A minor issue may need only a few minutes, while a creative task may benefit from a longer stretch.
The important thing is to set a point at which you decide whether to continue in the same way. Repeating the same unsuccessful step without gaining new information may not be persistence.
Ask for help in a way that shows where you are stuck
“Could you help me with this?” leaves much of the work to the other person. They have to find out what the task is, what you have tried, and what you need from them. You may not always have time to prepare a detailed explanation, but a few specific sentences can make a consultation much more useful.
For a routine work problem, you can use this structure:
- Goal: “I need to submit an overview using the same rules as last month.”
- Where you are stuck: “Two sources show different numbers of records.”
- What you have checked: “I checked the date range and the filters used.”
- A specific question: “Which source should this overview use?”
- Timing: “I need to know before I submit it tomorrow morning.”
This is not a request for someone to do the entire task for you. It is a request for the specific information you are missing. If you need someone to demonstrate a process, say so directly: “I understand the basics, but I’m not sure how to carry out this step correctly. Could you show me once?”
Do not confuse advice with handing over responsibility
When a problem has more than one reasonable solution, colleagues or people close to you can help you understand the consequences of each option. But they may not share your priorities. Their advice may reflect different experience, work responsibilities, or willingness to take risks.
It helps to distinguish between three questions: “What do you know about this?”, “What would you recommend?”, and “Who has the authority to decide?” The first asks for information, the second for an opinion, and the third clarifies responsibility. The answers may come from different people.
If you have the authority to decide, you can listen to different perspectives without needing unanimous agreement. If a project lead or another responsible person must make the decision, present the options and their consequences instead of quietly assuming you can choose on your own.
When someone rejects your idea, look for the specific obstacle
“That won’t work” is an assessment, not yet useful feedback. Rather than immediately defending the idea or giving up, try to find out what is behind the response.
You could ask: “Which part seems unrealistic to you?” or “What would need to be true for this to work?” You may uncover a genuine technical or time constraint. Alternatively, the other person may simply prefer a familiar way of working.
If the objection identifies a real obstacle, revise the proposal and check it again. If it remains a general impression, ask for a specific example or suggest a smaller test. Being open to criticism does not mean treating every rejection as proof that an idea is wrong.
A project example: when the numbers do not match
Imagine you are preparing a monthly overview for your team. Two internal reports show different numbers of completed tasks. Your manager expects the results the next day, and you have three options: guess which number is right, spend all afternoon investigating the system, or message a colleague.
You can break the situation into a few decisions. First, confirm how the overview defines a completed task. Then check the date and filters using a small sample. The discrepancy remains, but you do not have access to the rule that determines how one of the reports calculates its figures.
At that point, further independent testing is unlikely to reveal the missing information. Ask the person responsible for the reports exactly how the figures are defined. While you wait, you can complete the parts of the overview that do not depend on the disputed number.
Once you receive an answer, record the explanation in the workflow so the same uncertainty does not cost you another hour next time. Success does not mean doing everything without help; it means recognising the limits of the information you have.
Getting stuck does not always mean you lack ability
If you repeatedly cannot make progress, it is easy to blame yourself. But sometimes the missing pieces are access, budget, time, cooperation from other people, or a management decision. Improving your skills alone will not remove those barriers.
Separate what you can improve personally from what the working environment needs to provide. You can learn to prepare clearer supporting information, but you cannot approve someone else’s authority. You can suggest a more efficient process, but you cannot indefinitely make up for missing time or capacity.
Asking for help may therefore mean seeking advice. In other cases, it means identifying an obstacle you do not have the authority or ability to remove. That, too, is part of responsible problem-solving.
Use a quick check before choosing your next step
The next time you get stuck, ask yourself these five questions before opening another guide or sending a message:
- Do I know exactly what needs to be completed? If not, clarify the goal.
- What, specifically, am I missing? A fact, a method, a perspective, authority, or capacity?
- Is it safe to try a small step? If so, set a limit for the test.
- Who can provide what I am missing? Choose a source based on the question, not simply the first person available.
- What will I do once I have an answer? Agree on a decision or the next step you can verify.
When a suitable situation comes up, treat it as a small opportunity to practise this skill. Do not judge yourself by whether you asked for help or managed everything alone. Instead, consider whether you chose an approach that matched the information, time, and level of risk involved. That choice can determine whether you solve the problem efficiently or get stuck unnecessarily.
