2. selecting a solution

Goals? Well, they’re obvious aren’t they? “We need to fix our (inventory|security|llama|management|data) problem.” That should be good enough for anyone. Defining the requirements in any kind of detailed way is just going to eat up time. We want a solution now.

Don’t waste time looking at your local environment or talking to the staff. Who cares if the solution you choose is completely incompatible with your existing infrastructure? You want “best in class,” right? Just ask your vendor. Besides, they said the system requirements are pretty basic.

3. implementing the solution

There’s no need to talk to the people who will have to support and maintain the solution either. They’re just a bunch of whiners.

Buy it. Tell the support team you want to start using it next week–they should get busy.

4. failure

Congratulations! Your work here is done. If it doesn’t fail, it’s not because you haven’t tried. It will certainly at least be over budget and significantly over time. If you like, you can berate and blame your staff/consultants for the failure.