What I do
I take on work that is important, difficult to explain, and hard to finish inside one team.
Sometimes the first need is diagnosis. Sometimes the result is already clear and the work needs an owner. Sometimes the organization needs execution leadership, or ongoing fractional IT or security leadership.
I use the same operating method in each case. I do not force every problem into the same service.
How I work
- Start with the required result.
- Establish what is actually true.
- Follow the work across teams and vendors.
- Find what keeps causing it, not who to blame.
- Make the calls and unresolved items explicit.
- Produce usable artifacts.
- Hand the work back with clear ownership.
Durability matters. I once rejected an $8.5M single-year infrastructure proposal that had no requirements or business alignment and rebuilt it from inventory, stakeholder direction, current-to-future-state mapping, and TCO modeling.
The resulting 36 to 48 month roadmap received CFO endorsement, redirected already-approved spend, anchored the next two budget cycles, and was extended across four IT functions after I had left.