How to implementation almost anything...

This diagram summarises (my own view of) how to roll out almost anything in IT that is not too technical - not an systems deployment, perhaps (which would be full of technical preparations and tests) but certainly a new process or function.

It's quite obvious once you've nailed down the detail, but you may find it helpful. The steps for each of these tasks are summarised below:

1. Stakeholder workshops
   • Scope
   • Goals
   • Impact
   • Process
   • Expectations
   • Participation
2. Finalise key updates
   • Functions
   • Organisation
   • Products
   • Processes
   • Controls
   • Training
   • Intranet
3. Project kick-off
   • Scope + goals
   • Budget
   • Requirements
   • Sponsor + stakeholders
   • Mandate/Project definition
   • Issues + risks
   • Critical success factors + KPIs
4. Communicate with stakeholders
   • Expectations
   • Impact
   • Budget
   • Alignment
   • Authority to proceed
5. Identify audiences
   • IT stakeholders
   • Business stakeholders
   • Delivery managers
   • Development teams
   • Operations + support
   • Regulators & compliance
   • Cross-organisational teams
6. Capture current status
   • Function mapping
   • As-is process/systems
   • Awareness & interests
   • Functional impact
   • Implementation impact
   • SWOT, risks & issues
7. Validate roll-out process
   • Process walkthrough
   • Impact assessment
   • Participation requirements & plan
   • Risks & issues
   • Go/No Go decision
8. Tailor roll-out packages
   • Local expectations + impact
   • Entry/exit points/processes/products
   • Current level of knowledge
   • Local implementation process
   • Local interfaces, access, reporting, etc.
9. Communicate with SMEs & specialised functions
   • Expertise requirements
   • Participation in transition
   • Support during transition
   • Facilitation
10. Train users
    • Functional objectives
    • Walk through solution
    • Metrics & standards
    • Participation in transition
    • Cutover impact
    • Supervision & support
11. Train SMEs
    • [as for Train Users]
12. Brief stakeholders
    • Changes
    • Impact
    • Benefits/value
    • Transition process
13. Roll out components
    • Access tools & privileges
    • Localisation
    • Local integration
    • Measurement tools
    • Support arrangements
    • Remove existing systems/materials
14. Evaluate benefits
    • Take-up
    • Performance metrics
    • Quality metrics
    • User satisfaction
    • Transition costs
    • Stakeholder satisfaction
    • Compliance
15. Close project
    • Validate against requirements
    • Project performance
    • Update support
    • Residual issues
    • Lessons learned
    • Project closure

Of course, this assumes that you have actually captured the requirements, modelled the process and design the implementation components in advance, which isn't always the case. But this process should at least tell you what you need to have done before you get to implementation.