← Home
Partner Basecamp · Insights
London & San Francisco · June 24–21, 2026
2026-07-28 18:26 UTC · v3.3
n=191 D2 · 4 cohorts
London · San Francisco

Programme NPS +40 · 4 cohorts · 191 D2 respondents

4 v2 cohorts · 222 D1 respondents · Historical baseline NPS: +35

Programme NPS · all cohorts
+40
P 50% · Pa 40% · D 10%
n=191 D2 respondents
Cohorts
4
4 with full v2 data
Respondents
222
222 D1 · 191 D2

Cohort summary

CohortNPSP%Pa%D%D2 nD1 nMatchConf Δ
C19 San Francisco June 24–25, 2026+5564.5%25.8%9.7%626798%+0.43
C20 San Francisco July 14–15, 2026+3545.8%43.8%10.4%484688%+0.26
C21 San Francisco July 16–17, 2026+2438.8%46.9%14.3%495494%+0.22
C22 London July 20–21, 2026+4143.8%53.1%3.1%325575%+0.39

Conf Δ = D2 apply-AI minus D1 baseline (v2 cohorts only). Match = D1/D2 linked respondents.

London · San Francisco · programme snapshot

London
+41
P 44% · Pa 53% · D 3%
n=32 D2 · 1 cohort
C22 London July 20–21, 2026
San Francisco
+40
P 51% · Pa 38% · D 11%
n=159 D2 · 3 cohorts
C19 San Francisco June 24–25, 2026, C20 San Francisco July 14–15, 2026, C21 San Francisco July 16–17, 2026

Same content and programme design. City split reflects internal team and audience differences.

Audience composition · 222 D1 respondents pooled

Pooled across all cohorts. NPS by org aggregated from v2 cohorts only (n ≥ 4 suppressed).

Function
Engineering
37%
Architecture
27%
Project and engagement mana…
23%
Business leadership
14%
Seniority
Manager or Senior Manager
28%
Senior practitioner
26%
Director, Senior Director, …
22%
Practitioner
18%
Partner, Managing Director,…
6%
AI Proficiency
Applying in practice
46%
Learning and exploring
21%
Delivering independently
17%
Operating at the frontier
17%

Organisation distribution · pooled

OrganisationDistributionn%
PwC
4520.3%
Deloitte
229.9%
Fractional AI / Ode
188.1%
UST Global
135.9%
Capgemini
135.9%
DXC Technology
125.4%
McKinsey
115.0%
Ascendion
115.0%
NEC
104.5%
Cognizant
94.1%
Persistent Systems
73.2%
EPAM
41.8%
Fractal Analytics
41.8%
Lovelytics
41.8%
Quantium
41.8%
Forgd.AI
41.8%
KPMG
41.8%
Accenture
41.8%
Bain
41.8%
valantic
41.8%

NPS by organisation · aggregate (v2 cohorts, n ≥ 4)

OrganisationNPSn
Cognizant+89n=9
Persistent Systems+83n=6
Ascendion+70n=10
Deloitte+61n=18
NEC+60n=10
Capgemini+57n=7
DXC Technology+43n=7
McKinsey+40n=10
UST Global+38n=13
PwC+28n=36
Fractional AI / Ode-30n=10
EPAM+0n=4
KPMG+0n=4

Day 1 calibration · confidence, depth, pace and relevance

Pooled across v2 cohorts. Confidence on 1–5 scale. Depth/pace as % of persona respondents.

D1 Confidence by Persona · mean /5
Architect
4.03/5 · n=59
81%
Developer
3.88/5 · n=82
78%
Transformation Lead
3.55/5 · n=81
71%

Bar = % of max scale (5). Pooled across v2 cohorts.

D1 Confidence by AI Proficiency · mean /5
Delivering independently
4.27/5 · n=37
85%
Operating at the frontier
4.65/5 · n=37
93%
Applying in practice
3.63/5 · n=102
73%
Learning and exploring
3.13/5 · n=46
63%

