Competence-application gap
The perceived distance between one's own sense of competence after a digital IT learning process and the expected ability to apply that knowledge later under incomplete information, ambiguous fault patterns, technical dependencies, time pressure and responsibility.
What the concept does
The concept does not devalue the sense of competence. It limits what may be inferred from it. It describes neither a lack of ability nor poor instruction, but a diagnostic point: the place where the learning moment and the moment of application become distinguishable.
Delimitation
- From technology acceptance: acceptance models explain why a system is used, not whether someone can act later.
- From transfer of training: transfer research separates training, learning outcome and transfer conditions; the gap sits one step earlier, at the anticipated application.
- From self-efficacy: confidence is not application, and application is not yet reliable action.
Empirical status and limits
The basis is an exploratory quantitative study with a cleaned working sample of 221 usable cases from IT-related vocational, higher and continuing education contexts; 30 variables were collected. The central finding: perceived application competence did not automatically close the gap — both occurred together.
Source: Steinhardt, S. & Dulgeridis, M. (2026). Zwischen Kompetenzgefühl und Handlungssicherheit: Die Kompetenz-Anwendungs-Lücke in digitalen IT-Lernformaten. IU Discussion Papers Business & Management, Vol. 7, No. 15. doi.org/10.56250/4141 →
Controlled application tension
The point at which learners must use knowledge while the task is not fully resolved — guided, but not fully prescribed.
Why it must be dosed
Throwing learners into complexity produces overload, not reliable action. Removing all friction, on the other hand, creates a smooth learning space that produces success but prepares application only to a limited degree. Do not avoid complexity — dose it.
Design elements
- Incomplete information — clarify what is missing and which assumption is admissible
- Ambiguous fault patterns — hypothesis building and elimination become necessary
- Technical dependencies — systemic thinking becomes visible
- Obligation to justify a decision — a defensible next step must be formulated
- Feedback on reasoning — not only the result, but assumptions, risks and alternatives
- Variation instead of repetition — the same underlying logic across different contexts
What matters is not the size of the scenario but the quality of the friction. Good friction forces thinking and requires a justified decision; poor friction merely confuses or invites guessing.
Source: Steinhardt, S. & Dulgeridis, M. (2026), a. a. O., Abschnitt 6 und Tabelle 2. doi.org/10.56250/4141 →
Reliable action
Remaining capable of controlled action in complex digital IT environments: interpreting technical signals, justifying next steps, recognising the limits of one's own action, and deciding when to analyse further, act or escalate.
This is not intuition but professional stability under uncertainty. A sense of competence is the beginning; reliable action is the test.
Important qualification
Sources:
Steinhardt, S. & Dulgeridis, M. (2026), a. a. O., Abschnitte 3 und 9. doi.org/10.56250/4141 →
Steinhardt, S. & Ritter, L. A. (2026). Warum Virtual Labs pädagogische Akzeptanz brauchen. Wirtschaftsinformatik & Management. doi.org/10.1365/s35764-026-00608-2 →
CitationIf you refer to these concepts, please cite the original works rather than this page:
Steinhardt, S. & Dulgeridis, M. (2026). Zwischen Kompetenzgefühl und Handlungssicherheit: Die Kompetenz-Anwendungs-Lücke in digitalen IT-Lernformaten. IU Discussion Papers Business & Management, 7(15). https://doi.org/10.56250/4141
Steinhardt, S. & Ritter, L. A. (2026). Warum Virtual Labs pädagogische Akzeptanz brauchen. Wirtschaftsinformatik & Management. https://doi.org/10.1365/s35764-026-00608-2