Create clarity before velocity
Define the problem, constraints, decision owner, dependencies, and evidence required before accelerating execution.
Leadership profile
Technical depth is most useful when it improves the decision.
My career has moved from front-line support through systems administration, architecture, Tier 3 engineering, project delivery, and municipal IT leadership. Each role widened the system I was accountable for.
Download résuméHow I lead
Close enough to the work to ask better questions.
I am most effective where infrastructure, delivery, risk, people, and operations meet. I bring a senior technical perspective into planning while keeping decisions understandable to the people who own the outcome.
Translate across the room
Connect executive priorities, user impact, technical reality, and delivery tradeoffs without flattening the important details.
Design for operations
Include security, recovery, documentation, support, and adoption in the work instead of handing them to someone else after launch.
Raise the team around the system
Turn escalations into reusable knowledge, give people useful context, and make ownership visible without creating blame.
Leadership scope
Strategy that remains connected to execution.
- Infrastructure and cloud operations
- Incident escalation and root cause analysis
- Technology projects and implementations
- Governance, security policy, compliance, and risk
- Documentation, mentoring, and operational adoption