Close

4. Compass Rollout

Prior to commencing your Compass rollout, the following tasks should have been completed as outlined in section 3.

Checkmark icon

PHASE OBJECTIVE
Invite users to the platform, finalize component catalog details, and track benefits.

Caution icon

PRE-REQUISITE TASKS
Checkmark    The component catalog has been populated (Section 3.1)
Checkmark    Required tools/apps have been connected (Section 3.2)
Checkmark    Configure and populate compass ahead of inviting users to the platform.

4.1 Rollout Strategy

Having a strategy that enables your organization to adopt Compass whilst minimizing disruption and maximizing benefits requires careful planning. This guide includes a strategy that you can adapt to meet your specific needs.

4.1.1 Create an adoption schedule

Dividing your organization into logical groups and scheduling windows for adoption is a winning strategy for platform adoption across an organization. Creating windows where specific teams are scheduled to adopt the platform allows teams to plan for any tasks they may need to complete, and allows you to provide a better level of support by spreading demand.

Each adoption group should include an info session where you will provide:

  • Why you’re adopting an internal developer platform
  • An overview of Compass
  • What you expect people/teams to do (including timing)
  • How you will communicate with them
  • Avenues they have to reach out to you and your team for support.


The logical groups will be different for each company, but these could be by department, product, or line of business. The first logical grouping should be a pilot group. The pilot group will be a set of teams that you will use to test your rollout strategy and adjust the way forward based on what you learn.

An adoption schedule should be proposed, and provided to the senior leaders to propose any changes to the schedule. Some teams may have busier or quieter periods that are better suited for this type of activity. Senior leader agreement to the schedule is important, as it acts as a trigger for that team to plan their time to avoid competing priorities.

A suggested adoption schedule format is below:

Product deploy roadmap screenshot

4.1.2 Support strategy

Teams adopting Compass will need somewhere to go for support or have any questions. Below are some suggested techniques to provide support:

  • Create a dedicated Confluence Space—Making information available for teams to access when they need it goes a long way toward providing a great experience. A Confluence space providing all details of your plans, detailed instructions on what people need to do and by when, and support documentation will be valuable during your rollout.
  • Support chat channel—Creating an open channel in your organization's chat tool of choice is a great way to support adopters. People can ask questions in the chat channel and see previous questions that have been answered by your team.
  • Info session—As outlined in section 4.1.1, an info session prior to each group's adoption window goes a long way toward helping adopters become familiar with what they need to do, why they are doing it, and when they need to have it done.
  • Feedback avenues—You need to provide adopters with feedback avenues for your rollout and implementation. There are many ways to capture and triage feedback, with Jira Product Discovery being a particularly good solution.

Info icon

Using AI Agents for support
The AI virtual agent in Jira Service Management can significantly reduce the support burden. The virtual agent accesses your knowledge base to streamline and automate interactions through chat with your internal customers. More details on the AI virtual agent in Jira Service Management can be found here.

4.1.3 Communication strategy

Effective communication with stakeholders can be the difference between a successful rollout, and one that misses the mark. Below are recommended communications to the various stakeholder groups.

REFERENCE 4.1.2.1

Audience:
Senior engineering leaders, e.g. VP or General Manager level.

Purpose:
Inform senior leaders about Compass Rollout.

Key Messages:

  • What you’re doing (Rolling out a Developer Experience Platform)
  • Expected benefits (should come from Section 1.2, Goals and Objectives)
  • What you need from Senior Leaders and their teams
    • Support for the roll-out
    • Effort from their team to update the Component Catalog
  • How you will communicate with them?:
    • Cadence of communication
    • Reporting on Data Hygiene
  • Channels they can use to share feedback


Sent by:
Executive Sponsor

REFERENCE 4.1.2.2

Audience:
Senior engineering leaders, e.g. VP or General Manager level.

Purpose:
Inform senior leaders about Compass Rollout.

Key Messages:

  • What you’re doing (Rolling out a Developer Experience Platform)
  • Expected benefits (should come from Section 1.2, Goals and Objectives)
  • What you need from Senior Leaders and their teams
    • Support for the roll-out
    • Effort from their team to update the Component Catalog
  • How you will communicate with them?
    • Cadence of communication
    • Reporting on Data Hygiene
  • Channels they can use to share feedback


Sent by:
Executive Sponsor

REFERENCE 4.1.2.3

Audience:
Senior engineering leaders, e.g. VP or General Manager level.

Purpose:
Inform senior leaders about Compass Rollout.

Key Messages:

  • What you’re doing (Rolling out a Developer Experience Platform)
  • Expected benefits (should come from Section 1.2, Goals and Objectives)
  • What you need from Senior Leaders and their teams
    • Support for the roll-out
    • Effort from their team to update the Component Catalog
  • How you will communicate with them?
    • Cadence of communication
    • Reporting on Data Hygiene
  • Channels they can use to share feedback


Sent by:
Executive Sponsor

REFERENCE 4.1.2.4

Audience:
Senior engineering leaders, e.g. VP or General Manager level.

Purpose:
Inform senior leaders about Compass Rollout.

Key Messages:

  • What you’re doing (Rolling out a Developer Experience Platform)
  • Expected benefits (should come from Section 1.2, Goals and Objectives)
  • What you need from Senior Leaders and their teams
    • Support for the roll-out
    • Effort from their team to update the Component Catalog
  • How you will communicate with them?:
    • Cadence of communication
    • Reporting on Data Hygiene
  • Channels they can use to share feedback


Sent by:
Executive Sponsor

REFERENCE 4.1.2.5

Audience:
Senior engineering leaders, e.g. VP or General Manager level.

Purpose:
Inform senior leaders about Compass Rollout.

Key Messages:

  • What you’re doing (Rolling out a Developer Experience Platform)
  • Expected benefits (should come from Section 1.2, Goals and Objectives)
  • What you need from Senior Leaders and their teams
    • Support for the roll-out
    • Effort from their team to update the Component Catalog
  • How you will communicate with them?:
    • Cadence of communication
    • Reporting on Data Hygiene
  • Channels they can use to share feedback


Sent by:
Executive Sponsor