The Critical Incident File
5 min read · 4 principles · apply it by lunch
Morning. Before you write a single line of the advert, you need twenty stories.
The advert for this role is probably half-drafted already, in a document or in your head: can you name one specific thing the last good person in that seat did, on one specific day, that the last bad one wouldn’t have? Adjectives are what you’re left with when nobody wrote the stories down.
John Flanagan ran the Aviation Psychology Program for the US Army Air Forces during the Second World War, and one of its first jobs was to work out why so many candidates were failing flight training. Many of the reasons on file were clichés — lack of inherent flying ability, poor judgement, unsuitable temperament — every one a label dressed up as an explanation. So he changed the question. By 1944, instead of collecting verdicts, his team was asking combat veterans to describe particular occasions: exactly what an officer did, and whether it helped or hurt the mission. Classify several thousand of those and the requirements of the job assemble themselves out of evidence. Flanagan, who founded the American Institutes for Research in 1946, set the method out as the Critical Incident Technique in Psychological Bulletin in 1954, and it’s been used to build job requirements, training courses and rating scales ever since. What makes it work isn’t the paperwork; it’s the direction of travel. Ask people what a role needs and you get their theory of the role, usually a portrait of themselves on a good day. Ask them what happened, and you get the job.
The Critical Incident File is Day 191 of 365.
In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.
$29 a month · cancel any time · 7-day money-back guarantee