Headways
Guides

Building Workflows

Create and deploy custom learning paths to drive AI adoption.

Workflows are the primary mechanism for driving AI adoption in Headways. This guide covers creating, customizing, and deploying workflows.

Creating a Workflow

Navigate to Workflows > Create in the dashboard.

1. Define the Objective

Every workflow starts with a clear objective. What should participants be able to do after completing the workflow?

Good objective: "Team members can use AI to draft and refine customer communications."

Weak objective: "Learn about AI."

2. Set Prerequisites

Define what participants need before starting:

  • Required tool access (e.g., ChatGPT, Claude, Copilot)
  • Prerequisite workflows or knowledge
  • Minimum fluency score in relevant dimensions

3. Build Steps

Each step should include:

  • Title - Clear, action-oriented
  • Instructions - What to do and why
  • Resources - Links, templates, examples
  • Duration - Expected time to complete
  • Verification - How completion is confirmed

4. Add Checkpoints

Checkpoints verify understanding at key points. Types include:

TypeDescriptionWhen to Use
Self-AssessmentParticipant confirms completionSimple skill checks
Artifact ReviewParticipant uploads work productHands-on exercises
QuizMultiple choice or short answerKnowledge verification

Assigning Workflows

To Individuals

Navigate to the member's profile and assign workflows directly.

To Teams

Go to Settings > Teams, select a team, and assign workflows. All current and future team members receive the assignment.

Self-Serve Library

Toggle Library Visible to make the workflow available for anyone in the organization to start on their own.

Tracking Progress

The Adoption dashboard shows:

  • Completion rates by workflow, team, and individual
  • Average time-to-completion
  • Drop-off points (where participants stall)
  • Fluency score changes correlated with workflow completion

Best Practices

  • Keep workflows under 10 steps for completion rates above 80%
  • Include at least one hands-on exercise per workflow
  • Update workflows quarterly based on adoption data
  • Start with role-specific workflows before organization-wide ones

On this page