← back to the AI PM Portal
DEEN
Diagnosis, not a deviation list

Hidden Catch Audit

Find hidden blockers in projects and business processes before they cost you.

A project can be formally under control and still be fundamentally blocked by a problem nobody is looking at anymore. Processes run. Meetings happen. Reports are produced. Decisions are documented. KPIs are available. And yet the project does not really move forward. That is where the Hidden Catch Audit starts: it does not simply look for obvious deviations. It looks for the hidden catch — the problem that has become embedded in the way the project operates and therefore no longer appears to be a problem to the people inside it.

Available to organisations worldwide. Remote delivery worldwide; on-site engagements by arrangement. Based near Munich, Germany.

What is the Hidden Catch Audit?

The Hidden Catch Audit is a diagnostic format developed by Thomas Martin to identify hidden risks, flawed decisions and embedded inefficiencies in ongoing projects, business processes and complex systems.

“Hidden Catch Audit” is the English name for the diagnostic approach developed by Thomas Martin under the German term “Pferdefuß-Audit”. In German, a Pferdefuß (literally the devil’s hoof) is the hidden catch in something that looks fine at first sight. Both names describe the same format — the German original and its English positioning for international, English-speaking decision-makers.

At its core is one simple question:

What is actually preventing this project from working the way it should?

The point is not to document as many deviations as possible. It is to identify the one relationship that actually matters — a flawed decision that keeps triggering new follow-up decisions, a governance structure that slows decisions down instead of creating the safety it was meant to provide, a communication path that filters or distorts information, or a solution that formally works but systematically creates new work.

An audit is finished when the catch has been found — not when the clock runs out.

What is the “hidden catch”?

In English, “the catch” is the hidden drawback in something that looks fine at first sight — the part nobody mentions until it costs time or money. For this audit, the term stands for one specific thing: the hidden catch that has become normal to the people inside the project.

“Hidden Catch Audit” is not an established industry term. It is a deliberately distinctive name for an independent consulting format by Thomas Martin — not a software tool, and not a borrowed piece of standard audit vocabulary.

What does the Hidden Catch Audit examine?

The Hidden Catch Audit does not just look at individual processes or documents. What matters are the relationships through which a project works — or blocks itself.

Governance and decision-making

Who can actually make which decisions? Where do approval loops arise? Which decisions are unnecessarily escalated?

Communication and information flows

Who receives which information? Where is information delayed, filtered or processed repeatedly?

Roles and responsibilities

Are responsibility and decision authority actually aligned?

Hidden feedback loops

Which measures create the very problems they were intended to solve? Where does an undesirable situation reinforce itself?

Embedded inefficiencies

Which activities continue simply because they have always been performed?

Technical and organizational dependencies

Which dependencies actually determine the project? Which of them remain invisible in the official project structure?

Hidden Catch Audit vs. a conventional project audit

Conventional Project AuditHidden Catch Audit
Checks defined criteriaSearches for the overlooked problem
Focuses on complianceFocuses on actual effectiveness
Reviews processes and requirementsExamines relationships and feedback loops
Documents deviationsIdentifies the critical catch
May produce extensive findingsPrioritizes the relevant finding
Audit reportFinding + concrete options for action

The Hidden Catch Audit does not replace compliance, quality or other mandatory audits. It answers a different question.

When does a Hidden Catch Audit make sense?

Typical situations:

  • business processes with recurring rework, media breaks or unclear handoffs
  • stalled IT projects
  • recurring delays
  • increasing escalations
  • lengthy decision-making processes
  • conflicting stakeholder objectives
  • projects where additional resources do not produce the expected results
  • complex transformation projects
  • projects approaching a major investment or strategic decision
  • situations where management receives extensive reporting but lacks a convincing explanation of what is actually happening

A Hidden Catch Audit is particularly useful when a project should be working – but isn't.

What is the result?

The audit does not deliver as much documentation as possible. It delivers:

1. The catch — the critical underlying problem
2. The mechanism — why it occurs
3. The impact — on time, cost, quality and project success
4. The options — what can actually be changed
5. The priority — what needs to happen first

The value of the audit lies not in the number of deviations found, but in the quality of the explanation.

Two weeks. Fixed scope. Clear findings.

Fixed price. Fixed scope. Two weeks. No day rate, no open-ended clock — the fixed price is set from scope and target during the initial call. The offer is addressed exclusively to businesses, public bodies and freelancers under German commercial-client rules (§ 14 BGB).

An example

A complex project may initially look like a resource problem. More people are assigned. The situation improves temporarily. Then more coordination is required. Additional approval steps are introduced. More meetings are scheduled. The project becomes even more complex instead of faster.

The actual catch may not be a lack of resources at all. It may be the structure of decision-making and communication. Once that relationship is identified, the solution changes fundamentally — not more people, but a change to the system.

Why “Hidden Catch”?

“The catch” is the natural English idiom for what the German “Pferdefuß” means: the hidden drawback that trips a project up without anyone planning for it — not a literal translation. That is exactly what this audit looks for: a structure, a habit or an earlier decision that has quietly become part of how the project operates, and is therefore no longer recognized as the cause. The name is deliberately distinctive and functions as an independent product name, not as a claim to an established methodology.

Who provides the Hidden Catch Audit?

The Hidden Catch Audit is a diagnostic format developed and provided by Thomas Martin.

Thomas Martin, Dipl.-Ing. (Univ.), PMP®, is a project manager and IT consultant with experience in complex projects and transformation environments. The Hidden Catch Audit is not a generally established international standard method and not an ISO, DIN or PMI-certified audit format — it is an independent diagnostic format he developed himself, part of the same body of thinking as the PM rulebook and the HAL Test on this portal.

Request a Hidden Catch Audit →

Frequently Asked Questions

Can the audit examine a business process?

Yes. A defined business process or subprocess can be audited for hidden blockers, rework, media breaks and unclear handoffs. The two-week engagement covers the scope agreed in the initial call; implementation is optional and commissioned separately.

What is the Hidden Catch Audit?

The Hidden Catch Audit is a diagnostic format developed by Thomas Martin to identify hidden risks, flawed decisions and embedded inefficiencies in ongoing projects, business processes and complex systems. It is the English name for the approach he developed under the German term “Pferdefuß-Audit”.

Who provides the Hidden Catch Audit?

The Hidden Catch Audit is a diagnostic format developed and provided by Thomas Martin, a project manager and IT consultant with experience in complex projects and transformation environments.

Is the Hidden Catch Audit a conventional project audit?

No. A conventional audit checks defined criteria and documents deviations from requirements. The Hidden Catch Audit instead searches for the overlooked, decisive relationship and prioritizes one finding over an extensive list of deviations. It does not replace compliance, quality or other mandatory audits — it answers a different question.

How long does it take?

Two weeks, at a fixed scope and fixed price.

What is the result?

Not an extensive document, but five concrete elements: the catch, the mechanism behind it, its impact, the options for action, and the priority.

Which projects are suitable?

Particularly suitable for stalled IT projects, complex transformation projects, recurring delays, lengthy decision-making processes, increasing escalations, conflicting stakeholder objectives, and situations approaching a major investment or strategic decision.

Does a project have to be failing before an audit makes sense?

No. A Hidden Catch Audit is aimed exactly at the situation where a project should be working — processes run, reports are produced, KPIs are available — but progress stalls regardless. Nothing has to be failing yet for the analysis to be worthwhile.

An audit is finished when the catch has been found.

Request a Hidden Catch Audit

No obligation. Details — fixed price, scope and timing — are clarified in the initial call.