Thursday, January 24, 2019

Picking what NOT to do is an IT Strategy

Technology change and progress never stops. There is always a newer version, a better alternative piece of software or another way of supporting an evolved business process or two.
For internal technology departments and especially those within larger organisations, this rate of change means there's never an end in sight. In a world of infinite need and finite resources... there's usually a long list of things to do once the current projects & programmes have been delivered.
With all this demand and the expected pace of implementation (that can come from all angles including: business stakeholders, vendor sales people and consultants) it can feel like everyone wants to change everything at once:
New finance system? Yes
New HR software? Sure
New B2C website? Of course
New B2B website? No problem
New sales portal? Yeah
New customer data platform? Naturally

Faced with a these requests, perhaps along with a potential new-found investment in technology to fuel a "digital transformation", senior IT people will want to say yes. Who wouldn't want more resources, increased budgets, the chance for some new "toys" or the opportunity to stick a big 'look what I've done' post on their LinkedIn profile?
But like the proverbial plate spinner, who (theoretically at least) should know how many plates they can spin at once... those in a position to take on technical work need to understand how much change they can take implement before they hear the sound of virtual crockery smashing. Experience needs to inform them (and so do their managers, subordinates and peers) just how much change their organisation can take on in parallel.
But when the demand for so much change outpaces the organisation's ability to deal with that change, someone has make the important decision as to what to do and therefore what NOT to do. 

Nobody, least of all IT people (prehistorically noted for saying "the answer is no, now what's the question?") want to tell a business stakeholder that their project is less important than another... but sometimes there is only so much change you can do at once.

No comments: