Setup Guide, Week 4: Roll out and take action
Last updated: November 4, 2026
In week 4, you roll Span out to your teams and build it into the meetings and workflows they already run. You also name who owns it long term and set the outcomes you'll measure. This guide is for the admin and the engineering leader running the rollout.
Why it matters
Span pays off when it shows up where decisions already happen: standups, retros, 1:1s and leadership reviews. A tool people have to remember to open gets forgotten. Data that arrives in the meeting gets used.
For engineering leaders: a rollout order, a regular place for Span in each team's rhythm, and a clear way to show what changed.
For managers and engineers: Span answers in the meetings and tools they already use, plus a getting-started guide for their role.
How it works
You invite people in waves, starting with the managers and leaders who will answer questions. Then you attach Span to the rituals each team already has, so the numbers come up every week without extra work:
Ritual | How Span fits in |
|---|---|
Daily standup | A Team Slack Digest or playbook posts before standup, so the team sees which PRs are waiting on review |
Sprint planning and retros | The Sprint Tracking report shows what rolled over, and the team page shows where work waited |
1:1s | Engineers bring their Brag Sheet. Managers use the views their permissions allow |
Weekly team review | The focus-area dashboard and Targets show progress on your improvement |
Monthly or quarterly leadership review | Allocation and AI reports show where effort and spend went against the plan |
Day-to-day work | Engineers ask Src from Slack, Claude Code or Cursor without leaving their tools |
Setup
You need the Owner or Admin role to invite people.
1. Invite managers and leaders first
Why: They field the first questions from their teams, so they should know their own team views before engineers join.
How: Invite managers and leaders, and share their getting-started guide.
Docs: Getting started with Span: for engineering managers and leaders · How do I add a new user to Span?
2. Introduce Span to engineers
Why: Engineers who hear the purpose from a leader are more likely to trust the data and use it themselves.
How: Have a leader introduce Span on a team call and repeat what it's for. Point out what's in it for engineers, such as Brag Sheets for reviews and 1:1s, and asking questions from Claude Code, Cursor or the Span MCP Server.
Docs: Getting started with Span: for engineers · Signing in to Span · Brag Sheets · Ask from Claude Code or Cursor · Span MCP Server
3. Build Span into your team rituals
Why: This is what makes Span stick. When the numbers come up in meetings teams already hold, they get discussed and acted on every week.
How: Start with one ritual per team from the table above. Schedule a playbook or digest to post before that meeting, and put the dashboard or report link in the recurring invite or agenda. Spend the first few minutes of the meeting on it. Add a second ritual once the first one is routine.
Docs: See your team's numbers, and review them together · Get Span's answers delivered: Playbooks, digests and report subscriptions · Using Src Playbooks · Sprint Tracking Report · Brag Sheets
4. Invite everyone else who needs access
Why: Product, finance and executives can get answers themselves instead of asking engineering for reports, and can bring Span into their own reviews.
How: Add them once team views are being used, and confirm their access first.
Docs: Roles & Permissions in Span
5. Name your long-term owners
Why: Without owners, rituals lapse and data quality drifts as people join and leave and tokens expire. Then teams stop trusting the numbers.
How: Assign each role below, and put the weekly review on the calendar now.
Role | Owns |
|---|---|
Span Owner or admin | Permissions, integrations, roster and data quality |
Ritual owner, per team | Keeping Span in the team's standup, retro or weekly review |
Executive sponsor | Why your organization uses Span, and the quarterly outcomes |
Integration owners | Renewing tokens and fixing broken connections |
6. Choose one improvement experiment
Why: A before-and-after on one real problem is the clearest way to show Span is worth the time.
How: Pick one process problem you found, such as slow first reviews or large PRs, and one change to try for four weeks. Write down the owner, the metric, today's baseline, the target and the review date. Track it with a Target, and review it in the team's weekly ritual.
Docs: Targets · Custom dashboards
7. Ask engineers for feedback
Why: It tells you whether Span is helping in the rituals and what to change before you expand it.
How: Send a short survey asking whether Span is useful in the meetings where it shows up.
Docs: Span DX Surveys: Complete Guide
8. Schedule a 30-day check-in
Why: It turns your first experiment and first rituals into lasting habits.
How: Review the experiment and which rituals Span is part of. Decide what's next: keep it, add Span to another ritual, expand to more teams, or pick the next focus area.
Things to know
Use meetings you already have: don't add a new meeting for Span. Attach it to an existing one.
Put it in the agenda: a dashboard link in the recurring invite gets opened every time. A link shared once gets lost.
Keep early conversations at team level: walk teams through aggregate team views, ask what's missing or wrong, and celebrate what they change.
New hires: add Span, and auspex if you use agent traces, to new-hire setup so new people are counted from day one.
Tokens need an owner: integrations connected with a token stop syncing when the token expires. Your integration owner should renew tokens before then.
You're done when
Managers, leaders and engineers have been invited and have their getting-started guide.
Every team uses Span in at least one recurring meeting, with a named ritual owner.
Long-term owners are named and the weekly review is on the calendar.
One improvement experiment has an owner, a metric, a baseline and a review date.
A 30-day check-in is scheduled.
Related articles
Get Span's answers delivered: Playbooks, digests and report subscriptions
Getting started with Span: for engineering managers and leaders
Next: Days 31–90 with Span: turn your first experiment into lasting results
Need help?
Contact your Span account team or reach out to support@span.app.