Heuristic
Separate domain knowledge, tool skill and transferable capability
Different skill layers decay and transfer at different speeds.
Before you use it
- Use when
- A skill list mixes concepts such as 'finance', 'Salesforce', 'problem solving' and 'SQL' as if they were the same type.
Keep this limit in mind
- The categories overlap in practice; use them to reason about portability, not to force every capability into a perfect box.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Classify important capabilities into domain knowledge, tool or platform skill, and transferable skill or work activity. Then ask what each layer depends on and where it can be reused. Use the map to avoid mistaking mastery of one tool for mastery of the underlying job—or dismissing valuable tool depth as worthless.
An example
A workflow consultant separates platform configuration from process modelling, data reasoning and stakeholder facilitation.
Check your result
Each important capability has a layer and at least one plausible transfer path or limitation.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingSeparate domain knowledge, tool skill and transferable capability
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Use before this ideaDecompose the role into tasks before naming your skills
Evidence and sources
The current O*NET database separates occupations into tasks, work activities, essential skills, transferable skills, knowledge and technology skills, enabling comparison below the job-title level.
O*NET is U.S.-focused and its taxonomy should be treated as a structured comparison aid rather than a universal occupation model.
O*NET 31.0 Database · Database content areas
O*NET publishes transferable-skill and work-activity competency frameworks that can help identify capability overlap across occupations.
Framework overlap does not prove a person can perform a target role without context-specific knowledge and practice.
O*NET Competency Frameworks · Transferable Skills and Work Activities Competency Frameworks
All sources (2)
Edition and review
Version 0.1.0
No review details are supplied for this edition.