Even the mountain changes
Look at a mountain on two consecutive mornings and it seems permanent. Give water, ice, wind, and gravity enough time and the rock changes shape. A business can make a similar mistake about time. Its service still sells this quarter, so its leaders assume the market will be there when they next need it. By then, a change that was hard to see at first may have become expensive to address.
Bob Dylan put the point starkly in “It’s Alright, Ma (I’m Only Bleeding),” released in 1965. He sings that “he not busy being born is busy dying.” For an organization, renewal is a continuing obligation. An improvement fixed a problem under a particular set of conditions. The next improvement starts by asking whether those conditions still hold.
Look for causes while you still have choices
Suppose a staffing firm that supplies legacy software specialists sees renewal requests start to come in for shorter periods. It could be the budget cycle, a change in the mix of clients, or the beginning of a move to a different platform. The leader should find out which. Talk to the people who approve projects and the people who use the systems. Check budget decisions, migration milestones, and the vendor’s published support dates. Ask what evidence would favor each explanation.
If separate clients confirm that funding is shifting from maintenance to migration, trace what follows. The team may need people who understand both the old platform and the new one. That capability takes time to find and verify. Recruiters can test the market for it while the old business is still healthy. If the evidence points to a temporary budget pause, the same facts may support a much smaller commitment. Early signals buy time to learn.
The OECD calls the systematic search for emerging changes and their drivers horizon scanning. The practice is useful because possible changes can be investigated before they have fully developed. Pick a few assumptions whose failure would materially change your plans. For each one, write down who watches it, which source they will consult, and what finding would trigger a decision.
Practice honest improvement on a small scale
Ask the team to name a weakness in its own work alongside each threat it sees outside the organization. A missed opportunity may reflect a market change, a slow internal decision, or both. Record the actual sequence of events and invite someone close to the work to challenge the explanation. Leaders need to examine their own assumptions by the same standard.
Give one improvement a test. In the staffing example, try a small search for people who have supported an old platform during a migration. Predict what expertise you expect to find and which buyer would value it. Set a review date and compare the result with the prediction. The Deming Institute’s account of the Plan–Do–Study–Act cycle emphasizes that comparison. When the outcome differs from the prediction, you learn where your understanding needs to change.
Count the risk of standing still
Hesitation can be prudent when the downside is large. It can also become a habit. Work out what happens if you wait while the trend continues. If renewals fall and overhead stays fixed, the gap can eventually threaten the company’s ability to stay in business. Set a limit on what you will spend to learn, and compare that with the cost of being forced to act later.
The same discipline works for an individual. A technical professional can compare the work they do today with the work customers are starting to ask for, then test one gap with a small project and feedback from someone who uses the skill. Give the next review a date. Continuous improvement earns its name when you come back to check what changed.