Walking Contradictions - I Dont Love Leadership

There has been a contradiction in my life for years, and I have only recently started articulating it clearly. I have led communities before . I have been part of founding teams. I have worked inside startups. I repeatedly find myself in environments where leadership, impact are either finds me or is quietly handed to me. yet despite this pattern, I do not think of myself as someone who loves leadership. In fact, if I am honest, I have often avoided it.

From the outside, my trajectory might look intentional. It might appear as if I strategically pursue positions of influence. but internally, that has rarely been the case. most of the leadership roles I stepped into were not aggressively applied for. I was nominated, recommended, or invited. sometimes I simply filled a vacuum because something was collapsing or drifting without structure. I did not chase titles; I responded to dysfunction.

This is where the tension begins. I seem to fit naturally into leadership environments. I gravitate toward startups, toward communities being formed, toward spaces where structure is still fragile. I see inefficiencies quickly. I instinctively redesign systems in my head. I cannot sit comfortably inside a poorly constructed environment without imagining how it could be improved. And when you repeatedly do that, people start assuming you should lead.

But the truth is that I deeply enjoy being an individual contributor, I like depth. I like immersion. I like sitting alone with a problem and pushing it until it yields. I prefer building something tangible over managing conversations about building something. I do not enjoy becoming the project manager who constantly asks for progress updates. I do not get energy from monitoring. I get energy from creating.

Even when I lead, I rarely lead from a distance. I do not stand outside the system issuing instructions. I put my hands in the work. I code, I design, I draft, I restructure. This is not because I am compensating for weak management skills. It is because I prefer leading through architecture rather than supervision. Instead of hovering over people, I try to design teams that are self autonomous. I focus on clarity of roles, clear systems, and shared expectations so that constant checking becomes unnecessary.

If the environment is structured properly, management becomes lighter. once a team understands its direction and trusts its internal processes, it does not need someone repeatedly asking how things are going. It moves. that is the kind of leadership I can tolerate, and sometimes even enjoy.

What I dislike is ceremonial leadership. authority for the sake of hierarchy. endless coordination meetings. political navigation. status maintenance. those drain me quickly. when leadership becomes more about social positioning than system design, I begin withdrawing.

So am I contradicting myself? How can someone repeatedly end up in leadership roles while preferring individual contribution?

I think the answer lies in autonomy, I value autonomy deeply. I have written about it before , and it remains one of the few words that consistently explains my decisions. I do not want to be a passive follower executing someone else’s vague plan. but I also do not want to dominate others or control them for validation. the ideal state for me is being an individual contributor with autonomy. full ownership of output. freedom of execution. minimal unnecessary interference.

Sometimes leadership becomes the only way to secure that autonomy. If the environment is chaotic, I restructure it. If direction is missing, I define it. If the system blocks efficient work, I redesign it. In doing so, I inevitably step into leadership, not because I crave authority, but because I crave functional environments.

In that sense, leadership for me has never been about power. It has been about environmental control. not control over people, but control over structure. the ability to shape the conditions under which work happens. once those conditions are stable, I often drift back into contributor mode. I build alongside everyone else.

There is also another layer to this tension. leadership carries responsibility. responsibility means visibility. visibility means being accountable not only for your own output but for collective outcomes. that weight is not something I romantically admire. It is heavy. sometimes I avoid leadership because I do not want to carry that psychological load.

And yet, despite all of this hesitation, I cannot deny that leadership has been rewarding. watching a team grow because of systems you helped design is satisfying. seeing individuals outperform their own expectations is meaningful. observing a culture stabilize because of structural decisions you made months earlier produces a quiet sense of accomplishment. It is not glamorous, but it is real.

Perhaps the contradiction dissolves when reframed properly. It is not that I want to avoid leadership entirely. It is that I want leadership stripped of ego and bureaucracy. I want it reduced to architecture. If leadership becomes system design, autonomy protection, and clarity creation, I engage fully. If it becomes symbolic authority and endless coordination, I retreat.

So I may continue to find myself in leadership roles. I may even accept them in the future. but I will never chase them for status. If I step forward again, it will likely be for the same reason as before: because something needs to be structured properly, and because inside that structure, I can still operate as a builder.

The tension is not between leadership and individual contribution. It is between authority and autonomy. And if I have to choose, I will always choose autonomy, even if it occasionally wears the mask of leadership.