01FOUNDER · PROGRAM DESIGN
Building Moonroot Sanctum, a conservation and community initiative
I founded Moonroot Sanctum to explore a land-based conservation and community venture. I translated the concept into property research, field diligence, program designs, financial scenarios, and a working operating plan. Stakeholder input and evidence shaped the decisions, including rejecting a preferred property when field conditions contradicted the assumptions behind its apparent fit.
Read the full case study
Problem and ownership
I needed to test whether a conservation and community concept could become a workable venture. I owned research, property assessment, service and operating-model design, financial scenarios, and the decision process for pursuing or rejecting options.
Decisions and adaptations
A preferred Bedford property initially appeared to fit the concept and price. Field diligence challenged that assumption: the creek was not spring-fed as expected, and listed acreage did not match surveyed acreage. I rejected the opportunity rather than adjusting the story to preserve a favored purchase.
Outcome and handoff
The result is a working venture plan and decision system that can respond to new evidence. Property research, models, and program designs support development choices; they are distinct from an operating retreat center or completed conservation outcomes.
02PROJECT DELIVERY · LOGISTICS · RISK MANAGEMENT
Restoring a hazardous training range through cradle-to-grave project delivery
I led a 30-day range-restoration project with a 30-person team, clearing 782 acres and 21 road miles, removing 112 hazardous items, and restoring 48 targets. I coordinated scope, resources, weather constraints, and maintenance handoffs from planning through customer acceptance. The completed work returned training infrastructure to use and enabled 215 training flight missions.
Read the full case study
Problem and ownership
I surveyed the range with the maintenance lead before execution so we could identify which targets needed rebuilding and prepare materials. Clearance prioritized roads and immediate target areas to unlock maintenance work before expanding into surrounding sectors.
Decisions and adaptations
Weather affected productivity and sequencing. In inert training areas, I authorized sector-by-sector release so maintenance could work behind the clearance teams. The live range required full clearance before maintenance entered. I personally owned those release decisions.
Outcome and handoff
Team leaders validated field completion; I consolidated their reporting, coordinated customer acceptance with Range Control, and completed formal operational and resource closeout. The restored infrastructure enabled 215 training flight missions.
03PROPOSAL · FUNDING · CONSTRUCTION · ADOPTION
Turning a funded proposal into an enterprise training environment
I researched and wrote a proposal for a realistic training environment, advocated it to senior leaders, and secured $510,000 across two funding sources. I coordinated contractors, managed scope changes, and accepted the completed facility with contracting. The seven-acre site supported 350 local personnel and visiting teams across the Air Force, Marine Corps, and Army.
Read the full case study
Problem and ownership
Existing buildings constrained realistic training. I researched and wrote the proposal with team input, advocated it to leadership, and coordinated two funding sources totaling $510,000. Requirements drew on deployed experience and the needs of multiple response functions.
Decisions and adaptations
Cost growth required scope changes. I worked with contracting and vendors to remove selected vendor-provided elements and shift work to internal civil engineering support so the project could stay within budget.
Outcome and handoff
The contracting representative and I accepted the completed work. EOD retained access control, and the environment supported local exercises, broader training events, and visiting teams across service branches. The durable output was a usable training capability with an operating owner.
04TEAM DEVELOPMENT · COACHING · PERFORMANCE
Bringing leadership and rebuilding a stalled team-leader pipeline
I rebuilt a stalled team-leader development pipeline around clearer scheduling, practical instruction, and coaching matched to individual readiness. The program combined 400 hours of instruction and 86 hands-on exercises to qualify six new leaders and reduce completion time by 40%. Training records, qualified supervisors, and distributed responsibility helped the team sustain the improvement through frequent turnover.
Read the full case study
Problem and ownership
Frequent personnel turnover made continuity difficult. I forecast arrivals and departures, cleaned training records, and rebuilt scheduling so new members could begin promptly. I also looked beneath poor-performer labels for gaps in mentoring, task fit, or team dynamics.
Decisions and adaptations
I maintained common standards while varying support by readiness: autonomy for capable performers, clearer structure where needed, and explicit accountability for underperformance. Emerging leaders received meaningful project ownership while experienced supervisors supported them.
Outcome and handoff
The program combined practical exercises, direct coaching, qualified team leaders, records, and replacement training. Six new leaders qualified and completion time fell by 40%, while responsibility became less dependent on one individual.
05TECHNOLOGY IMPLEMENTATION · CHANGE MANAGEMENT
Implementing a shared emergency-response platform to improve situational awareness
I identified a recurring communication problem in emergency-response exercises and led the operational implementation of ATAK with the Air Force Research Laboratory. I coordinated requirements, funding, pilots, training, and adoption across response functions. Live positions and shared hazard maps improved the operating picture, while a practical handoff gave Emergency Management the capability to continue the work.
Read the full case study
Problem and ownership
Repeated after-action reviews called for better communication without identifying a concrete solution. Separate reporting, missed radio updates, and manual map reconstruction fragmented the picture. I owned operational requirements, funding, stakeholder coordination, pilots, adoption, and handoff; the research laboratory provided technical configuration and development support.
Decisions and adaptations
I built support within EOD, then brought in fire, emergency management, security forces, and senior leaders. Testing progressed from work-center to unit and wing exercises. Field use revealed that gloves made touchscreens difficult; styluses resolved that practical barrier. Manual reporting remained a trained fallback.
Outcome and handoff
The effort took approximately eight months overall, including about two months from funding approval to full implementation. User feedback and exercise evaluation supported the capability’s usefulness without a claimed percentage improvement. Handoff to Emergency Management included training, documentation, access, processes, and technical-contact continuity.
06PARTNERSHIP · TRAINING · CULTURAL ALIGNMENT
Building a durable cross-cultural response partnership
I developed a U.S.–Republic of Korea Air Force partnership from limited team-level contact into reciprocal learning and coordinated response. Joint practice, mixed teams, and practical language guides addressed communication barriers. I also expanded and routed the bilateral operating agreement, helping turn trusted relationships into recurring collaboration with clearer permissions, shared expectations, and continuity beyond my assignment.
Read the full case study
Problem and ownership
I began with shared meals, reciprocal observation, and repeated joint practice. Korean and U.S. teams brought different strengths and learned from one another as peer experts. Mixed teams co-developed practical language guides rather than depending on interpreters being available for every response.
Decisions and adaptations
I substantially rewrote and expanded the existing bilateral memorandum of understanding across training, range clearance, emergency response, access, equipment use, and exercise integration. I managed Korean and English routing through legal, Public Affairs, and both command chains. The extensive rewrite and repeated language revisions took approximately 18 months.
Outcome and handoff
The approved agreement enabled joint off-base emergency responses, reciprocal aircraft-response support, and range-clearance operations. I treated the partnership as a continuing operating standard and handed it into relationships already established below the senior-leader level. The agreement and timeline reflect my firsthand reconstruction.
07QUALITY ASSURANCE · READINESS · CONTINUOUS IMPROVEMENT
Leading readiness evaluations and quality improvement
I led EOD readiness evaluation and co-led civil engineering evaluation, turning readiness questions into observable objectives and realistic tests. Across six exercises, 23 objectives, and seven discrepancies, I connected findings to corrective action and retesting. Three management-control tools and 17 checklists provided an ongoing quality layer so leaders could assess whether gaps had actually closed.
Read the full case study
Problem and ownership
I translated readiness questions into observable objectives and designed conditions capable of exposing known or suspected weaknesses. The purpose was to learn whether procedures remained workable under realistic constraints, rather than simply repeat routine responses.
Decisions and adaptations
Evaluators’ findings were consolidated into documented issues and recommendations. The cycle moved from after-action review to corrective action, retraining or process change, and retesting. A corrective action was not considered sufficient merely because it had been recorded; unresolved gaps returned in later exercises.
Outcome and handoff
Three management-control tools and 17 functional-area checklists complemented live evaluations between exercises. Together, they connected ongoing controls with demonstrated performance and gave leaders evidence of whether gaps had actually closed.
08PROCEDURE VALIDATION · TECHNICAL REVIEW
Validating high-consequence procedures with the Department of Energy
I served as the local point of contact for a Department of Energy procedure-validation effort involving approximately 12 participants and two systems. We exercised 85 proficiency tasks, documented 57 deficiencies, and reconciled operational findings with procedural controls. The work authenticated response procedures and contributed to their first major update in 20 years.
Read the full case study
Problem and ownership
I served as the local point of contact with DOE, selected participating teams, and built an exercise plan that we refined together. Full operational execution let us examine the procedures from start to finish rather than rely on desk review alone.
Decisions and adaptations
Execution and after-action review exposed sequencing improvements alongside discrepancies. I worked through differences between operational usability and strict procedural control with DOE, which retained final publication authority. The 57 deficiencies included known issues and newly discovered problems.
Outcome and handoff
Local completion meant exercising required tasks and documenting findings. Publication changes were a later outcome, with updates occurring within roughly a year according to my reconstruction. The work contributed to the first major response-procedure update in 20 years.
09EMERGENCY RESPONSE · DECISION-MAKING UNDER UNCERTAINTY
Leading a high-stakes emergency response under uncertainty
During a time-sensitive convoy mission, an unverified report raised concern about a possible explosive hazard. When the first suspected object did not support the report, I reassessed the underlying threat and identified a separate concealed hazard. I balanced safety, evidence, time, and route value, communicated recommendations, and required layered verification before releasing the route.
Read the full case study
Problem and ownership
An unfamiliar source provided potentially useful but unverified information. When the first suspected object did not support the report, I challenged the conclusion that there was no threat and reassessed the underlying problem.
Decisions and adaptations
I owned the EOD-specific assessment and release decisions inside a larger mission commanded by an Army platoon leader. I balanced safety, time, evidence preservation, and route value, then communicated findings and recommendations to the supported leader.
Outcome and handoff
Layered verification preceded route release. Recoverable evidence and formal reporting supported broader analysis and learning. The transferable method is to test assumptions, adapt decisively as evidence changes, and verify before returning a system to operation.
10USER RESEARCH · REQUIREMENTS · TECHNOLOGY EVALUATION
Testing robotic platforms against real user needs
As a field-user representative, I helped evaluate roughly 10 robotic platforms for enterprise acquisition. Standardized tasks and realistic scenarios exposed usability, reliability, and operational tradeoffs that controlled benchmarks could miss. I translated operator experience into scoring and recommendations, helped challenge requirements, and contributed to a ranked shortlist while acquisition stakeholders retained the final procurement decision.
Read the full case study
Problem and ownership
I represented Air Mobility Command’s field users alongside other operators, engineers, acquisition stakeholders, AFCEC, and vendors. The objective was a ranked shortlist; I contributed evaluation and recommendations, while the acquisition organization retained final procurement authority.
Decisions and adaptations
Standardized tasks provided a common comparison. Open-ended scenarios tested whether performance held up under realistic use. Evaluation considered setup burden, interface usability, mobility, reliability, environmental performance, cameras, communications, transportability, and operator workload.
Outcome and handoff
Field evidence changed how some requirements were weighted: a rigid threshold could exclude a platform that performed better overall. Scoring, discussions, after-action reviews, and written recommendations carried user feedback to engineers, vendors, and program stakeholders. The result was better-informed selection criteria and a ranked shortlist, rather than a procurement decision owned by me.
11STAKEHOLDER FACILITATION · OPERATING MODEL · PARTNERSHIP
Building recurring collaboration with FBI and local response partners
I initiated a partnership with FBI personnel and a local bomb squad, then designed four comparative scenarios to reveal differences in procedures, communications, jurisdiction, and risk judgments. I facilitated learning among peer experts and carried findings into shared response practices. The effort developed into recurring collaboration with clearer escalation, stronger evidence handling, and more consistent expectations.
Read the full case study
Problem and ownership
Peer organizations could converge on the same incident while using different procedures and authorities. I owned initiation, partner coordination, scenario design, scheduling, safety, resources, evaluator structure, execution, and after-action review.
Decisions and adaptations
Each organization initially used its normal approach while the others observed. That made differences in evidence handling, equipment, jurisdiction, escalation, and risk judgments visible. I facilitated learning among experts and incorporated stronger partner practices rather than assume our approach was always correct.
Outcome and handoff
Findings informed call sheets, procedures, checklists, agreements, and follow-on training. The partnership became recurring—approximately quarterly with the local bomb squad and semiannual with FBI participation according to my reconstruction—with clearer communication and shared expectations for joint response.
12PROOF OF CONCEPT · CROSS-FUNCTIONAL DELIVERY · ADOPTION
Turning an airfield-recovery concept into a usable local capability
I planned and executed a local airfield-recovery proof of concept to test whether a new approach could reduce a bottleneck for follow-on repair teams. I coordinated safety planning, resources, multiple work centers, and Korean partners under realistic constraints. Practical adaptations supported execution, and the results moved into recurring local training and operating procedures.
Read the full case study
Problem and ownership
The existing recovery approach created a bottleneck before follow-on repair teams could restore damaged airfield surfaces. I owned formal safety planning, approvals, resources, sequencing, and execution across civil engineering work centers, with Korean partners participating in planning and integration.
Decisions and adaptations
The evaluation considered recovery speed, staffing, equipment, safety, repeatability, training burden, and downstream repair needs. Heat, fatigue, protective equipment, and language constraints shaped the execution plan. Planned team rotations helped manage the human-performance limits of realistic testing.
Outcome and handoff
The approach moved into local standard training and operating procedures; later exercises practiced it without recreating the original live test. This was separate from the enterprise Guam exercise. My firsthand account also describes wider command-level uptake, but the local test and recurring local adoption are the clearest bounded outcomes.
13PEOPLE LEADERSHIP · COACHING · SUCCESSION
Developing people who can own the work
Across operational leadership, temporary First Sergeant duties, and resiliency training, I combined clear expectations with individual coaching and meaningful responsibility. I looked beneath performance labels for training, task-fit, or team problems, then adjusted support to readiness. Delegation, qualified people, and practical succession helped teams own the work while maintaining accountability and supporting one another.
Read the full case study
Problem and ownership
When someone struggled, I examined training, mentoring, task fit, and team relationships before accepting a poor-performer reputation. I paired people deliberately, coached directly, and allowed manageable mistakes in training followed by constructive debriefs.
Decisions and adaptations
I adjusted autonomy and structure to readiness and gave emerging leaders projects they could own with experienced support. Succession relied on qualified people, procedures, records, and distributed authority rather than a single expert.
Outcome and handoff
Temporary First Sergeant service broadened my work to emergency travel, quarantine support, and personal check-ins during COVID restrictions. In resiliency training, I coached facilitators toward more meaningful delivery. Wounded Warrior Ambassador engagements added peer advocacy and communication with both junior personnel and senior leaders.
14AI WORKFLOWS · INFORMATION GOVERNANCE · DECISION SUPPORT
Building an AI-assisted workflow with human review
For Moonroot and my founder-led work, I built AI-assisted research and information workflows with source checks, structured handoffs, and human review. Actual failures informed decision logs, review gates, and recovery rules. The resulting operating system supports research, scenario analysis, and reusable evidence while keeping authority clear as information moves between tools and changes over time.
Read the full case study
Problem and ownership
Research, models, drafts, and decisions could diverge as work moved between tools. Actual failures made the need concrete: preserve source provenance, distinguish current authority from derived material, and make handoffs and changes traceable.
Decisions and adaptations
I used standardized briefs, project state, decision and activity logs, structured handoffs, model routing, fallback rules, and explicit review gates. Information states separated intake, review, canonical material, publishing, and archive.
Outcome and handoff
The workflow supports research synthesis, scenario analysis, and reusable evidence with source checks and human approval at decision points. It remains a founder-led operating system that requires maintenance and correction; its value is in accountable support for real work and recovery when tools fail.
