Discussion of use cases and implementation experience integrating with Workday

["Nathan A. Dors" <>]

Since discussion is beginning, I thought I'd ask about our tactics for vendor management, as well as related coordination with our local stakeholders and implementation projects.

We have a set of topics in our wiki and want to use this list, the wiki, calls, and, most importantly, the Workday Community process (brainstorms, voting, etc.) to advance topics of shared interest in a coordinated way to amplify our collective voice and influence Workday.

How should we go about this generally?

What kinds of intermediate milestones are useful to track?

e.g.  "discussion is now open on a topic" or "consensus on a topic has been achieved" or "a brainstorm is now available for review" or "it's time to go vote up that brainstorm".

How do we use votes, comments, and Workday's "reputation events" to maximize our influence?

Is there an article in Workday Community about the Workday Community process?

I've had casual conversations with local project stakeholders, where I've asked if it's OK with them for us (IAM team members with Workday Community accounts) to go and vote up the brainstorms that matter to us, without prioritizing them against other functional requirements and other needs. These stakeholders control our Workday Community accounts, and I don't want them to deprovision them because we're overzealous about IAM enhancements.

PROPOSAL: how about I email Chris Co and Archana Ramamoorthy to let them know we have this InCommon community discussion going and seek their advice on how best to work with them on the handful of current/future topics.

That's just a strawman step and more experienced folks might have better ones.

-Nathan