Running a Team Readiness Check
Use the free Team Readiness Check to scope a Headways pilot — what to codify first, which connectors to wire, what to deliver in the first month.
This guide walks you through running the Team Readiness Check for one or more teams and turning the output into a concrete pilot scope.
Before You Begin
- Identify the team or teams you want to assess (start with one — the one with the most repetitive, high-volume work)
- Allow each respondent 10–15 minutes
- You don't need a Headways workspace yet; the check is free and external
Step 1: Share the Link
The check lives at headways.ai/diagnostic. Send the URL to:
- The team lead
- One or two operators on the team
- Whoever currently approves the team's outbound work (brand, legal, leadership)
Each respondent gets a unique session. Results from multiple respondents on the same team aggregate into one team report.
Step 2: Complete the Sections
The check walks each respondent through five conversational sections — tool footprint, the recurring work, the bottlenecks, the team's stack, and the constraints they have to respect. Each section adapts based on prior answers.
Step 3: Read the Report
The report focuses on three actionable outputs:
- Top 3 Shared Skills to start with — Concrete workflows the team already does that are good candidates to codify
- Connector picks — Integrations that would unlock the fastest wins (usually Slack, the team's primary doc store, and one CRM-or-ticketing source)
- Pilot shape — A 2-3 week pilot scope: which Skills get authored, which Connectors get wired, what to deliver
Step 4: Plan the Pilot
Use the report to frame the kick-off conversation:
| Report says… | Pilot move |
|---|---|
| Several team members are heavy AI users but solo | Codify their best workflows as Shared Skills first |
| One person is the bottleneck for review | Wire that review into the Outbox gate |
| Same task done three different ways | Author one canonical Skill, retire the variants |
| Lots of context lives in one doc store | Wire that Connector first; populate the Knowledge Graph from there |
| Strong compliance / brand constraints | Set up Governance protection rules before Skills publish |
Tips for a Useful Result
- Run the check on one team at a time. Aggregating across an org dilutes the signal.
- Have an operator (not just a manager) complete it. The work knowledge is what makes the report useful.
- Be honest about who the bottlenecks are. The report isn't going on anyone's review.
- Re-run quarterly per team. The report tracks how the team's pattern shifts as Headways gets adopted.