Your Performance Isn’t Just Your Abilities
Why the environment around you matters as much as what you bring to the work.
It is easy to judge someone’s performance by what they produce. One person finishes a project early. Another misses a deadline. One team seems to move effortlessly, while another takes weeks to reach the same point. The conclusion is very natural: the first are more capable; the second needs to improve something.
Those are the obvious conclusions we get from our observations. But before making a judgement, there are other factors that need to be taken into account.
Imagine an experienced analyst asked to prepare a report by the end of the week. The task seems familiar. The calculations are straightforward. The analyst knows which questions the report needs to answer. Yet the information sits in three different systems that do not speak to each other. One requires permission from a manager who is away. Another requires some accesses that need to be negotiated with the technical support. The final numbers have to be copied and reconciled by hand.
Friday comes and the report is still not there.
From the outside, that delay may look like poor planning or a lack of discipline. But from inside the work, it looks different: most of the week was spent trying to make the task possible and pulling things together.
The blockers we don’t assume
We tend to describe performance as though it belongs entirely inside the person. Skill, motivation, judgment, experience: these elements factor in the equation, and they always will. But in organizations especially, the ability to act rarely rests on individual qualities alone.
Even a simple assignment can depend on someone else’s approval, a reliable software, access to a database, a functioning tool, or a decision made three departments away. Each dependency adds a condition to performance and enough small conditions can become a wall.
The person may know exactly what to do and still be unable to do it.
That distinction is relevant here because organizations often respond to slow output by asking people to work harder, organize better, or attend another training session. Sometimes that is actually appropriate. Sometimes it asks a person to become more skilled at surviving an environment that should have been itself improved.
Get MXI.Studio’s stories in your inbox
Join Medium for free to get updates from this writer.
This is especially true when the organization is built on people who want to save face even as the organization itself loses its own. Relegating instead the entire burden on the workforce while assuming the environment is never at fault.
And never taking care of the workflows can induce silent costs. Experienced employees learn which instructions are outdated, who can unlock a blocked request, and which spreadsheet contains the real answer. These workarounds can look like expertise. Often, they are expertise. But they are also evidence that the official process does not fully support the work.
When those employees leave, their invisible infrastructure leaves with them.
Enabling the work
This is where Work Enablement begins: not with the question of whether people are trying hard enough, but with whether the conditions around them allow their abilities to become useful.
An enabled environment makes essential information accessible, connects the steps that depend on each other, gives people appropriate authority, and provides tools they can rely on. It does not eliminate every rule or approval. Some friction protects quality, privacy, and safety. The point is to distinguish necessary safeguards from obstacles that exist simply because no one has redesigned the process.
And there is a trap in the desire to improve things quickly.
Organizations can buy faster software, automate one step, or add a new dashboard and still make the overall experience worse. A better tool that requires duplicate data entry is not necessarily an improvement. A streamlined approval that overwhelms the next team merely moves the waiting elsewhere. A policy designed without consulting those who follow it may look efficient on paper and become impossible in practice.
Work is connected. People are part of those connections. Changing one piece without understanding what surrounds it can create new bottlenecks while leaving the old frustration intact.
Imposing a new workflow is also not enabling work. Rather it might disrupt the flow, the governance and the established relationships within the teams.
So, the useful question is not simply, “How can he be faster?” It is, “What must be done for him to do the work well?”
The difference is subtle, but it shifts attention from visible output to the conditions producing it. It invites us to follow a real task: where it slows, what it waits for, what employees quietly repair, and which tools make the next step harder rather than easier.
This relationship between human capability and the systems that allow it to be expressed forms the foundation of the Work Enablement axis of our Power Series.
And once that relationship becomes visible, another question starts to emerge: how much of what we call individual underperformance is actually a signal from the environment?
