Practical mastery

This is where knowledge turns into output. You will learn to commission work rather than ask questions, to engineer the context you provide, to run an agent, and to build an assistant on your own knowledge — and then to verify all of it before you put your name to anything.

OPENING STORY

Two hours, then two hours

Fawzooz was asked to produce a risk assessment for an entire system, which would normally be a week's work. He sat down in the morning and gave the system the context it needed: the architecture, the incident log, and the standard the system is held to. Two hours later he had an organised report in front of him, written in clean language, with a structure nobody could fault.

And he felt exactly the feeling I am warning you about now: the intoxication of speed. He very nearly sent it.

Then he spent another two hours going back over it, and found three errors. Two of them were minor. The third was a security control attributed to a clause of the standard that simply does not exist — a clause number in the right format, phrasing that matched the standard's own style exactly, and content that had been invented outright. Had that clause reached the audit committee, it would not have sunk the report alone; it would have taken his credibility with it.

The lesson he came away with is the title of this entire degree: the tool shortens the time it takes you to produce something; it does not shorten the time you carry responsibility for it. The first two hours made him productive. The second two made him a professional.