"I Didn't Know" Isn't an Answer Anymore
A director signs off on a project plan that ignores a tool the company already licenses. A manager tells her team no one internally has done this kind of analysis before, when someone two floors down did it eighteen months ago. An employee waits three weeks for a decision that a five-minute search could have made for himself.
None of them lied. They just didn’t know. For most of history, that was a complete defense. It isn’t anymore, and most people haven’t updated their behavior to reflect it.
Approximately 1,800 words · 9 minute read
Published September 3, 2026
The Excuse That Used to Be True
Not knowing used to be a legitimate state. Information was expensive to find, gatekept behind credentials, or simply too slow to reach the person who needed it. You could work in a building for ten years and never learn what the team on another floor was building, because there was no reasonable way to find out short of asking the right person at the right happy hour.
That was real friction, and it earned real sympathy. “I didn’t know” was an accurate description of the world.
The friction is mostly gone. What used to take a phone call, a favor, or a research trip now takes a prompt. The gap between not knowing and knowing has closed from days to minutes, and it happened fast enough that most organizations still run their expectations, and their excuses, on the old timeline.
Where the Question Goes First
A 2026 global survey from MyIQ found that nearly three-quarters (74%) of employees who regularly use AI now direct questions to a chatbot they would previously have asked a colleague. That’s become the default first move for most of the workforce that has adopted these tools at all. Adoption itself is no longer rare: KPMG’s 2025 American Worker Survey found nearly nine in ten workers (87%) now use AI at least weekly, with over half using it daily.
Put those two numbers together and the shift is obvious. The habit of not knowing, and quietly staying that way until someone happened to explain it, is disappearing across the entire workforce, not just the technical corners of it.
Something real gets traded away in the process. The same research found that around half (48%) of workers now report fewer spontaneous conversations during the working day since adopting AI as a default first stop. That’s a genuine cost, and it’s happening regardless of whether any individual leader or contributor wants it to. The more useful question is what obligation that creates now that it’s already here, not whether the shift itself is good.
It Isn’t Just the Office
This pattern isn’t confined to the workplace. It’s a human one, and the office is just where it happens to have a budget attached.
Not knowing how to cook a dish, fix a running toilet, or get a wine stain out of a couch used to mean a cookbook, a call to a parent, or a patient afternoon with a library book. Now it means thirty seconds of typing. Aviva’s 2026 research found that half of Brits have already used AI for home repairs like hanging a picture frame, unclogging a drain, or fixing a leaky tap, and 70% said the AI-guided attempt actually worked.
Nobody’s writing a strategy memo about their leaky faucet, but the pattern running through it is identical to the one running through every section above. The cost and effort of finding out, the thing that used to make “I didn’t know how” a reasonable, sympathetic sentence, has quietly collapsed in the kitchen and the garage right alongside the boardroom. The stakes are smaller at home, which almost makes it a cleaner example: nobody has to overthink a picture frame the way they might overthink a headcount decision, and yet the same twenty-minute search that used to feel unnecessary now feels obvious.
If the excuse is gone at home, where the only thing at risk is a Saturday afternoon, it’s a lot harder to argue it still holds up at work, where the stakes are usually higher.
For Leaders: The Capability You Didn’t Know You Had
Leaders have a specific version of this excuse, and it’s an expensive one.
TalentLMS’s 2026 Skills Visibility Report found that nine in ten managers (90%) say they understand their team’s skills, while only 69% of employees agree. That twenty-one point gap has a real price tag attached: half of respondents say their company hires externally for skills that current employees already have.
That statistic used to have a built-in excuse. Skills inventories were manual, out of date the week they were compiled, and buried in HR systems nobody checked before a hiring decision. That excuse is thinning out fast. A leader can now ask a direct question, of an internal tool, a search system, or the team itself, and get a real answer about what already exists in the building, in less time than it takes to write a job requisition.
“I didn’t know what my team was capable of” used to describe a genuine information gap. Increasingly, it describes a question that was never asked because asking used to be expensive, and the leader hasn’t noticed that it no longer is.
For Contributors: The Asymmetry That Closed
Contributors have historically operated at an information disadvantage relative to leadership. Leaders had context: the strategy conversations, the budget realities, the political map of who owned what. Waiting to be told, or routing everything upward before acting, was often the rational move, because contributors genuinely couldn’t verify things for themselves.
That asymmetry has narrowed more than most contributors realize. McKinsey’s 2026 State of AI Global Survey found that about half of respondents say AI has helped them make better decisions, an effect the survey found holds consistently across organizational levels, not just among executives with more context to draw on. Contributors can now independently verify what’s true, what’s possible, and who else has solved a similar problem, without waiting for someone above them to explain it.
“I didn’t know that was an option” and “I didn’t know who to ask” used to describe a real ceiling. Increasingly, they describe a choice not to check.
A manager’s judgment and the context that comes from experience still matter. But the default posture of waiting to be told, when the answer was reachable independently, is no longer the safe or neutral choice it used to be.
The Excuses Every Org Has Heard
The classic version of “I didn’t know” lives in a specific set of phrases, and every large organization has heard all of them:
- “I didn’t know who to talk to.”
- “I didn’t know that was an opportunity.”
- “I didn’t know we already had this capability.”
- “I didn’t know someone else solved this last year.”
These aren’t new problems. What’s changed is how cheap they are to close. Mapping who owns what across a forty-thousand-person org used to require actual detective work, favors called in, and a lot of institutional memory that lived in a handful of long-tenured heads. Increasingly, it requires a search that returns an answer in seconds.
The gap itself hasn’t disappeared. Most organizations still don’t have a clean, searchable record of who’s already solved a given problem, which is a structural issue worth solving properly rather than working around one conversation at a time. That’s the same gap I wrote about in a previous piece on why great teams are built through the middle: someone still has to stand between the people pushing forward and the people holding the line, and search getting faster doesn’t retire that role. It just makes the role easier to find. What it retires is the excuse for not looking. A contributor who says “I didn’t know who to ask” today is usually describing a search they didn’t run, not a wall they actually hit.
The Law Already Has a Word for This
In Willful Blindness: Why We Ignore the Obvious at Our Peril, Margaret Heffernan traces a legal doctrine used in the Enron prosecution: you are responsible for what you could have known and should have known, even if you deliberately avoided looking. Courts have never accepted “I made sure not to find out” as a defense.
Most of daily organizational life now fits that same shape. The doctrine used to apply narrowly, to fraud, to negligence, to situations where someone actively looked away. Now it describes something close to ordinary behavior: not looking, when looking costs almost nothing, in decisions that have real consequences for other people.
A missed internal search doesn’t carry legal liability. But the underlying logic of the doctrine, that ease of access changes the moral weight of not knowing, applies well beyond a courtroom.
The Payoff
The goal isn’t constant, anxious verification of everything, or treating every gap in knowledge as a personal failure. Judgment about what’s worth checking still matters, maybe more than ever, precisely because checking is now so cheap that the real skill is knowing what’s worth the five minutes.
The same logic extends to markets and industries. Not knowing where a market is moving, who’s winning, or what’s about to change is a weaker excuse than it used to be; that information is more available in real time than at any point before now. Some of the people reading this are the ones building that market, not watching it from behind. If your work is genuinely ahead of what’s out there, a search is only checking you against an index that hasn’t caught up yet, not against the truth.
But the baseline has moved. For leaders, the cost of under-scoping a decision because you assumed you knew what your team could do is no longer a reasonable oversight. For contributors, the old excuse for waiting to be told, or staying quiet about an idea because you weren’t sure it was your place, has lost most of its footing.
Leadership doesn’t become obsolete because of any of this. What a leader can’t outsource to a search is judgment about what the information means, and the accountability for the call made on top of it. Information got cheap. That didn’t.
The reverse holds too. What a contributor still can’t get from a search is the political read, the trust, and the standing to act on what they’ve found. Verifying an answer and having the authority to use it are different things.
“I didn’t know” used to be the honest end of a conversation. Now, more often, it’s the point where the conversation should have started.
Where has “I didn’t know” stopped being a good enough answer in your organization, and who’s still using it anyway?