Royal Army College

Lesson Overview

The last lesson taught you to plan: to take a problem apart by the estimate, weigh the factors, choose a course of action, and turn it into orders. That happens at the planning table, or its field equivalent of a map on a knee and a few quiet minutes. This lesson is about what happens next, when you stand up, fold the map, and lead the section out to do the thing. It is where the calm of the plan meets the friction of the ground, and where junior leadership is made or found wanting.

Leading is not planning. The plan is something you do to a problem; leading is something you do with people, in motion, while the problem changes under you. A leader who plans beautifully and then freezes when the first leg goes wrong has learned only half the craft. This lesson teaches the second half: how to grip a task and drive the section through it, decide when there is no time for another estimate, keep your head when things go wrong, adapt when the plan and the ground disagree, and trust the people you lead. The thread through all of it is the command task, both a real demand and the College's chief tool for building leaders.

A word at the outset, as in every practical lesson of this Army: this is the method, but the doing is certified in person. You build and prove these skills on the command tasks and field exercises of this course, under instructors and under the mild stress no planning table can supply. By the end you will be able to describe how a junior leader grips and runs a command task from start to finish, use a simple decision cycle to make a sound decision under time pressure and act on it, keep your head and the section's when a plan goes wrong, adapt a plan to the ground while holding the intent fixed, and delegate to and trust your second-in-command and your section.

Key Terms

Command task: a practical leadership problem the section solves together, under time pressure and mild stress, with one person in command; both a real field demand and the College's chief means of developing and testing a junior leader.
Grip: taking and holding control, so the section acts to your direction rather than drifting; the first thing a leader does on receiving a problem and the thing they never let slip while it runs.
The decide-and-act loop: the cycle by which a leader keeps pace with a changing situation, taking in, making sense, deciding, acting, then looking again; an observe-orient-decide-act loop in plain field terms.
Tempo: the speed at which a leader takes in, decides, and acts, relative to the speed at which the situation changes; keep a faster tempo than the problem and you stay in control of it.
The good-enough decision: a sound decision made and acted on in time usually beats a perfect one made too late, so a leader decides on incomplete information and adjusts rather than waiting for certainty that never comes.
Keeping your head: staying calm and in control under pressure, neither freezing (doing nothing) nor flapping (doing anything, fast, without thought); the leader's calm is the source of the section's calm.
Adapting: changing the method when the plan meets a reality it did not foresee, while keeping the purpose fixed; flex the how, hold the what and the why.
Commander's intent: the purpose of the task and the result wanted, expressed so those carrying it out can act in its spirit when its letter no longer fits; the seed of mission command.
Delegation: giving a part of the task, with the authority to do it, to your second-in-command or another soldier, then trusting them to get on with it.

What a command task really is

A command task is a problem the section solves together, with one of you in command, against the clock and with just enough pressure to make it real. The shape is familiar: a stated object, a few constraints, kit that is not quite enough, ground that is not quite cooperative, a time limit that is a little short, and a leader who must grip it, make a quick plan, give orders, get the section moving, and bring it to a finish. Get a load across a gap that cannot be crossed directly. Recover a casualty from a place a stretcher will not easily reach. Move the section and its stores from here to there by a time, through ground that argues with you. The puzzle changes; the demand on the leader does not.

A command task is two things at once, and confusing them makes people lead them badly. First, it is a real demand. Getting people and loads across difficult ground, reaching someone who needs help, organising a small team for a physical job under time pressure: these are exactly what an RKA section meets on a search, a relief task, or a flood. Treat it as an artificial game to be gamed and you learn nothing you can use. Second, it is the chief tool by which a junior leader is grown and tested. It puts pressure on the very things this course is about: can you take control, think under a clock, give an order people can follow, keep your head when your first idea fails, and trust your team to work. The instructor is reading those things far more than whether the load actually got across.

So do not resent the time pressure and mild stress. The pressure is the point. Anyone can make a sensible plan with an hour and a quiet room; the Army needs to know whether you can make a workable one in ninety seconds with the section watching and the clock running, because that is the only kind of decision the field will ask of you. The stress is kept mild and the setting safe so that you can fail here and learn, at no cost worse than a hard word and a lesson, instead of failing for the first time on a real task where the cost falls on someone else. Go to a command task expecting to be stretched, expecting some attempts not to work, and meaning to learn from each one in the after-action review that Lesson 07 teaches.

Gripping the task: from problem to movement

