You will be able to decide when to keep trying alone and when to ask, and prepare before asking.
Wei Jie started as a junior engineer at a facilities management firm two weeks ago. On Tuesday morning he was asked to pull last year's maintenance costs for one of the firm's buildings in Paya Lebar. He couldn't find the right report. He tried the shared drive, then three spreadsheets, then a different shared drive. He didn't want to look slow, so he kept going. At 5pm he asked his senior, who replied in two minutes: "It's in the finance system, not the drive. Here's the link."
He lost a day. His senior would happily have spent two minutes on it at 10am.
Most people make one of two mistakes. Some ask too early, before they've looked, and end up asking questions the team wiki already answers. Others, like Wei Jie, ask too late, after hours of being stuck. Both are fixable with a simple routine.
Before you ask anyone, spend a few minutes checking where the answer usually lives. In most workplaces that means the shared drive, the team wiki or intranet, past email threads and the chat history. Search the chat for the name of the report, the error message or the client. Someone has often asked the same question before, and the answer is sitting in a thread from six months ago.
This does two things. Often you find the answer and save everyone time. And when you don't, you can say where you looked, which makes your question better and shows the person you're asking that you've done your part. Lesson 4.2, Ask with context: goal, what you tried, where you are stuck, builds on exactly that.
Don't let the search take over, though. Five or ten minutes of looking is usually enough to know whether the answer is easy to find.
The second habit is to decide in advance how long you'll stay stuck before asking. A stuck limit is a time you set yourself, after which you stop trying alone and ask for help.
For a routine task, something your team does often and you're expected to learn, 30 minutes is a reasonable starting point. For harder or newer work, you might allow longer. For anything urgent or blocking other people, it should be much shorter, sometimes just a few minutes.
The number matters less than having one. Without a limit, being stuck has no natural end. You keep thinking the answer is one more search away, and before you notice, the morning is gone. With a limit, you know that at 10.30 you'll ask, and that frees you to work properly until then.
Set your limit by the cost of being stuck, not by how embarrassing the question feels. A question that seems basic is often the one with the quickest answer.
Many people, especially early in their careers, hold back because they worry asking makes them look less capable. In most teams the opposite is true. What managers notice is work that comes back wrong, or late, because someone guessed instead of checking.
Think about what the delay actually costs. If you spend a day stuck and then ask, the team has lost a day. If you guess and get it wrong, the team loses the time you spent plus the time to fix it, and sometimes a client or a deadline as well. A two-minute question at the right time is the cheapest option on the list.
In many Singapore workplaces there's an extra layer of hesitation about troubling someone senior, or about seeming not to know. It helps to remember that your manager hired you knowing you'd need to learn the job. A well-timed question shows judgement. Being stuck for a day in silence doesn't.
If you're unsure what your own manager prefers, ask them once: "When I'm stuck, would you rather I come to you, or try someone else on the team first?" Lesson 3.3 covered how to agree this kind of thing.
When you do find an answer, whether by searching or asking, write down where it was. It can be a line in a personal note: "Maintenance costs by building: finance system, Reports, Facilities, filter by year." Or, better, add it to the team wiki or reply in the original chat thread so the next person's search turns it up.
This helps you as much as anyone. In six months you'll need the same report and won't remember where it was. It also helps the next new joiner, who will be in Wei Jie's position soon enough. Teams where people leave a trail like this get faster over time, because the same question doesn't have to be answered twice.
You probably already have a sense of when you've been stuck for too long, but it's rarely a number. Choosing one, and noticing when you pass it, is the activity below.
Write down your own stuck limit for routine tasks and apply it to the next problem you get stuck on.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).