# You Think You Can Control Us?
Source: https://www.yegor256.com/2018/10/09/can-you-control-us.html
I was explaining how [Zerocracy](https://www.zerocracy.com) works to one of our prospective
clients yesterday. He texted me today:
"[At Zerocracy] there is no commitment and anybody is free to leave any time,
so the risk of entrusting a highly important project to such
a platform and failing to deliver it on time is very high.
We will develop it on our own with hired developers who
will have salaries, and I'll be architect and project manager,
that way it will be under our entire control." I think this word "control"
he used deserves a comment.
{% jb_picture_body %}
First, I know how much we hate the word "control" when it's being applied to
us sensitive and fragile individuals, also known as computer geeks. We don't
want to be under anyone's control. We also don't want to control others. We prefer
to think that things just move forward on their own, not because someone
stays on top of them and controls them.
However, this is an illusion.
We and our projects have to be under control in order for the projects to be completed.
{% quote We have to be under control in order for the projects to be completed %}
OK, replace it with managed, organized, or (I love this word) orchestrated.
The bottom line is: you control it or you lose it.
What does control technically mean? According to
[Wikipedia](https://en.wikipedia.org/wiki/Control_%28management%29),
it means "setting standards, measuring actual performance and taking _corrective action_."
What are the corrective actions in the context of people management?
There are two: rewards and punishments. In order to keep even the
[most talented people]({% pst 2014/aug/2014-08-13-strict-code-quality-control %})
under control, we have to reward them for their successes and
punish or [fire]({% pst 2015/sep/2015-09-16-how-to-fire-someone-right %})
them for their failures.
The question is how you do that. How do you reward and how do you punish?
Even if you don't want to admit that you do it, you still do. You reward
and you punish. How does it happen in a traditional management model with the
"hired developers" my prospective client was talking about? I've explained it already
in a few blog posts. [_How to Pay Programmers Less_]({% pst 2016/dec/2016-12-06-how-to-pay-programmers-less %})
and [_How Do You Punish Your Employees?_]({% pst 2016/jan/2016-01-05-how-to-punish-employees %})
are probably the best two of them. Managers invent [nice words]({% pst 2018/aug/2018-08-29-soft-skills %})
for these things, but in reality it's still the same carrot-and-stick, only with no predictability and
no explicit [rules]({% pst 2015/oct/2015-10-13-competition-without-rules %}).
{% youtube ezE0hRH9BnQ %}
However, if you think that you can control _professional_ programmers
using the methods explained in my blog posts above, you are mistaken.
We are way smarter than you. We know how to pretend to be working, while
doing something else. We know how to create an illusion that we are loyal
to the project, while searching the market for a new job. We know how to
organize our time such that you only get ten percent of it, if you are lucky. We know
[how to manage]({% pst 2017/aug/2017-08-01-how-to-manage-a-manager %}) you,
our ~~stupid~~ managers.
As our manager, expecting us to be under control and loyal just because you hired us with
[monthly salaries]({% pst 2015/jul/2015-07-21-hourly-pay-modern-slavery %}),
you are demonstrating only one thing to us:
you have no idea how to manage senior developers. Instead, we will manage you.
You will be under our control, not the other way around.
If you are lucky, the project will _maybe_ see its end.
But in most cases this doesn't happen.
Do you want to know what real control is? Read this [Policy](https://www.zerocracy.com/how-it-works),
which is how we _control_ programming in Zerocracy. That is the level of
control true professionals enjoy. That document, fully supported by our
[automated chatbot]({% pst 2018/mar/2018-03-21-zerocracy-announcement %}),
guides every small piece of reward and punishment a programmer may have on a project.
This is what true commitment means for our guys: personal and
[explicit responsibility]({% pst 2014/apr/2014-04-13-no-obligations-principle %}) for
every single step they make. This level of commitment is incomparably better than what
you will likely find when hiring full-time 9-to-5
[office]({% pst 2015/oct/2015-10-06-how-to-be-good-office-slave %}) ~~slaves~~ employees.
What are they really committed to? To giving you a month's notice when they
finally find a better place to scroll through Facebook eight hours a day?
Seriously?