When a task lands on you, grip it. To grip is to take hold of the task and of the section, so that from this moment they act to your direction rather than standing about or drifting into their own ideas. Grip is mostly bearing and voice in the opening seconds: step forward, take charge visibly, stop the talk, and make it plain by how you stand and speak that someone is now in command. A section can feel within seconds whether anyone has the helm, and one that senses no grip fills the silence with chatter and half-starts you must then gather back in. Take the helm at once, even before you know the answer. You can grip a task you do not yet know how to solve; you cannot solve one you have not gripped.

With the section in hand, run the estimate of Lesson 05 cut to its bones, in your head, in the time you have. What result do I actually need (the object stripped to its purpose, the intent)? What have I got, and what works against me? What are my realistic ways, and which fits the time? You are not looking for the perfect plan but for one good enough to start moving on. Choose, and choose in time.

Then give orders, in the manner Lesson 05 taught but cut to the length the moment allows. The section does not need your whole reasoning; it needs to know, plainly and in order, what the result is and why, who does what, and any control you are setting: the timings, the safety, the signal that means stop. Keep it short and in a sequence people can hold, and finish by checking it landed, a brief-back from your 2IC and the look on the faces, so you are not launching a section that has not understood you. Then get them moving. There is a moment after the orders and before the first soldier steps off where a task can die of hesitation; break it with a clear word and a start, because a section in motion can be corrected and a section standing still cannot. Once it is moving, do not subside into a spectator. Watch, keep control, compare what is happening to what you intended, and adjust. Grip is not a single act at the start; you keep your hand closed on it until the task is done.

   GRIPPING A COMMAND TASK: from problem to finish

   1. GRIP IT          step forward, take charge, stop the drift.
                       "I have this." Take the helm before you
                       know the answer.

   2. QUICK PLAN       the estimate of Lesson 05, cut to the bone,
                       run in your head:
                         - what result do I actually need? (the intent)
                         - what have I got / what works against me?
                         - what are my ways, and which fits the time?
                       Choose a plan good enough to start on.

   3. CLEAR ORDERS     short, in order, the way Lesson 05 taught:
                         what and why, who does what, control + safety.
                       Check it landed (a brief-back, the faces).

   4. GET THEM MOVING  break the hesitation with a clear word and a start.
                       A section in motion can be corrected;
                       a section standing still cannot.

   5. ADJUST           watch, compare to your intent, and flex the
                       method as the ground answers back.
                       (The decide-and-act loop, running the whole time.)

   You GRIP once at the start and keep the hand closed
   through 4 and 5 until the task is done.

Deciding under pressure: the decide-and-act loop

At the planning table you decide once, carefully. In the field you decide again and again, quickly, as the situation keeps changing, and you need a method that does not collapse under pressure. The Army teaches a simple loop you run continuously, almost without naming it once it is habit: take in what is happening, make sense of it, decide, act, then look again. It is the field form of what the wider Army calls an observe-orient-decide-act cycle, in the words a section leader can use while standing in a stream with the light going.

Take each step for what it is. To take in is to gather what the situation is actually telling you, with your own eyes and ears and from your section: where are my people, what has changed, what has gone wrong. To make sense is to fit that against what you are trying to achieve: minor wrinkle or broken plan, time to change or not. To decide is to choose what to do now, plainly enough to turn into an order. To act is to give the word and get the section doing the new thing, because a decision that stays in your head changes nothing. Then you look again, because your action has changed the situation, and the loop begins once more.

   THE DECIDE-AND-ACT LOOP  (run it continuously)

         +---------------------------------------------+
         |                                             |
         v                                             |
    TAKE IN  -->  MAKE SENSE  -->  DECIDE  -->  ACT  ---+
    what is        what does it      choose       give the word,
    happening,     mean against      what to      make it happen
    really         my intent? is     do now       (a decision in
    (eyes, ears,   the plan still                  your head
    the section)   good?                           changes nothing)

    ...then LOOK AGAIN: your action has changed the picture,
    so you take in afresh and go round once more.

    The aim is TEMPO: keep going round this loop FASTER than
    the situation is changing, and you stay in control of it.
    Fall behind it, and the situation starts commanding you.

The loop exists for tempo: keeping your own cycle running faster than the situation is changing. A leader who cycles quicker than the problem moves stays ahead of it and in control; one who falls behind is forever reacting to a situation that has already moved on, and the section feels driven by events rather than led through them. You do not gain tempo by sprinting in a panic. You gain it by being practised enough that taking in, making sense, and deciding happen quickly and surely, which is exactly what the command tasks of this course drill into you. The loop is not a form to fill in. It is a habit of mind, and like every habit it gets faster and smoother with repetition until you run it without knowing.

The good-enough decision: deciding in time

