Urgent vs Important on a Student Satellite Team’s Launch Month

Every team that builds hardware for orbit eventually learns the same lesson: the loudest problem on the whiteboard is rarely the one that decides whether the mission works. This is the story of a small, made-up student satellite group, and how sorting urgent from important changed the way they spent their final launch month. If you have ever stared at a task list where everything is flagged red, you will recognise the mood.

Picture eight students sharing a cramped lab, one soldering station that never cooled down, and a small cube-shaped spacecraft due to be handed over to a launch integrator. They had weeks left, not months. Their task board had forty-odd cards, and every one of them felt like an emergency.

The week everything looked urgent

On Monday the radio board threw an odd reading on the bench. On Tuesday the faculty adviser forwarded a request for an updated mass table. On Wednesday a sponsor asked for photos for a newsletter. By Thursday the team had spent three days answering whatever pinged loudest and had moved exactly nothing on the checklist that mattered most.

The group’s systems engineer, a quiet role-holder who tended to say little in meetings, finally drew a plain cross on the whiteboard. One axis was how soon something was due. The other was how much it mattered to the satellite surviving, talking to the ground and doing its job. Then every card got dragged into one of four boxes.

What landed in each box

The sorting was uncomfortable, mostly because of what ended up where. Here is roughly how the four boxes filled up.

  • Urgent and important: the integrator’s paperwork deadline and a connector that kept loosening under vibration. These were done first, by named owners, that same day.
  • Important but not urgent: a full end-to-end rehearsal of the commissioning sequence, and a careful review of the power budget in eclipse. Nobody was shouting about these, which is exactly why they were at risk.
  • Urgent but not important: the sponsor photo request, the tidy-up of the lab wiki, and the logo on the cover of the test report. Quick, visible, and nearly irrelevant to flight.
  • Neither: a stretch goal for an extra telemetry dashboard and a debate about the mission patch colours. These were parked without guilt.

The urgent-but-unimportant box was the revelation. It held nearly half the cards and had been eating most of their hours, because those jobs were small, concrete and gave a quick feeling of progress.

Why the important work kept slipping

Important jobs in spaceflight tend to be quiet. A power-budget review does not blink or buzz. It simply waits, and if nobody schedules it, it ends up compressed into a sleepless final night. The team noticed that every near-miss in their short history came from a task that had sat in that second box for weeks.

If you are curious about why the power and thermal picture matters so much, it helps to understand the environment first. A readable primer on getting oriented with low Earth orbit explains why a small craft swings between sunlight and shadow many times a day, which is precisely what the eclipse review was meant to probe.

Protecting the important block

Sorting is only half the trick. The team’s second move was to put the important-not-urgent work onto the calendar as fixed appointments, before anything else. They held two long sessions a week with phones face down and the lab door shut. The commissioning rehearsal went first, because a satellite that cannot wake up properly after separation is simply a very expensive paperweight.

During the first rehearsal the group discovered that the sequence assumed a ground contact that would not actually occur until the third pass. Nobody had written that down. It was a minor timing mistake on paper and a lost spacecraft in practice. It had never been urgent for a single minute, and it was among the most important things they found all month.

For anyone planning similar work, it is worth reading how mission timelines are usually broken up. A clear explanation of how the stages of a flight follow one another helps you see which checks belong before separation and which belong afterwards.

Handling the urgent noise without ignoring it

The students did not pretend urgent items vanished. They changed how those items were treated. The quick, unimportant jobs were collected into one short block on Friday afternoon, done in bulk, and then closed. The sponsor got its photos. The wiki got a tidy. Neither task was allowed to leak into the mornings reserved for flight-critical work.

A few small rules grew out of this habit:

  1. Ask what changes if this sits untouched until next week. When the truthful reply is “very little”, the task is not important.
  2. Ask what happens if it never gets done. If the answer is “the mission suffers”, it is important, even if nobody is chasing it.
  3. Give every important job a date on the calendar, not just a place on a list.
  4. Say out loud who owns each card, because an ownerless task is the one that slides.

A short detour for the curious

Space is a field that attracts people with a taste for browsing, and the same trait applies to cities and culture. Away from the lab, some of the group liked to unwind with weekend ideas, and one of them mentioned a Jaipur-focused site where you can scan what is on around town, browse places to go and read community chatter as a handy place to look when planning a day out. It is a good reminder that downtime needs scheduling too, or the urgent will swallow it.

What happened at hand-over

When integration day arrived, the team was calm in a way that surprised their adviser. Their paperwork was in, the connector issue had been fixed with a locking compound and a re-test, and the commissioning sequence had been rehearsed enough times that two members could recite it half asleep. The cosmetic items that had once consumed their evenings were quietly finished, or politely dropped.

One member later described the shift simply: before the cross on the whiteboard, they had been reacting; afterwards they were choosing. The satellite did not become easier to build. The work simply got sorted into things that could shout and things that actually carried the mission.

Take this into your own project

You do not need a spacecraft to borrow the method. Next time your list feels like a wall of red, try the following in about fifteen minutes:

  • Write every open task on its own note.
  • Place each on a two-by-two grid of soon-versus-significant.
  • Do the top-left box immediately and book the top-right box into your diary before you do anything else.
  • Batch the bottom-left box into a single short slot.
  • Delete or park the rest and notice how little you miss them.

The real discipline lies in the second box. Urgent things will always find you. Important things need an appointment, and the teams that make one tend to be the teams that reach orbit with their calm intact.