The business managers and users do real work, just as they would in their offices and cubicles. When they hit a snag, they call a developer over to explain what isn't working as well as it could and describe what they'd like the system to do instead.
Being gurus, the IT developers either make the system do it, or they explain that making the system do what the users described would be very expensive, complicated, and fragile. But here's something that would be much easier that's close, and would that work well enough?
They get to an agreed-upon solution and the developers, being gurus, implement the change quickly. (You might recall the statistic, reported in Frederick Brooks' classic "The Mythical Man Month," that the best programmers are 10 times more productive than average ones.) Rinse and repeat.
Modern IT departments understand their role is to collaborate with everyone else in the business to make designed and planned change happen. CRP is an excellent methodology for succeeding in that role. If you're an ERP guru, you're just who they need.
But wait! There's more! Remember the single-actor practices we've been talking about for the last couple of weeks? In future columns we'll talk in depth about what sorts of technology single-actor practitioners will need. For now, we'll leave it at this:
The nature of a single-actor practice is that no two situations are exactly the same, and success will never look exactly the same, either. As a result, single-actor practitioners will constantly ask IT to get its systems to do just one more thing (fare thee well, Peter Falk). By the way, there's serious revenue on the line, but to get it, we have to act quickly.
Traditional IT hurls all over this sort of request, often offering the popular phrase, "A lack of planning on your part doesn't constitute a crisis on my part," in response.
Future IT understands that even in businesses that aren't entrepreneurships anymore, when it comes to taking care of high-margin customers, the business had better be more entrepreneurial than before.
Which means, that's right, IT doesn't say no anymore and doesn't look down its nose at the requester, either. Instead, it connects the company's single-actor practitioners with its ERP gurus. They saddle up. They do the job. Then they ride off into the sunset until they're needed again.
This story, "A surefire bet for IT job security," was originally published at InfoWorld.com. Read more of Bob Lewis's Advice Line blog on InfoWorld.com. For the latest business technology news, follow InfoWorld.com on Twitter.