How the skills hold together

The defaults of work used to be cultural. Now they are computational, and authorship erodes through a hundred small choices nobody made. Seven capabilities pulling in different directions under pressure do not add up to judgement. What holds them together is a rhythm, not an eighth skill.

Share this line as a card

What changed#

The defaults used to be cultural: weekly meetings, quarterly reviews, manager sign-off. Many are now computational. Calendars accept invites without asking. Sprint boards pull tasks forward. Editors offer drafts before you have thought. Release systems ship unless somebody flips a toggle they never set. Poor analysis used to look poor, and now arrives as polished charts and confident percentages.

It runs well beyond workplaces. Autoplay rolls the next episode, recommendation engines choose what you discover, maps route whole towns down side streets, triage queues label cases routine, lesson planners strip out hard questions, risk scores nudge bail decisions. The line Rahim Hirji puts on it is short: if you do not set the defaults, the defaults set you.

How authorship goes#

Not in one concession. The book's illustration is a chief of staff who spent a morning moving between auto-accepted meetings, opened a blank document at four o'clock to write a strategy memo he had promised his chief executive, and had half an hour. He asked the editor for a draft. Three pages arrived in twelve seconds, confident, generic, every recommendation optimised for speed and scale, none of them asking whether speed and scale were what the company needed. He removed the language he would not use and sent it. The chief executive liked it and began socialising it. Two months later the company pivoted on a strategy that was wrong, and nobody could say where the error began.

The system wrote it. He signed it. Authorship vanished into the gap between the two. That gap is what the whole of this research is about, and the reason it is hard to govern is that no rule was broken and no decision was visibly made. The related accounts are at drift versus design and custody.

Why a system rather than more skills#

Software running without structure has every application fighting for memory and every process competing for attention, and the machine eventually stops. The same happens to judgement under pressure.

Without something holding them together, curiosity fights efficiency, empathy fights speed, and principle clashes with pragmatism. Each capability pulls in a different direction, and the week fills with activity while emptying of intent. Adding an eighth capability does not fix a coordination problem. What is needed is a rhythm that decides what gets priority, what gets delegated and what must stay human, even when the week tries to decide for you.

That rhythm is the Five Loops, and the reason each loop carries a closure signal naming a person is that resetting a default requires somebody to do it deliberately. The mapping from the seven capabilities to the parts of a decision is at how the seven skills produce judgement.

Where to start#

Where the defaults are strongest. That is usually the calendar, the first draft, and whatever ships unless somebody intervenes. The book's instruction is not to master all of it at once, which is the correct advice and the one most transformation programmes ignore.

What this does not establish#

The argument is from observation and advisory practice rather than from measurement. Nothing here counts how much of professional work now runs on computational defaults, and the illustration is a single disguised case that shows the mechanism is real without establishing how common it is. That the loops fix it has not been tested, and the page says so where the loops are described.

Source#

Rahim Hirji, SuperSkills: The Seven Human Skills for the Age of AI, Kogan Page, 2026, chapter eight.

Related SuperSkills research#

• How the seven skills produce judgement
• The Five Loops
• Drift versus design
• Human skills in the age of AI