The Military Station Was My First Classroom

How growing up inside a military station quietly built everything I know about leading projects, managing operations, and eventually writing my own rulebook.

There are places that shape you before you know you’re being shaped.

For most people, it’s a school corridor, or a grandparent’s kitchen, or a neighbourhood street where the rules were invented by whoever was oldest. For me, it was something altogether different. It was a military station, the kind of place where the grass is always cut to an exact height, where gates are manned by people whose posture makes you instinctively straighten your own, and where the first sounds of morning are not birds, but boots.

I grew up inside that world. And for a long time, I thought it was just normal.

It wasn’t until years later, sitting across a conference table, managing a complex multi-stakeholder project with competing timelines, misaligned teams, and a delivery deadline that wasn’t going to move, that I realised I had been trained for exactly this. Not in any formal classroom. Not by any certification programme, though those came later. But by simply watching, listening, and absorbing everything that happened around me in those years when I didn’t yet have the vocabulary to name what I was learning.

The Station Didn’t Ask If You Were Ready

Military stations have a particular quality that takes time to articulate: they do not adjust themselves to you. You adjust to them.

The schedule is the schedule. The standard is the standard. There is no version of showing up late to a parade and explaining that you were tired. There is no edition of a briefing where it’s acceptable to say you didn’t fully understand the objective but decided to proceed anyway and see what happened.

As a young person living inside that environment, not as a soldier, but as someone embedded in that community by birth and circumstance, you absorb these values through osmosis. You don’t sit down and study them. You simply live inside them until they become the unremarkable backdrop of your entire understanding of how things work.

Discipline, I learned early, is not punishment. It is the infrastructure that allows everything else to function. A well-run military station operates with a kind of quiet efficiency that most organisations spend years and enormous consulting fees trying to replicate. Nobody was having loud meetings about accountability. Accountability was simply the operating standard. You did what you said you would do, by when you said you would do it, to the standard required. Full stop.

I didn’t know at the time that I was watching the foundations of project management being demonstrated to me every single day.

Commanders/Officers Who Didn’t Know They Were Teaching Me

I want to be specific about something, because vague inspiration is cheap.

I watched commanders/Officers run briefings. Not once or twice, repeatedly, across months and years, in different contexts, with different teams, different objectives, different stakes. And what I noticed was not the authority in the room, though there was plenty of it. What I noticed was the structure.

Before any operation, however small, however routine, there was a briefing. Objective stated clearly. Resources confirmed. Roles assigned without ambiguity. Contingencies discussed. Questions invited. Timeline confirmed. Then everyone left knowing exactly what they were doing and why.

No one left that room with a vague mandate to “sort it out.” No one was unclear about what success looked like. No one had to guess who was responsible for what.

I was a kid sitting at the edges of these interactions, sometimes literally, sometimes as a fly on the wall in the way that children in close-knit communities become invisible to adults who know them well enough not to guard their words. I watched those briefings dozens of times. I watched how different commanders ran them, some crisply efficient, some who invited more discussion, some who were stricter, some who had a dryness about them that cut straight to the point.

What they all had in common was this: clarity before execution. Always. Non-negotiably.

Decades later, I would learn the formal language for this, stakeholder alignment, scope definition, RACI matrices, risk monitoring, project charters. But the felt understanding of why these things matter? That was already inside me. It had been placed there, quietly, by people who were just doing their jobs.

The Debrief After Every Mission

One thing the military does that the corporate world has never quite managed to institutionalize with the same seriousness is the debrief.

After every exercise, every operation, every significant event, there was a debrief. What happened? What was supposed to happen. Where they diverged and why. What would change next time. Not as a blame exercise, though there was honest accountability when it was warranted, but as a genuine learning process. A structured attempt to improve the system by examining the last run of it without ego getting in the way.

I sat in on some of these as a young person. I witnessed others secondhand. And even at an age when I couldn’t fully decode what was being discussed, the practice of it lodged somewhere in me, the idea that you don’t just finish something and move on. You examine it. You ask what you learned. You adjust.

