Positive Agility in practice: signals, not slogans

Organisations adopt agile vocabulary quickly. Within a year of beginning a transformation, most teams can speak fluently about sprints, epics, WIP limits, and psychological safety. The words are right. The behaviour, often, is not.

Psychological safety becomes a phrase that everyone agrees with and nobody practices. Transparency becomes a principle on a wall poster and a liability in a status report. Retrospectives become a space for discussing tools and process hygiene while the real issues (tension between teams, concerns about direction, questions about leadership) are carefully avoided.

The vocabulary is not the problem. The problem is when the vocabulary substitutes for the change it is supposed to describe.

Psychological safety is not when people say they feel safe. It is when someone raises a problem that implicates their manager, and the manager thanks them, investigates, and changes something. The signal is in the response, not the claim.

Transparency is not open dashboards. It is when a senior leader shares bad news early and accurately, before being asked, and without framing it as someone else's fault. The signal is in what people choose to make visible when they are not required to.

Continuous improvement is not a retrospective. It is when a team changes something in its third retrospective that it first identified in its first, and can explain why the first two attempts did not work. The signal is in the iteration, not the ceremony.

Empowerment is not autonomy granted on paper. It is when a team makes a decision that the leader disagrees with, the leader voices their concern, the team commits to the decision anyway, and the leader supports them. The signal is in what happens when there is genuine disagreement.

One practical way to move from slogans to signals is to conduct a simple audit with a team or leadership group. The questions are direct: Give me an example of a time in the last month when psychological safety was real: when someone raised something uncomfortable and the response made it safe to do that again. If the examples are specific and recent, you have a signal. If the response is general or conceptual, you have a slogan.

Do this with each of the elements you care about. Empathy. Trust. Transparency. Continuous learning. Resilience. For each one, ask for a recent, specific example. The specificity test is brutal but honest.

This is not about finding failure. It is about understanding where the organisation actually is, so that efforts to improve are directed at the right places.

Once you know which elements are real and which are performative, the work becomes much clearer. You are not trying to introduce a concept; you are trying to create the conditions for a specific behaviour to occur and be reinforced.

If transparency is only a slogan, the question is: what makes transparency costly? Usually it is that the bearer of bad news is punished while the person who packages bad news prettily is rewarded. Change that dynamic, and transparency tends to follow.

If empowerment is only a slogan, the question is: what happens when a team makes a decision that leadership dislikes? Usually the decision is quietly overturned or the team is second-guessed until it gives up. Change that dynamic, and real autonomy tends to follow.

The signal work is not soft. It is about identifying the specific leadership behaviours that create the conditions for genuine agility, making those behaviours visible, modelled, and expected.