Operational Troubleshooting and Recovery

What gets done

• Finding the actual problem. Usually it is not the one the team is arguing about, and it is rarely only technical.
• Separating what is broken from what was never built: a missing procedure, an undefined authority, an assumption nobody wrote down.
• Prioritising corrective action by what unblocks the most, so the programme moves before everything is perfect.
• Rebuilding the processes that have failed, in a form the team will actually use, and being there while they use them the first time.
• Re-establishing confidence with the people who have lost it - a client, an approver, a harbour master, or the operators themselves.
• A clear position on what is safe to resume, what is not yet, and what has to be true before it is.

What you get

Someone with no stake in how it got here, who has stood in the middle of a programme that was not working before. You get a straight answer quickly, and the work to fix it rather than a report recommending that you fix it.

How it runs

Fast. Days rather than weeks to the first read, then whatever the fix takes. On site where being in the room matters, which in this kind of work it usually does.

If the honest answer is that the programme needs to stop rather than be recovered, you will be told that too.