Skip to main contentBook Now

I Want to Be the Person Who Removes the Obstacle

I Want to Be the Person Who Removes the Obstacle

Founder Journal · November 15, 2026 · Nikita Khandheria · 5 min read

When someone asked what I wanted my role at ERIA to become, I said that I wanted to take barriers out of my team’s way.

That answer felt much more natural than describing a calendar full of approvals. I like solving a problem that does not yet have an obvious answer. I like seeing a possibility that changes what the team can do next.

I used the word firefighting in that conversation because I enjoy the energy of figuring something out. But the useful part is the problem solving, not the fire. A company does not become better because its founder has an endless supply of emergencies to rescue.

The role I want is one where capable people can do their work, and I can help when something meaningful is blocking them.

Find the obstacle before offering the answer

A team member may arrive with a request that describes only the first version of the problem. They need a supplier, a decision, more time, or a different budget. The founder can answer the request quickly and still miss what is actually making the work difficult.

I think the more interesting question is what the person is trying to achieve and why the current route is failing.

Perhaps the desired result is clear but the available approach is too expensive. Perhaps two requirements conflict. Perhaps the team has the skill but not the authority to make the decision. Each situation needs a different kind of help.

That is where I enjoy looking at the problem from another angle. The value is not that I know every answer. It is that I can sometimes see a connection or an alternative that makes the next step possible.

Intervention should leave ownership intact

There is a difference between helping someone solve a problem and taking the entire problem away from them.

Taking over can feel efficient. I know what I want to do, so I do it. But if that becomes the default, the team learns to deliver difficulties to me instead of developing its own judgment. My calendar fills, and their confidence has fewer opportunities to grow.

The better outcome is that the person remains responsible for their part of the work while receiving the help they need. I might challenge the assumption, make an introduction, clarify the priority, or decide something that genuinely belongs at my level.

Then the work should return to the person leading it. The founder’s involvement should make their job more possible, not make their authority disappear.

This is part of why I value the different strengths within our team. I do not need to become the operations specialist in order to support one.

Escalation needs judgment on both sides

A team should not feel that asking for help is a failure. It should also not feel that every uncertain decision must travel upward.

I would want people to understand the difference between a choice they can make, a choice that needs a second perspective, and a commitment that changes what we have promised the client. Those distinctions are more useful than telling everyone to use their judgment while leaving the boundaries mysterious.

The person escalating can help by bringing context. What outcome are we protecting? What options have been considered? What makes the decision difficult? What happens if we wait?

The founder has a responsibility too. If I respond impatiently to a well-judged escalation, I should not be surprised when someone delays the next one. If I reverse every reasonable decision, I am teaching the team that authority is mostly decorative.

Solve the recurring problem as well

A clever solution is satisfying. A recurring obstacle deserves a second look after the immediate pressure has passed.

Was the problem unusual, or did it reveal a gap in the way we work? Did the team lack information? Was responsibility unclear? Did a promise get made without the people delivering it being involved?

I want to remain available for creative challenges. I do not want to become necessary because we have failed to make ordinary decisions easier.

That distinction matters in event planning, where each celebration is personal but not every operational problem is entirely new. The company should learn from experience while keeping room for the genuinely unfamiliar.

The most rewarding version of my role is not being the only person who can save the day. It is helping a capable person get past something difficult and watching them continue with more clarity than they had before.

If I have removed the obstacle well, the team can move. The work becomes theirs again, and I can turn my attention to the next thing that needs to be built.

Explore all planning guides → Sausalito celebrations →

Plan With ERIA

Ready to bring this to life?

Tell us what you are planning. Our team will help you shape the experience from first idea to final detail.

Start a Conversation
Problem solvingFounder leadershipTeam developmentOperations

Continue Reading

Recent Articles