Impact
Outcomes before chronology.
My experience makes the most sense when it is organized by what changed: people became ready, programs became repeatable, technical work became understandable, and leaders had better information.
Selected figures are rounded and presented at a sanitized level for public review.
Leadership
Make the standard clear. Make the support real.
Leadership is not only assigning work. It is creating the conditions where people understand the mission, see the standard, receive useful feedback, and can say when the system is failing them.
Readiness coordination
Aligned personnel, tasks, training requirements, instructors, and leadership expectations in high-accountability environments.
Decision communication
Translated technical findings and program status into concise briefings that supported action rather than simply reporting activity.
Performance accountability
Used qualification standards, progress tracking, and feedback loops to make readiness visible and improvement concrete.
Program development
Turn requirements into an operating system.
Programs work when roles, workflows, evidence, metrics, and review cycles reinforce one another.
Define
Clarify the outcome, decision rights, evidence standard, and what “ready” or “done” actually means.
Operationalize
Build the workflow, resources, documentation, tooling, and support structure around real constraints.
Improve
Track blockers and outcomes, learn from failures, and update the system without hiding the version history.
Technical operations
Technical credibility, translated.
More than 2,500 hours of network analysis inform how I think about evidence, uncertainty, adversary behavior, vulnerabilities, and operational risk.
Observe
Find the signal
Analyze systems and activity with attention to context, evidence quality, and what is still unknown.
Explain
Make the consequence visible
Connect technical facts to mission, business, privacy, resilience, and leadership decisions.
Act
Build the response path
Define ownership, priorities, escalation, remediation, and the feedback needed to know whether the risk actually changed.
Training & communication
Teaching is not a side skill. It is how change becomes durable.
I love the moment when a complicated idea clicks for someone. Good instruction respects the learner, reveals the structure beneath the complexity, and gives people a safe way to practice before the stakes are real.
See the training case studyWritten analysis
Governance research turned into a practical modernization model.
The PAPER approach translates a broad cybersecurity challenge into a cycle leaders can plan, assess, produce, execute, and reevaluate.
Explore the paperGRC · AI governance · human risk
An Integrated Approach to Cybersecurity Governance
Graduate research grounded in NIST, CISA, legal obligations, industry research, and the Colonial Pipeline case.