camiseta del everton 2011 -
Unless you're the world's most dedicated Luddite, you're likely to be pretty enthusiastic about the ability of technology to transform your business for the better. In shared services in particular, IT has an almost magical capacity to improve efficiency and effectiveness - and to do so across wide swathes of the organization, freeing up huge sums to go back into the business and generally improving life no end.
However, before you can attain the Nirvana of process perfection it's necessary to go through the altogether less enlightened state of actually implementing the technology in the first place. And as many camiseta del everton 2011 of you can testify, that's not necessarily just a piece of cake: many's the gray hair that's manifested itself as a result of putting a new system in place - only to be torn out at the root during yet another round of "improvements" (i.e., making right all the cock-ups of the initial implementation.)
However, help is at hand. In order to preserve the wits - and hair - of network members looking to put new technology in place, SSON has asked a few experts for their advice on the things that can make the difference between the smoothest implementation and the roughest of rides. So if you're looking down the barrel of new technology and worried you might be in for a difficult time, fear not: just get stuck straight in to SSON's Top Ten Tips for Optimal System Implementation…
1. Keep focused
No matter what area of business you're in, the implementation of a new system opens up whole new galaxies of possibilities - at least, in the minds of those who're going to be using it. It's incredible how easily "scope creep" can kick in: you might start off just aiming to centralize and systematize payroll, but once the team gets its heads together and looks at all the possible added extras, within a matter of moments you might be looking at a company-wide HR transformation project (this kind of issue can be particularly problematic with solutions developed in-house where keeping reins on the imaginations of the developers can feel like a full-time role). Remember what your objectives are for this system implementation and stick to your path; if useful doors open up along the way showing new opportunities, all well and good, but make sure you get where you want to go rather than getting lost in wonderland.
"Keep a tight well defined scope," urges Philip King of Atos Consulting. "This is where most systems implementations founder; don't try to bite off more that you can chew; start small and extend in later phases if desired; for example in a new HR system many will start with basic data and administration functions before moving into more advanced services."
2.Optimize from the beginning
The old adage "a stitch in time saves nine" applies just as effectively, if not quite as literally, to systems implementation as it ever did to knitting - especially if you're designing your own system. Remember how far this system is going to penetrate into your operations, how many people (perhaps across many different business areas) will be using it, and how many other systems it has to interact camiseta del everton 2011 with in one way or another: it's up to you as the one in charge of the project to make sure every last ‘t' is crossed and ‘i' is dotted in terms of compatibility, flexibility, efficiency, effectiveness, accessibility and a whole lot else. Putting a system in place that then needs constant fiddling and reworking for the next five years to make sure it doesn't throw obstructions in the way of existing processes is a quick route to deep hot water: you're not going to get it exactly right at go-live but if you've tried to optimize on an end-to-end basis - or as far down towards each end as is realistic - from the beginning, you'll have done yourself and the system's operators one massive favor.
"In your design of new systems, you should take into consideration also all aspects of the infrastructure to make the operation of the system smooth and adequate to the user's expectations after the ending of the project," says PBI's CIO, Rafael Carrasco Vidana. "Whether it be a payroll system to pay to 15,000 policemen, an ERP, or a banking system, besides user requirements for the system, careful considerations about availability, security, capacity planning, serviceability, regulations compliance, ITIL disciplines, etc, need to be considered. It is not so strange to see new systems with bottlenecks that prevent customers from receiving the expected service levels. Then optimization begins (things not taken into account before), but additional phases, redesign, resources, upgrades - time and money - have to be added."
3. Get the buy-in
It's been said before, and it'll be said again: whatever the project, getting it running smoothly is a heck of a lot easier if you've got support from the movers and shakers towards the pinnacle of your organization. It's all the more important when it comes to system implementation because of the sheer scope of the transformation which might apply to so many different individual fiefdoms. Even if what you're doing isn't the slightest threat to John Doe down the hall in Room 102, he might still get shirty about having to lose "his" staff for a couple of days' training when he's already looking like he might miss his quarterly target. Well, watch him wind his neck in when he realizes this project's got the green light from on high…
"Obtain and maintain sponsorship," recommends Philip King. "A new system will bring changes to ways of working. It will require budget and sustained allocation of resources. The project may come into conflict with other business priorities. Key decisions will need to be made on timing, scope, resources, and cost. So strong and sustained governance is imperative."
(For a few handy guidelines on how exactly to ensure that critical sponsorship, why not check out SSON's camiseta del everton 2011 own?"Top Ten Tips for Ensuring Buy-In from the Top")
4. Take time getting the right team for the job
You might have the best people in the world working for you - but right now they're the best people in the world at doing Task A and, at the very least, this implementation's going to change that into Task A 1.2, if not Task B. Furthermore, and more importantly, the team you have are going to be running the system you're implementing - not implementing it themselves, or at least not by themselves. Putting in new technology - especially a big system - requires specifically skilled talent, and it's almost certain that you're going to go outside your team, if not outside the company, to get that talent. So put the time in: this implementation team may be temporary but that doesn't make these folks any less important, or getting the makeup of the team right any less critical. After all: they're the ones doing the work…