← Home
Partner Basecamp · Org Profile

LTM

4 cohorts  ·  0 feedback entries  ·  0 open actions
Programme record · LTM

Quantitative data from post-programme surveys. NPS, participation, and benchmark against programme average across all cohorts attended.

Pooled NPS
+73
77% promoters  4% detractors
n=26 D2
vs Programme
+30
programme avg +43
Cohorts attended
4
CohortCityDatesD1 nD2 nNPSProg avgGapP/Pa/D
C30San FranciscoAugust 27–28, 202655+40+31+9
P 60%/Pa 20%/D 20%
C31San FranciscoSeptember 9–10, 202611+100+36+64
P 100%/Pa 0%/D 0%
C32San FranciscoSeptember 15–16, 202687+86+56+30
P 86%/Pa 14%/D 0%
C33San FranciscoSeptember 17–18, 20261313+77+40+37
P 77%/Pa 23%/D 0%
Capability Profile
Persona mix
Developer 26%Architect 48%T.Lead 26%
AI proficiency
Learning 19%Applying 67%Independent 11%Frontier 4%
Seniority mix
Sr Prac 75%Mgr 25%
Content depth
About right 93%Too advanced 7%
Pace
Well paced 89%Too fast 11%
Relevance (mean)
4.4 / 5
D1 confidence (mean)
4.4 / 5
Confidence Δ (D1→D2)
+0.15
Confidence growth by domain
Build Δ
+0.15
Design Δ
+0.12
Commercial Δ
+0.00
Persona × Seniority
PersonaIndividual ContributorSr PractitionerMgr / Sr MgrDirectorSVP / C-Level
Architect3
Developer32
Transformation Lead
Persona × AI Proficiency
PersonaLearningApplyingIndependentFrontier
Architect1921
Developer16
Transformation Lead331
Satisfaction by Persona
Developer
n=6 · too few
Architect
n=13 · too few
Transformation Lead
n=7 · too few
Strategic Insights
Team composition: Well-balanced across Developers, Architects, and Leaders — NPS +73 reflects strong multi-functional engagement
Partner stability: Consistent engagement across 4 cohorts — reliability signal for strategic expansions
Feedback log · LTM

Anecdotal feedback from partner reps, stakeholders, and other sources. Each entry is sourced and benchmarked against survey data where available. Hearsay entries are flagged — weight accordingly.

No feedback logged yet. Run org_intake.py to add entries.
Action items · LTM

Org-specific actions arising from survey data and feedback. Programme-wide actions are tracked separately in programme-actions.yaml.

No open action items.