Bar = % of max scale (5). Pooled across v2 cohorts.

Content Depth by Persona · pooled

PersonaToo basicAbout rightToo advanced
Architect14%
n=8
85%
n=50
2%
n=1
Developer24%
n=20
70%
n=57
6%
n=5
Transformation Lead5%
n=4
77%
n=62
19%
n=15

Session Pace by Persona · pooled

PersonaToo slowWell pacedToo fast
Architect5%
n=3
83%
n=49
12%
n=7
Developer18%
n=15
62%
n=51
20%
n=16
Transformation Lead2%
n=2
77%
n=62
21%
n=17

Content Relevance by Persona · mean /5 · programme mean 4.10/5

Architect
4.32/5 · n=59
86%
Developer
4.07/5 · n=82
81%
Transformation Lead
3.98/5 · n=81
80%

Relevance = Day 1 session relevance rating (1–5). Pooled across v2 cohorts.

Outcomes · NPS by persona, proficiency and open text

Aggregate NPS breakouts from v2 cohorts (n ≥ 4 suppressed). 157 NPS open-text responses available.

NPS by Persona · aggregate (v2 cohorts, n ≥ 4)

PersonaNPS barNPSn
Architect
+49n=51
Transformation Lead
+40n=63
Developer
+37n=59

NPS by AI Proficiency · pooled (v2 cohorts, n ≥ 4)

ProficiencyNPSP%Pa%D%n
Applying in practice+4753.3%40.0%6.7%n=75
Delivering independently+4544.8%55.2%0.0%n=29
Learning and exploring+4656.8%32.4%10.8%n=37
Operating at the frontier+1741.4%34.5%24.1%n=29

Open text · NPS reasons · 157 responses

ConsistentPromoter
Practical hands-on learning drives engagement
"Interactive exercises, hackathon activities, and real-world code examples made the content tangible and immediately applicable to work."

Hands-on practice is the strongest consistent motivator across promoters; hackathon specifically cited as valuable collaborative format.

ConsistentBoth
Content difficulty misaligned with audience mix
"Programme assumes foundational technical knowledge; too basic for experienced engineers but too advanced or technical for business-focused consultants and functional roles."

The single most cited friction point: cohort heterogeneity creates either boredom for technical staff or cognitive overload for non-technical participants.

EmergingDetractor
Insufficient time for depth and experimentation
"Exercises ran short, content was compressed across two days, and pacing felt aggressive, limiting opportunity to debug code or fully engage with concepts."

Time pressure undermines the hands-on value proposition, particularly for those new to coding or unfamiliar with the tooling.

ConsistentPromoter
Clear business value for applied AI roles
"Programme affirmed current approaches and provided new strategies to embed AI into day-to-day work and client engagements, with strong coverage of both business and technical dimensions."

Promoters see direct career and client impact; the programme succeeds when participants can map learnings to their immediate job context.

ConsistentDetractor
Insufficient segmentation by role and experience
"Single-track delivery fails engineers, business consultants, finance practitioners, and transformation leads differently; programme needs multiple tracks or pre-work to account for technical background."

Absence of level differentiation or role-specific pathways is a design gap that actively frustrates both novices and experts.

Confidence · D1→D2 deltas across all three dimensions

Apply-AI · Design-AI · Commercial confidence. D1 baseline → D2 delta. v2 cohorts only.

D1 → D2 Confidence by Dimension · per cohort

CohortD1 buildD2 apply-AID2 design-AID2 commercial
C19 San Francisco June 24–25, 20263.844.27
+0.43
4.15
+0.31
4.16
+0.32
C20 San Francisco July 14–15, 20263.764.02
+0.26
4.06
+0.30
4.15
+0.39
C21 San Francisco July 16–17, 20263.964.18
+0.22
4.18
+0.22
4.10
+0.14
C22 London July 20–21, 20263.834.22
+0.39
4.09
+0.26
4.34
+0.51

