The work before the work
You’ve rewritten the to-do list. The task is still there.
By evening, you’re tired of a piece of work you haven’t touched. And explaining why feels harder than the task itself.
You know what the finished thing should look like. You may even have done harder work last week. That makes today’s blank document harder to explain.
So you look for something you can finish. A quick reply. A tidier desk. A better way to organize the notes. Each one gets done. The work you meant to do keeps its place on the list.
If you recognize that afternoon, this is where we begin. With the moment you turn away from the task, and what might make returning to it easier.
Or perhaps you do start. A message arrives, lunch happens, someone needs an answer. An hour later, you’re reading your own last paragraph as if a stranger wrote it.
These are the moments Neutype is interested in: getting into a task, staying with it, and finding your way back when the day interrupts.
Advice often arrives at the wrong scale. “Write the proposal” describes the result. It leaves the first few minutes for you to figure out. “Stay focused” names the wish. It says little about what to do when you’ve already drifted.
We want to look more closely at those minutes. The file you can’t find. The decision you haven’t made. The email whose first sentence feels harder than the rest of the day.
There may be several reasons a task is difficult to begin. This essay offers a few things to try with the work in front of you. Keep what helps. Notice what doesn’t.
Give yourself a first move
Consider an item that has been sitting on your list: “Update the portfolio.” It contains a small crowd of decisions. Which projects belong there? Does the layout need changing? Is the writing good enough? Where did you save the images?
Choose one action you can take before settling all of that.
On the list: Update the portfolio.
First move: Open the last project’s folder and pick one image.
A place to stop: Save that image in a folder called “Portfolio update.”
That action leaves something behind. When you return, there is an image to work with and a place to put the next one.
A useful first move has a visible end. You can point to the sentence, the selected file, or the question you sent. It can be small enough to try in a few minutes; the exact number matters less than whether you know what to do.
Sometimes the first move reveals a dependency. You open the folder and discover that you need permission to use the image. Now the next action is clear: ask for permission. The task has become more specific.
If you’re still stuck, name the unresolved choice. “I haven’t decided who this is for” gives you more to work with than another copy of “Update portfolio.”
Leave a way back
A day with no interruptions is a fine thing to hope for. It is a fragile thing to build your whole working method around.
Before you leave a task, write a short note for the person returning to it. That person will be you, with less of the context in mind.
Where I stopped: Picked the opening image and drafted the caption.
Next: Check the project date in the original brief, then finish the caption.
Still open: Can I name the client publicly?
Put the note beside the work: at the top of the document, in the task, or next to the file. Give it a home you will encounter when you come back.
When you return, try the next action before reorganizing the whole project. If the note no longer makes sense, update it. Its job is to help you resume, and it is allowed to be untidy.
A working method should have room for the days you lose the thread. Being able to return is part of doing the work.
Make room for company
Some work becomes easier to approach when another person is nearby. You might try a quiet session with a friend, or agree to exchange rough drafts at a time that suits you both.
Keep the agreement specific and modest: “I’ll send you the opening paragraph this afternoon.” Say what kind of response would help. Perhaps you only need to know whether the point is clear.
Leave room to say that you got stuck. A check-in that only accepts success makes it harder to describe the actual problem.
You can share the state of the work without sharing the work itself. “I’m choosing between two openings” may be enough. Client information, personal details, and unfinished material can stay private.
If another person’s presence makes the task feel heavier, try working alone. The useful question is what happened during this attempt, and what you would change next time.
Give AI a smaller job
An AI tool can produce a plan long enough to become a project of its own. A request for help can leave you with more to sort through than you started with.
Try giving it the particular problem you have reached.
“I need to write a short introduction to this project. Ask me one question about the intended reader, then help me draft two opening sentences.”
Or use it to prepare a return note:
“From these notes, identify the decision I made, the question still open, and one action I can take next. Flag anything you would have to guess.”
These are starting prompts to adapt. Check the result against your own material. A confident answer can still miss the point or contain an error.
Before sharing source material, check what you’re allowed to share and the tool’s data settings. A made-up example may be enough to work through the structure.
Once you have something usable, bring it back to the actual task. Put the sentence in the document. Make the choice. Open the file. That gives you a way to judge the exchange: did it help you take the next step, or did you spend the session refining instructions?
We’re interested in finding out where AI earns its place in that sequence.
Decide what counts as enough
“Work on the essay” has no obvious end. “Write three sentences explaining who it’s for” does.
Choose a stopping point before you begin. You can continue if you want to, but you’ll know when the small commitment you made is complete.
For one session, enough might be a rough paragraph. For another, it might be a question that lets a colleague unblock the work. An honest decision to postpone or drop a task can also be useful. Write down the decision so you don’t have to keep making it.
At the end, leave a brief record: what you tried, what happened, and what remains. Over a few attempts, those notes may help you see which arrangements are worth keeping.
The aim is a way of working you can use on an ordinary day, with room left for the rest of your life.
What we’re here to publish
Neutype is an independent magazine about getting started and finding your focus. This essay sets out the questions we want to follow.
We’ll look at the first few minutes of a task, the practicalities of returning after an interruption, and the places where AI helps or gets in the way. We want to publish concrete examples: what someone tried, under what conditions, and what happened next.
A personal account, a practical suggestion, and a research finding each tell us something different. When a claim depends on research, readers should be able to find the source and see its limits. When we’re trying an idea, we’ll say so.
The suggestions in this essay are invitations to experiment with everyday work. They don’t establish why you find something difficult or promise the same result for everyone.
Our first issues are in preparation. We’re starting with the work you keep putting off, and paying attention to what makes it possible to begin.