The real problem: demand outruns skill mix
Skilled staff shortages surface late on most projects. Scope expands, sales adds commitments, and the same headcount delivers with a thinner skill mix. Critical work piles onto two or three people, new hires ramp slowly, and knowledge stays in key-person heads instead of systems.
Hiring does not fix next sprint—even with budget, ramp-up takes weeks. Until then you need visible capacity, packaged work, and searchable knowledge.
Symptoms and hidden costs
| Symptom | Practical cost |
|---|---|
| One senior on every critical path | Single point of failure |
| New hire unproductive for weeks | Opportunity cost and rework |
| Same questions in chat | Senior time fragmentation |
| Scope accepted without capacity check | Unrealistic commitments |
| "Only X knows this" | Attrition risk |
Shortages hurt quality and morale, not just dates. Overloaded experts skim reviews and skip mentoring.
A three-layer framework: Measure → Package → Transfer
1. Measure — make capacity visible
Before any new commitment:
- Sum remaining estimates on open tasks per person
- Tag specialist work (infra, legal, design system)
- Look at least two weeks ahead
If demand exceeds capacity, that is a portfolio decision—not "work harder."
2. Package — structure work for handoff
Work packages split large efforts into assignable units with clear scope, definition of done, owner, reviewer, and linked dependencies. Packaging without context is just smaller tasks. Packaging with wiki context lets juniors or contractors enter safely.
3. Transfer — knowledge onboarding
Close skill gaps with:
- Wiki / knowledge hub — runbooks, ADRs, decisions
- Shadowing on real PRs or reviews
- Week-one checklists in the tool—not stale PDFs
Goal: a new teammate finds "why we built it this way" by day three.
Operating rules for PMs and leads
Capacity gate before yes — No critical assignment without a heatmap check.
Protect expert time — Cap WIP for seniors; fragmentation blocks mentoring.
Document while shipping — Team rule: merge without wiki update for new features = incomplete.
Planned cross-training — One secondary skill per quarter on the backlog.
Where WKFGo helps (honestly)
WKFGo does not invent experts. It improves visibility and knowledge:
workload_heatmap— see remaining hours per person- Packages — scope work for assign and track
- Knowledge hub / wiki — onboarding next to tasks
- Teams and permissions — mentee access without admin chaos
Structural gaps (no security skill at all) still require hire or outsource—the tool surfaces pain earlier.
Common scenario: "Only one person knows the API"
Imagine release week and your only backend senior falls ill. The board is full of tasks but no package or wiki describes service boundaries. Juniors do not know where to start; the PM hunts chat for "someone who knows." That is skill shortage without transfer—not bad luck.
The way out:
- A heatmap would have shown that senior at overloaded capacity—a red flag before illness
- An "API v2 migration" package with DoD and wiki links could enable handoff
- A knowledge hub runbook could shrink recovery from days toward hours
No tool prevents illness alone—visibility and doc gaps surface before crisis.
Skill capacity in planning meetings
Before committing to a date:
- List critical skills for the release (security, data, UX review)
- Match against the heatmap—does each have an owner who is not red?
- If gap: temporary outsource, scope cut, or date shift—before verbal yes
This simple gate often prevents heroics.
Packages in practice
A good package includes: one-line objective, in/out scope, skill tags, minimum wiki link, acceptance criteria. Packages without wiki are bigger tasks—packages with wiki are onboarding units.
Anti-patterns
- Measuring capacity from green status meetings
- Hero experts without backup
- Writing wiki only after a crisis
- Packages with no owner
Frequently Asked Questions
Does shortage always mean hiring?
No. Re-scope, temporary outsource, or automation may suffice. Quantify demand vs capacity first.
How do we track skill mix?
Labels on tasks plus monthly retro: "which skill was the bottleneck?" Start simple.
How long should onboarding take?
Depends on doc quality. Teams with active knowledge hubs ramp faster—because of discipline, not magic.
Are packages overkill for small teams?
Small teams need clear handoff most when one person is out.
Summary
Skill shortage is not headcount-only—visibility, packaging, and knowledge transfer are three levers before hiring. Do not normalize red heatmaps; do not write wiki only after crisis. Show sponsors structural gaps with data.
Next step
Open a recently slipped project. List the three people with highest remaining hours. Ask: is their skill replaceable? If not, write one "how we do X" wiki page this week.