Team Effectiveness

Where it sits

Last, and only when it is warranted. The AI Photo qualifies the starting point, the AI Readiness Scan produces the ranked opportunities and the roadmap, the Capability Sprint builds the first working use case with your own people. Team Effectiveness is what follows if that reveals a gap the existing team cannot close.

It is deliberately optional. Most gaps turn out to be a mandate problem or a skill problem, and hiring for those makes them worse rather than better.

Training or recruiting

The distinction is worth being strict about:

• A skill gap is closed by learning. Someone does not yet know how to judge a model output, and can be taught
• A quality gap is not. Nobody in the team is willing to contradict a decision that has already been made, and no course fixes that

Recruiting to solve a skill gap is expensive and demoralising for the people who could have learned it. Training to solve a quality gap simply does not work, and the trajectory quietly stalls a second time.

Why a structured judgement

Qualities like this are exactly the ones a CV does not show, and exactly the ones where a hiring decision drifts into gut feel. That is why the assessment used is named and structured rather than impressionistic: see the APAC framework, which measures adaptability, personality, awareness and connection.

What durable means here

The test is not whether the new way of working survives the first month. It is whether it survives the departure of the person who championed it. Anchoring in a team means more than one person can carry it, which is the same standard AI Capability is measured against.