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

How I Became Someone People Only Talk to When They Need Something





I didn’t notice it forming — the way interactions began with needs rather than connection — until I was already living inside the pattern.

I used to think work relationships were, at their core, functional connections: people who talk to each other when tasks overlap, when collaboration is helpful, when context is needed. But somewhere along the way, my presence in conversations began to narrow — from being a peer in dialogue to being a destination for requests. I started noticing that most interactions with me weren’t about rapport, curiosity, or shared observation — they were about *need.*

At first, I brushed it off. I told myself it was normal: that people come to others when they need something. That’s how work gets done. But then I began to notice the rhythm of those interactions, the pattern beneath them, and how rarely anyone’s engagement with me wasn’t transactional.

This wasn’t dramatic exclusion like being left out of informal decisions, the way I described in “How I Realized I Was Being Left Out of Informal Decisions”. It wasn’t overt, it wasn’t pronounced, and it certainly wasn’t spoken aloud. It was far subtler — woven into the cadence of everyday interaction until it became the *default* way people approached me.

The First Time I Actually Noticed the Pattern

It was a Thursday afternoon, late in a sprint cycle. A colleague pinged me with a Slack message: *Hey – can you send over that template? I need it to prep for a deadline.* Fine. I sent it. Then another: *Quick question on your part of the deck…* Then another: *Can you help clarify this point before leadership review?* And as I responded to each one, I realized something odd: I hadn’t had a single message that day that wasn’t a direct ask. Not a check-in, not a casual conversation starter, not a comment about something human and unrelated to task progression. Just requests.

That evening, I replayed the day in my head. When I think about normal human exchange outside of work — a quick comment about weather, a remark about a shared Netflix show, a mutual groan about diet soda running out in the break room — none of that showed up in my interactions. Mine were all needs and questions and clarifications. No casual engagement, no connective tissue beneath the work surface.

It reminded me of what I wrote in “What It Feels Like When You’re Left Off Emails Without Explanation”, where omission communicated something I had to sit with internally. Here, presence *only when needed* was a form of omission too — an omission of relational context, of nuance, of *just being present with someone.*

People only reach out when something needs to be solved — and that pattern became the only reason people spoke to me.

At first, it didn’t feel problematic. I responded. I helped. I answered clearly and promptly. I didn’t mind being useful — it felt like a contribution. And for a while, that was enough. But over time, I started noticing how quickly interactions ended once the need was met. A simple thanks, a brief acknowledgment, and then silence until the next request. Not warmth. Not curiosity. Not casual exchange. Just a transactional hydraulic of needs flowing toward me and away once they were resolved.

I began to notice it in meetings too. Someone would bring a question into the room that pertained to my work, and once we clarified it, the conversation would immediately pivot. That tilt of attention wasn’t surprising — meetings move fast — but what struck me was the absence of any continued engagement afterward. No follow-up that said anything human. Just task clarity.

And it wasn’t even universal. Certain colleagues interspersed small talk effortlessly with work talk. But with me, it was almost always *work-first.* I began to notice it not because it was dramatic, but because it was consistent. A pattern that carved a pathway through my days.

At lunch one day I caught myself realizing: people don’t ask me how I’m doing. They ask me what I can do. They don’t start with observation; they start with need. They don’t engage in exchange; they engage in extraction.

And somewhere in the quiet of that realization, I felt a shift inside myself too. I began to realize how it shaped how I showed up — ready to solve, ready to answer, ready to help — without anyone actually wanting to sit in the space of *presence* with me.

It’s interesting how easy it is to confuse usefulness with connection. When someone reaches out to you frequently, it feels like they’re thinking of you. It feels like care. But utility isn’t the same as connection. The difference lies in whether someone engages with you even when they *don’t* need something. Whether they reach out not to ask, but to share.

