CareerEvents


Project maintained by HealthyGamer Hosted on GitHub Pages — Theme by mattgraham

The Magic of “I Don’t Know”

Sometimes, just saying “I don’t know” and moving on doesn’t work at the moment. Sometimes action is required immediately, and we must make our best guess and implement it. Other times, there is no way to know the answer, so we pick an answer and move on.

Most work situations aren’t like this. Taking a bit of time to research an answer, asking someone with the required knowledge, and acknowledging that lack of information are all options available. They result in better outcomes, but we still don’t always use them.

Why is This so Hard?

Why is it so hard to admit we don’t know something? After all, no one knows everything, so this should be simple, right?

External Pressure

Internal Experience

While the source often comes from external issues, this can create an internal experience that is difficult to overcome.

Concequences

What happens when we pretend to know things? Sometimes nothing, which is why it’s such a common strategy. Either the consequences of getting it wrong are minor, or we guess right. The pressure to answer is relieved, and we go on with our lives. The most significant issues occur when we get it wrong or pick a bad solution that might still kind of work. The direct result is one issue that has to be resolved, but it isn’t the only one.

When we consistently pretend to have all the answers and keep making mistakes, it will eventually erode our colleagues’ trust. How are they supposed to take your advice when there’s such a high chance of it being either useless or outright destructive? Even when you do know what to do, they won’t be able to trust that your information is accurate.

We also rob ourselves of opportunities to learn the answer when we fake knowledge or experience. We’ll discuss this later, but one of the best ways to handle these situations is to defer answering until you get more information. Then the next time the question comes up, you will know the answer, and things will move more smoothly than if you kept getting it wrong.

Creating a Culture Where This is Acceptable

Before we get to the practical “how-to” part, I want to stop for a minute and talk about some ways to create a culture within the workspace that allows “I don’t know” as an answer to questions.

Saying “I Don’t Know” in Corporate

How we talk at work often differs from how we speak in other aspects of life. A direct “I don’t know” might work okay, but it creates a new problem for the person to solve. Instead, providing a possible way to gather the info needed alongside your response establishes a path forward.

A basic outline of responding has three parts that you can tailor to your situation:

  1. Be upfront with your current level of knowledge. You might have no idea, but it’s common to know part of the answer but not the whole thing. Part of gaining confidence in your skills involves understanding your limitations, which shows when you answer this way.
  2. Provide potential next steps. If you need to do something, try to give a due date. Knowing what to expect will make the other person more comfortable not having an immediate solution.
  3. Follow through on anything you agreed to. If you said you would email them by tomorrow afternoon, send an email. It may just be that you need another day, but it builds trust that they will get an answer and makes them less likely to pressure you for an immediate response in the future.

Examples

Here are some examples of what those first two parts might look like:

Wrapping Up

Admitting to not knowing things is a skill that takes practice, and it’s not easy. However, it’s incredibly freeing to feel like you don’t have to hide any information gaps from your coworkers. That short-term discomfort pays off massively in the long term as the quality of our work improves and our colleagues learn to trust our answers.