The Incomplete Script

Reflections on burnout, disillusionment, and questioning the stories we were told

A publication of first-person essays naming what work feels like — without hero framing. These are lived reflections, not advice.

Empty office conference table with notebook, papers, and laptop in a subdued modern workplace

Why I Stopped Asking for Help With Things I’m Supposed to “Just Know”





There wasn’t a single moment when I decided to stop asking — it was a slow internal shift that happened as I began to notice how every request seemed to underline something I was *expected* to already understand.

I used to ask questions freely — about tools, procedures, naming conventions, minor clarifications that helped me get my work done. I saw questions as part of how work operates: you don’t know something, you ask, you learn, you move forward. But over time, I began to notice a particular tone in the responses, a kind of subtle hesitancy or almost‑hidden impatience that made the act of asking feel like something other than learning.

It wasn’t that people were rude. In most cases, they were neutral or even polite. But there was a faint emotional subtext — a ripple in the air — that said, *you should already know this.* And over enough repetitions of that subtle signal, I began to stop asking about the things I didn’t truly understand, especially when those things were in the category of what the group acted like everyone was supposed to just know.

It’s similar to what I wrote about in “Why I Notice Every Time Someone’s Tone Changes Toward Me” — the way tiny shifts in communication carry more meaning than the words themselves. Here, it wasn’t the direct meaning of a phrase like “Just go ahead and do it” that sank in — it was the invisible layer underneath it, the sense that some knowledge was assumed rather than taught.

When “Just Know” Starts to Sound Like Judgment

At first, the expectation that I should already know something was something I brushed off internally. I told myself it was efficiency — people didn’t want to explain the obvious. But after a while, I began to notice a pattern: the things I felt least confident asking about were the things other people seemed to take for granted. Tools, conventions, unwritten shortcuts, assumptions that hovered beneath documented processes.

The first few times it happened, I didn’t see it as a shift. It was one question about a formatting style. Another about where a template lived. Another about how to interpret a performance metric. Each time, someone responded with clarity on the surface, but their tone — not in volume, but in texture — conveyed that I *should* already know this. Not explicitly, not as a reprimand — just as an unstated baseline.

And over time, I realized I was experiencing something akin to what happens when you’re *never the first person asked*, as I explored in “What It’s Like When You’re Never the First Person Asked”. There, the pattern isn’t exclusion in a direct sense — it’s a rhythm of attention that repeatedly places others ahead of you in conversational sequence. Here, the pattern isn’t hostility — it’s an expectation that others assume you already hold information they treat like common knowledge.

And whether intended or not, that assumption carries emotional weight. It shapes how you begin to *expect* yourself to know things without ever being shown how. So you stop asking. You internalize the idea that you’re supposed to just know certain things. And in doing so, you begin to operate silently in the cracks between what you *actually* understand and what the culture *implicitly* assumes you should.

When “you’re supposed to just know this” becomes the unspoken baseline, asking feels like a confession of incompetence rather than a step toward understanding.

There were moments early on when I still tried to ask questions about these assumed things — not boldly, but gently, cautiously. I’d preface with “Sorry, I’m still getting up to speed…” or “I might be misunderstanding, but…” and then pose a question that seemed simple. And often the response would be accurate and helpful — but the emotional resonance was something else. A click of teeth in phrasing I couldn’t quite name, a swift answer that landed with a fraction of impatience, a reply that was technically correct but felt like it carried an implicit dismissal.

At first, I didn’t register the *feeling* as anything meaningful. I told myself I was sensitive. I told myself people didn’t mean anything by it. But when the pattern repeated — in different meetings, in different threads, with different colleagues — I began to see it as an emotional undercurrent in the workplace culture. I began to anticipate that slight shift under a direct response, and eventually I began to *fear* the sensation more than the question itself.

Questions that were truly about understanding became emotionally tangled with the unspoken assumption that I should already know the answer. And because I felt that tension in my body before I even spoke, I began to hesitate. Then delay. Then avoid.

