KSA Flow

Across multiple programs I kept encountering the same pattern: learners completed instruction, passed assessment, and still could not perform reliably in the working environment. Completion data looked healthy. Performance did not.

Standard knowledge-skills-abilities language treated capability as three parallel buckets. It gave designers no way to locate where a specific population was stalling, and no vocabulary to argue for practice, feedback, or organizational change as part of the solution.

Capability is not a set of categories; it is a flow with predictable failure points. Information becomes knowledge only when it is organized and retrievable. Knowledge becomes skill only through structured practice. Skill becomes judgment only through varied conditions and feedback. Judgment produces performance only when the organization permits it.

• Originated and authored the framework
• Developed the stage model and diagnostic language
• Built the visual model and explanatory materials
• Applied the framework across program design and analysis work

I treated the framework as a diagnostic instrument first and a design instrument second. Rather than prescribing a methodology, KSA Flow asks where the flow is currently interrupted for a specific population and specific task — then indicates which class of intervention is likely to matter.

• Stage decompositionBreaking capability into observable transitions rather than static categories.
• Failure-point analysisNaming what specifically stops each transition from occurring.
• Intervention mappingMatching each interrupted transition to a class of solution.

The first version of the model was too linear. In practice, populations move backward under new conditions — an experienced performer facing an unfamiliar system re-enters an earlier stage. The current model treats the progression as directional but re-enterable, which made it substantially more useful in real diagnosis.