The Visibility Trap: When Smooth Becomes Invisible

Part 4 of a series on contextual intelligence in HR leadership.

At the offshore consulting firm where I started my career, I was visible. I knew this at the time, and I attributed it to the quality of my work. My deliverables were sharp, my timelines were reliable, my frameworks were well-received. The feedback loop between effort and recognition was tight. I produced good work, and people noticed.

What I didn't understand then was that the visibility wasn't something I had earned. It was something the operating model had given me. In an offshore consulting setup, the team is small relative to the work. You collaborate closely with onshore colleagues. Your output passes through few hands before reaching someone with evaluative authority. The structure itself makes your contribution legible. You don't need to narrate your impact because the system narrates it for you.

I mistook structural visibility for personal achievement. And that mistake quietly shaped my assumptions about how professional recognition works for the next several years.

Invisible by design

At the government ministry, visibility operated on entirely different terms. As I described in Part 3, I was an outsider on deputation, embedded inside the system to do substantive drafting and conceptual framing work. The policies I helped shape affected a couple hundred of public enterprises. The parameters I drafted for MoU guidelines and strategic sector classification were consequential pieces of work.

None of it carried my name.

This wasn't an oversight. It was the architecture of the role. Policy work in government is institutional by nature. Documents are authored by the office, not the individual. The Special Secretary's name appeared. The department's name appeared. The officer on deputation who spent weeks drafting and redrafting the frameworks did not appear, and was never expected to.

I accepted this. The work was intellectually demanding, the access was unusual for someone at my level, and the trade-off felt clear: you get meaningful work in exchange for anonymous contribution. Visibility was not part of the deal, and I had made my peace with that.

What I didn't realize was that this acceptance was recalibrating my instincts. After the PSU, where I had learned (painfully) to focus on process and relationships rather than output. And after the ministry, where I had learned to do significant work with no expectation of personal credit. I had internalized a specific stance: do the work well, serve the system, and trust that the right people will notice.

This stance was about to become a serious liability.

Returning to consulting, but not the same consulting

When I joined Deloitte India, I expected something familiar. I had started my career at Deloitte's offshore practice. I understood the consulting model. I knew how engagements worked, how deliverables were structured, how client relationships were managed. Moving from a government ministry back into consulting felt like returning to a language I already spoke.

The language was the same. The dialect was completely different.

Offshore consulting and domestic consulting for Indian clients are structurally different experiences. At the offshore firm, your primary interface was with US colleagues. Client interaction was mediated through layers. The work was production-intensive: build the framework, design the analysis, polish the deliverable. Your value was measured by the precision of what you produced.

Domestic consulting with Indian clients was far more relational. The client relationship was personal and trust-based in a way that the offshore model never required. You were in the room. You were travelling to client sites. You were not just advising but implementing, not just designing but delivering. And the client's assessment of you was based not just on the quality of your documents but on how they experienced working with you: your responsiveness, your judgment, your ability to handle ambiguity, your willingness to own problems rather than escalate them.

This was where the ministry experience became an unexpected edge. The skill I had built at the ministry, the ability to hold ground diplomatically with difficult, senior stakeholders, translated directly into client management. I could handle demanding clients without escalating. I could navigate ambiguity without panicking. I could manage competing workstream dependencies without needing a partner to step in.

And that was precisely the problem.

The MNC Project

For a large multinational establishing operations in India, I was leading two critical workstreams: change management and competency mapping. The work was highly ambiguous from the start. The client didn't have a clear picture of what they wanted done. They were anxious about making sure the India office would open and function smoothly, but the anxiety was diffuse, it expressed itself as a demand for constant reassurance rather than clear requirements.

My workstreams required constant integration with other teams: programme management, IT, finance, legal. The change management piece in particular demanded a kind of continuous, low-friction coordination that doesn't show up in project plans but determines whether the project actually moves.

The client counterpart on my workstreams had a reputation for demanding what people internally called "white-glove service." She was not initially a champion. She was skeptical, exacting, and required a level of responsiveness that left little room for error.

Over the course of the engagement, I managed both workstreams to green-light status. In a project where other workstreams were struggling, mine were on track, on budget, and on time. Invoices were raised and cleared without friction. The client counterpart who had started as a sceptic became an advocate. When performance reviews came around, she wrote a glowing recommendation.

My partner attended meetings on this workstream twice. Twice, across the entire engagement.

Managers from other workstreams on the project praised how smoothly things were running. The client was happy. The revenue was flowing. And I received no credit for any of it.

Why smoothness is invisible

The partner didn't know what I was doing because he had no reason to look. The projects that demanded his attention were the ones that were on fire. The ones generating escalations, client complaints, budget overruns. Those were the projects where the manager's name came up in leadership conversations, sometimes negatively, but at least it came up. The problems created visibility. The problem-solvers became known.

My projects produced no noise. No escalations. No client complaints. No emergency calls. The partner's absence from my projects wasn't negligence. It was a rational allocation of attention: he went where the problems were, because that's where he was needed. The projects running smoothly didn't need him. And because they didn't need him, they didn't exist in his field of vision.

