Separate learning from the conditions needed to perform
Ask whether the problem is knowledge, skill, context, access or process. A seller may know discovery theory but lack accurate product boundaries. Another may understand the product but receive poor account research. Each needs a different intervention.
Use training for practice and feedback, and enablement for usable materials and operating design. Inspect actual tasks and resulting records. Avoid measuring success only by content views, attendance or completed quizzes; those measures describe participation, not commercial capability.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Skill gap | Operator struggles with a role-relevant decision | Practice with feedback and a new case |
| Context or material gap | Accurate product, buyer or example information is missing | Repair the playbook or supporting asset |
| System or process gap | Access, ownership or workflow prevents action | Fix the operating conditions rather than repeat training |
Work through the decision
Illustrative seller: their discovery notes do not separate buyer statements from inference. Practice and review can improve that skill. Another seller has accurate notes but cannot route a technical question because no product owner is named. That is a process gap.
A third cannot explain the standard integration because the material is outdated. Update the enablement asset, then test application. Classifying the cause prevents a team from prescribing more courses for every performance issue.
Participation is reported as readiness
A completed course may establish exposure to content. Ask the operator to apply it to a relevant unfamiliar task and explain the decision. Use the result to choose practice, material repair or system change.
A concrete next step
Select one recurring performance issue and classify its cause with the table. Apply the smallest relevant intervention, then inspect an actual operating artifact.
Sources and research notes
- GitLab commercial sales enablementCompany operating handbook
- GitLab customer-ready shadow programCompany operating handbook
Primary sources reviewed October 6, 2026. The operating recommendations and worked scenarios are Daavid’s analysis. Illustrative numbers are assumptions, not measured client results. Company marks identify sources and prior experience; they do not imply a customer relationship or endorsement.
Schematic