Rolling Exec Out to Your Team

Everything up to this point works single player. Scores start moving once your team practices. This guide walks the whole path from a workspace of one to a team with assignments, due dates, and results you can act on.

---

​

Before You Invite Anyone

Invitations land better when there is something worth doing on the other side. Before adding teammates, make sure you have:

1. One published scenario that sounds like your business. If your first build still has a generic character, edit it until the objections and details match reality. Your team will forgive a rough scorecard, but a scenario about the wrong company loses them on day one.
2. A session of your own on the board. Run the scenario yourself so you can tell people what to expect and what a scorecard looks like. Complete Your First Roleplay covers the mechanics.

---

​

Step 1: Invite Your Team

---

​

Step 2: Assign Your First Scenario

An unassigned scenario is a suggestion. An assigned one is a commitment. From the scenario page, assign it to specific people with three settings:

• A due date. End of the week works well for a first assignment.
• A minimum passing score. Silver is the right bar for a first pass. Gold is for scenarios the team has already seen.
• An attempt count. Requiring at least two attempts turns the scorecard into a feedback loop instead of a one-shot test.

Assigned roleplays land at the top of each person’s home screen, and completions and scores roll into the scenario page as they happen. Assign Scenarios covers every option, and Manage Assignments shows how to track who has finished.

---

​

Step 3: Make It a Rhythm

One assignment proves the mechanics. A rhythm changes how the team performs. The pattern that works across teams:

1. One scenario per week, assigned Monday, due Thursday or Friday.
2. A minimum score, so completing the assignment means clearing a bar rather than logging an attempt.
3. A short team review, where you look at the most common misses from the week’s scorecards and pick next week’s scenario from them.

The team guides have a version of this rhythm tuned to each audience: sales, support, customer success, and managers.

---

​

Step 4: Graduate to Programs

When you have more than a couple of scenarios and a cohort to move through them, switch from one-off assignments to a Program. Programs bundle roleplays, videos, surveys, and announcements into a timeline with launch dates, prerequisites, and a progress dashboard. Enrolling someone in a program can assign their seat automatically, so new hires get access and their first assignment in one step. Two setup details save most of the trouble we see: set component close dates a week or two past the due dates so PTO does not zero anyone out, and give same-day components a one-minute offset so the timeline reads cleanly. Launch and Lifecycle covers both.

---

​

Step 5: Measure What Moved

Three places to look once sessions start rolling in:

• The scenario page shows completions and scores per assignment as they happen.
• The skill dashboard aggregates evaluation criteria across sessions, so you can see which skills are improving and who needs attention. Skill analytics are a Professional feature.
• Call Scoring closes the loop: connect a recorder and compare practice scores against live calls. It works on every plan, and you pay only for the calls you score.

If scores plateau, the fix is usually in the scenario rather than the people. Edit it to raise the difficulty, tighten its evaluation criteria, or build the next scenario from whatever the skill dashboard says the team misses most.

---

​

Next Steps

---

​

Getting Help

Need help? Contact us at [email protected] for guidance on rolling Exec out to your team.