Cadre, risk assessments, and accountability — three habits that transfer directly into TPM work.
Three habits that transferred
Serving as a Chemical Officer with the Ohio Army National Guard is a different rhythm from telecom program work — one weekend a month, two weeks a year, and a small unit accountable for people, equipment, and readiness. But three habits from that world map directly onto industry program leadership, and I use them every week.
1. Cadre before initiative
The Army never lets you skip cadre. Before any collective training event, you certify the trainers first. The reason is simple: whatever the trainer half-knows, the unit will half-learn, at scale.
In program work, the equivalent is your leads. Before you launch a new process, an intake form, or a review cadence, you certify the leads who will run it. Every hour spent on lead alignment pays back tenfold in reduced downstream noise.
2. Risk assessment as a document, not a feeling
Every mission gets a written risk assessment — hazards identified, controls named, residual risk rated, and a named approver at a specific level. It sounds bureaucratic; it's the opposite. It forces the team to be honest about what could go wrong and who is accepting that risk on behalf of the organization.
The industry version I run: for any material program decision, a one-page pre-mortem with hazards, mitigations, residual risk, and the named approver. If nobody wants to sign as the approver, that answer itself is the decision.
3. Accountability as a daily culture
In the Guard, accountability of $2M+ in vehicles, PPE, and CBRN equipment isn't a quarterly inspection — it's a daily hand-receipt culture. Someone signs for something. When it moves, the signature moves.
The same principle stops program work from drifting. Every deliverable has a single named owner. When it moves, the ownership moves — visibly, with a timestamp. Diffuse ownership is the root cause of most missed program milestones I've ever seen.
The transferable core
Cadre, honest risk documentation, and single-name accountability aren't military ideas. They're just enforced more visibly there. Bring them into a corporate program and you shorten the distance between decision and execution — which is really the only thing a TPM is paid to do.