I have spent twelve years building things that people use, but rarely knowing who built them.
A support tool that quietly handled ninety percent of ticket volume for a telecom app used by millions. A facial recognition system that helped reunite missing children with their families. A digital wallet that moved from one payment processor to another without users noticing a single failed transaction.
My name was not on any of it. And, structurally, that is the job.
It sounds simple. If I did good work, surely at some point someone would say my name in the room where decisions were being made.
So I collected the certifications. Learned the frameworks. Wrote the roadmaps. Sat through the workshops. Worked with engineers, support teams, customers, and stakeholders.
I kept waiting for the moment when the invisible work would become visible. It rarely did. And when it did, people usually remembered the product, not the person behind it.
There is a specific kind of loneliness in that. It is not the loneliness of being alone. I was rarely alone. There were standups, stakeholder meetings, Slack threads, customer conversations, and endless discussions. It is the loneliness of being structurally unnecessary to remember.
A product manager who does the job well often disappears into the seams of the company. The engineers remember shipping the feature. The support team remembers the ticket queue getting quieter. The users remember the app just working. Nobody remembers the person who spent three months arguing that the ticket queue and the app working were the same problem.
That is the strange part of the job.
When things are going well, people stop chasing you. There is nothing to escalate. No fire needs to be put out. The silence becomes proof that things are working.
It is also the reason nobody thinks to say that things are working.
The team brings you problems because they believe you can solve them. Stakeholders bring you their concerns because they believe you understand the work.
You sit somewhere in the middle. Close enough to management to be treated like part of it. Close enough to the team to still be treated like one of them.
You become trusted by both sides, but fully claimed by neither.
I wrote once that if your absence breaks delivery, your system is fragile. I believed it then and I believe it more now, but what it costs the person building that resilience. You are, by design, making yourself easier to forget.
Every good process you create removes another dependency on you. Every problem you solve quietly removes evidence that you were needed.
That can be uncomfortable.
I do not think the answer is to stop doing the work invisibly. Leadership is often a thankless job. So is parenting. So is building systems that keep working when you are no longer there. Recognition is not a phase that eventually arrives. For many of us, it may never be the shape of the career.
I looked at two pictures of myself ten years apart, A decade had passed.
I had learned more. Built more. Experienced more. But the thing that had changed was not that I had suddenly become visible. Maybe that was never the point.
I am invisible in the places where invisibility means the thing worked. And I am okay with that.
I would rather save my wish to be seen for the places where it actually matters: the people who chose to stay, and the work I chose to put my name on anyway.
Tahir Shahzad
Tahir Shahzad is a Product Manager, Product Owner, and technology consultant with over a decade of experience helping startups and organizations build products people actually use. If you are working on a product problem worth solving, reach him at tahirshahzad.com/contact/
