Our approach.


No two pieces of consultancy work are the same, and we obviously strive to make to make the most efficient use of ours and your staff’s time.

Firstly, and most importantly – we take the time to listen to exactly where the problems are perceived to be; we then write an outline proposal detailing what our intended approach would be, and why.

Once this has been agreed, the consultant would interview key people, and write a Terms Of Reference document, and this will drive the assignment. The TOR would include our estimates for the amount of consultancy (in terms of days work) and the likely time required from your staff. We then agree a mutually convenient time for the Consultant to start.

We often get asked to analyse a group of projects, or a programme of dependent projects, and report on the working practices between IT groups from Business Analysis through to 3rd-line support

Occasionally, we are asked to look at a specific project, and overlay our Implementation Process on the methodology being used by the project to get an early view on the likelihood of post-implementation failures or issues will occur. In some cases, the method in use may ensure that recurring issues and shortcomings are dealt with early on in the lifecycle, in which case we would report on this. This has proved to be useful for client companies keen to illustrate more than "due diligence" to demanding end-users.



Implementation Planning


Technical Project Management


Support Acceptance