4c. Manage the Implementation – completion

ACT//DO//DELIVER

Completing the implementation

Every type of digital project might have different tasks that you should undertake as the project comes to an end. For example, a website development is likely to require user acceptance testing, training in the content management system, and a “snagging period” where any errors discovered during use, can be quickly corrected.

Remember – let people play with the new digital development, and soft launch it first. Get a friendly group of audience members in, and watch how they navigate through the new systems so that any help that you provide online and off can support common questions.

All projects should have a start and an end, and just as you will have formally agreed to start a project, you should look to formally close down the project once it is launched and just part of “normal activity”. The closedown should include :-

  • ensure completion of all financial spend
  • completion of a file containing all project documentation (including throwing away anything that is no longer relevant)
  • storing and sharing any assets (e.g. photographs, videos, contracts)
  • reflection and evaluation
  • Once a project is completed why not invite everyone who is involved to a social event as a recognition of their involvement in making it a success? If there is something to show – such as a new website, or some videos, make this the centre piece of the event.

     

    What’s Next?

    You have successfully completed the AmbITion Approach through the auditing of where you started from, the diagnosis of your needs, the development of a business case, and through the implementation itself. Throughout that process you should have been reflecting and evaluating, and that should continue once the project ends.