The Language of Execution: Measuring Team Maturity in Real Time

Imagine if managers could measure focus, alignment, organizational learning, behavioral change, and social engagement in real time, on a continuous basis? Most organizations use financial results, hard project indicators, or surveys as proxies for the performance of the abstract concepts above. These proxies are approximations that do not identify the real drivers of focus, alignment, or behaviour.

Well, a simple observational method based on team language exists. It can consistently capture organizational maturity and decision-making flow in a remarkably simple way, as long as managers have the skills to observe. All the relevant information is implicit in the language group members use among themselves in meetings, feedback sessions, and project planning. It works in groups or in pairs. Silence and inaction are also revealing forms of communication to consider.

A few days ago, I observed a colleague leading a workshop with twenty technical experts, portfolio managers, marketers, and sales teams. The teams were composed of young and senior professionals from three different continents. Their goal was to design projects from scratch to address specific commercial challenges. My colleague introduced a method that addresses key dimensions of business success by requiring the team to build mockups representing each element of the desired solution.

For me, however, what stood out was the method for monitoring the concrete impact of the learning and behavioral change her method triggered. The language participants use in building the mockups reveals much about the culture they are immersed in, their fears, the degree of autonomy and engagement, and their confidence in their ability to succeed. Above all, it reveals the impact of the senior managers who micromanage their work.

In this simple method, managers just need to observe language. The objective is not to judge individuals. The goal is to understand the dynamics that distract, slow, confuse, blind, and stop a group. It also reveals how much the team can learn and which negative mindset patterns keep the team from progressing as a group.

For our purposes, we classified the possible outcomes of team language into four levels, based on our long-term experience in project management. Team dialogues contain typical phrases that reflect their states of mind and reveal what is likely to happen during project execution.

LEVEL 1 – ASPIRATIONAL

High ambition, low causality. It signals an intent-based, not action-based mindset. Typical phrases:

• “We need buy‑in”
• “This is strategic”
• “In the future we will…”
• “They should support us”

LEVEL 2 – STRUCTURED BUT FRAGILE

Planning exists, but dependencies are unclear. It signals that elements exist, but the team does not notice how they connect. Typical phrases:

• “Marketing will handle this”
• “Phase 1 / Phase 2”
• “IT will need to build…”
• “We assume delivery by Q4”

LEVEL 3 – OPERATIONALLY COHERENT

Projects can realistically be delivered. Cause-and-effect understood and managed. Typical phrases:

• “If supplier X delays, we reduce scope”
• “This decision belongs to Anna”
• “The margin comes from this step”
• “This only works if we hit volume Y”

LEVEL 4 – EXECUTION‑READY & ADAPTIVE

Projects can survive reality. It indicates that the team thinks in systems, time, and adaptation. Clear sign of independence, autonomy, and flow. Senior managers remain strategic and give space in execution. Typical phrases:

• “If momentum drops, we shorten cycles”
• “We designed this to fail safely”
• “We revisit this decision after signal Z”
• “We trade speed for cost here”

Returning to the audit measurement, how does this simple tool work as a performance index? Well, based on repeated observations across different industries*, the team’s mind maps, readiness, and learning capabilities, expressed in their own language, will correlate with their probability of success.

At level 1, the team is fragmented, with poor leadership and ownership; their challenges and solutions lack causality. The probability of success is as low as 20%.

At level 2, the team displays a partial structure to address the challenge; they demonstrate clarity among themselves but lack understanding of all stakeholders, leading to weak execution. Their success rate ranges from 40 to 50%.

At level 3, the team is immersed in a coherent system provided by the organization, including structure, policies, resources, and feedback; leadership and ownership are clear, making it easy for the team to control execution. Success rate goes up to 75%.

At level 4, the team is part of an integrated, self-managed system with internal mechanisms for correction. Senior leaders do not need to intervene in daily routines, but they do need to care for the system. Projects are adaptive and can survive the unexpected. Success rate above 90%.

In the exercise above, as team members had to confront reality by observing real mockups, their thinking and language were forced to change. They managed to double the likelihood of project success in a single workshop as we observed the maturity level shift from one to another. The team’s language, sense of ownership, and decision flow changed within hours. Their language changed how they thought, interacted, and contributed to the project’s design. The perception of their role towards success was altered.

* Project Management Statistics 2025-26: Success Rates, Trends & KPIs PMI & Wellingtone Data | PM Study Circle; THE RELATIONSHIP BETWEEN PROJECT MANAGEMENT MATURITY AND PROJECT SUCCESS