When I later ran agile retrospectives in software teams, Hospital Staffs and Ground staffs I recognized the shape of something familiar. The vocabulary was different. The setting was different. But the intent, honest collective reflection in service of future improvement, was identical.

The military had been running agile retrospectives long before anyone called them that.

Dignity That Wasn’t About the Uniform

I need to say something about the officers and senior personnel I grew up around, because it shaped something in me that pure professional training simply cannot.

These were people of extraordinary dignity. Not the performative kind, not dignity that required an audience. The kind that is consistent whether someone is watching or not. They treated people with a particular quality of respect that I have spent my entire adult life trying to understand and replicate: they took you seriously without making it about them.

A senior officer speaking to a junior rank didn’t condescend. The hierarchy was absolute, but within it, there was a tradition of genuine respect flowing in every direction. I watched people of tremendous authority listen carefully to subordinates who had operational knowledge they didn’t. I watched commanders ask their teams direct questions and actually wait for the answers. I watched people be corrected firmly but without cruelty.

I have been in boardrooms since then, many of them, and I have noticed how rare this is. How many rooms full of qualified, intelligent people are derailed by someone who cannot separate their authority from their ego. How many projects limp along because a leader cannot hear a concern raised by someone two levels below them on a chart.

I learned early that genuine authority doesn’t shrink when it listens. It grows. The most trusted commanders I watched were trusted precisely because everyone knew they would hear the truth without punishing the messenger.

I carried that into every team I ever led. Every project. Every client relationship. The 300-plus people who have worked with me over the years, I hope they would say that I listened. That I took them seriously. That disagreement was welcome as long as it came with a reason.

That started on the ground, watching a commander I admired ask a young soldier a question and wait, with genuine patience, for the answer.

The Long Walk from Observation to Method

The path from that military station to a desk covered in project plans, client timelines, and compliance documentation was neither straight nor short.

There was education in between. There were early professional experiments, some that went well, some that were valuable precisely because they didn’t. There were industries I moved through: hospitals, healthcare, recruitment, SOP governance, Training, Audits Management, pharmaceuticals, technology, operations, each one teaching me something that the previous one hadn’t fully covered. There were certifications that gave formal structure to things I already half-understood intuitively. There were projects that nearly broke me and projects that genuinely thrilled me and the gradually growing understanding that I was becoming someone with a very specific, synthesized way of looking at problems.

What the military background had given me was not a methodology. It had given me values, discipline, clarity, accountability, respect for the people doing the actual work, belief in the debrief, and those values were portable across every environment I entered.

What I had to build, over years of practice, was the actual system. The method that could hold all of those values and translate them into something a team could follow, a client could trust, and a project could be built on.

VIRSAFEED: When You’ve Seen and Experimented Enough to Write Your Own Rulebook

I didn’t set out to coin a methodology. Nobody wakes up one morning and decides to write a framework. It evolves, like most honest things do, slowly, from necessity, from the accumulated scar tissue of doing the work.

VIRSAFEED is the name I gave to the operating system I had been quietly running for years before I formalized it. Visionary, Innovative, Resilient, Strategic, Agile, Focused, Efficient, Effective, and Dynamic. Nine dimensions that I had come to understand, through practice, failure, and relentless refinement, were the non-negotiable pillars of any project or operation worth delivering.

Not a replacement for Agile or Waterfall or Scrum or any of the frameworks I had trained in and used extensively. A lens through which to apply all of them. A way of asking: before we choose our method, have we done the thinking that makes any method viable?

Visionary (V): State precisely what you want to see done by the time we are through with this project. This establishes the foundation for all aspects of the strategy.

Innovative (I): Inspire creativity and inventiveness in order for new ideas on how to solve problems or approach situations differently from others will be created still.

Resilient (R): Developing fortitude so that no matter what happens (whether it involves failure or not) we may continue moving forward without being shaken off course entirely even though at times hurdled by misfortunes along life’s way.

Strategic (S): Strategic planning should be used so as projects align their objectives with those of an organization thereby making them an integral part of its overall mission statement by using coherent approaches which are based on aim effectiveness even though changing in nature all time long.

Agile (A): Make use of agile methods so as to quickly adjust to changes and stay flexible. 