Pretty soon, I wasn’t asking about things I *didn’t* know. Not because I suddenly knew them. But because I didn’t want to feel the tiny pinch of expectation that came with asking. I didn’t want to internalize the implication that I was somehow behind the curve. So instead of asking, I started to try to figure things out on my own, frantically piecing together hints and fragments of context rather than stepping into a direct question.

It sounds simple — just ask — but the emotional cost made it something else entirely. The act of asking became weighed down with all the silent assumptions of competence, independence, and prior knowledge that are never explicitly taught but are assumed by the rhythms of communication.

And as I stopped asking, something curious happened: I began to *think* that I knew these things, even when I didn’t. I started to fill in the gaps with patterns and guesses rather than clarity. I learned to tolerate confusion because asking for clarification felt like admitting I was behind an invisible baseline. I internalized this unspoken expectation as proof I *should* already know, until I wasn’t even sure where knowledge ended and assumption began.

This shift happened quietly, and it shaped how I navigated work life in ways that felt both efficient and precarious. On one hand, I learned to be resourceful. I started solving problems by observing others, inferring patterns, deducing procedures without asking. On the other hand, I started building silent walls around my uncertainty. I didn’t share the places where I was unsure. I didn’t acknowledge when I was confused. I just *acted* as if I already knew.

And that became exhausting in a way that isn’t dramatic — it’s the kind of exhaustion that sits in your chest when you’re reading documentation you don’t quite follow but don’t ask anyone to explain. It’s the tension in your shoulders when you send a message you’re not confident about because you couldn’t bring yourself to ask for help. It’s the small, persistent worry that everyone else effortlessly walks through a terrain you’re only pretending to understand.

Over time, I began noticing other patterns — like how people only talk to me when they need something, as I explored in “How I Became Someone People Only Talk to When They Need Something”. When I stopped asking for help, I rarely initiated conversational openings. There were no check‑ins about how I was doing with this or that. I wasn’t part of the informal mentoring currents that others seemed to access naturally. I was just… expected to *just know*.

So I stopped asking. Not in a moment of clarity or defiance — just in the way patterns settle into your bones. I began avoiding questions that showed lack of understanding. I started to clip the edges off my own curiosity, trimming the parts of interactions that would expose uncertainty rather than expand clarity. And the more I did that, the less I asked, and the more I *acted* like I already knew.

This isn’t about pride. It’s about survival. Asking felt like exposing a vulnerability that wasn’t welcomed into the conversational field — a vulnerability that was met with indirect signals of expectation rather than explicit teaching. So I learned to adapt. I learned to infer. I learned to navigate the spaces between what I knew and what others assumed I should know, without saying a word about it.

And what’s strange is how comfortable that adaptation can start to feel. Once you stop asking, you don’t have to deal with the emotional cost of being *assumed to know.* You can just operate in the gaps, silently assuming competence where there’s uncertainty. You can avoid the tiny sting of those unspoken expectations by internalizing them as norms rather than conditions to be questioned.

But that comfort is fragile. Not fragile like stress or burnout — fragile like a quiet tension that never goes away. It lodges itself in how you approach tasks, how you interpret others’ responses, how you weigh uncertainty against the cost of asking. It sits behind your eyes when you draft that Slack message without hitting “Send”; it buzzes in your chest when you choose silence over clarification; it lingers in your mind when you wonder what you *actually* know versus what you *assume* you should.

So when I look back on the times I used to ask freely, I see a shift not in my competence but in my willingness to expose uncertainty. I see how I began to treat questions as admissions of inadequacy rather than as part of how humans learn. I see how workplace norms around assumed knowledge reshaped my internal compass until asking for help felt like stepping onto unstable ground.

And I see now that I stopped asking long before I realized it — not because I knew more, but because I had absorbed the unspoken message that I was *supposed to know* more than I actually did.

I stopped asking for help not because I stopped needing it, but because the unspoken expectation that I should already know felt too heavy to articulate.

Leave a Reply

Your email address will not be published. Required fields are marked *