STEMMONS Roadmap


Roadmap

Strategic roadmap planning is very important within a Company because it sets long term goals by planning more specific shorter term goals in order to accomplish an ultimate goal. This is often a process that is hard to keep track of or visualize. Central allows for progress to be tracked and recorded within the system so that, using reports, anyone involved in the process can visualize the entire process. Managers will be able to analyze progress and make decisions on where to allocate resources in order to fulfill long term goals within the planned time.

User Experience:

  • Director assigns case to team to create a strategic roadmap
  • Instructions for planning a roadmap are provided in Standards
  • Quest for is used to hold structured meeting, plan out roadmap and decide on mission statements, high level goals, and mid level goals
  • Goals are registered into Entities and associated to team, department or person in Departments
  • Cases are created according to goals outlined in roadmap
  • Recurring CAST will call for status meeting be held by team or department
  • Instructions to hold structured status meetings will be provided 
  • Quest form is used as a structured meeting agenda and any necessary additional cases are created
  • Progress of roadmap can all be tracked in a Roadmap report

Functional Setup:

  • Roadmap case type must be created
  • instructions on how to hold a structured roadmap meeting must be created and documented in standards
  • Quest form for structured meetings must be created
  • Entity types for mission statement along with high/mid level goals must be created
  • Association of goals with their respective department, team or employee must be created
  • Case  types for any case necessary to reach a roadmap goal must be created
  • Report tracking all roadmap cases and their completion status must be created
  • CAST must be programmed to assign periodic status meeting cases to team members

Best Practices:

  • It is important that everyone agrees and understands the various goals that are set in place in order for everyone to work toward the same goals
  • Ensure instructions are specific and that Quest forms cover all aspects necessary for a roadmap meeting
  • Assign initial cases to a team Hopper so that anyone can take ownership of a task, unless specific task requires a specific person
  • Associate roadmap cases to the mission Statement or high/mid level goal in order to allow for tracking of progress

Leave a Reply

Your email address will not be published. Required fields are marked *