Briefing Three

You didn't become a researcher to feel like you're always behind

You finished 3 things today. Your to-do list grew by 7. And somehow you still feel like a failure.

You remember why you started this.

The curiosity. The feeling of a problem cracking open after weeks of thinking. The particular satisfaction of making something complicated suddenly clear.

That version of you still exists. But right now, you can't find them.

Instead, you've got 47 browser tabs open. A literature review that has been "almost done" for three weeks. An email from your supervisor that you keep reading and not answering. And a creeping, low-grade anxiety that everyone else in your cohort is publishing while you're still trying to find a clean hour to think.

Here's what I want to say to you:

This is not a discipline problem.

You have more discipline than most people will ever have. You chose a path that asks you to sit alone with hard problems for years. That takes a specific kind of courage.

This is a system problem.

The infinite list that academic work creates

Most productivity systems are built for finite work. You finish the task, tick it off, move on.

Academic work is never finished. A literature review can always be more comprehensive. A draft can always be more refined. A research question can always be more precisely defined.

So you're using a finite tool to manage infinite work — and then wondering why you always feel behind.

Space engineers face a version of this on every mission. There is always more data to monitor, more scenarios to model, more contingencies to prepare for. The work is functionally infinite.

But the best ones don't feel behind. Because they don't try to do everything. They operate with mission parameters — a defined scope for this shift, this phase, this console.

They separate "what I'm responsible for right now" from "everything that exists."

Most academics never make this separation. Everything feels equally urgent. Everything feels equally overdue.

​
​The reframe that changes everything

Your research is not a task list. It's a mission.

Missions have phases. Each phase has a specific objective. When the objective is met, you close that phase and move to the next. You don't keep the previous phase open "just in case."

This week, your mission is not "finish the PhD." Your mission is: write 500 words on the methodology section. That's it. That's the whole mission.

When you complete the mission, you close the console. You don't open new ones.

This is how the highest-performing people in high-pressure environments stay sane. It's how you can start doing the same.

If this resonated — there's a community built entirely around this way of working.

Ad Astra,
Sumana.

P.S. If this resonated, forward it to the one person in your department who needs to hear it.