• Aug 1

The Standard No One Set

In R&D, no one can say when these documents are good enough. Technology roadmaps. Technology screenings. Risk assessments. Capability plans. Strategy updates.

The differences are real. A roadmap and a risk assessment are built by different people, for different rooms, on different cycles. But each one is judgement work produced to support a decision, and the same question goes unanswered on all of them. Is this good enough yet, or does it need more?

One review stays with me. The document was a three-year product roadmap, and its job was real: line up the right product development projects, planned and sequenced, so the organisation and the research move together over three years. The room treated it as done. So I asked about the specific projects. If we start this one on this date, will it have what it needs? The right competences, ready and available? And the new technology the product depends on, will that be ready when the project needs it? People began to answer, then slowed down. We had not seen the technology roadmap. Nobody was sure it even existed yet. We took a short break, brought a few technology experts into the room, and it became clear the two roadmaps were badly out of sync. The product plan had gone to the table as finished while built on a technology plan no one had checked.

Not every case is that stark. Often the gap is smaller. I ask in the thin places, the answers are there, the author had them, they just never reached the page, and we close them in the meeting. But whether the gap is a missing sentence or a missing roadmap, the document arrived as finished before anyone had said what finished means. That is not carelessness. It is what happens when no one sets the standard.

Think about the two people involved. The producer has no target, so they polish toward their own standard, or they hold back because they cannot tell what the review actually wants. The commissioner approves because the work looks complete, with no way to tell whether it is. Both are acting reasonably. The work passes review and still carries thin spots the author could have filled in a sentence. The waste is the reinvention itself, task after task, with the judgement never made explicit.

The usual objection is that you cannot standardize this. Judgement work resists a checklist, and roadmaps are not risk assessments. That is true, and it is beside the point. Knowing when something is good enough is itself a skill. It can be developed and taught, like estimating effort or reviewing a design. It means seeing what good enough looks like for this specific piece of work, and where more analysis stops adding value. That is judgement, and no template contains it.

This is where the most senior person in the room matters most. They can name what is missing. Or, holding a document they believe is finished, they can put the question to the group: I think this is done. Does anyone see a gap? From a colleague, that can read as testing someone. From the head of R&D, it sets the standard. It makes the check a normal thing to do, and the judgement starts to build across the team instead of staying with a few individuals.

One complication worth keeping. Some of this work is uncertain enough that good enough is a range. A risk assessment for a mature technology can be pinned down. A screening of something genuinely new cannot, and pretending otherwise just hides the uncertainty instead of removing it. So the aim is smaller and harder than a single line every document must cross: to have the judgement, and the conversation, at all.