Origin Story
Twenty years of service, and the framework it produced
The Consulting C™ was not designed in a business school. It was assembled over two decades in an organization where planning failures have consequences that arrive the same day.
- Service
- United States Coast Guard, active duty
- Length of service
- 20+ years
- Retirement
- November 1, 2026
- Doctrinal foundation
- NIMS / Incident Command System
- Incident action planning, management by objectives, span of control, unity of command
- Core values
- Honor, Respect, Devotion to Duty
- The commitment half of the Success Model
- Frameworks authored
- The Consulting C™ and the Success Model
- In progress
- The Consulting C™ — a book on the framework
The service
I spent more than twenty years on active duty in the United States Coast Guard. I retire on November 1, 2026.
The Coast Guard is a small service with an unusually broad portfolio. On any given day it is conducting search and rescue, enforcing law at sea, responding to environmental disaster, maintaining the aids to navigation that commercial shipping depends on, and standing by for whatever arrives without warning. The service operates on the assumption that resources will be insufficient, information will be incomplete, and the situation will change while you are responding to it. Its motto is Semper Paratus — always ready — and the operative word is always, because readiness that depends on favorable conditions is not readiness.
What that environment produces, over twenty years, is a specific kind of professional instinct. You stop believing plans that depend on everything going well. You develop an intolerance for objectives that cannot be measured. You learn that the quality of an operation is determined long before execution, in how carefully the situation was understood and how honestly the constraints were named. And you learn that the difference between a unit that performs and one that does not is almost never talent. It is discipline applied to process, held consistently, especially when nobody is watching.
[VERIFY] Specific assignments, units, cutters, ratings, rank, and awards are intentionally omitted from this account pending review. This section is written so those details can be added without restructuring the narrative.
Learning to plan under pressure
Somewhere in the middle of that career, the National Incident Management System and its Incident Command System stopped being a qualification I had earned and became the way I thought about problems.
ICS is the management doctrine that governs how the United States responds to incidents, from a single-vehicle accident to a hurricane requiring the coordination of thousands of responders across dozens of agencies. Its central achievement is that it allows people who have never worked together to coordinate effectively within hours, because everyone is operating from the same structure, the same vocabulary, and the same planning sequence.
The sequence is the part that stayed with me. Incident action planning is drawn as a letter P. The leg of the P is walked once at the beginning of an incident: initial assessment, briefings, and the first set of objectives. FEMA's own doctrine describes the incident briefing as the moment that marks the transition from reactive to proactive incident management — a single line that describes something profound. Nothing about the incident has changed at that moment. What changes is the posture of the people managing it. They stop responding to events and start directing them.
The loop at the top of the P is the part that repeats. Every operational period, the objectives are reviewed and validated or revised, tactics are developed, a plan is written and approved, and the plan is briefed and executed. Then it happens again, informed by what the last period actually produced. Not a linear march to completion — a governed cycle that improves its own inputs.
I ran that cycle, in various forms and at various scales, for two decades. And at some point I noticed that the failures I was seeing in operations were the same failures I was seeing everywhere else, including in my own life.
The pattern that showed up everywhere
People who were entirely capable would set a goal, plan it poorly, execute it enthusiastically for two weeks, and abandon it. Organizations would identify a problem, commission a solution, implement it, and discover that the original problem was still there because it had never been the actual problem. Teams would work extraordinarily hard against objectives nobody could connect to an outcome.
None of these are effort failures. They are process failures, and they are the same process failures that ICS was designed to prevent — with a critical difference. In an incident, the consequence of skipping the assessment step arrives that day, visibly, and it is attributed to the omission. In business and in personal life, the consequence arrives in six months, diffusely, and gets attributed to something else. Discipline. Culture. Willpower. Market conditions. Anything except the fact that nobody ever established what was actually true before building a plan on top of it.
That asymmetry is why business and personal planning fail so much more often than incident planning does, despite operating under vastly easier conditions. The feedback is too slow and too ambiguous to correct the behavior.
The obvious question followed: what if the sequence that works under the hardest conditions were applied to the ordinary ones? Not the terminology, not the organizational chart, not the command structure — the sequence. Understand the situation before setting objectives. Set objectives before building the plan. Commit resources only after the plan exists. Report honestly, review formally, correct on evidence. Repeat.
Applying it to myself first
I did not develop this framework as a product. I developed it because I needed it.
By my early forties I was carrying the accumulated cost of a career spent in service to everything except my own condition. A sedentary billet. A two-hour daily commute. A former athlete's self-image attached to a body that no longer resembled it, and a decade of sincere, well-intentioned, uniformly failed attempts to change that. Every attempt followed an identical arc: a triggering event, an ambitious plan built during peak motivation, excellent adherence for eleven to fourteen days, one disrupted week, and quiet abandonment. Then months of low-grade guilt until the next trigger.
What finally broke the pattern was applying the discipline I had used professionally for twenty years to my own situation. I established the actual trigger, which turned out not to be health at all — it was a retirement date and an identity with an expiration date attached to it. I documented what was verifiably true, including facts I had been routing around: available training days, a prior abdominal mesh repair, cervical arthritis, a medication protocol, and a genuinely unflattering baseline fitness test. I built a plan for a four-to-six week block rather than a year, with a small number of measurable objectives and written rules for what happens on a bad week. I put it in writing. I started inside twenty-four hours instead of on a future Monday. And I reported weekly, honestly, including the weeks that went badly.
It held. Not because I had finally located sufficient willpower, but because the plan was built for the version of me that exists on a Tuesday in week five, rather than the version that exists in the first hour of enthusiasm.
That program is still running. It is documented as a Motivational Action Plan, structured in blocks, with weekly SITREPs and block-end After Action Reviews — the same instruments this platform now provides to clients. I am not offering a method I have theorized about. I am offering the one I run on myself, and I will tell you where it is currently uncomfortable.
The framework takes shape
Formalizing it came later, and it came from a specific realization: the sequence I was using had six discrete phases, each answering a distinct question, and each producing an artifact the next phase required. When I named them, every one began with the same letter.
Clarify. Comprehend. Construct. Contract. Commit. Commence.
The naming was not a branding exercise; it was a discovery, and the shape it produced turned out to encode the most important structural feature of the method. Drawn as a C, the framework opens rather than closing. That opening is the Decision Point, and it exists because the framework is not a linear process that terminates in success. Clarify and Comprehend are walked once, like the leg of the Planning P. The remaining four phases cycle, block after block, each iteration starting from a better position than the last. An engagement does not finish at Commence. It cycles there until the client no longer needs me to hold the discipline in place.
Alongside the framework, a second thing needed articulating: not what to do, but why it works. That became the Success Model. Success requires both vision and commitment, and neither substitutes for the other. Vision has three components — direction, motivation, and focus. Commitment has three as well, and those three I did not have to invent. They had been issued to me on my first day of recruit training and reinforced for the following twenty years: Honor, Respect, and Devotion to Duty.
Those are the Coast Guard's core values. What a long career teaches you is that they are not a list of admirable traits on a wall. They are the working components of commitment itself, and they fail multiplicatively. Integrity and duty without respect for the people around you burns out your team and then you. Respect and duty without integrity cannot be relied on when unobserved, which is nearly always. Honor and respect without devotion to duty performs beautifully while motivated and vanishes the moment the work turns tedious.
The transition
I retire on November 1, 2026, and I am deliberate about what that means and does not mean.
It does not mean I am a business consultant who happens to have served. The claim I am making is narrower and, I think, more useful: I spent two decades in an organization that treats planning as an operational discipline with consequences, and I know how to apply that discipline to problems that are not emergencies. That is a real and transferable skill, and it is uncommon in a market where most frameworks are derived from case studies of companies that succeeded — a selection-biased evidence base that tells you what winners did without telling you what everyone who did the same thing and failed also did.
I am also clear-eyed about what military experience does not automatically confer. Rank does not transfer. Authority does not transfer. In the Coast Guard, when I directed something, it happened, because the structure guaranteed it. A civilian client can dismiss every recommendation I make and hire someone more agreeable. That constraint is healthy. It means the method has to earn its authority on the merits, every engagement, which is a considerably higher bar than a chain of command.
The transition I am making is the same one many of my clients are making, in different clothing: leaving an identity that came with an institution and building one that does not. I understand that problem from the inside, which is a large part of why I do this work.
How I work
I will tell you the uncomfortable thing. That obligation is written into the Mutual Commitment Agreement every client signs, because a consultant who protects the relationship at the expense of the truth is charging you for company. If your plan is not working, you will hear it from me in plain language, with the evidence, and with a proposed correction.
I will also decline engagements. If Clarify cannot produce a real trigger, or Comprehend reveals constraints that make the objective unreachable within the horizon you have, I will say so in the first month rather than discovering it in the fourth. That is the cheapest possible time to find out, and it is the point at which most prospective clients are turned away — correctly.
I do not do open-ended coaching relationships. The purpose of an engagement is to install a battle rhythm you can run without me: your own reporting discipline, your own honesty in review, your own willingness to correct a plan rather than defend it. When that is in place, we graduate. Clients return when a new trigger fires, which is the right reason to return.
And I stay inside my lane. I am not a physician, an attorney, an accountant, or a therapist. When an engagement requires clearance or expertise I do not have, the plan gates on it and waits. It does not route around it.
Sources
What this method rests on
Every doctrinal claim on this site traces to public source material. The Incident Command System and the incident action planning process are documented by FEMA's Emergency Management Institute. The Coast Guard's core values are published by the service. None of it is proprietary, and none of it is being represented as something I invented.
What is mine is the translation: the six-phase sequence, the Motivational Action Plan structure, the Success Model's articulation of vision and commitment, and the practitioner instruments that make it teachable. That translation is what The Consulting C™ is.
CROS3 Consulting is a private company and part of Crose Holdings. References to Coast Guard service and to public federal doctrine describe the professional experience and source material behind this methodology. They do not imply endorsement by the U.S. Coast Guard, the Department of Homeland Security, FEMA, or any government agency.
Start Here
A conversation, not a pitch
Thirty to forty-five minutes at no cost. If this is not the right method for your situation, I will tell you that and point you toward what would actually help.
CROS3 Consulting is a private practice. References to Ryan Crose's U.S. Coast Guard service and public federal doctrine describe professional background only; they do not imply endorsement by the U.S. Coast Guard, the Department of Homeland Security, FEMA, or any government agency.