Competence
Competence is the ability to put existing knowledge and skills into successful action in a real situation.
Competence differs from plain knowledge in that it only shows up in action. You can know a procedure by heart without being able to apply it reliably under time pressure or when something goes wrong. You become competent only when you combine knowledge, skills, and experience into a fitting result in a concrete, often unpredictable situation. A qualification, by contrast, is just the formal proof, a certificate or a degree, and says nothing about whether the action actually succeeds day to day.
In practice, competence is usually split into four areas. Technical competence covers the concrete subject and method knowledge of a field, such as operating a machine or handling bookkeeping. Methodological competence is the ability to approach problems systematically, for example using PDCA or structured troubleshooting. Social competence and self-competence cover working with others and managing your own way of working, including self-organization and how you handle setbacks.
Competence doesn't come from listening to a presentation, it comes from repeated action with feedback. Someone who sees a new method once in a training session has gained knowledge, but not yet competence. Only after applying the method several times, making mistakes, getting feedback, and adjusting does the ability actually take hold. That's why building competence takes time, real tasks, and a setting that allows mistakes instead of punishing them.
Practical Example
A workshop with 12 employees introduces a new setup procedure. After a two-hour training session, everyone knows the steps in theory, but setup time barely drops from 45 to 42 minutes. Only after three employees practice the procedure on real setups for four weeks, discuss intermediate steps with their supervisor, and refine their own sequence, does setup time drop to 27 minutes. The gap between 42 and 27 minutes is the gap between knowledge and competence.
How Leanshift Helps
Competence is the real foundation of any improvement in a business, because no standard and no method works if nobody can apply it reliably. The Kata mindset deliberately relies on short practice cycles with reflection instead of one-off training sessions, because that's what actually builds competence. When you deliberately grow your own competence, you're not just improving a single task, you're building the foundation to become someone who improves things themselves.
Frequently Asked Questions
What's the difference between knowledge and competence?
Knowledge is the theoretical understanding of something, competence is the demonstrated ability to apply that knowledge successfully in a real situation.
Can competence be measured?
Not directly with much precision, it's usually assessed through observable behavior or results on real tasks, such as error rate, time, or the quality of the outcome.
What's the fastest way to build competence?
Short practice cycles with a real task, immediate feedback, and the chance to adjust your approach afterward are the most effective.