I realized I was missing that. The messages, the pings, the exchanges — they all came with an implicit bottom line. A need. A gap to be filled. A question to be answered. They weren’t conversations; they were *requests with faces attached.* And I became the person on the receiving end of these requests so constantly that I started to unconsciously shape my presence around readiness to respond rather than readiness to *just be.*

This wasn’t a conscious decision on anyone’s part. No one said, “We only talk to you when we want something.” It was just the way things happened. People assume you’re okay with transactional interactions when you respond quietly and helpfully. They don’t see how omission of relational context accumulates into a distinct pattern.

Over time, I began to feel something subtle whenever a message popped up with my name on it — not the mild anticipation of engagement, but a readiness to *solve.* My internal posture changed. My shoulders tensed slightly. My eyes automatically scanned for tasks rather than human nuance. I became reflexively responsive rather than mutually present.

And that changed how I *experienced* being approached. I no longer showed up with curiosity — I showed up with answer‑seeking. I didn’t sit in the moment before responding; I moved to resolution. Not because I didn’t want conversation, but because the pattern of engagement I was living invited me to *fix* rather than *exchange.*

I started noticing how differently I responded to requests than conversations. Requests activated something in me — a kind of professional instinct — and conversations required something softer, more open, more uncertain. But because most interactions I had were structured around needs, I rarely practiced the softer mode. I just moved into answer mode — the mode that matched the pattern people had trained me into.

And because it felt normal — because work is built on requests and responses — I didn’t question it for a long time. But one afternoon, after a long stretch of ping after ping after ping, I paused. I looked at the list of messages that all began with questions and ended with “thanks.” I realized that not one of them had begun with something like “just wanted to share…” or “I saw this and thought of you…” or even “hey, how’s your day?”

And that’s when it settled in me: I had become someone people contact *only* when they needed something.

It made me wonder how much of my own energy was wrapped up in that identity. How often I measured my presence by usefulness. How often I held back relational instinct because it didn’t seem functional. How often I practiced being available for need rather than available for exchange.

This isn’t about resentment. It’s about noticing patterns. It’s about seeing how our roles in workplaces aren’t just defined by job duties, but by the *ways people choose to engage with us.* I began to see that my days were dense with communication, but light on connection. And there’s a difference between density and depth.

I began to notice how other people navigate communication — how some messages begin with personal context before task context, how some conversations linger without purpose before they’re purposeful, how some interactions happen without bottom lines. I saw what relational engagement *feels like* when it isn’t anchored first in need.

And I saw — quietly, unobtrusively — how rarely that happened for me.

Some days I tried to initiate conversations without agenda — to comment on something trivial, to share an observation, to ask about someone’s weekend. But those tries often felt awkward, like deviating from the pattern people implicitly expected. They would respond politely, quickly, and then steer back to tasks. Not out of dismissal, but out of habit.

And habit is powerful. It shapes how we engage, and over time, it shapes *how we show up.* People show up to me with needs, and I show up with responses. Not warmth. Not ease. Not curiosity. But help. Clarification. Solutions. Fulfillment of requests.

So I sit with that. I notice when messages arrive. I notice what they carry. And I notice how my internal posture shifts — how my body prepares for resolution instead of connection.

It’s not what I *wanted* work relationships to feel like. It’s what they came to feel like through repetition, through pattern, through the quiet entrenchment of transactional engagement.

And it’s not about anger or blame. It’s about recognition. About seeing how the shape of communication with me became defined by necessity rather than mutual presence. And how that pattern quietly shifted how I *understand my presence* in the workplace.

Most interactions with me begin not with hello, but with *what do you have?* Not because people are unkind, but because patterns in workplaces tend to prioritize function over connection, need over presence, task over person.

And somewhere along the way, I became the person who is *spoken to when something is needed,* and not simply when something is noticed.

When people only talk to you when they need something, you begin to understand how presence and usefulness can feel indistinguishable until you notice the pattern quietly forming between them.

Leave a Reply

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