A customer support team is asked to become more adaptable. Demand is changing, several tools are being replaced, and managers want staff to suggest improvements. The message is reasonable. The team still needs to know which work can move, how suggestions will be assessed, and what happens to service commitments while people learn the new system.
A memorable work quote can help people understand an intention. It cannot supply those decisions. The risk is a gap between the language of improvement and the arrangements needed to carry it out. That gap deserves examination without assuming that every encouraging message is an attempt to conceal a problem.
Productivity theatre is a useful description when visible expressions of progress become detached from the work they are supposed to support. The phrase should describe an observed pattern, rather than a diagnosis of someone’s motives. Three documented quotations provide a way to examine that distinction through planning, working relationships, and responses to change.
Planning Is Preparation, Not a Reason to Discard Every Plan
Plans are worthless, but planning is everything.
Dwight D. Eisenhower used this sentence in his remarks to the National Defense Executive Reserve Conference on 14 November 1957. He introduced it as a statement he had heard earlier in the Army. The source establishes his use of the wording; it does not establish that he invented it.
The remarks concern preparation for emergencies whose actual course cannot be fully predicted. Eisenhower’s point was that studying the problem helps people respond when events differ from expectations. The passage is a poor basis for claiming that preparation, schedules, or recorded commitments are unnecessary.
For the support team, a useful application would involve examining demand, likely service interruptions, staffing, and the conditions under which a rollout would change. The team might agree that a tool transition pauses if a defined support dependency is unavailable. That is preparation for adaptation.
A less useful application would be to change the rollout date repeatedly while saying that plans never survive reality. The issue is then whether commitments are being updated with evidence and authority. Staff need the current position and a route to questions, even when the earlier plan no longer fits.
The quotation can open that conversation. It should not settle it. A military planning statement provides a perspective to consider, rather than proof that a particular business method will improve productivity.
Valuing People Includes Designing the Work Around Them
Individuals and interactions over processes and tools
This is one of the values in the 2001 Manifesto for Agile Software Development. Its concluding explanation preserves value in the items being compared while giving greater weight to the preferred side. The manifesto is not a claim that tools and process can be removed without consequence.
The support manager might apply the value by involving advisers in the design of the new workflow. They can explain which information is difficult to find, which requests need specialist help, and what a customer must understand before a case closes. That experience can improve the proposed process.
The contribution needs a route into decisions. If staff identify that a new form creates repeated clarification work, someone should assess the evidence and explain whether the form, guidance, or service expectation will change. Listening is useful; a suggestion process with no available response leaves the operating question open.
An informal conversation can reveal something a dashboard misses. A shared record can preserve something a conversation would otherwise lose. The team can use both while being clear about their purpose. Valuing interaction should not require staff to reconstruct the same information through repeated calls because nobody maintains the current instruction.
This is also where resources matter. Asking people to contribute to design while retaining their full case allocation creates an additional commitment. A manager needs to decide how the time is provided or which contribution is being reduced. An appeal to collaboration cannot make that capacity choice disappear.
Responding to Change Requires a Choice About Existing Work
Responding to change over following a plan
This value comes from the same manifesto. It expresses a preference in how software development is approached. It does not establish that every new request should immediately displace work already under way, or that a different priority requires no explanation.
Suppose a major customer requests a change during the support-system transition. The manager can examine the consequence of responding now, deferring, or providing an alternative. The relevant decision may involve customer impact, staff preparation, configuration work, and the commitments already made to other teams.
If the request is accepted, identify what changes in the plan. Another task may move, the scope may narrow, or extra support may be provided. Communicate that decision to the affected people. Otherwise the team may be asked to satisfy the new priority while still being assessed against the old one.
A useful response to change can also be to continue with the current work. The new information may not justify disruption, or the team may need evidence before making a consequential commitment. Adaptability includes judgement about the response, rather than movement as an end in itself.
The article on unclear strategy examines how broad ambitions become conflicting demands. A quote about flexibility becomes practical when it helps identify who will choose between those demands and how the result will reach the team.
Examine What Follows the Message
A statement of intent is best assessed alongside what people are asked and enabled to do. After the adaptability announcement, does the team receive usable priorities, time for learning, and access to decisions? Can it raise a problem with the new tool without having to present the problem as enthusiasm?
Those questions can be answered through actual cases. Follow a suggestion from an adviser, a changed customer request, or a service issue during the transition. Establish what was raised, which decision followed, and what changed in the work. The result may reveal an effective response, a genuine constraint, or a gap that needs repair.
Avoid inferring a whole culture from one sentence. A manager may use a familiar phrase while also doing the necessary preparation. Another may speak precisely while leaving commitments unresolved. Language is evidence of what was communicated, but the operating account needs more than wording alone.
The distinction also applies to criticism. Calling an initiative theatre can become another slogan if nobody explains the mismatch. A specific account is more useful: training was requested but not scheduled, the new form increased repeat contacts, or a suggestion reached no role able to decide.
An acknowledgement can be an appropriate first response. It should make clear whether the issue is being accepted for assessment, what evidence is needed, and when the team will hear the result. It need not promise that every proposal will be implemented.
Replace a General Exhortation With a Workable Agreement
The manager could turn the adaptability message into an agreement about the transition: the supported workflow, the time available for training, the conditions for pausing rollout, and the role that can resolve competing priorities. Staff would then have something they can apply and question.
Some choices remain outside the manager’s remit. A centrally retained budget or service promise may require a sponsor’s answer. The manager can prepare alternatives and state the uncertainty instead of privately asking staff to absorb it. The related discussion of responsibility without authority explains how to make that boundary explicit.
A short improvement trial can provide evidence. The team might compare the revised form with the current one for a defined class of requests, examining clarification work, staff effort, and whether customers understand the response. Record the limits of the comparison and who can authorise a wider change.
Follow up where the work happens. Update the guidance and allocation, explain the decision to affected colleagues, and remove obsolete instructions. A clear presentation can still fail to help if the daily process continues to ask for something different.
A manager can also explain a decision not to change the process. Staff may have identified a real inconvenience that is outweighed by another requirement. The account should name the relevant requirement and the alternatives considered, rather than repeat a motivational phrase as the answer.
Keep Encouragement Connected to Evidence and Support
Encouragement has a place in difficult work. People may value recognition, confidence, and a shared explanation of why a change matters. A supportive message becomes more credible when it acknowledges constraints and explains the help available. Recognition can also be specific: describe the contribution, the conditions in which it was made, and what it enabled.
Check the result after the transition. Can staff describe the current priority? Do training and coverage match the promise? Are unresolved questions reaching a role able to answer them? These observations are more informative than counting how often the organisation repeats its preferred values.
The companion article on efficiency quotations examines slogans used to justify optimisation. Here the concern is the relationship between the message and the commitment. A useful work quote helps people ask a clearer question; the organisation still needs to answer it through decisions, resources, and follow-through.
