A useful warning sign in a team is the sentence: "we are very adaptable." It can mean something healthy: people notice reality, update assumptions, and do not worship last quarter's plan. It can also mean something much less impressive: nobody wants to say what the standard is, because a standard creates a reference point, and a reference point makes avoidance visible.
The problem is not flexibility itself. In product work, marketing, hiring, sales, and almost every serious business function, rigidity is expensive. Markets move, customers contradict our assumptions, and internal plans often age faster than the slide deck suggests. A team that cannot change its mind will eventually protect the plan more than the outcome.
A standard is not a prison
A lot of people react badly to standards because they associate them with bureaucracy, control, and people who enjoy saying no. That association is sometimes earned. There are organizations where the process exists mainly to protect itself, and where doing the sensible thing requires a small act of rebellion. Nobody reasonable wants more of that.
Still, rejecting bad bureaucracy is not the same as rejecting standards. A standard is simply an explicit agreement about what good enough means in a given context. It may describe how decisions are made, what evidence is required before a launch, who owns a customer promise, how quality is reviewed, or what kind of behavior is acceptable in a team under pressure.
The useful part is not the document. The useful part is shared expectation. Without it, people do not become more creative. They become better at negotiating reality from scratch every week. That can feel dynamic for a while, especially to intelligent people who enjoy improvisation, but it burns attention on questions that should already have an answer.
Adaptability needs something to adapt from
The strange thing about adaptability is that it only has meaning against a baseline. If everything is fluid, nothing is adaptation. It is just movement.
A product team that changes scope every few days may look responsive, but the better question is whether it knows what promise it is trying to protect. A leadership team that keeps reorganizing may look decisive, but it may also be avoiding the discomfort of staying with one set of tradeoffs long enough to learn from them. A founder who changes positioning after every conversation with a smart person may call it learning, while the team experiences it as noise.
There are situations where the change is correct. Sometimes the original assumption was weak. Sometimes the market really has moved. Sometimes a customer tells you something so clear that not changing would be vanity. The point is not to defend old decisions. The point is to notice the difference between learning and being emotionally available to the last stimulus. Learning has memory. Reactivity has momentum.
The social comfort of vagueness
One reason teams avoid standards is that vagueness protects relationships in the short term. If nobody defines quality, nobody can be told clearly that the work is not there yet. If nobody defines ownership, nobody has to confront the person who is acting involved but not accountable. If nobody defines decision rights, everyone can keep participating without carrying the full cost of a decision.
This is understandable. People are not machines that optimize for truth all day. They optimize for belonging, status, safety, and not making the afternoon more unpleasant than it needs to be. I do not think that makes them bad. It makes them human.
The problem is that teams pay for this comfort later, usually with interest. The skipped conversation returns as coordination overhead. The undefined standard returns as uneven quality. The avoided disagreement returns as passive resistance. Then, because nobody wants to admit that the original issue was social, the team looks for a more technical explanation: better tooling, clearer dashboards, another framework, another meeting format.
Good standards are alive
There is a bad version of standards, and it deserves criticism. It treats past decisions as sacred. It confuses consistency with intelligence. It punishes context because context is inconvenient to manage.
The useful version is different. It is explicit, but revisable. It gives people a default, but not an excuse to stop thinking. It allows exceptions, but asks for the reason. Not because every exception needs a courtroom, but because reasons are how an organization learns what its standards are actually worth.
In that sense, a standard is not the opposite of adaptability. It is the thing that makes adaptation legible. When the team changes course, people can see whether it is responding to evidence, pressure, fear, taste, politics, or boredom. Those are not the same forces, and mature teams should not pretend they are.
The harder question
When a team says it wants to be more adaptable, I would listen for the missing second half of the sentence. Adaptable to what? Evidence? Customer pain? Market structure? Strategic learning? Or just internal anxiety, senior opinion, and whatever sounded persuasive in the last meeting?
That does not mean every team needs a thick rulebook. Usually it needs fewer, clearer agreements, held with enough seriousness that people can trust them and enough humility that they can be changed. The balance is not easy, and maybe that is why so many teams prefer the attractive ambiguity of being flexible.
At some point, though, the question stops being whether the team can change. Most teams can. The better question is whether the team understands what should remain stable while it changes. On that point, the vague answer is usually the honest one.