Skip to content
Northwind Engineering
Menu

Adoption overview · Northwind Engineering

No adoption data yet.

No adoption data for this period yet. Ingest events and run pnpm aggregate.

Last 30 days · 0 unique actors · anchor week 2026-08-24

Nudges: 3 sent, 2 moved up a stage. 2 of 3 nudged teams moved up within 2 weeks; 2 of 3 within 4 weeks. Playbook actions leaders marked as sent, joined to stage movement 2 and 4 weeks later. Aggregate counts only — whether the nudged team or person moved up a stage. Full formula: Methodology page.

Security incidents

7 security incidents in this org

Review incidents →

3 critical production items open — fix before sharing reports.

Open production checklist →

More filters
Clear filters

Needs attention Teams ranked by how many people are stuck, weighted by how stuck they are (idle counts most). Ranking weight: each idle seat counts 3, poor-quality use 2, shallow use 1. A team appears when its weight reaches 3 or its stuck count grew vs the prior period. Full formula: Methodology page.

No teams need attention. 0 teams tracked.

Where teams are

Adoption funnel Unique actors grouped by highest stage reached this period. Each bar is a filter link. One person counts once at their best stage, not once per tool-week row.

0 unique actors

  1. Not using Seat paid, zero or minimal activity. No meaningful sessions this period. 0 · 0%
  2. Activated First real session beyond hello-world. Threshold: at least one substantive session. 0 · 0%
  3. Habitual Used on 3+ active days per week, mid-task. Habitual = 3+ active days/week with real tool use. 0 · 0%
  4. Deep Agentic multi-file work ending in commits. Habitual week with commit outcome and agentic depth: ≥1 subagent or ≥5 tool calls (PostToolUse only — PreToolUse pairs are not double-counted). 0 · 0%
  5. Multiplying Creates shared patterns others reuse. Patterns or artifacts others pick up (subagents, shared workflows). 0 · 0%

Click a stage to filter the overview. Works with JavaScript disabled.

No team × week stage data in this window.

Industry medians for context: 3.6 hrs/wk (Time saved (daily AI users)); ~22% (AI-authored merged code). Directional only — peer percentiles unlock when 5+ installs opt in. Benchmarks settings →

Week over week

Week of 2026-08-24 vs prior week

Stage Current Previous Δ
Not using 0 2 -2
Activated 0 1 -1
Habitual 0 1 -1
Deep 0 0 0
Multiplying 0 0 0

Stage transitions

Last 30 days vs Prior period · best stage per actor

Moved up

0 actors

0

Reached a higher adoption stage vs the prior period.

Regressed

0 actors

0

Dropped a stage but still active (not idle).

Churned to idle

2 actors

2

Ended at Not using after prior-period activity.

  • lee@northwind.dev Activated → Not using
  • nina@northwind.dev Habitual → Not using
How they're using it

Tool mix

No tools in this slice.

Are they using it well

Three adoption gaps Where coaching effort should focus: idle, shallow, or poor-quality use.

Not using Seat paid, zero or minimal sessions.

0

Seat paid, zero or minimal sessions.

Using shallowly Short sessions, low tool depth, no commits.

0

Short sessions, low tool depth, no commits.

Using poorly High abandonment, errors, token waste.

0

High abandonment, errors, token waste.

Cost

Estimated spend this period: $0

Collector health

Which tools are sending data and which need attention.

View details →
Tool Status Actors Recent sessions Recent events Last seen
Claude Code Healthy 10 0 4 2026-08-27T10:00:00.000Z
Codex Healthy 4 0 1 2026-08-27T10:00:00.000Z
Cursor Healthy 7 0 2 2026-08-27T10:00:00.000Z
Copilot Needs setup 0 0 0 never