Rigour is a capability, not a department
Most organisations keep their rigour in one place, usually finance or compliance, and improvise everywhere else. The method travels. The reason it does not is that nobody has written it down.
Ask where the rigour lives in a company and you will be pointed at a department. Finance, because the numbers have to reconcile. Compliance, because the regulator checks. Legal, because contracts are read closely. Everywhere else, decisions are made in meetings, recorded in nobody's notes, and reconstructed later from memory.
This is a choice, even if nobody remembers making it. Rigour is a method, and a method can be applied to an operating process or a board paper as readily as to a tax return. The reason it stays in one department is that it was never described as a method. It was described as a job.
What the method is
Stripped of its departmental clothing, rigour is four habits.
- Evidence before opinion. The claim comes after the facts have been gathered, not before. In a tax return this is obvious. In a decision about which market to enter it is rare.
- The tradeoff is named. Every option gives something up. A rigorous recommendation says what, in the same breath as what it gains.
- One owner per outcome. A result nobody owns is a result nobody is responsible for. Finance teams know this; product teams relearn it every quarter.
- The trail is kept. What was decided, on what evidence, by whom. Not for blame, but so the next decision can start from the last one instead of from zero.
None of these requires a specialist. They require a standard, a template and someone who holds the line for the first few cycles until the habit forms.
Where it travels
A compliance engagement is the sharpest proof point because the test is binary: the filing is on time or it is not. The same four habits produce a different kind of proof elsewhere.
In operations, evidence before opinion means mapping the process as it happens before redesigning it. The tradeoff is usually speed against control, and naming it stops the redesign from quietly choosing one. One owner per hand-off is the whole of a working escalation rule.
In communication, the method becomes a document structure: the recommendation first, the evidence second, the tradeoff stated. A board paper written this way is read in a third of the time and decided in one meeting. The trail is the paper itself, filed where the next one can cite it.
In product and engineering, it is the discipline that keeps a design system consistent: a decision recorded once, an owner for each part, a standard that is checked rather than remembered.
The tradeoff of rigour itself
Rigour is slower at the start. Gathering evidence before forming a view takes longer than forming a view. Writing the trail takes time that the decision itself did not. For a small team this cost is real, and it is paid every week.
What it buys is that decisions stop being re-made. The question that was settled in March is not reopened in June because nobody can find why it was settled. The notice is answered from the file. The new hire learns the process from the playbook, not from whoever is free. Over a year, the time saved exceeds the time spent, but the spending comes first and the saving comes later, and any honest account of the method says so.
Making it a capability
The move from department to capability is mostly a writing job. Take the four habits, write them as a one-page standard in the language your teams use, and apply it to one process outside the department that already has it. Hold the line for three cycles. Then take the next process.
The standard is short because it has to be used, not admired. The practice we run keeps it to one page, and we have not found a process it does not fit.