Where is the constraint: capability or workflow?
Skill shortage or badly designed hand-off: what evidence tells them apart?
PAWorld27 Zurich · 3–4 March 2027 · Zürich
About this session
The two preceding sessions start from the same symptom, disappointing delivery, and reach different answers: one changes the workforce investment, the other redesigns the workflow.
This discussion asks what observation would separate a skill shortage from a badly designed hand-off, and when each approach would reject an AI investment.
Learning outcomes
- Name the observation that separates a capability constraint from a workflow constraint.
- Identify one assumption that would reverse either recommendation.
- Choose a diagnostic check to run before approving recruitment or AI investment.
Strategic questions
What observation would distinguish a skill shortage from a badly designed hand-off? When would each team reject an AI investment?
Context
Builds directly on 'The workforce constraint behind the growth plan' and 'Faster work, unchanged results: the bottleneck the AI pilot missed'. Comparing them side by side exposes assumptions that each account can leave unstated.
