So lets pretend you are on a high profile (and as you are led to believe ) important project. Lets also pretend that this project is on a specific piece of hardware. The hardware is important because it is all powerful. The goal (also lets pretend) is to take existing software and make it work on the fast hardware making the combination of machine and software a delight to the customer.
Did I say the project was important? Let me reiterate. Its important.
But since its on a specific piece of hardware, you would imagine, yes?, that you need that hardware to build on or at the very least, test your delightful software on. No?
So how would you demotivate your team on this important project? Its simple if you follow these important steps:
1. Only supply one platform what at least two is needed. That way the people on the project are fighting for time/space/sanity.
2. That one box must show up late. So late in fact that the entire team must, absolutely must, spend evenings and weekend to meet a deadline for a beta demo. This overtime would otherwise have been avoided if the specific hardware it required showed up on time.
3. Make additional absurd demands. Late breaking bug shows up in the middle of the night on Sunday. Then expect that bug to be fixed by Monday morning from a team that already worked the weekend to get basic functionality working for a beta candidate which was delayed by 1, and 2 above.
4. Blame the team. Ensure you blame the people on the team loudly, publicly, and abusively if that issue in 3 is not fixed on Monday morning. Do not consider that items 1 or 2 had anything to do with beta release time or quality. Ignore the fact that they have been working weekends and evenings because of 1 and 2.
The absurdity of this combination of steps are guaranteed to demotivate your staff.
skip to main |
skip to sidebar
My Brain on Karate, security, and whatever...
