Dave Christiansen over at Information Technology Dark Side is talking about perverse incentives in project management, which he defines as:
Any policy, practice, cultural value, or behavior that creates perceived or real obstacles to acting in the best interest of the organization.
One class of these perverse incentives comes from the methodology police. These departments exist to turn all processes into checklists. If only you would follow the checklist, everything will work. But more importantly, if you follow the checklist you can’t be blamed if you fail.
How’s that for perverse?
A great example is that there is rarely any incentive to not spend money. Before you decide I’m out of touch with reality, notice I didn’t say “save money.” I said “not spend money.” Here’s the difference.
IT by the numbers
Let’s say you do internal IT for a company that produces widgets. Someone from Operations says that they need a new application to track defects. If you follow the checklist, you:
- engage a business analyst, who
- documents the business requirements, including
- calculating the Quantifiable Business Objective, then
- writes a specification, which is
- inspected for completeness and format, then
- passed on to an architect, who
- determines if there is an off-the-shelf solution, or if it needs custom development.
At this point you’re probably several weeks and tens of thousands of dollars into the Analysis Phase of your Software Development Lifecycle. Whose job is it to step in and point out that all Ops needs is a spreadsheet with an input form and some formulas to spit out a weekly report?
Let’s put some numbers to this thing.
Assume the new reporting system will identify production problems. With this new information, Operations can save $100,000 per month. A standard ROI calculation says the project should cost no more than $2.4-million, so that it will pay for itself within two years.
Take 25% of that for hardware costs, and 25% for first-year licensing, you’ve got $1.2-million for labor costs. If people are billed out at $100/hour – and contractors can easily go three to four times that for niche industries – that’s 300 man-weeks of labor. Get ten people on the project – a project manager, two business analysts, four programmers, two testers, one sysadmin – and that’s about seven months.
If everything goes exactly to plan, seven months after the initial request you’re $2.4-million in the hole and you start saving $100,000 per month in reduced production costs. Everyone gets their bonus.
And 31 months after the initial request, assuming nothing has changed, you break even on the investment. Assuming the new system had $0 support costs.
But what if …
Way back at the first step, you gave a programmer a week to come up with a spreadsheet. Maybe the reports aren’t as good as what the large project would have produced. You only enable $50,000 per month in savings. That week to produce it costs you $4,000 in labor, and $0 in hardware and licensing.
You are only able to show half the operational savings, so you don’t get a bonus. You don’t get to put “brought multi-million dollar project in on time and on budget” on your resume.
And 31 months after the initial request, the spreadsheet has enabled over $1.5-million in operational savings.