Relinquishing control to our Council - A radical experiment


January 21, 2016

It’s true. Our Council members wield significant power and influence. Revenue targets, profit margins, important company policies - they make decisions in all of those areas and more.

But who are these people? If you’re imagining a bunch of grey haired, suited and serious folks sitting around a large mahogany table, here's some stats:

How did they get the job, you ask? They got elected. Democratically. There’s a fixed number of council seats. There’s a nomination and voting process - not very different from how you’d expect a democratic system to function.

The eligibility criteria to get nominated? 6 months of experience at Multunus. That’s it. Nothing more, nothing less.

If you’re rolling your eyes in disbelief, read on. There’s a method to the madness.

The fundamentals

A key question that every company with more than 10-15 people needs to answer is this:

This question cannot be answered without sufficient context. The following question needs to be answered first:

And to answer the above question, the following question needs to be answered before that:

So let’s start from the last question and work upwards from there.

What type of business are we in? What does success mean for us?

We’re in the software services business. We build software products for our customers, augment their existing tech teams and also provide technology and design consulting services.

In that context, here’s what success means for us:

What type of culture will ensure the most amount of success for our business?

Needless to say, our culture needs to be be aligned with and support our vision well. If everyone is to be a CxO, a key attribute that we’d need to consider would be Autonomy.

NOTE: Autonomy is * not* Empowerment. If we’re drawing the boundaries of a playground and inserting our team members as players with those constraints in place, that’s empowerment. Its when we remove those constraints, look away and trust our team to do the right thing, that we become truly autonomous.

The next logical question then is this: What functions of our business need to be autonomous? Just those parts that are most relevant to the day to day work of each team member? Or all other functions of the company as well? For example should we include Finance, Marketing, Operations and Sales, as well under everyone’s purview?

If we applied logical reasoning here, we’d probably come to the conclusion that these are functions that require deep experience in their own right, to make critical decisions. And it’s best to leave it to the “professionals”.

While that’s a reasonable conclusion for most companies, it’s not aligned with our vision of everyone playing the role of a CxO. For us to make that vision a reality, we need to provide as many avenues as possible for our team to engage in our business. No holds barred.

But how do we make that happen? How can we have people with little or no experience in these functions make important decisions, without compromising the sustainability of our business?

That finally brings us back to the question we started this section with:

What kind of organization structure makes the most amount of sense for us? A hierarchical one? Or a flat one?

Those are the two obvious choices available these days.

A strictwith its command and control style of functioning - leaves almost no room for experimentation and failure, thereby leading to little engagement in the business as well.

Aat the other end of the spectrum seems, on the surface, like an ideal solution for creating an autonomous workplace. But this doesn't work well in practice. A lack of rules or guidelines combined with little or no delineation of responsibilities could result in risking business sustainability.

What if we could meet somewhere in the middle? Here’s the structure that we currently have at Multunus:

Heads Council Everyone Circles

How well is it working?

Here’s some of the key decisions that the council (and the rest of the team) has taken so far:

Those are some discreet examples of important decisions made by the council.

But here’s a magical moment that happened a couple of weeks after we rolled out the council  system: One of our newest employees (a fresh grad barely out of our on-boarding program) had an open debate with the founder (yours truly) in a public forum. I later commended him on the courage he’d shown in openly voicing his thoughts.

His response:

I couldn’t have said it better, myself. That, in a nutshell, is engagement in the business.


This experiment is still in its early days and we’re battling some rough waters. Here’s some of them:


Relinquishing control is a scary proposition for most founders and executives. But if done carefully, it's worth it. We’ve been pleasantly surprised by the maturity of decisions that our Council has taken so far.

There is one potential issue though. Of the original founders of the company getting lost in a sea of many other founders and CxO’s.

Still worth it, we think ;-)