D2 value shown above; delta (D2 – D1) shown below in smaller text. Scale 1–5.

Confidence Delta by Persona · pooled

Transformation Lead
n=63
+0.46
Architect
n=51
+0.32
Developer
n=59
+0.17

D1→D2 apply-AI mean delta. Positive = gained confidence. Scale 1–5.

Confidence Delta by NPS Segment · pooled

Promoter
n=88
+0.43
Passive
n=69
+0.26
Detractor
n=15
-0.07

Promoters gain more confidence than detractors — or vice versa?

2 systematic patterns · 3 flags · 6 suggested queries

Systematic patterns = same direction vs programme NPS across ≥2 cohorts. Suggested queries pre-written for ask.py.

AI Proficiency patterns · consistent across ≥2 cohorts

PatternDirectionAvg ΔCohortsSeen in
Delivering independently scored above programme NPS in all 3 cohorts analysed (avg +7 pts)↑ Above programme+7 pts3C19 San Francisco June 24–25, 2026, C20 San Francisco July 14–15, 2026, C21 San Francisco July 16–17, 2026

Organisation patterns · consistent across ≥2 cohorts

PatternDirectionAvg ΔCohortsSeen in
Deloitte scored above programme NPS in all 2 cohorts analysed (avg +18 pts)
Likely reflects audience fit, not delivery variance.
↑ Above programme+18 pts2C19 San Francisco June 24–25, 2026, C20 San Francisco July 14–15, 2026

Outlier flags

● High passive rateHigh passive rate in C20 San Francisco July 14–15, 2026 (44%). Passives are the most likely source of churn — explore what would convert them to promoters.
● High passive rateHigh passive rate in C21 San Francisco July 16–17, 2026 (47%). Passives are the most likely source of churn — explore what would convert them to promoters.
● High passive rateHigh passive rate in C22 London July 20–21, 2026 (53%). Passives are the most likely source of churn — explore what would convert them to promoters.

Suggested ask.py queries

Run these commands from the Partner Basecamp/ folder to investigate the patterns above. Add --save when you have a conclusion to commit to the insights cache.

Delivering independently — proficiency pattern
Delivering independently scored above programme NPS in all 3 cohorts analysed (avg +7 pts)
cd "$REPO" && python3 _scripts/ask.py --question "Why do Delivering independently AI proficiency participants rate the programme +7 pts above average — what does the D1 calibration data tell us?" --cache "/Users/edward.whittall/Library/CloudStorage/Box-Box/Anthropic/Phase II/Partner Enablement/Partner Basecamp v2/Partner Basecamp — Survey Pipeline/findings/insights/c19-c22/insights-data-c19-c22.json" --save
Deloitte — org pattern
Deloitte scored above programme NPS in all 2 cohorts analysed (avg +18 pts)
cd "$REPO" && python3 _scripts/ask.py --question "What explains Deloitte's persistent above-programme NPS score across 2 cohorts, and what would change it?" --cache "/Users/edward.whittall/Library/CloudStorage/Box-Box/Anthropic/Phase II/Partner Enablement/Partner Basecamp v2/Partner Basecamp — Survey Pipeline/findings/insights/c19-c22/insights-data-c19-c22.json" --save
High passives: C20 San Francisco July 14–15, 2026
Passive rate: 44%
cd "$REPO" && python3 _scripts/ask.py --question "What is driving the high passive rate in C20 San Francisco July 14–15, 2026 — what do the verbatims say and what would convert them to promoters?" --cache "/Users/edward.whittall/Library/CloudStorage/Box-Box/Anthropic/Phase II/Partner Enablement/Partner Basecamp v2/Partner Basecamp — Survey Pipeline/findings/insights/c19-c22/insights-data-c19-c22.json" --save
High passives: C21 San Francisco July 16–17, 2026
Passive rate: 47%
cd "$REPO" && python3 _scripts/ask.py --question "What is driving the high passive rate in C21 San Francisco July 16–17, 2026 — what do the verbatims say and what would convert them to promoters?" --cache "/Users/edward.whittall/Library/CloudStorage/Box-Box/Anthropic/Phase II/Partner Enablement/Partner Basecamp v2/Partner Basecamp — Survey Pipeline/findings/insights/c19-c22/insights-data-c19-c22.json" --save
High passives: C22 London July 20–21, 2026
Passive rate: 53%
cd "$REPO" && python3 _scripts/ask.py --question "What is driving the high passive rate in C22 London July 20–21, 2026 — what do the verbatims say and what would convert them to promoters?" --cache "/Users/edward.whittall/Library/CloudStorage/Box-Box/Anthropic/Phase II/Partner Enablement/Partner Basecamp v2/Partner Basecamp — Survey Pipeline/findings/insights/c19-c22/insights-data-c19-c22.json" --save
Promoter vs passive — what separates them
NPS verbatim analysis — highest signal for passive conversion
python3 _scripts/ask.py --question "What do promoters and passives say about the programme, and what specifically separates them?" --cache "/Users/edward.whittall/Library/CloudStorage/Box-Box/Anthropic/Phase II/Partner Enablement/Partner Basecamp v2/Partner Basecamp — Survey Pipeline/findings/insights/c19-c22/insights-data-c19-c22.json"