Now the hardest truth in this lesson, the one that most separates those who can command from those who can only plan. In the field, a good decision made and acted on now almost always beats a perfect decision made too late. The situation does not wait for you to be certain. The casualty is still where they are, the light is still going, the water is still rising, and every second spent reaching for the perfect answer is a second the problem uses against you. A leader must be willing to decide on incomplete information, act, then adjust.

This goes against a deep and understandable instinct. We are taught, rightly, to weigh things up, and it feels responsible to gather more information and reckless to act without it. But there is a point, and in the field it comes fast, where the cost of waiting for more certainty exceeds the cost of acting on what you have. Past it, the careful-seeming choice ("let me just find out a bit more first") is the reckless one, because while you delay, the situation worsens and your options close. The leader's skill is not to make perfect decisions; it is to judge when they have enough to act on, then act, knowing the decision is imperfect and meaning to correct it.

Two things keep this from being a licence for rashness. The first is the loop: because you keep looking again after you act, a decision made on thin information is not a leap in the dark but a first move you refine the moment you see its result. You are not betting everything on being right; you are starting, watching, and steering. The second is the commander's intent, which the next section takes up: because you are clear on the result you actually need, even a quick, imperfect decision can be pointed the right way and a wrong turn put right against a fixed purpose. A leader who must be certain before they move will, in the field, never move in time, and a section that cannot be moved in time has stopped being led.

Keeping your head when it goes wrong

Sooner or later, on a command task and on a real task, something goes wrong. The plan that read so cleanly meets a gap wider than you thought, a piece of kit fails, a soldier goes down, the time runs short. This is normal, not a sign you planned badly; expect it rather than be shocked by it. What matters in that moment is the leader's head, because the section takes its emotional temperature from you, faster and more surely than from anything you say. Stay calm and they stay calm and keep working the problem. Lose your head and theirs go with it, and a recoverable setback becomes a collapse. The leader's calm is the source of the section's calm. That is not a comforting saying but a mechanism, and the single most useful thing to know about leading when things go wrong.

There are two ways to lose your head, opposite in appearance and equally fatal. The first is to freeze: to do nothing, to stand there with the loop stalled, hoping the situation resolves itself or that someone will tell you what to do. Freezing feels like caution but it is surrender, because while you do nothing the situation does as it pleases, and the section, seeing no grip, drifts. The second is to flap: to do something, fast, anything, to fill the fear with motion, changing the plan every ten seconds, barking contradictory orders, rushing the section from one half-started idea to the next. Flapping feels like decisiveness but it is panic wearing its clothes, and it is worse than freezing because it spends the section's effort and trust on nothing. The discipline is to do neither: keep your head and run the loop, calmly and in time, with your heart going and the section's eyes on you.

   WHEN IT GOES WRONG: the two failures, and the way between

   FREEZE  <------------ KEEP YOUR HEAD ------------>  FLAP
   do nothing,           run the loop, calmly:         do anything, fast,
   stall, hope           take in -> make sense ->      without thought;
   it resolves           decide -> act, in time        change the plan
   itself                                               every ten seconds

   feels like CAUTION    decide in time on what         feels like DECISION
   but is surrender:     you have, point it by          but is panic:
   the situation does    the intent, then adjust        it spends the
   as it pleases                                         section's effort
                         The section takes its calm     on nothing
                         from YOUR calm. Steady the
                         leader and you steady the
                         section.

Keeping your head is partly temperament, but far more a trained habit than people think, and the command tasks of this course are where you train it. The first time a task goes wrong under pressure, most people feel the pull to freeze or flap; the value of doing it again and again, in a safe setting, is that the feeling loses its grip and the trained response, steady down and run the loop, takes its place. A few practical aids help on the day. Breathe out slowly before you speak, which steadies you and stops the rushed, high voice that tells the section you are rattled. Speak in named, ordered tasks rather than vague urgent noise: "Cole, Adesina, get the line across; the rest of you, stand fast," not "come on, quickly, someone do something." And give yourself the one or two seconds it takes to take in and make sense before you decide; those seconds are not delay but the difference between a decision and a flail. The calm you show may be partly manufactured at first. It works anyway, because the section cannot see the effort, only the steadiness, and the steadiness is what holds them.

Adapting: no plan survives contact unchanged

There is an old soldier's saying that no plan survives contact with the enemy, and the humanitarian, defensive form is just as true: no plan survives contact with the ground. The gap is wider, the route blocked, the kit short, the light gone faster than you reckoned. This is not the failure of the plan but the normal life of every plan, and a leader who expects the plan to run as drawn will be undone the first time it does not. The plan is not a promise about how the task will go. It is, as the Patrolling and Tactical Movement course puts it, a control tool: a shared starting point that lets the section begin together and stay together while reality is dealt with. Hold to it as far as it serves and change it the moment it stops serving.

