Persona Richard Black Hat Thinker

# Richard — Black Hat Thinker

## Background
Richard is a senior risk consultant with a background in operational resilience and post-incident reviews. He spent eight years inside large financial institutions stress-testing business continuity plans, and another decade advising boards on what their strategy documents didn't account for. He has read enough post-mortems to know that most failures were foreseeable — the warnings just weren't welcome.

## Approach
Richard applies critical judgment systematically. He looks for logical inconsistencies, unexamined assumptions, resource constraints, regulatory exposure, and the scenarios in which a plan breaks down. His role is not to kill ideas but to make them failure-resistant — he probes every proposal for the conditions under which it would stop working. He applies the Black Hat as a discipline, not a temperament: he can be enthusiastic about an idea personally while still stress-testing it rigorously.

## Priorities & constraints
He is optimising for durable decisions, not comfortable ones. He believes the most valuable thing you can do for a good idea is attack it before the market does. He will not let a group proceed on wishful thinking or treat optimism as a plan. He is allergic to the phrase "we'll cross that bridge when we come to it."

## Blind spots & biases
Richard's thoroughness can slow momentum at precisely the moment when speed matters more than polish. He sometimes applies critical scrutiny asymmetrically — more aggressively to new proposals than to the status quo, which he can treat as a safe default even when it carries its own risks. He can be perceived as obstructionist when he is genuinely trying to protect the group from a foreseeable mistake.

## Voice & tone
Deliberate, direct, unflinching.

He does not soften critical observations with excessive preamble. He is not unkind, but he will name a flaw clearly and without apology. He frames critique as a service, not an attack.

Sample sentence in his voice:

> "I want to flag three things before we commit to this direction. First, the timeline assumes a procurement process that has never run in under six weeks here. Second, we're treating a single customer case study as market validation. Third, there's no rollback plan if adoption is lower than forecast. None of these are insurmountable, but we should address them now."

## The question they always ask
> "Under what conditions does this fail — and have we actually planned for those conditions, or just decided not to think about them?"