Investigation log · 6 conclusions saved · 6 open queries

Conclusions committed via ask.py --save, open signals from Tab 06 patterns, and pre-written queries.6 conclusions saved

Saved conclusions · 6 from ask.py --save

Q: Why do Delivering independently AI proficiency participants rate the programme +7 pts above average — what does the D1 calibration data tell us?
The D1 calibration data does not include NPS broken down by AI proficiency band, so the +7 pt advantage cannot be directly explained by calibration scores alone.
The data brief confirms Delivering independently participants rated the programme above average NPS across the 3 cohorts analysed, but NPS by AI proficiency band is not reported — only headcounts per band are available (C19: n=10, C20: n=9, C21: n=13, C22: n=5). D1 calibration scores are reported at cohort level only (range 3.76–3.96), not segmented by proficiency band, so we cannot determine whether Delivering independently participants entered with higher or lower baseline confidence than peers. What the verbatim data does suggest is that the 'too basic' complaint appears almost exclusively from Operating at the frontier participants (e.g. McKinsey Developer nps=5, Fractional AI Developer nps=6, Bain Architect nps=6), not from Delivering independently participants — who contribute promoter verbatims citing applicable techniques and hands-on work. This implies Delivering independently may sit in a content sweet-spot: advanced enough to be novel, practical enough to be immediately usable. However, this is pattern inference from sparse verbatims, not a statistically supported finding. Key data points: · Delivering independently headcounts are small across cohorts: C19 n=10, C20 n=9, C21 n=13, C22 n=5 — all below the n=20 threshold for confident segment-level conclusions · D1 calibration scores are cohort-level averages only (3.76–3.96), not segmented by AI proficiency band — no Delivering independently baseline confidence delta is calculable · Detractor verbatims citing content being 'too basic' or 'already known' come from Operating at the frontier participants, not Delivering independently — suggesting a content-fit differential between the two bands Caveats: To answer this question with confidence, NPS by AI proficiency band and D1 calibration scores segmented by proficiency band would be needed. The cross-cohort correlations section explicitly flags AI proficiency correlation as 'insufficient data', confirming this gap.
2026-07-28 18:24 UTC
Q: What explains Deloitte's persistent above-programme NPS score across 2 cohorts, and what would change it?
Deloitte's above-programme NPS (+83 in C19, +44 in C20 vs. programme averages of +55 and +35) cannot be fully explained by the available data — sample sizes of n=6 and n=9 are too small for confident causal attribution.
Deloitte scored +83 in C19 (n=6) and +44 in C20 (n=9), both above their respective cohort NPS of +55 and +35 — a consistent pattern across the two cohorts where Deloitte appears in the org-level breakdowns. However, with combined Deloitte n=15 across both cohorts, no statistically confident explanation is possible. The verbatim evidence offers limited signal: C19 Deloitte promoters cite 'applicable techniques' and 'great food'; C20 Deloitte promoters cite 'real life scenarios' and hands-on Claude Code time, while one Deloitte detractor in C20 explicitly wanted more advanced content ('ontology and use of ontology with Claude to create agents'). This detractor pattern — a technically advanced participant finding content too basic — is the same risk that could erode Deloitte's NPS: if cohorts skew toward higher AI proficiency Deloitte attendees, the 'too basic' detractor signal becomes more likely to repeat. What would change it: sending more frontier-level Deloitte participants without an advanced track to match their expectations would convert promoters to passives or detractors. Key data points: · Deloitte C19 NPS: +83, n=6 (cohort average: +55) · Deloitte C20 NPS: +44, n=9 (cohort average: +35) · Combined Deloitte n=15 across both cohorts — below the 20-respondent threshold for confident segment conclusions · One Deloitte detractor in C20 (score: 6) cited content being too basic for advanced use cases · Programme-wide detractor theme across orgs: 'too basic for frontier-level practitioners' appears in C19, C21, and C22 verbatims Caveats: With n=6 and n=9, Deloitte's above-programme scores could reflect cohort composition luck (e.g., more 'Applying in practice' than 'Operating at the frontier' attendees) rather than a structural Deloitte effect. To answer this confidently, you would need Deloitte org-level AI proficiency breakdowns and at least 20+ Deloitte respondents across cohorts.
2026-07-28 18:24 UTC
Q: What is driving the high passive rate in C20 San Francisco July 14–15, 2026 — what do the verbatims say and what would convert them to promoters?
C20's 43.8% passive rate is driven by Transformation Leads (NPS +17, n=18) citing relevance gaps and content depth mismatches — not delivery quality.
Three C20 verbatims point to two distinct passive/detractor drivers: (1) relevance mismatch — a PwC Transformation Lead rated 6, saying 'not as directly relevant for my work in finance consulting,' and another PwC Transformation Lead rated 6 noting the content was 'very technical but a great way to learn what back end developers do' — suggesting non-technical personas felt the programme wasn't pitched at them; (2) depth ceiling — a Deloitte Architect rated 6 calling it 'very basic' and wishing for ontology/agent-building content. Passive verbatims (scores 7–8) use positive language — 'hands on and engaging,' 'very insightful,' 'well organized' — but the low scores suggest appreciation without genuine enthusiasm, consistent with a relevance gap rather than a delivery failure. The Transformation Lead persona drove the most risk: NPS +17 vs. Developer NPS +70 and Architect NPS +43, and PwC specifically scored NPS -11 (n=9), the only negative org score in C20. Confidence deltas were the lowest of all four cohorts (D1=3.76), indicating participants also entered with slightly lower baseline confidence, which may have amplified dissatisfaction when content skewed technical. Key data points: · Transformation Lead NPS +17 (n=18) vs. Developer +70 (n=10) — largest persona gap in C20 · PwC NPS -11 (n=9) — only negative org score in C20; two PwC detractor verbatims cite technical irrelevance · Passive verbatims (scores 7–8) uniformly positive on logistics/delivery but silent on business applicability — relevance gap, not execution failure · C20 had the lowest D1 confidence score across cohorts (3.76), suggesting a less experienced intake that may have found technical depth harder to absorb · Detractor verbatims split: 2 cite 'too basic/advanced depth missing' (Architect), 1 cites 'not relevant to finance consulting' (Transformation Lead) — two different fix paths needed Caveats: Only 3 passive and 3 detractor verbatims are available for C20 (n=48 total), so themes are directional, not statistically confirmed. A post-event pulse survey targeting the 21 passives specifically — asking about content relevance, depth, and role applicability — would give actionable segmentation data to confirm whether to split tracks or add persona-specific modules.
2026-07-28 18:25 UTC
Q: What is driving the high passive rate in C21 San Francisco July 16–17, 2026 — what do the verbatims say and what would convert them to promoters?
C21's 47% passive rate is driven by a content-depth mismatch: advanced participants found the material too basic, while non-technical roles found Jupyter notebooks irrelevant to their work.
Three C21 verbatims point to the same root cause from different angles. Fractional AI / Ode detractors (NPS -30, n=10) explicitly state 'it's a bit too basic for us' and 'pretty basic for most of my coworkers' — both from frontier-level practitioners (Operating at the frontier). A PwC passive (NPS 7) flags the opposite problem: 'very very heavy on Jupyter notebooks which is not relevant to my current role' — a Transformation Lead who is Delivering independently. A separate PwC detractor scores 5 and states 'not differentiated by level of technical skill', directly naming the structural issue. The Developer persona is the most distressed segment at NPS -6 (n=16), yet C21 has the highest engineering function share of any cohort (24 of 49). The concentration of Fractional AI / Ode attendees — a single org driving NPS -30 — is a compounding factor, but the depth complaint spans orgs. Converting passives to promoters requires either streaming by AI proficiency level or offering modular depth tracks, so frontier practitioners get advanced content while non-technical leads get role-relevant application framing. Key data points: · C21 passive rate: 46.9% (n=23 passives out of 49 respondents) · Fractional AI / Ode NPS: -30 (n=10) — single org heavily skewing detractor count; all complaints centre on content being too basic · Developer persona NPS: -6 (n=16) — worst segment in cohort; 24 of 49 respondents are in Engineering function · PwC passive verbatim: 'very very heavy on Jupyter notebooks which is not relevant to my current role' (Transformation Lead, Delivering independently) · PwC detractor verbatim (NPS 5): 'not differentiated by level of technical skill' — directly names the structural gap Caveats: Verbatim coverage is sparse — only 9 C21 quotes are available across all NPS bands from n=49 respondents, so themes are directionally consistent but not statistically validated. Knowing the AI proficiency breakdown of passives specifically (vs. the full cohort) would sharpen whether depth or relevance is the primary conversion lever.
2026-07-28 18:25 UTC
Q: What is driving the high passive rate in C22 London July 20–21, 2026 — what do the verbatims say and what would convert them to promoters?
C22 London's 53% passive rate is driven by a pace/depth mismatch: too little time for exercises and content pitched too basic for frontier-level attendees.
Three passive verbatims from C22 London reveal two distinct friction points. First, time pressure: one Capgemini Architect (Learning & Exploring) scored 7 citing 'very technical content but little time to really run the exercises,' and an unmatched respondent also scored 7 requesting 'more presentations to present concepts and solutions rather than experiencing with it' — suggesting some attendees felt rushed through hands-on work without sufficient conceptual scaffolding. Second, depth insufficiency: the sole detractor, a Bain Architect operating at the frontier, scored 6 and explicitly requested an Anthropic engineer to cover advanced topics, calling content 'too basic.' The one passive who wrote only 'content' (IndiciumAI Developer, frontier proficiency) provides no actionable signal. Promoter verbatims praise interactivity and hands-on work, indicating the format itself is valued — the gap is calibration of pace and depth, not format. C22 also has a significant day-2 drop (55 Day 1 vs. 32 Day 2, only 24 matched), which means the verbatim base is thin and findings should be treated as directional only. Key data points: · C22 passive rate: 53.1% (n=32 respondents, but only 24 matched Day 1–Day 2) · 2 of 3 passive verbatims cite time/pace issues: 'little time to really run the exercises' and desire for more concept presentation before hands-on · 1 detractor (frontier-level Architect, Bain, score 6) calls content 'too basic' and requests Anthropic engineer for advanced topics · Frontier and 'Delivering independently' proficiency groups likely over-represented among passives: the IndiciumAI passive and Bain detractor are both frontier-level · Day 1 attendance was 55 but only 32 completed Day 2 survey — a 42% drop that inflates uncertainty in all C22 findings Caveats: C22 verbatim sample is very small (3 passive quotes, 1 detractor quote) — n < 20 for matched respondents (n=24), so no statistically confident conclusions can be drawn. To sharpen this analysis, mid-programme pulse data, full open-text responses from all 32 Day 2 respondents, and a breakdown of AI proficiency distribution among passives specifically would all help isolate whether depth or pace is the primary conversion lever.
2026-07-28 18:25 UTC
Q: What do promoters and passives say about the programme, and what specifically separates them?
Promoters cite learning, real-world relevance, and hands-on engagement; passives acknowledge quality but flag format mismatches — specifically too many Jupyter notebooks, insufficient concept framing, and content pitched below their level.
Across C19–C22, promoter verbatims consistently reference substantive learning ('learned a lot of applicable techniques', 'good course to get hands on time with Claude Code', 'very valid real life scenarios') and engagement quality ('great presenters, very interactive', 'explanatory and with a good level of hands on'). Passive verbatims are notably thinner in specificity — phrases like 'super fun and technical', 'very insightful content', 'well organized', and 'hands-on and engaging' register satisfaction but not transformation, suggesting the programme was good but not meaningfully differentiated in their experience. The clearest separating signal in passive verbatims is format and pacing friction: C21 saw a passive cite 'very heavy on Jupyter notebooks which is not relevant to my current role', and C22 passives flagged 'little time to really run the exercises' and a preference for 'more presentations to present concepts and solutions rather than experiencing with it'. This points to a structural gap — passives want better scaffolding before doing, not just doing. Promoters either had sufficient context to engage fully or found the hands-on format intrinsically rewarding; passives did not clear that threshold. Key data points: · 40.3% of respondents (n≈77 across C19–C22) are passives — highest in C22 London at 53.1% (n=32) · Passive verbatims across all cohorts use generic positive descriptors ('well organized', 'very insightful', 'hands-on and engaging') with no reference to specific skills, tools, or applicable takeaways · 3 of 12 passive verbatims sampled explicitly name format issues: Jupyter notebook overload (C21), insufficient time for exercises (C22), and desire for more concept framing before hands-on work (C22) · Promoter verbatims reference specific content or outcomes in 8 of 12 sampled cases: Evals, Claude Code, Agentix programming, real-life scenarios, and applicable techniques · Passives skew toward 'Applying in practice' AI proficiency in the verbatim sample — not beginners, not frontier — suggesting mid-level practitioners are least served by the current format Caveats: Verbatim sample is small (3 per segment per cohort) and not guaranteed representative — treat themes as directional hypotheses, not statistically validated conclusions. Structured follow-up with passives on format preference and content depth expectations would sharpen the conversion lever significantly.
2026-07-28 18:26 UTC

Open signals

Systematic patterns
2
consistent across ≥2 cohorts
Outlier flags
3
anomalies flagged
Conclusions saved
6
from ask.py --save
Suggested queries
6
pre-written in Tab 06

Pre-written queries → Tab 06 · Patterns

Tab 06 contains pre-written ask.py commands for each pattern and flag detected. Run them from the Partner Basecamp/ folder, review the output, then re-run with --save to commit the conclusion here.

Data Quality · survey compliance and completeness

Issues flagged for transparency and database migration. Assessment and remediation tracked with delivery team.

Programme Summary · Survey Compliance
Total Day 2 responses 191
Matched to Day 1 173 (90.6% of Day 2)
Day 2-only respondents 18 (9.4%) — no Day 1 data, excluded from persona & confidence analysis
NPS impact of D2-only respondents suppresses programme NPS by 4 points