What lets you change the plan without losing the section is the commander's intent: the purpose behind the task and the result you actually need, as against the particular method you chose. When you give orders, state the intent first and most clearly, because it is the part meant to outlast the plan. If the section knows the result wanted is "get this casualty to the road by last light, because the vehicle can only reach the road and the light is going," then when the planned route proves impassable the change is obvious and the section makes it without missing a beat: the method flexes while the purpose stands fixed and points the new method the right way. But if all the section was given was the method, "carry the casualty along the streambed," then the moment the streambed fails they are lost, because they were never told what it was for. Fix the purpose and you can change everything else freely; lose it and you have nothing to steer by when the method breaks.

This is the seed of something larger you met in Foundations of Military Leadership and will live by ever more as you rise: mission command, the Army's whole philosophy of leading by intent rather than by detailed instruction. At your level it shows up small and immediate, the section adapting a stuck plan because it knows what the plan was for, but it is the same idea that lets a whole scattered force keep pulling toward one purpose when its communications fail. The habit starts here, on the command task, in always telling the section the why and not only the what, and holding the why fixed while you flex the how. Build it at section level now and you are building, in miniature, the thing that lets a small humanitarian Army act with judgement spread all the way down to the soldier on the spot.

Delegating and trusting the team

You cannot do a command task alone, and the leader who tries is making a beginner's mistake. A section has a second-in-command and seven or eight other capable people, and your job is to get everything done through them, not to do everything yourself. That means delegating: giving a part of the task, with the authority to carry it out, to your 2IC or another soldier, then letting them get on with it. The 2IC is your first and most important delegate. While you read the whole problem, decide, and keep the section together, your 2IC can run a part of it, getting the kit forward, organising the carry, holding the rear, so the task is worked on two fronts and you are freed to do the thing only you can do: command the whole. A leader who keeps every job in their own hands becomes the bottleneck the task waits on, and exhausts themselves doing badly what others could have done well.

Delegate the result, not a list of every step, the intent again at the smallest scale: "get the line secured to that far tree, you sort the how." Then supervise enough to keep them pointed right without standing over them undoing their work. This does two things. It gets the task done faster, several jobs running at once instead of one at a time through you. And it develops the section, because a soldier given a real piece of the problem, with room to solve it their own way, grows as one who is only ever told exactly what to do never will. The same trust you hope your own commander shows you, you owe downward. You will sometimes be disappointed by a delegated job done in a way you would not have chosen; that is the price of developing people, and worth paying, because a section in which only the leader can think stops dead the moment the leader is occupied, and for a small Army that is a fatal weakness.

There is a sobering reason the 2IC matters beyond any one task. The leader may be taken out of the picture, hurt on the ground, called away, simply unreachable for a time, and the section must not stop. The 2IC has to be able to step up and command, which means they must have been brought into your thinking all along, must know the intent, must have been trusted with real responsibility before the day they need it. A leader who has done everything themselves and told the 2IC nothing leaves, when they fall, a section with no one ready to take the helm. So delegating to your 2IC is how you get today's task done and how you make sure the section can carry on without you, one of the truest tests of whether you have led it well.

In Practice: A River-Gap Command Task at the Training Area

On a command-task serial at the training area, a Kaharagian section is given a problem and a clock. A casualty, a weighted dummy on a stretcher, must be moved across a fast, shallow stream too wide to bridge directly and too quick to wade casually, using only the kit to hand, a length of rope, two poles, some webbing, and got to a marked point on the far bank by a stated time. An instructor stands back to watch the leader, not the dummy. The newly appointed section second-in-command, Corporal-designate Vasic, is in command for this serial.

She grips it at once. As the section crowds the bank and offers ideas, she steps forward, stops the chatter with a word, and makes it plain she has the task; the section settles to her. She does not yet know how she will cross the casualty, and does not pretend to. In her head she runs the estimate cut to the bone: the result is the casualty dry, secure, and at the marked point by the time, that is the intent; what she has is the kit and eight pairs of hands; what is against her is the current, the width, and a tight clock. She settles on a way good enough to start, a rope handline to steady a wading party carrying the stretcher, rather than a more elegant scheme she has no time to build, and gives short orders in sequence: the result and why, Cole and Adesina to get the rope across and made fast, the stretcher party told off, the handline named as the control and "no one crosses until it is secure" as the safety. She checks it landed with a quick brief-back, breaks the hesitation with a clear word, and the section moves.

