This post was originally published on Spend Matters.
Your company has chosen a Vendor Management System (VMS) and you’re anxious to get started on implementation …but STOP! An implementation project’s success begins with a well-organized and thought-out plan prior to kick off.
As Winston Churchill stated, “He who fails to plan is planning to fail.”
Last Friday brought the final jobs report of the year and of President Obama’s tenure. While the headline number of 156,000 new jobs was below analysts’ expectations, this was hardly a negative report. The most exciting news came from wages which increased by 2.9 percent - the largest year-over-year wage growth we’ve seen since 2009. Average hours remained steady, while the labor force participation rate rose to 62.7 percent.
As the year comes to a close, what changes can we expect in the workplace next year? For this month’s workforce wrap up, we collected articles highlighting workforce trends for 2017.
Today, Ross Blythe, a member of the Business Process Management team at SAP Fieldglass returns to the blog to discuss the significance of proper documentation during the implementation process. Welcome, Ross!
When faced with implementing a Vendor Management System (VMS), documentation is traditionally everyone’s least favorite task – except for the lucky few of us who enjoy design documentation. However, it is absolutely critical to laying the foundation for a successful implementation project.
When I started in my new role as Global Manager for Customer Engagement and Advocacy at SAP Fieldglass in July, I knew we had great customers. From working directly with them to simplify their process or educating them on our technology, I had interacted enough to know that they were passionate and driven. They love what they do and strive to balance running a day-to-day program while staying ahead for the curve. The past six months re-engaging our broader, global customer community has reopened my eyes to how our customers continue to rise above the rest.