By the time the client's recommendation letter arrived at performance review season, the narrative had already been set. I had been invisible for the duration of the engagement. A single letter, however glowing, arriving at the end couldn't retroactively create a presence that hadn't been felt throughout.

This is where the concept of signalling, drawn from Michael Spence's work in information economics, becomes uncomfortably relevant. Spence's core insight is that in environments where there is asymmetry between what someone knows about their own performance and what an evaluator can observe, competence alone is not enough. Competence must be signalled, made observable through actions the evaluator can see, interpret, and remember.

In the offshore consulting model, the structure did the signalling for me. The team was small, the deliverables passed through visible checkpoints, and the operating model made individual contribution legible. I didn't need to signal because the system signalled on my behalf.

At the ministry, signalling was irrelevant. The work was anonymous by design. Nobody expected individual credit, and the evaluative structure didn't depend on it.

At Deloitte India, signalling was the game. And nobody told me.

The three visibility regimes

Looking across these three contexts, a pattern becomes clear that I wish I had seen at the time.

	How visibility works	What I assumed	What was actually required
Offshore consulting (USI)	Structural: the operating model makes your contribution legible to evaluators automatically	My work speaks for itself	Nothing beyond good work (the system handled visibility)
Government ministry	Absent by design: contributions are institutional, not individual	Visibility is not part of the deal	Acceptance of anonymity in exchange for meaningful work
Domestic consulting (India)	Performative: contribution must be actively narrated to evaluators who cannot observe it directly	My work will speak for itself (same assumption, different context)	Active signalling: regular updates to partners, strategic escalations, narrative construction around impact

The dangerous column is the third one. "My work speaks for itself" was true at USI, not because it is universally true, but because the system amplified the signal. When I carried that same assumption into Deloitte India, the system had changed. The signal was no longer being amplified. It was being absorbed. Smooth delivery doesn't generate the escalations and interventions that create partner-level visibility. The better I was at my job, the less reason anyone in leadership had to know I existed.

What "demonstrating impact" actually means

After this experience, I started paying closer attention to colleagues who were effective at visibility. Not the ones who were self-promoting in a crass sense, but the ones who understood that impact must be narrated, not just delivered.

What they did was structurally different from what I did. They created moments of visibility within the engagement, not just at the end. A brief update to the partner after a difficult client conversation. A proactive flag about a risk that hadn't materialized yet but could. A short note after a milestone was hit, framing what had been achieved and what it meant. None of these were dishonest or inflated. They were acts of translation: converting work that was happening below the partner's line of sight into information the partner could see, process, and remember.

The skill, I eventually understood, is not self-promotion. It is legibility management. Making your contribution legible to people who are not in the room when the contribution happens. At USI, the room was small enough that everyone was already present. At Deloitte India, the room was large, the partner was elsewhere, and legibility had to be actively constructed.

This distinction matters because most professionals frame the visibility problem as a personality issue. "I'm not good at self-promotion." "I don't like talking about my achievements." "I prefer to let the work speak for itself." These frames treat visibility as a character trait, something you either have or you don't, something that's slightly distasteful to cultivate.

But visibility is not a trait. It is a structural feature of the system you're operating in. Some systems make you legible by default. Some systems make you invisible by default. The skill is not learning to self-promote. The skill is diagnosing which kind of system you're in and adjusting your signalling behaviour accordingly. Without this diagnosis, you can be excellent, reliable, client-loved, and completely overlooked.

The compounding cost

I said earlier that the visibility problem followed me and I'm still working on it. That's worth being honest about, because I think it's more common than people admit.

When you spend your formative professional years in systems that either provide visibility structurally (offshore consulting) or make it irrelevant (government), you don't build the muscle for active signalling. And then when you enter a system that requires it, the deficit is not just a skill gap. It is an instinct gap. Your reflexes are calibrated for a world where doing the work well IS the signal. Overriding that reflex requires conscious, sustained effort. It feels performative. It feels unnecessary. It feels like it shouldn't be required.

And in some ideal world, perhaps it shouldn't be. But the world you're operating in is the world you're operating in, not the world you think it should be. Contextual intelligence, the theme running through this series, includes the ability to see that the rules of recognition are not universal. They are local. And if you don't read them correctly, you will be valued where you shouldn't be, and invisible where it matters most.

The ministry taught me to do substantive work with no expectation of credit. That was the right lesson for that context. But I held onto it too long. And in a context where credit was the mechanism through which career advancement happened, the same lesson became a quiet, compounding cost.

Think about your own career for a moment. In which of your roles was your visibility structural, provided by the system without you having to work for it? And in which roles did you assume the system was making you legible when it actually wasn't? The gap between those two answers is where the most important unlearning lives.

In the spotlight | Photo by Tima Miroshnichenko: https://www.pexels.com/photo/woman-in-velvet-dress-performing-on-stage-5135100/