By Sam Balch and Sara Roger
Nobody warns you. They just hand you the keys, wish you luck, and walk away.
The first year of key development (KD) time as a Major is unlike anything that comes before it. For the first time in your career, the accountability runs in both directions. What you do matters. What you fail to do matters just as much. You are no longer executing someone else’s plan. You are building the plan, resourcing it, communicating it, and holding the line when everything around you is moving faster than you ever get to fully grasp.
Between the two of us, we have sent SIRs at midnight, argued over ESR stats, and stared at PGR problems we did not create and were somehow now responsible for fixing. Sara started her KD time dual-hatting as a battalion S3 and XO, navigating a deployment to Romania she did not plan. Sam took on the full weight of his unit’s unforgiving OPTEMPO as the battalion XO in the ramp-up to a CTC rotation.
Together, we navigated the full weight of battalion operations while building systems, networks, and a hard-won understanding of where the job actually begins and ends.
We came out the other side with different frameworks, different scars, and a lot of overlapping conclusions.
This is for the next generation of KD majors stepping into their jobs, slightly terrified, trying to look like they aren’t. Everything below is what we wish someone had told us on day one and is worth reminding those even with just one more day left.
On What You Are Actually Walking Into
Sam: If you are reading this as a MAJ in your KD time, the feeling you have right now is normal. You are overwhelmed. You feel like you are constantly failing. You are running from one dumpster fire to the next, and no matter how much of yourself you give, you cannot seem to reach that state of “good units doing routine things routinely.”
Here is the truth: that state of “doing things routinely” is a myth in today’s Army. Our operational environment and technology is dramatically increasing in complexity, and none of us are in position long enough to make anything truly routine. You’ll probably get one CTC rotation, maybe one operational deployment, and it will feel like its the first time your unit has ever done it; because it is. By the time you figure out the job, and have a few systems in place, you are already rotating out. The feeling of chaos is normal, and it is the baseline in today’s Army. And I’m here to tell you that it’s okay. Accept that it is the baseline, and move the ball forward.
What makes the position of a KD MAJ uniquely hard is that for the first time, your inactions carry the same weight as your actions. As a CPT, the accountability was straightforward. Did you do the thing? Did you do it well? As a MAJ, Every minute you don’t spend on a problem, or developing guidance, is another minute you are taking away from your entire formation to plan, prepare, and execute. One of the emails sitting unread in your inbox on Saturday might be the one that determines whether your Soldiers eat hot chow during an upcoming three-week training exercise.
Sara: I had three months in my new unit. New platform. New country. And somewhere in the middle of a CPX with Corps, I got pushed down to a battalion. Ten days later, I was on a bus to Romania for an exercise I didn’t plan, serving as both the S3 and the XO for the next 6 months.
What I learned very quickly: Lead with empathy. Every single time. Everyone is just trying to figure this whole Army thing out. At every rank. At every echelon. In every organization. No one has it perfectly dialed in, and anyone who tells you otherwise is selling something. The more we lead with empathy, the more cohesive our teams, our relationships, and our networks become. Embracing and promulgating this mentality is a force multiplier for development, cohesive teams, and a positive work environment.
Sam: Neither of us has a clean solution to the impossibility of the job. What we can tell you is that the feeling of overwhelm you are carrying is not a sign you are failing. It is a sign that you understand the scope of your job, and that you care.
On Your Actual Job
Sam: “Your Job is TPME.”
Let’s start with what your job is not. Your job is not to have the best ideas in the room. It is not to shape the culture you want or redirect the unit’s energy toward your vision. You may have all of those things. And it may be a fantastic vision. Set it aside. As a MAJ, you are the instrument through which your commander’s vision becomes reality.
Okay, so I achieve my commander’s vision. But how? The framework that took me too long to figure out as a MAJ is Task, Purpose, Method, End State (TPME).
The end state is the most important aspect of TPME, and belongs to your commander. It is the picture of success, and it is what you are owed before you can build anything else. What they do not teach you at CGSC is that you are not a passive receiver of the end state. You are a spirit guide. Your job is to give your commander the information, constraints, limitations, and counterarguments they need to arrive at a clear and achievable end state before you walk out of the room. Ask the right questions. Surface the constraint they have not considered. Tell them what is not feasible and why. Whatever they hand you at the end of that conversation is the end state. It is theirs. Your job from that point forward is to achieve it. If you aren’t happy with your commander’s end state, you did not do a good enough job helping them develop it.
The purpose is the second most important aspect of TMPE, and also your commander’s lane. The “why” behind the end state. Purpose gives you the boundaries you need to make good decisions when your commander is not in the room, and you will hit those moments constantly.
The task. As a MAJ, this is your lane that nobody ever tells you about. Take the end state and purpose and turn them into a specific, actionable, time-bound task that can be handed to a real person. Not a concept. Not a good idea. A task. Not shouted to the room or in the direction of a staff shop, but given to a specific human who owns it. What exactly they are doing? When it is due? What does success looks like? Defining and assigning the task is your job as a MAJ.
The method belongs to your action officer or NCO. Once you hand them a task, how they execute it is largely theirs to figure out. Your institutional knowledge is the shortcut they do not have. Tell them who to call. Point them toward the right form or regulation. Don’t hold their hand through each step; that’s micromanagement. Give them a Task, Purpose, End State, a road map for the Method, and let them go.
Sara: “Your Job is to Translate the Vision. Communicate It Clearly.”
Your commander will hand you minimal intent and a seemingly impossible end state, and it is your job to take that and work backwards. What are all the wickets you have to hit? What tasks have to be accomplished, in what sequence, to get there? Who owns what?
And then, once you have mapped all of that out, you have to communicate it clearly to your staff. Not in the way that makes sense in your head. In the way that lands for them. Clear communication is not a soft skill at the field grade level. It is the job. If the staff doesn’t understand the path to the end state, they can’t execute it, and that’s on you, not them.
Here is something that took me too long to learn: message sent does not mean message received. And message received does not mean message understood. That last part is the one we skip most often.
As a field grade, you are responsible for ensuring your guidance is actually landing. Communication is a two-way street, and the burden of clarity sits with you, not your subordinate.
One thing I implemented was requiring a back brief after every task I assigned. But I want to be clear about how I introduced it, because the framing matters. In my initial counseling with each person, I explained the why upfront: my request for a backbrief is not due to lack of trust. I ask for a back brief because I don’t fully trust myself. Am I communicating clearly? Is my intent actually coming through the way I think it is? I had a couple of projects go sideways early in my KD time, and when I traced the problem back, it was never someone failing to execute. It was me failing to ensure that the action officer fully understood the task, intent, and end state.
Thirty seconds. That is all a back brief takes. Thirty seconds of “tell me what you’re hearing” saves hours of rework, missed timelines, and frustration on both sides. When your people understand from day one that the back brief exists to protect them from unclear guidance, not to check up on them, it becomes a normal and welcome part of the rhythm.
Your other job as a field grade is to look at the staff as a whole, identify where the gaps are, and figure out how to close them.
One thing I stood up as XO was what I called the Task Analysis Working Group. The premise was simple: flipping higher headquarters tasking orders is not the S3’s job. It is a whole-of-staff effort. So we brought the staff together, reviewed what higher had published, did the crosstalk, and the staff proponent for each task owned it from acknowledgment all the way through completion.
It sounds simple but it served as a dual purposed staff sync and operations planning time that was protected. Two birds, one meeting.
Your job is also to eliminate the battle rhythm events that are not driving change. If a meeting exists because it has always existed, that is not a reason. Every touchpoint with subordinate units or higher headquarters should drive something forward. If it does not, cut it or fix it. Guard your staff’s time like it is a resource, because it is.
On Initiative
Sara: “Don’t wait for permission. Go until you’re told to stop.”
I spent the first few weeks waiting. Waiting for my commander to give me permission. Waiting for explicit guidance. Waiting for someone to hand me the keys.
He was waiting for me to start driving.
Once I stopped waiting and started moving, everything shifted. I could take charge of running the battalion so that he could actually command it. The iron major runs the staff. The commander commands the unit. When those two things are in sync, it is a beautiful thing to be a part of.
Sam: “Build the structure. Set the conditions. Clearly communicate the task. Then get out of the way.”
The flip side of this is knowing what to do with the iniative and momentum once you have it. If you find yourself making the product, executing the brief, or doing the task you just assigned to someone else, something has gone wrong. The moment you pick up the pen and start doing the work yourself, you have stopped being a MAJ and started being an over-qualified and over-paid captain. Iniative is crucial, but it can also leave you with a task in your own hands when it should be in the hands of someone else.
On Developing Your Staff
Sara: “Systems are People.”
This one is non-negotiable, and it is also the one most of us skip because we think we do not have time.
Here is the math: your battalion commander and sergeant major have roughly six times as much time in the Army as the rest of the staff. You have about three times as much. Your staff knows little to nothing about being a staff officer or NCOIC. That is not a character flaw. It is just where they are in their career.
If you invest in developing them early, they will fill the gaps. They will perform. They will become a staff. If you do not, you will spend every day frustrated by broken systems and doing work that should be distributed.
Here is the mindset shift that changed everything for me: systems are people. When the system is broken, look at the people first, not the process.
Part of developing your staff also means being honest with your commander about where they are. If your commander wants a high-level product completed on a tight timeline, it is your job to tell him the truth. Is that timeline feasible given where the staff is right now? Advocate for realistic timelines, and close the gap as fast as you can.
Sam: “Invest in your people and the system will come.”
I will confess something from my first year: I spent too much time building systems and not enough time developing people.
Systems feel productive. A well-built tracker, a clean battle rhythm, a polished SOP. You can see them. You can brief them. They feel like progress. But systems do not deploy. Systems do not lead soldiers. Systems do not carry the institutional knowledge of a unit forward when you rotate out. Systems do not close with and destroy the enemies of the United States. People do.
Every time you choose the product over the person, you are borrowing against the future of your unit. I made that trade too many times in year one. In my second year, I am choosing people, because a team of developed, confident, capable people will build better systems than I ever could on my own.
On the Calendar
Sam: Somewhere in your S3 shop there is a 2LT who has access to the unit calendar. They can put things on it and take things off. Do not mistake that for calendar management.
That 2LT does not have the context to know which meeting affects which event, which conflict is acceptable, or which commander’s priority just made everything else irrelevant. Calendar decisions are yours, and they are not ones you can delegate.
Sara: Something I tried to build into our battalion culture was applying the PACE plan to calendar management. Primary. Alternate. Contingency. Emergency. We use it constantly in the field, but it applies just as much to day-to-day staff operations.
What is your primary method for tracking the battalion calendar? What is the alternate? What happens when the system goes down, when the NCOIC is on leave, when the S6 tells you the server is down? How are you creating shared understanding across the whole organization?
A PACE plan for calendar management sounds basic until the moment you need it and do not have one.
On Communicating Risk
Sam: Here is the tension nobody prepares you for. You cannot do it all, but you also cannot always see what you are not going to accomplish until you are already past the point where something could have been done about it.
The instinct as a high performer is to protect your commander from bad news and find a way to make it work. That instinct will betray you. When you absorb risk quietly and something fails, you have not protected your commander. You have taken away their ability to choose what succeeds and what fails. That decision belongs to them, not you.
Tell them early. Tell them clearly. Give them the options. Let them choose.
On Your Network and the People You Serve
Sam: As a MAJ, you do not have direct command authority over any of the people you need things from. You are completely reliant on other people choosing to help you.
Stop approaching problems as you versus the person who controls the resource you need. It is never you versus them. It is you and them versus the problem. The moment the person across the table feels like a partner instead of an obstacle, everything changes.
Your network is built by being the kind of person that people want to answer the phone for.
Sara: That same principle applies to your company and battery commanders. Get in close with them early. Let them know your door is open. You are their advocate. You are the person who will go to bat for them when they need it, and you are also the person who will quietly pull them aside and say, “Hey. Not this. Not right now. Trust me.”
They need to know you are in their corner, and also that you will be honest with them when they are off base. Those two things are not in conflict. That is just what good leadership looks like from where you sit.
Your door should always be open, except when you genuinely need five minutes to decompress. And then it is back open, because that is allowed too.
On Making Peace With the Job
Sam: There is a story about a Russian cosmonaut who was aboard a space station when the world he knew ceased to exist. While he orbited the earth, the Soviet Union collapsed beneath him. The country that launched him was gone and his once clearly defined objectives were gone. He was truly alone, and he did not know if and when he would ever be rescued. And somewhere in the silence and desolation of space, a rhythmic, ceaseless tapping started inside the hull of his spacecraft.
He spent weeks looking for it. Checking every panel, every conduit, every compartment. He could not find it. He could not stop it. It began to drive him mad. He checked every panel again and considered just tearing the spacecraft apart to make it stop. Eventually, floating alone in orbit with no country to return to and no way to silence the noise, he stopped fighting it. He decided to just fall in love with the sound.
As a MAJ, you have to fall in love with the sound.
The chaos is not going away. The tapping does not stop. The inbox does not clear. Your list of things to do will always grow at a rate faster than you can do them. At some point you have to stop searching for the source of the noise and make peace with the fact that it is just part of where you live now. Accepting it is not a weakness. It is the only way to function.
I would have given myself more grace in year one. More grace that I could not do it all. That leaving things unread when I went home on Friday was not a moral failure. That feeling like I was drowning did not mean I was doing the job wrong. It meant I understood the scope of it.
Sara: The iron major role is one of the most uniquely positioned jobs in the Army. You are close enough to the lieutenants and captains to still understand what is happening at the ground level, and connected enough to brigade and higher to see the bigger picture. You live in both worlds simultaneously.
If you walk into the office disgruntled, your staff will be disgruntled. If you spend your days complaining about higher headquarters or venting about the batteries, young lieutenants, captains, and staff sergeants will mirror that back to you and then some. The culture of your staff starts and ends with you.
You have to be the carrier of positivity and purpose. Not in a toxic positivity, pretend-everything-is-fine kind of way. In a grounded, genuine, this is why we do what we do kind of way. Your staff needs to understand the why behind the tasking, the friction, the long days. That understanding is your job to give them.
So make the most of it. Have fun with it. It is demanding and exhausting and wildly rewarding all at once, and there is truly nothing else quite like it.
It’s up to you whether you choose to grow or grind through it all.
Sara is a Major currently serving as a Brigade Operations Officer in Vilseck, Germany. Sam is a Major currently serving in [Sam’s current role]. Between them, they have served as battalion S3, XO, and pseudo-brigade S3 across multiple countries and operational environments.
