Phase 01: Analysis

Learning Needs Analysis

We diagnose before we prescribe. Our LNA identifies the gap between current performance and target product outcomes.

What we need (Inputs)

  • Product analytics & drop-off data
  • Support ticket trends
  • SME Interview access
  • Existing documentation/V1 decks

What you get (Outputs)

  • Prioritized Task Inventory
  • Persona Knowledge Gap Map
  • Critical Incident Report
  • Measurement Strategy

The Audit Process

1

Data Triangulation

Comparing support tickets against product logs to find where users "quit" out of frustration versus lack of knowledge.

2

Workflow Decomposition

Breaking down complex features into "Minimum Viable Actions" that a user must master to see value.

3

Constraint Discovery

Identifying technical or cultural barriers that might prevent a user from applying new skills (e.g., IT permissions).

Definition of Done (LNA)

An LNA is considered complete when:

✅ Personas are validated with specific pain points.
✅ Tasks are ranked by "Business Criticality."
✅ Success metrics are agreed upon by stakeholders.

Phase 02: Design

Instructional Blueprint

We don't build modules; we build behavior-change architectures. The Blueprint ensures every learning activity leads to a measurable product outcome.

Curriculum Architecture

A bird's-eye view of how we structure role-based learning paths to ensure logical progression.

Core Foundations

Universal product concepts for all buying roles.

Role-Specific Paths

Workflow-heavy content for Admins, Users, or Execs.

Performance Support

On-demand resources for moments of need.

The Alignment Model

ComponentFunctionOutcome
Terminal ObjectiveThe high-level behavior change (e.g., 'Optimize workspace').KPI Movement
Enabling ObjectiveThe granular skills needed to hit the terminal goal.Knowledge Retention
Performance TaskScenario-based practice mirroring real workflows.Skill Mastery
AssessmentProof that the learner can execute the task without help.Data Validation

Blueprint Standards

Scenario-First

We lead with a problem to solve, not a feature to click.

Cognitive Load

Information is pruned to only what is required for the task.

A11y-Native

Navigation and modality are designed for inclusion from day one.


Phase 03: Development

Interactive Prototypes

We build high-fidelity simulations and walkthroughs to test comprehension and friction early, ensuring the final build is optimized for performance.

Simulation Modalities

💻

Software Simulations

Risk-free sandbox environments where users practice workflows without touching live data.

🔀

Branching Scenarios

Decision-based narratives that test soft skills and complex problem-solving logic.

📍

In-App Walkthroughs

Contextual overlays that guide users through critical 'aha' moments in real-time.

The Pilot Feedback Loop

Time-on-Task

How long does it take a persona to complete the critical workflow?

Decision Accuracy

The percentage of correct choices made during branching scenarios.

Confidence Score

Self-reported user readiness before and after the interaction.

Development Standards

SCORM / xAPI Ready

Full tracking for completions, scores, and custom data verbs.

WCAG 2.1 Compliant

Screen-reader friendly, keyboard navigable, and high contrast.

Responsive Design

Seamless experience across desktop, tablet, and mobile browsers.

Ready to start your project?