# data[].attributes.body
Post Go Live support and follow up has been great

# data[].attributes.headline
Cretae more training videos that can be used later 

# data[].attributes.subject
Cretae more training videos that can be used later 

# data[].attributes.body
Communications
Training Materials
Testing Materials

# data[].attributes.headline
It would have been better to understand the gaps upfront current process - vs new world

# data[].attributes.subject
It would have been better to understand the gaps upfront current process - vs new world

# data[].attributes.body
While team meetings were important - they took up alot of time out of our day to day schedule and maybe there could of been less to not have as much as an impact on own roles.

# data[].attributes.body
Testing & Training ended resource usage was quite high and difficult to cover it whilst staying on top of Day to Day functions

# data[].attributes.body
Reiterate the approach we are taking to prevent scope creep

# data[].attributes.headline
Maybe on the discovery days we should have involved more peolple. The parts challenges may have been explained more.

# data[].attributes.subject
Maybe on the discovery days we should have involved more peolple. The parts challenges may have been explained more.

# data[].attributes.body
Great to have the support & production knowledge of the system from the US Team who us it

# data[].attributes.headline
Discovery could be improved, to concetrate on areas that created most difficulty

# data[].attributes.subject
Discovery could be improved, to concetrate on areas that created most difficulty

# data[].attributes.body
Great to have support from US colleagues

# data[].attributes.headline
Defined owners of ERP, IE it is easy with Roel, SAP more challenging 

# data[].attributes.subject
Defined owners of ERP, IE it is easy with Roel, SAP more challenging 

# data[].attributes.headline
Being able to demo the US solution really early. Drip feed of content / questions

# data[].attributes.subject
Being able to demo the US solution really early. Drip feed of content / questions

# data[].attributes.body
Comms were very good throughout

# data[].attributes.body
Preparation was critical
Involving as many users as possible supported highlighting issues and getting buy in from all
After go live support was and still is critical to maintaining buy in from all

User training, was difficult to allocate time with small engineer team

Time lines were very tight and our day to day duties were impacted

# data[].attributes.headline
Technical analysis up front to find issues with data/ integration

# data[].attributes.subject
Technical analysis up front to find issues with data/ integration

# data[].attributes.body
Remote training was a new challenged. I think it was recieved well by the FTs. we must keep feeding video and support over the next few weeks

# data[].attributes.body
In the UK we haven't yet completed end to end process testing (all processes). This is an important part of the implementation and is needed to ensure we encounter no surprises on issues on go live.

# data[].attributes.body
Leaving the complex integration work until the very last week before scheduled Go Live

Left little / no time for testing, understanding & fall back if delays were met

# data[].attributes.headline
Things to think about as an entire project team including technicial team, business, testers, SMEs etc

# data[].attributes.subject
Things to think about as an entire project team including technicial team, business, testers, SMEs etc

# data[].attributes.body
How was the project run?
Did we have the right SMEs and support?
What was testing / training like?
How did we manage being remote?
Were we accepting or resistant to change?
What would have made us more efficient?
Were the meetings and cadence effective?
Was the solution as expected?