Articles about connecting capabilities, priorities, and organizational transformation.
26 articles
Does the organization need breadth, depth, or integration? Generalist, specialist, and hybrid are possible answers, not identities the architecture should fix permanently.
To decide what comes after the pilot, examine which decisions changed, which outcomes followed, and what it costs to sustain the mechanism. Participation and coverage do not yet demonstrate value.
Although importance, scarcity, and advantage are often compressed into the label “critical skill,” each dimension requires different evidence and investment. Separating them changes what must be protected, sourced, or built as a system.
Even when two areas work differently, they can still share an architecture. Adaptation stops being local when it changes meaning, comparability, or the rights attached to use.
To choose among building, hiring, moving, partnering, or automating, compare the demand, the time horizon, and the dependencies each response creates.
Splitting, merging, and retiring a skill correct different failures. Even if the catalog looks tidier after the change, the choice depends on which distinction in the work must be preserved and which decisions will change.
On the eve of a launch, an incomplete interface can immobilize capability that each team does possess.
A correlation between skills and outcomes is useful for opening an investigation. A claim of contribution requires an explanation of the mechanism, the timing, and the alternatives.
An organization can have the right skills and still fail to produce the expected capability. Even when the inventory is accurate, the rules of work may prevent those skills from being used.
Even when someone develops a skill, the organization may retain the same constraint if the opportunity, support, or authority to apply it is missing.
Consider an unexpected absence: a capability is fragile when its absence interrupts a critical outcome and no alternative has demonstrated that it can restore that outcome in time.
Work without Jobs proposes looking beyond the job as a whole and brings into view a layer that skill architectures often overlook: the work that needs to be organized.