It goes wrong, as these things do. The first soldier across finds the far anchor point a metre of slick, undercut mud, no good for the handline at all. Here is the moment the instructor is really watching. Vasic does not freeze, staring at the failed anchor, nor flap, shouting the section into the water on a half-thought. She breathes out, takes in what has happened, and makes sense of it against her intent, which has not changed: the casualty still needs to be dry, secure, and at the marked point by the time. She decides in time on what she has rather than waiting for a perfect answer the clock will not allow: shift the crossing ten metres upstream to a firm rock where the rope will hold, accepting a longer carry on the far side. She gives the new word, and because the section was told the why and not only the carry-along-the-rope, the change costs no confusion; the method flexed and the purpose held. Through the carry she delegates the far-bank organisation to her 2IC and keeps her own eyes on the whole, and when one soldier slips and lets the stretcher dip she steadies the section with a calm, named correction. The casualty reaches the marked point inside the time, a little later than the first plan promised and by a route nobody drew at the start.

In the after-action review that follows, the method of Lesson 07, the instructor barely mentions whether the dummy got across, because that was never the real question. The questions are the ones this lesson is about. Did she grip it, or let it drift? Decide in time on what she had, or hold out for certainty? Keep her head when the anchor failed? Hold the intent fixed and flex the method, or lose her way when the plan broke? Use her section and her 2IC, or try to carry it all herself? Those are the things a command task is built to test and to grow, and the things a real river, a real flood, a real casualty on a real bad day will one day ask of her for keeps. The training area is where she finds out, and improves, at no cost worse than a hard, fair word and a lesson well learned.

Check Your Understanding

Explain what a command task is and the two things it is at once. Why does it carry time pressure and mild stress, and why should a junior leader welcome the chance to fail at one in the safe setting of the course rather than resent it?
Describe the decide-and-act loop in your own words, naming its four parts and what "look again" adds. Explain what tempo means and why a leader who keeps a faster tempo than the situation stays in control of it. Why does a good decision made and acted on in time usually beat a perfect one made too late, and what two things keep deciding on incomplete information from being mere rashness?
There are two opposite ways to lose your head when a plan goes wrong. Name them, say why each is fatal, and describe the way between them. Then explain how the commander's intent lets a leader adapt a broken plan without losing the section, and why this small skill of holding the why fixed while flexing the how is the seed of mission command taught in the Foundations of Military Leadership course.

Reflection (write a short paragraph): This lesson turns on a hard truth: in the field, a sound decision acted on now usually beats a perfect one made too late, so a leader must decide on incomplete information and then adjust, all while keeping their head and holding the section's calm. Think honestly about how you tend to behave when a plan you were counting on falls apart under pressure. Do you lean toward freezing, waiting for certainty or for someone to tell you what to do, or toward flapping, doing anything fast to fill the fear? What would it ask of you, personally, to do neither, to breathe out, run the loop, decide in time, and stay steady because the people beside you are reading your face for the answer? Why is this a thing you must build by doing, on the command tasks of this course, and not something you can simply resolve to do on the day?

Summary

A command task is a problem the section solves together under time pressure and mild stress, with one of you in command: both a real demand of the kind RKA tasks pose, and the College's chief tool for growing and testing junior leaders. That is why it carries pressure and why it is the safe place to fail, learn, and improve.
Grip a task by taking the helm at once, even before you know the answer, then run the estimate of Lesson 05 cut to the bone, give short clear orders, check they landed, break the hesitation, and get the section moving, keeping your grip closed until it is done.
Keep pace with a changing situation by running the decide-and-act loop continuously: take in, make sense against your intent, decide, act, then look again. The aim is tempo: cycle faster than the situation changes and you stay in control of it.
A sound decision made and acted on in time usually beats a perfect one made too late, so decide on incomplete information and adjust; the loop and the intent are what keep this from being rashness.
When a plan goes wrong, the leader's calm is the source of the section's calm. The two failures are freezing and flapping; the discipline is to do neither but steady down and run the loop, a trained habit built on the command tasks of this course.
No plan survives contact with the ground unchanged. The method flexes while the commander's intent stands fixed and points the new method the right way; holding the why while flexing the how is the seed of mission command from the Foundations of Military Leadership course.
You cannot do it all alone: delegate to your second-in-command and trust the section, both to get the task done and so the section can carry on if you fall. These skills are built and certified through the in-person practical exercises and the after-action review of Lesson 07; this lesson gives you the method to bring to them.

Leading in the Field: Command Tasks and Decisions