← Home
Partner Basecamp · Org Profile

EPAM

7 cohorts  ·  0 feedback entries  ·  0 open actions
Programme record · EPAM

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

Pooled NPS
too few to report
n=14 D2 · need ≥20
Cohorts attended
7
CohortCityDatesD1 nD2 nNPSProg avgGapP/Pa/D
C12San FranciscoMay 28-29, 202632-50+50-100
P 0%/Pa 50%/D 50%
C18San FranciscoJune 22–23, 202622+0+35-35
P 0%/Pa 100%/D 0%
C19San FranciscoJune 24–25, 202633-33+55-88
P 0%/Pa 67%/D 33%
C20San FranciscoJuly 14–15, 202611+100+35+65
P 100%/Pa 0%/D 0%
C25San FranciscoJuly 29–30, 202611+100+44+56
P 100%/Pa 0%/D 0%
C27LondonJuly 29–30, 202633-33+43-76
P 0%/Pa 67%/D 33%
C29San FranciscoAugust 24–25, 202622-50+48-98
P 0%/Pa 50%/D 50%
Capability Profile
Persona mix
Developer 13%Architect 60%T.Lead 27%
AI proficiency
Applying 20%Independent 40%Frontier 40%
Seniority mix
Sr Prac 62%Mgr 38%
Content depth
Too basic 53%About right 47%
Pace
Too slow 13%Well paced 67%Too fast 20%
Relevance (mean)
4.1 / 5
D1 confidence (mean)
4.4 / 5
Confidence Δ (D1→D2)
n=14 · too few
Confidence growth by domain
Build Δ
n=14 · too few
Design Δ
n=14 · too few
Commercial Δ
n=14 · too few
Persona × Seniority
PersonaIndividual ContributorSr PractitionerMgr / Sr MgrDirectorSVP / C-Level
Architect41
Developer11
Transformation Lead1
Persona × AI Proficiency
PersonaLearningApplyingIndependentFrontier
Architect225
Developer11
Transformation Lead31
Satisfaction by Persona
Developer
n=2 · too few
Architect
n=8 · too few
Transformation Lead
n=4 · too few
Strategic Insights
Advanced readiness: 40% at Frontier level — partner is ready for complex implementation engagements
Feedback log · EPAM

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 · EPAM

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

No open action items.