It's time to get your teams involved with the Flow launch!
Set up enablement sessions
Note: Before you have your enablement sessions, take some time to review your merge suggestions and merge users as needed. This will help ensure the best data to use for your sessions.
Build on the momentum from your initial launch email or meeting and set up enablement sessions. These will help people understand how you’re going to use Flow, and give them the chance to ask questions. The number of sessions varies depending on your organization, but make sure you get these groups enabled quickly:
-
Admins—people responsible for setting up and maintaining your Flow configurations.
-
Team leads/champions—people who will be leading the use of Flow on their teams. They may be managers on those teams, or others who are invested in the success of their teams.
-
Individual contributors—team members who will be using Flow with the rest of their team.
-
Executives—specifically the executives who will be using Flow data and driving the initiatives Flow will help with.
-
Non-engineering leadership—leaders who may not lead developers, but who will use the Flow insights to help improve their work.
Tip: Depending how large your organization is and how many different groups you need to enable, we recommend having two to three different enablement sessions.
Enablement announcement emails
To help you lead a successful enablement, here are a couple of enablement announcement email templates to get you started.
Use this template for enablement announcements for leaders and champions:
Subject: Have you heard of Pluralsight Flow? It’s great for the team.
Welcome to Pluralsight Flow!
You and your team will soon have access to Pluralsight’s Flow platform. Flow helps engineering leaders transform their organizations to increase visibility, efficiency, and predictability. In addition to rich value stream data, Flow brings a proven transformation approach, deep process and talent resources, and an experienced team. Flow provides engineering leaders with metrics in context to ask better questions and advocate for the team with substantive data:
- How much of your team's burn is going toward refactoring old code?
- Did the change to our sprint cycle have a net-positive effect?
- How well do we share knowledge in code reviews?
- What did engineering accomplish last week?
Flow aggregates historical git and ticketing data into easy-to-understand insights and reports to help make your engineering teams more successful.
As we know, it can be a challenge for senior leadership and product managers to understand the business value of your engineering team. The conversation is always the same: ship more good quality software, ship faster.
With Pluralsight Flow, you can advocate for the work your engineers are doing and help remove roadblocks so they can focus on what they really love to do: solve problems.
You will have access to Flow on [DATE]. Here are some next steps to help you:
- A training session will be held on mm/dd @ 0:00 PM.
- Access the Flow Help Center for articles and other helpful information.
Soon, with Flow, you and your engineers will have insights to view your daily, weekly, and yearly work in a meaningful way and communicate in a way the rest of the business understands.
Please reach out to [CONTACT] if you have any questions.
Best,
[NAME]
Use this template for enablement announcements to your individual contributors:
Subject: Flow is here! Learn more
Welcome to Pluralsight Flow!
You now have access to Pluralsight Flow. Flow is an organizational tool, pioneering a different way of measuring and communicating how software delivery work gets done at organizations like ours. Driving improvements in our development process goes hand in hand with improving the experience of our developers.
Flow was built by engineers, for engineers. Demonstrate the impact your initiatives have on the team, flag when external variables are slowing you down, avoid wasted efforts, and have productive one-on-ones to further your career.
You will have access to Flow on [DATE]. Here are some next steps to help you:
- A training session will be held on mm/dd @ 0:00 PM.
- You can access the Flow Help Center for articles and other helpful information.
Please reach out to [CONTACT] if you have any questions.
Best,
[NAME]
Host your enablement sessions
Tip: Consider investing in enablement from our Professional Services team (opens in new tab) to augment your team's enablement plans. These experts can help you launch Flow in the most successful way and bring insights on how best to use Flow to your organization.
Once you set up your invites and let your team know, take some time to build out what you want to share in your enablement sessions.
Make sure you communicate your Flow goals, strategic directions, and use cases. Connect them to your organization’s initiatives and reiterate the information you’ve shared in your emails. Give your team members a sense of how and why Flow will prove invaluable for your organization.
If possible, record these sessions and make them available so people can refer back to them later.
Top tips from Flow’s Professional Services team
-
Data is exciting for some people and overwhelming for others. Let your teams know you are going to support them on this journey.
-
Especially when it comes to individual contributor data, highlight that data is for learning, not inspection.
-
Pick one or two reports to share with your audience during your session. On each report, pick a handful of things to share. Usually just one or two metrics is enough. Don’t overwhelm your team with all the information right now—you can always share more later!
-
Tell your team who they can reach out to for Flow-related questions.
Invite your users
After you finish your enablement sessions, it’s time to invite users. It may be tempting to invite them before they finish enablement, but waiting ensures they have guidance and context on what Flow means for your organization.
Learn more about inviting users to Flow.
If you use SSO to manage your users instead of manual invites, have your team leads check to make sure their teams and metrics look accurate.
Note: Double-check your merge suggestions and merge users as needed before you invite your users.
What's next?
Now that you've enabled your team, review the resources you or your team might want to use as they’re exploring Flow.