In this exclusive interview with Malavika Mookherjee Mitra, Chief of Staff · Trusted Operator for UHNW Principals, we explore the often unseen but deeply influential role of a Chief of Staff in modern leadership ecosystems. From managing invisible complexity to enabling strategic clarity, she shares powerful insights on trust, execution alignment, leadership dynamics, and the evolving nature of operational stewardship in high-stakes environments.
IT Voice- When you step into leadership discussions, at what point do you decide to actively influence a conversation versus staying in the background?
Malavika Mookherjee Mitra- My default is to observe first. I listen for what’s being said, what’s being avoided, and what the room’s energy is telling me that the words aren’t. Most of the time, the most valuable thing I can do is hold space — pay attention to the undercurrents and let the leader’s lead.
I step in when I notice that a conversation is about to move in a direction that will cost us later. That might be a decision being made on incomplete information, a key stakeholder perspective going unrepresented, or an assumption that everyone has silently agreed to but nobody has actually examined. When I see that, I consider it part of my responsibility to surface it — not loudly, not as a challenge, but as a question or a reframe.
The other trigger is when I can see that the leader I support needs an anchor. Sometimes a conversation accelerates past the point of clarity. In those moments, a well-placed synthesis — “so what we’re agreeing to is…” — creates the pause that allows a better decision to emerge.
I don’t think of it as influence. I think of it as stewardship. My role is to protect the quality of the outcome, not to be visible in the process.
IT Voice- What’s a situation where you had to challenge a leadership viewpoint and how did you approach it without disrupting trust?
Malavika Mookherjee Mitra- There was a period when the organisation I was supporting was moving towards a structural decision — a significant one — at a pace that concerned me. The leadership had strong conviction, which I respected. But I had visibility across multiple functions, and I could see that the ground-level assumptions the decision rested on had shifted. The data the team was using was three months old, and three months in that environment was a long time.
I didn’t walk in and say the decision was wrong. That would have been both presumptuous and counterproductive. Instead, I requested a private moment with the principal and said something like: “I want to make sure we’re looking at this with the most current picture. Can I share what I’m seeing from the ground before we finalise?” That framing — not “you’re wrong” but “let me add to what you know” — kept the relationship intact while creating space for reconsideration.
We ran a rapid cross-functional check. Two of the core assumptions did not hold. The decision was adjusted, and the outcome was meaningfully better.
What I’ve learned is that trust is not disrupted by disagreement — it’s disrupted by how disagreement is delivered. If the leader knows your intention is to serve the outcome and not to be right, they will hear you. That has to be true in your behaviour over time, not just in the moment you’re challenging them.
IT Voice- How do you identify which issues truly need leadership attention versus those that can be resolved within teams?
Malavika Mookherjee Mitra- I use a simple internal filter, though it took years to develop the instinct behind it.
The first question I ask is: does this require a decision that only leadership has the authority or context to make? If the answer is yes — if it crosses strategic lines, involves significant resource commitments, or has implications beyond one team’s remit — it goes up. If a capable team can own it fully, it stays with them.
The second question is: what happens if this is wrong? Low-stakes, reversible decisions belong to the people closest to them. High-stakes, difficult-to-reverse decisions need a different level of scrutiny and ownership. That distinction matters enormously in a fast-moving environment.
The third question — and this one is often overlooked — is: what does this issue signal? Sometimes a seemingly small operational problem is actually a symptom of something structural. When I see a pattern, even in minor issues, I bring it to leadership not as a problem but as a trend worth watching.
What I’m always trying to avoid is two failure modes: overloading leadership with things they shouldn’t be deciding, and under-informing them on things that will eventually surprise them. Both are failures of the Chief of Staff role. The filter has to work in both directions.
IT Voice- In fast-moving organisations, priorities shift constantly. How do you ensure continuity without slowing things down?
Malavika Mookherjee Mitra- Continuity, in my experience, lives in systems and relationships — not in any individual’s memory or availability.
The first thing I establish with any principal is a set of standing priorities: the things that are always true regardless of what else is happening. These become the north star against which every new shift in priority is tested. When something new comes in urgently, the question isn’t “should we do this” but “where does this sit relative to what we’ve committed to, and what would we deprioritise to accommodate it?” That clarity prevents the kind of reactive thrashing that eats momentum.
The second thing is documentation discipline. I keep decision logs, briefing notes, and action registers that don’t depend on anyone holding information in their head. When a priority shifts, the context travels with it. People don’t have to reconstruct what was agreed and why.
The third is communication cadence. I hold short, regular touchpoints with the teams and stakeholders that matter most — not to review everything, but to catch misalignment early before it becomes friction.
Speed and continuity are not actually in opposition. The organisations that lose continuity when priorities shift are the ones that were moving fast in an unstructured way. The structure is what allows you to move fast without losing the thread.
IT Voice- What does a typical ‘high-impact day’ look like for you in this role?
Malavika Mookherjee Mitra- A high-impact day rarely looks dramatic from the outside. That’s almost the point.
It usually begins before the principal’s day does. I review what’s coming — not just the calendar, but the context behind each meeting. Who will be in the room, what they need, what the desired outcome is, and what could go sideways. I prepare the briefing notes or talking points where needed, so the principal walks into every conversation already two steps ahead.
During the day, I move between strategic and operational threads — sometimes in the same hour. I might be synthesising a complex set of advisor inputs into a clear recommendation brief, and then managing a logistical issue that could affect a critical trip. Neither is more important than the other; both need to be handled with the same precision.
The moments I find most valuable are the ones where I can prevent a problem before it surfaces. A call I make proactively, a misalignment I catch in a draft before it reaches the wrong eyes, a conversation I broker between two people who were moving in different directions without knowing it.
By the end of a high-impact day, the principal has been protected from noise, supported in their decisions, and surrounded by a world that ran exactly as it should — without them having to manage any of it. The best days are the ones they don’t notice, because everything simply worked.
IT Voice- How do you manage information flow — deciding what leaders need to know, and just as importantly, what they don’t?
Malavika Mookherjee Mitra- This is one of the most consequential and least discussed aspects of the role.
Information overload is its own form of paralysis. A leader who is receiving everything is effectively receiving nothing — they are spending cognitive energy sorting rather than deciding. Part of my function is to be a filter, and that requires genuine judgment about what matters.
My framework is built around three questions: Is this actionable? Is this time-sensitive? Does this change what we’re doing or thinking? If the answer to at least two of those is yes, it goes to the leader. If it’s a one-out-of-three, I hold it and monitor. If it’s none, I handle it and file a note.
What I never do is filter based on whether I think the leader will be pleased or displeased by the information. The instinct to protect leaders from difficult news is well-intentioned but dangerous. My job is to ensure they have an accurate picture of reality, especially when reality is uncomfortable. They can decide what to do with it — that’s their role. Ensuring they have it — that’s mine.
I also maintain a weekly summary practice for the principals I support — a brief, structured note that covers what was resolved, what is pending, and what I’m watching. It gives them a consistent rhythm of awareness without requiring them to chase information through the week.
IT Voice- What’s one capability or mindset that you believe is essential to succeed as a Chief of Staff, but is often overlooked?
Malavika Mookherjee Mitra- Institutional patience.
Not patience in the passive sense — not waiting, or deferring, or holding back. I mean the capacity to play a long game with deliberate intention. To understand that trust is built across hundreds of small moments, not in a single impressive act. To resist the temptation to make your value visible in the short term at the cost of what actually serves the organisation in the long term.
Most people who struggle in this role do so because they are optimised for recognition. They want the credit, the visibility, the title that matches the scope of their contribution. I understand that impulse — it’s very human. But the Chief of Staff who is constantly trying to be seen is, almost by definition, not doing the job correctly.
The paradox is that the less you need recognition, the more trusted and effective you become. Principals and leaders can sense, very quickly, whether someone is serving them or serving themselves. When they sense the former — consistently, over time — the access, the influence, and the genuine impact follow naturally.
The other dimension of this is patience with complexity. The situations I navigate rarely have clean answers. The ability to hold ambiguity without rushing to false resolution is something I’ve had to cultivate consciously, and I believe it is one of the most differentiating qualities a Chief of Staff can develop.
IT Voice- How do you handle situations where alignment exists at the top but breaks down at the execution level?
Malavika Mookherjee Mitra- This is one of the most common and underestimated challenges in any organisation, and it usually comes down to translation — or the lack of it.
When leadership aligns on a direction, that alignment often lives in language that is abstract at the top and needs to become concrete for the people executing it. “We’re going to move fast on this” means something very different to a strategy team than it does to an operations team. If nobody translates the intent into specific, contextualised action, you get divergence — not from resistance, but from reasonable people filling in the gaps differently.
My first move when I see execution breakdown is to go back to the source of the decision and understand what was actually agreed — not the headline, but the intent, the constraints, and the non-negotiables. Then I sit with the teams at the execution level and understand where the disconnect is. Is it a clarity problem? A resource problem? A prioritisation problem? A relationship problem between teams?
In most cases, I find that nobody has been deliberately obstructive. The breakdown is usually structural — a gap in how the decision was communicated, or a place where two teams have made different but equally reasonable assumptions.
Once I understand that, I bring the relevant parties together — not to adjudicate, but to create a shared operating picture. My role in that room is to hold the connection between the strategic intent and the practical reality, and to facilitate the conversation that closes the gap.
IT Voice- Have you seen the role of Chief of Staff vary across different leadership styles? How do you adapt to that?
Malavika Mookherjee Mitra- Enormously — and I think the ability to adapt is foundational to doing this work well.
I’ve worked with leaders who are deeply analytical — they want data, frameworks, structured options before they decide. With them, my preparation is rigorous and thorough. I present information in a way that supports their process without pre-empting their judgment.
I’ve worked with leaders who are highly intuitive — they make decisions quickly, from experience and instinct, and they need someone who can keep pace and then document and implement without slowing the momentum. With them, I stay very close to the operational layer and become the anchor that holds the follow-through.
I’ve worked with leaders who are deeply relational — where the work is as much about managing the ecosystem of people around them as it is about any formal task. With them, I pay close attention to the quality of those relationships and how they’re being tended.
What I’ve found constant across all of them is the need to understand, at a very precise level, what they value. Not what they say they value — what they actually respond to, what frustrates them, what makes them feel supported or exposed. That understanding can only come from paying careful attention over time, and from asking honest questions early in the relationship.
I adapt my style, my communication cadence, my level of proactivity, and the way I present information based on what I observe. The role is not fixed — it is shaped by the leader I serve, and that is not a limitation. It is the nature of the work.
IT Voice- What is one aspect of your role that delivers the most value to the organisation but is least understood by others?
Malavika Mookherjee Mitra- The management of invisible complexity.
People see deliverables — a meeting that ran well, a project that completed on time, a decision that was made cleanly. What they don’t see is the infrastructure behind that outcome: the pre-calls that aligned stakeholders before they were in the same room, the version of the document that was never sent, the conversation I had with someone three levels down who was quietly about to create a problem nobody had anticipated.
The most valuable work I do is often the work that leaves no visible trace, precisely because it was done well. A crisis averted is invisible. A misalignment caught early looks like nothing happened. A decision that was made with full information, because I ensured the right information was in the room, looks like good leadership — which it is. I just made it possible.
This creates an interesting challenge: how do you communicate the value of what didn’t go wrong? I’ve learned not to try too hard. The principals I work with, over time, come to understand what they’re holding when they have someone in this role — because they notice when it’s absent.
What I would want people to understand is this: the Chief of Staff is not a coordinator or an executive assistant with a more impressive title. Done properly, this role is the operational conscience of a leader — the person who holds the complexity so that they can lead with clarity. That is quiet work. And it is the work I find most meaningful.
