Cognitive Transition · Book One

Chapter 11 · A 15-Year Resilience Framework

“Dig where you are. The gold is down, not off to the side.”

Summary

You open the strategic plan you wrote five years ago and find that almost nothing that mattered was in it. The last chapter starts from that scene and draws a method from it: stop predicting, start designing. There are six pieces, and none depends on the pace of change or on the tool of the moment. Look at infrastructure first and the discourse second. Read incentives before promises. Spread the risk across human capabilities, with a core of deep judgment and an orbit that travels from one sector to another. Tend the three assets that compound over the years: judgment, network, and reputation. Review all of it once a year. And decide, finally, where to stand so that you occupy the space AI cannot occupy. The chapter closes the book with its eleventh tool, an annual review in seven questions, and with a thought about the timeframe in the title: fifteen years is not a forecast, it is a design measure.

Extended content

Liquid part: this text keeps growing after the printed edition.

A date in the calendar

Open your calendar now and find a working day within the next thirty, with no meetings and far from any deadline. Write "Review" on it and block the whole day, or half of it if you are quick and honest. An intention without a date always loses to urgency, and urgency never gives notice.

Two weeks ahead, start a folder. Put in it the cognitive architecture template from Chapter 10, the Delegation Control Framework, the warning signs, and the Hybrid Decision Templates from Chapter 6. Add the one thing you may not have: your calendar for the year, with the names of the people whose judgment you tested against your own.

Andrés and his first review

Andrés is an independent logistics consultant who has worked with an AI assistant for three years. He arrives at his review day convinced things are going well. He answers the second question with his calendar open and finds four conversations that were worth something, against seven the year before. He answers the third and discovers that his website says "warehouse management" while what clients pay him for is diagnosing why a plant's flows break down. At the fifth he compares lists: a year ago he delegated four tasks, today it is nine, and for only two of them does he remember making the decision. The other seven slipped in through inertia.

The first question surprises him in the opposite direction. His judgment for estimating transport lead times is still sharp. The one that has gone dull is the one he uses to review carrier contracts, which he has been skimming for months. He leaves the day with one sheet of paper and no urge to punish himself. He writes three dated decisions: review one contract by hand every month, put carrier selection back on the list of what cannot be delegated, and spend a quarter in a sector community.

A ten-minute test for the tool of the month

Think of the last tool you adopted, or the one a colleague is pushing you to adopt. Answer the four questions of the infrastructure test in writing. The one people skip most is the second: what happens to my work if that infrastructure fails or its terms change? Write the answer around a concrete case, a Thursday with a deadline bearing down and the tool offline. If the answer is "nothing serious," adopt. If it is "I'm stuck," adopt with conditions: a tested alternative and a manual procedure you know how to run.

Answering with proof, deciding with dates

The trap of the day is the generous grade. To avoid it, attach a condition to every answer: one line of evidence with a date, a name, or a document. "My network is fine" fails the filter. "In March a colleague warned me about a regulatory change before it was published" passes. If you can't write the evidence, the honest answer is "I don't know," and that is already a finding.

It works in both directions. Note also what is going better than you feared, because the review serves as much to recover your sense of proportion as to spot leaks.

Close with a sheet you can read at a glance:

One capability you will deepen, with the specific project where you will exercise it.
One red line you will protect or adjust, with the exact sentence that will go into your template.
One action for your weakest compound asset, with a start date and an end date.

Write next to each one how you will know, a year from now, whether it was done. A decision with no way of checking it is a wish.

Questions for whoever reads your sheet

Choose someone who doesn't owe you favors and hand over what you wrote with these questions:

Which answer strikes you as too comfortable?
Where is the evidence missing?
Which of the three decisions would cost me least to break, and why did I write it that way?
What change from this year am I sparing myself from mentioning?

Listen without defending yourself. The reader doesn't have to be right. It is enough to point out where you told yourself the kinder version.

Where to go next

With the day done, the final tool is running and the other ten are calibrated. What remains is to give a name to the terrain you have crossed, and the epilogue takes care of that.

Difunde el mensaje