Ask First vs. Don’t Ask, Just Figure It Out

When you’re working in a company, especially as a new hire, there are two phrases that can be incredibly confusing: “Ask before you do it” and “Don’t keep asking—just figure it out.”

You ask because you don’t know, and they tell you not to ask. Then the next time, you struggle on your own, check everything you can, and move forward only to hear, “Why didn’t you ask first?” For a new employee with no decision-making power and little experience, it’s maddening. What exactly are you supposed to do?

The truth is, if you don’t want to hear either of those complaints, there is a kind of baseline to look for. This is something I’ve picked up from the things supervisors have actually vented to me about.

First, the psychological meaning behind “Ask before you do it” is this: “If you mess this up, I’m the one who may be held responsible, so get my approval.” Employees who work with a pure focus on the task itself and think only about finishing it cleanly often miss this point. Honestly, even understanding that you’re supposed to work with that in mind is still frustrating and hard to accept. But office life is not driven by “work” alone. There are countless interests tangled together, and relationships with people play a huge role.

Take this example. Let’s say a team member handled some documents on their own and sent them out externally. If nothing unusual happened, the company would probably not have paid much attention. But then the exact same documents are sent the exact same way, and this time something comes up. A rule changes, or the vendor changes its request.

Then everything gets stuck somewhere unexpected, deadlines start slipping, and before long it turns into a report to management. If you force it through without reporting it, the situation can become even bigger. And once that dreaded reporting begins, what everyone expects happens: the criticism starts rolling downhill. A supervisor who had paid no attention to that same document before suddenly starts shouting, “Why on earth did you do it that way?” at every step, questioning the handling process and bringing up the “manager’s lack of judgment” for not reviewing it properly. After going back to the office, that manager ends up unloading on the person in charge: “Please just ask first.”

On the other hand, “Don’t ask—just figure it out” comes up in the exact opposite situation. When you’re making and sending out the same document, there have been no problems and no real interest before, so the manager wonders why you keep asking about something so easy. From the team member’s point of view, they’re simply asking for confirmation according to procedure, but from the supervisor’s perspective, it just feels annoying and unnecessary. They’re probably thinking, “You still can’t handle something like this on your own?”

There’s another case too. It’s when the task has nothing to do with the supervisor’s own performance, and even if something goes wrong, it seems like only the person doing it will be held responsible. To put it bluntly, it means: “Don’t drag me into it—just handle it yourself.” A team member who senses that kind of tone can feel deeply let down, and the emptiness can be enough to make them feel burned out on the spot.

In the end, both situations come from the supervisor’s own judgment, so there is no single manual-style answer that says, “If this happens, do that.”

Still, if I had to draw a practical line, it would look something like this.

If you’ve done the task before and your boss does not seem especially interested in it, go ahead and handle it the usual way, then make sure you leave a post-report. If you’re sending it by email, put your supervisor on CC. Whether they read it or not, there’s a record. If it’s by mail or fax, scan the document and keep it as a PDF, then send a quick line in your weekly report or messenger saying, “Completed.” The supervisor doesn’t have to respond, and because they were informed, it’s harder for them to raise the issue later.

On the other hand, if it’s your first time doing the task, or if a problem could create unclear responsibility later, build in a safety net with a midstream update. Gather as much information as you can, prepare a draft, and report it like this:

“I’ve drafted this, but there are a few points I can’t confidently decide on myself, so I’m reporting it first. What direction would you like me to take?”

From the boss’s point of view, they don’t have to do much, but they still feel like they’re in control. When work is carried out after that kind of instruction, you’ll hear a lot less of the “You should have asked first” complaint.

Of course, these two methods won’t be perfect in every situation. In the end, this is about dealing with people, so reactions vary widely depending on the person. But if you build in some safeguards and sometimes ask, sometimes don’t, and move things forward step by step, the number of confusing scoldings you hear will noticeably decrease over a month or two.

And once the two of you start getting used to each other, at some point your boss will probably think to themselves:

“We work pretty well together.”