When I Was Treated as a Function

A moment when identity narrowed into output.

I noticed it in the language being used around the work. Shorter. Cleaner. Focused entirely on what needed to happen next.

There was no space in it for how I thought, how I arrived at decisions, or what I noticed along the way.

Only the result mattered.

Everything else had quietly fallen away.

When contribution becomes mechanical

I realized I was being engaged as a function rather than a person.

What I delivered mattered. How I carried it didn’t.

The system interacted with me the way it interacted with any process—expecting consistency, not perspective.

My presence had been translated into utility.

I didn’t object to the shift.

I just felt myself become smaller inside the role.

I stopped offering nuance that wasn’t requested. I answered what was asked and nothing more.

If I was being treated as a function, then expanding beyond it felt unnecessary.

Function doesn’t carry history.

It doesn’t remember effort, judgment, or restraint.

It executes, produces, and moves on.

Being treated this way didn’t feel hostile—it felt flattening.

No one questioned my capability.

The structure simply didn’t engage with anything beyond it.

The feeling aligned closely with what’s described in Invisible at Work—present, useful, and yet not encountered as a whole person.

Function was enough.

I didn’t resist being treated this way.

I just stopped expecting recognition where none was designed to exist.

The system needed outputs, not identities.

This was another quiet unfolding of The Interchangeable Feeling, revealed through reduction to function.

That was when I realized I was being treated as a function, not a presence anyone needed to hold.