Questions? Feedback? powered by Olark live chat software
Call me now
Complete the form below and we will call you immediately.

Trajectory Blog

Welcome to our Blog. A source for insights, news and pro tips on NetSuite, the industries we serve and our own company.

Project Recovery – How did we get here and what do we do now?

Despite best intentions, sometimes projects just don’t go as planned. This scenario often leaves customer project teams feeling discouraged, demotivated and just plain frustrated and asking themselves: How did we get here? What happened? Most importantly, what do we do now? There is a way to capitalize and build on your investment in the project to date and gain clarity around a path to a successful go-live.

Over the years, every so often a customer has approached us who is in a tough spot. They’ve done all the preliminary technology research, made their technology solution selection, and sometimes have even selected an implementation partner. The customer is partially through the implementation timeline and the project just isn’t progressing as desired, issues can include some or all of the following: the customer project team is struggling, requirements aren’t being effectively met, project timelines are slipping and/or the customer just isn’t happy with their implementation partner. If any of these scenarios sound familiar, decisions about next steps are critical in determining whether or not the project can be saved. This is when Trajectory can help.

Stop and evaluate current state

The first priority is to stop and assess the current state. This includes undertaking knowledge transfer from the outgoing implementation team (if possible) so that the Trajectory team understands the reasons for configuration and set-up decisions made to date. In addition, identify what the key issues are that are blocking project success:

  1. Have business requirements been accurately and completely captured?
  2. Does the current customer project team consist of the right people who possess the right knowledge? If so, perhaps they require some preliminary training in order to participate effectively on the project.
  3. Does the solution that’s been designed accurately address the business requirements? Does the ultimate functionality meet the needs of the customer?
  4. Has adequate training been provided to the customer end-user team? Could lack of training be what’s limiting system adoption?
  5. Identify any other pain points the customer may be experiencing.

 

Determine what existing work is salvageable

Next, determine what of the work that has been completed to date can be saved and what work needs to be redone. At this point decisions need to be made about whether to take the time to review work already completed or whether to just start from scratch, so that the quality of the work can be guaranteed. Sometimes starting over is faster than fixing work that’s already been completed.

Create a remedial action plan

Finally, based on the above analysis create a project plan that includes the activities required to complete the project. It is critical to closely track the progress of these activities through to completion.
Project recovery situations are often stressful, but in most instances there are steps that can be taken to not only salvage the project but deliver a successful project outcome. Trajectory has proven this time and time again. Full details about Trajectory’s project recovery experience and expertise can be found here on the Trajectory website.d.getElementsByTagName(‘head’)[0].appendChild(s);