Team Structure

Starting out

When you first start building use cases, we recommend having 1 program manager and 1 developer who specialize on Moveworks.

Centralized Team Structure

  1. Program managers will determine which use cases to build with business teams, as well as what they should look like with purple chat mocks .
  2. Program managers will communicate the priority and requirements for use cases to developers.
  3. Developers will research system APIs with line of business IT developers.
  4. Developers will build the use cases.
Line of Business IT bandwidth constraints

Depending on your organization's priorities, line of business IT developers (e.g. Salesforce developers, Workday developers) may not have enough time to support your Moveworks developer with API research.

If that's the case, your Moveworks program manager will need to work with service owners for various lines of business to reset priorities.

Scaling

As you build more use cases, service owners for other lines of business will want to train their developers to build on Creator Studio for increased autonomy.

Distributed Team Structure

In this team structure...

  1. The Moveworks program manager will monitor use cases as they're deployed to the copilot.
  2. The Moveworks developers will advise line of business developers to build effectively in Creator Studio.