In our schools today there is a special word we use when we talk about teamwork.
From the moment we enter elementary school, straight on through high school and well into college, this concept gets drummed into our heads every time the idea of teamwork comes up.
We call teamwork: cheating
It’s cheating. If they catch you working together on tests or problem sets or exams, you get in trouble and they kick you out. So it’s not just that we don’t teach teamwork in the schools, it’s that we actively discourage it.
So it’s no wonder that when you get out in the world, and assign work to someone, and the work comes back not done, that the usual response is to throw up your hands, saying “delegating is hard,” “you just can’t trust people,” and “it’s easier just to do the work myself.”
We can’t blame you. That’s what you’ve been taught since elementary school. That you have to do all the work yourself.
We are excited to share with you a better way.
It’s called Collective Engineeringtm and it’s literally the process for developing great teams. Collective: of the group. Engineering: the process of putting knowledge to practical use.
See, the thing that probably no one has ever taken the time to fully teach you is that delegating is a process, and the first step in that process is the work not getting done.
Collective Engineering is the set of strategies you apply next, to move the process forward, developing trust and communication so that work can get done even when you are not there.