Automate

Hello WUGgers-

I am leading my organization's transition from manually managing SAP master data via excel templates and archaic data acquisition processes to the WOW (world of Winshuttle).  

As a starting point, we are working with the Winshuttle developers and are in the process of developing the MM & Source List create & change workflow, forms and scripts. 

Suffice it to say, we have several additional Winshuttle development opportunities.

My ask of you - what planning process have you all used to rationalize a sensible Winshuttle development queue?  Or, how have you listed and prioritized your Winshuttle development opportunities?

Thank you so much for your feedback!

Regards & remain healthy-
Luke

------------------------------
Luke Lenahan | Master Data Manager
Panasonic USA | 770-883-1112
------------------------------

Hi Luke,
I would prioritize the "quick wins" first. Relatively quick to deploy, and has a high impact. Some criteria I look at is if it is high volume, repetitive, frequent, and impacts several users. You also have to build in some X-Factor where the team that screams the loudest or has the most pain gets a slight edge in priority. 

I've also seen some companies implement a Winshuttle steering committee. They get an Executive sponsor and nominate some key users. Then, they participate in a monthly meeting to discuss all things Winshuttle and review the priority list together.

------------------------------
Yoon Chung | SE
Winshuttle North America
------------------------------