Efficient (E): Use resources and procedures in a way that brings greatest productivity and least wastage.

Effective (E): Make sure that outcomes of projects meet or exceed the set objectives.

Focused (F): Watch on those critical tasks and objectives that define the success of the project.

Dynamic (D): Be dynamic and promptly responsive to alterations in situations and demands.

Every project I had run that went well had honoured these nine dimensions, whether I had named them or not. Every project that went sideways had failed one or more of them, usually early, usually quietly, and usually in a way that I could see in retrospect with painful clarity.

VIRSAFEED didn’t emerge from a whiteboard session. It emerged from 150-plus deliveries, from lessons learned documents nobody reads, from debrief conversations that I took seriously because a group of commanders had shown me, decades earlier, that the debrief is where the real work happens.

Twenty Projects. Twenty Clients. Three Thousand People Who Needed It to Work.

The numbers, when I say them out loud, still feel slightly unreal.

More than twenty concurrent projects at various points. More than twenty client relationships, each one a different organisation, a different culture, a different set of expectations and pressures, different solutions and histories. Thirty-plus team members across those engagements, developers, analysts, QA engineers, technical leads, business stakeholders, clinical researchers, compliance officers, surgeons, hospital administrators, advisors and project sponsors. Three thousand customers downstream of all of it, real people whose workflows, whose patient records, whose clinical data, whose daily professional lives were directly affected by whether we delivered well.

That last number is the one I come back to most often. Three thousand people who didn’t know my name, who didn’t attend any of our sprint reviews or stakeholder meetings, who simply lived with the consequences of how seriously we took our work.

You cannot hold three thousand faces in your head simultaneously. But you can remember that they exist. You can make decisions accordingly. You can ask, when the pressure is on and the shortcuts are tempting, whether the people at the end of this delivery deserve what you’re about to give them.

I ask that question a lot. It was, in a roundabout way, taught to me by people who carried that kind of responsibility every day in a very different context. Soldiers who understood that the quality of their preparation was not an abstract professional metric. It was someone’s actual safety.

What That Young Person on the Ground Would Think

I think about this occasionally. That younger version of me, watching the morning formations, eavesdropping on briefings, taking in the rhythm of a community built on purpose, precision, and a particular kind of quiet excellence.

I don’t think he would be surprised by the methodology. He saw methodologies being practised around him long before he had the word for them.

I think he might be surprised by the scale, not in an overwhelmed way, but in the way that someone is surprised when they realise that the things they watched and absorbed without fully understanding them actually went somewhere. That the seed was real.

What I learned in a military station was not tactics or strategy in the formal sense. What I learned was how organisations with genuine stakes, where failure is not a quarterly metric but an actual consequence, prepare themselves to succeed. How they build trust through consistency. How they hold standards without sacrificing humanity. How they debrief without abnegation. How they brief without ambiguity.

And how they respect the person standing in front of them, regardless of rank, because in the end, the mission only succeeds if everyone in it believes they matter to the outcome.

Twenty projects. Twenty clients. Thirty team members. Three thousand customers.

Every one of them mattered to the outcome.

Still do.

VIRSAFEED is the operating methodology I developed across twelve years of project management and operations delivery in hospital, healthcare, Robotics, pharmaceutical, CRO, Ed-Tech and technology sectors. It is not a proprietary product sold as a solution. It is the distilled thinking of someone who grew up watching how people with genuine stakes approach preparation, execution, and the honest examination of what went well and what didn’t.

If it sounds slightly military in its discipline, that is entirely intentional.

Know the Author

Hey there, readers! Welcome to my little corner of the internet. I ain’t just your average blogger — I’m a seasoned project manager with a knack for diving deep into research and unraveling the mysteries of project management. But that’s not all there is to me! With a background in Healthcare, IT and Pharmaceuticals for Project management, hospital management and a passion for travel, hiking, and trekking, I’m all about blending the professional with the adventurous. So, join me on this voyage where we’ll explore the ins and outs of strategy, project management and share tales from the management, travels, and maybe even swap tips along the way.

Feel free to visit my site to know more about my researched output in the form of blogs: http://www.virsafeed.com/