This is Steveer Robbins. Welcome to the Get It Done Guys, quick and dirty tips to work less and do more.

Timmy is on to a new adventure. He's learning to program computers. And the class that he's taken has put him in a group project.

We just love group projects, building the control software for a missile that will someday be used by a renegade group

of zombie hunters to enslave what remains of the post-apocalyptic world of 2024. They added him

to a project team that was already up and running. Oh, he's thrilled. His new teammates are

great people. They've started the project already. They've laid the groundwork. They've already

programmed the foundation of the

system. And they've made a lot of mistakes. Their scripts don't work. Their builds don't build.

They've simply created bad software. Timmy is pulling his hair out, which is a shame because

he has pretty much flawless hair. He looks sort of like Peter Parker, crossed with teenage

Clark Kent. He wants to call

his team together and tell them, it's an honor to be part of your team. Unfortunately, you're all

incompetent boobs. Your designs are wrong, your scripts are broken, you have no idea what you're

doing. And then, of course, he'll tell them the right way to do everything. He'll be so grateful

from then on that they totally listen to everything he has to

say, and they adopt all of his ideas without challenging them. They'll also have him kidnapped,

roll him naked in Oreo ice cream cake, and leave him tied to the top of a mound of Texas fire ants.

They might even test out the missile on him. This would be a terrible, terrible waste of an

otherwise scrumptious Oreo ice cream

cake. There's got to be a better way. And there is. When you want to give your co-workers feedback

that their design sucks, do it in a way that has them thanking you for it. The first step to lovingly

criticize your loyal teammates is to understand what it is that you want to criticize them for.

...