First, find out
what’s wrong.
We agree what needs fixing before I change anything.
How the work gets done.
TRACE: investigate, agree, implement, hand over.
Trace
Map
Read-only collection in your environment, including dependencies and expected behaviour.
You getCurrent-state map
Reconcile
Compare
Record differences across configurations, outputs and source records, each linked to evidence.
You getEvidence and exceptions
Assess
Prioritise
Separate confirmed findings from suspected causes. Rank the work by impact and risk.
You getFindings and recommendations
Correct
Repair
Agree scope and acceptance criteria. Test each change with a rollback plan in place.
You getTested changes
Embed
Hand over
Deliver the runbook, monitoring and knowledge transfer. Verify the agreed outcome.
You getRunbook and handover
The first three steps are investigation only. I make changes only after you approve a separate project.
Working rules.
Evidence, explicit decisions and named owners.
Configure before coding
Use existing platform features before building something custom.
Keep evidence with you
Read-only collection in your environment. Data and credentials stay there.
Get approval before changing production
An assessment does not authorise changes. Every production change needs approval.
Separate facts from hypotheses
Each finding has an evidence reference and a confidence level.
Agree the work in stages
Investigation, implementation and acceptance are separate decisions.
Leave it maintainable
Code in your repository. Runbooks, owners and handover included.
What stays with you.
Deliverables agreed per project, ready for your team to use.
- Scope and assumptions
- Current-state inventory
- Architecture or dependency map
- Evidence and exception register
- Risk and impact assessment
- Prioritised backlog
- Acceptance criteria
- Implementation in your repository
- Change and rollback plans
- Test results
- Operational runbook
- Ownership register
- Before-and-after measurements
- Knowledge transfer
Scope and boundaries.
Scoped engineering engagements. Your team keeps day-to-day operations.
- No staff augmentation or ticket queue cover
- No 24/7 or on-call service
- No managed service, SOC or NOC
- No penetration testing or compliance certification
- Investigation delivers evidence and recommendations; a fix is not guaranteed
What needs fixing?
Pick what applies, or email me directly. We’ll work out a first step.