Stop Time-Blocking. Start Context-Blocking.
A framework for people who work hard, care deeply, and still can’t figure out why nothing feels done.
You sit down to work. You have the time, you have the intention, you have the coffee. You open your laptop and you begin. Hours pass. Somehow, at the end of it, you have very little to show — or what you have doesn’t feel done, even though you’ve been “working” this whole time. You feel tired, frustrated, vaguely guilty, and confused about where the time went.
Your friends don’t seem to have this problem. They open their laptops, they do the thing, they close their laptops.
So you start believing it’s a you problem. A discipline problem. A motivation problem.
Here’s what I want to tell you before we go any further: it is not a you problem. It is a systems problem. And systems problems are the best kind of problem to have, because systems can be redesigned.
This article is about redesigning yours.
The Actual Problem Nobody Names
Most productivity advice tells you to work harder, work smarter, use a timer, make a to-do list, eat the frog, time-block your calendar. You’ve probably tried some of these. Maybe they worked for a day or two and then quietly fell apart.
Here’s why: none of that advice addresses the actual problem, which is this — your brain is being asked to do two fundamentally incompatible things at the same time, and nobody told you they were incompatible.
Those two things are generating and evaluating.
And when they collide — which they do, constantly, invisibly, in every unstructured work session — the result is exactly what you’ve been experiencing: hours of effort that produce almost nothing, a feeling of being stuck without knowing why, and a growing suspicion that something is wrong with you.
Nothing is wrong with you. Your brain is just running two modes that crash each other every time they open simultaneously.
Let’s understand what those two modes actually are.
The Two Modes Your Brain Lives In
Generative Mode
This is the mode where your brain is producing possibilities. It’s making things that don’t exist yet — sentences, ideas, designs, structures, solutions. It’s reaching into uncertainty and pulling something out of it.
Generative mode needs one specific condition to work: psychological safety. Your brain needs to believe, at least temporarily, that what it produces won’t be immediately judged. Why? Because judgment is a threat signal. And when the brain detects a threat, it stops producing and starts protecting. It tightens. It censors. It second-guesses before anything has a chance to exist.
Think about the best brainstorming session you’ve ever had — the one where ideas just kept coming. There was probably a looseness to it, a “yes and” energy, a sense that nothing was too stupid to say out loud. That’s generative mode working the way it’s supposed to. The inner critic was quiet, and because it was quiet, your brain felt safe enough to reach further, make stranger connections, surprise itself.
Now think about every time you’ve sat down to write or design or create something and the inner critic showed up in the first five minutes. “That’s not good enough.” “That’s too obvious.” “That doesn’t make sense.” Generation shut down almost immediately. Not because you ran out of ideas — because the evaluator arrived before the generator had a chance to produce anything worth evaluating.
Generative mode is about volume first, quality second. Its job is to make. It is not the job of generative mode to make good things. That comes later.
Evaluative Mode
This is the mode where your brain is assessing something that already exists. It’s looking critically at a draft, a structure, a decision. It’s asking: what’s wrong here? What’s missing? What could be clearer? What needs to go?
Evaluative mode needs a completely different condition: critical distance. It needs to be able to look at something without sentiment, without the vulnerability of the person who made it getting in the way. The inner critic isn’t just allowed here — it is the entire point.
When evaluative mode is working correctly, it’s surgical. It identifies exactly what needs to change and why. It’s not cruel, it’s precise. It makes good work better. It’s the reason your second draft is stronger than your first.
But evaluative mode needs something to evaluate. It can’t work on nothing. Without an artifact — a draft, a diagram, a paragraph — to apply itself to, it starts evaluating potential things, imagined things, ideas before they’ve been given a chance to exist. And that is where the whole system collapses.
What Happens When They Collide
Here’s the scenario. You sit down to write the introduction to a case study. You’re in generative mode — or you’re supposed to be. You type a sentence.
Your evaluative brain immediately appears: That’s too vague. You’re burying the lead. Who’s going to care about that opening?
You delete the sentence. You try another.
Still not right. Too formal. Not compelling enough.
You delete that one too. Maybe you rewrite the same sentence six times. Maybe you give up on the intro and jump to a different section. Maybe you open a reference document to “get inspired” — which is really just your brain trying to escape the threat of evaluation by going back to gathering, which feels safer.
An hour passes. You have nothing. Or you have one sentence you’re not sure about.
This is not writer’s block. This is not laziness. This is two cognitive processes running simultaneously that are neurologically incompatible, each one undermining the other in real time.
The generative brain needed the evaluator to be quiet long enough to produce something. The evaluative brain needed the generator to finish before it had anything real to assess. Instead, they kept interrupting each other, and the output of that interruption is: nothing completed, enormous energy spent, and a feeling of personal failure that belongs to a systems problem, not a character flaw.
This collision is especially brutal in creative and knowledge work because there’s no external signal that says “generation is over, evaluation may begin.” Done is a judgment call. The task is partially undefined by nature. So without an internal structure, the two modes bleed into each other constantly — and it looks like procrastination from the outside, but from the inside it’s your brain trying to create and protect you at the same time.
Your depth is not the problem. The missing structure around it is.
The Neuroscience (Just Enough to Be Useful)
The brain science here is worth a quick look because it makes the whole thing feel less like a personal failing and more like a mechanical reality.
Generative thinking is associated with the default mode network — the same system that activates during mind-wandering and imagination. It works best in a low-threat, exploratory state. Evaluative thinking is more associated with the executive control network, responsible for focused, deliberate judgment. These two networks are largely anti-correlated — when one is highly active, the other tends to be suppressed. The brain toggles between them, and every toggle has a cost.
Research on task-switching shows that shifting between cognitively distinct modes takes real time and energy, even when the tasks seem related. The reorientation period can take anywhere from a few minutes to over twenty minutes depending on complexity. If you’re switching modes every ten minutes without realizing it, you are mathematically incapable of reaching the depth where your best work lives.
This is why naming your mode before you start — not after you drift — is one of the highest-leverage things you can do.
Introducing Context Blocks
A time block says: work on this for 30 minutes.
A context block says: be in this specific cognitive state, applied to this specific object, until this specific thing exists.
Those are completely different instructions. One sets a container. The other fills it with something your brain can actually hold onto.
Here’s the formula:
Context Block = MODE + OBJECT + DONE STATE
You need all three. Two out of three doesn’t work. Here’s why each one is load-bearing.
MODE answers: what kind of thinking am I doing right now?
There are five modes worth knowing:
Explore — gathering information, reading references, understanding a space. You are not making anything yet. No judgment, no output pressure.
Define — structuring, deciding, outlining. You’re making decisions about shape and direction before building begins.
Create — producing an actual artifact. A screen, a paragraph, a diagram, an annotation. Something that didn’t exist before this session.
Critique — reviewing something that already exists and identifying what needs to change. Not fixing yet. Just seeing.
Communicate — writing to someone, preparing something to share, finalizing something for an audience.
The one distinction which is difficult: Define vs. Create.
Define is deciding what you’re going to make. Create is making it. They feel similar because they’re close in the timeline, but they’re completely different cognitive tasks. Define is: what sections should this case study have, and what does each one need to say? Create is: writing the actual words of section two. If you try to figure out the structure while simultaneously writing the content, both suffer. The structure never gets decided cleanly, and the writing keeps getting interrupted by structural questions. Run them separately — always Define before you Create — and both go faster.
Why does naming the mode matter? Because it creates a rule for the session. Anything that violates that mode is now an identifiable intrusion, not just “more work.” Without the name, every drift feels justified — it’s all “working on the same project.” With the name, you have a border.
OBJECT answers: what specific thing am I applying this mode to?
Not “my portfolio.” Not “the case study.” Not “the presentation.” Those are projects. An object is the smallest meaningful unit within the project that can be completed in one session.
“The second paragraph of the problem statement” is an object. “The escalation flow diagram, version 2, the middle section” is an object. “The three bullet points under ‘What I learned’ on the final slide” is an object.
The object should feel almost embarrassingly small. That’s correct. Small objects get completed. Completed objects compound into finished projects.
DONE STATE answers: what will I be able to point to when this block ends?
This is the most important piece and the most commonly skipped one.
The done state is a sentence that begins with “I will have...” and ends with something you could show someone as evidence.
“I will have a rough draft of the intro paragraph — messy is fine, just words on the page.” “I will have identified three specific things I want to change in the escalation diagram.” “I will have a list of five references I want to pull from for this section.”
Notice what done states are NOT: they are not “I will be finished.” They are not “I will be happy with it.” Those are feelings, not endpoints. Your brain can’t navigate toward a feeling. It can navigate toward a thing.
The done state is also what protects you from the endless session. Without one, “working on something” can last eight hours because there was never a definition of completion. With one, the session has a natural close. You reach it, you stop, you acknowledge that you did what you said you’d do. That small moment of closing the loop is neurologically satisfying in a way that hours of undirected work never is.
The One Sentence Test
Before every work session, complete this sentence in under 60 seconds:
“I am [MODE]ing [OBJECT] until I have [DONE STATE].”
If you can’t complete it in 60 seconds, the session isn’t ready. Don’t start. Spend another 2 minutes defining it. It will save you 2 hours.
Let’s look at this in action.
The Framework in Action: Real Examples
Example 1: The Designer Who Can’t Finish Her Case Study
Before context blocks:
“I’m going to work on my portfolio today.” She opens Figma. She’s not sure where to start, so she looks at reference portfolios. She finds one that’s incredible and feels discouraged. She starts adjusting typography on the first page. Then realizes she hasn’t written the problem statement yet. She starts writing it. Doesn’t like the first sentence, rewrites it five times. Gets frustrated, opens Twitter. Comes back. Now she’s questioning the images on page 3. Two hours later, nothing is materially further along than when she started.
After context blocks:
She spends 3 minutes defining her block.
Mode: Create Object: The problem statement for the Relay case study — just the first two sentences Done state: I will have two written sentences I can paste into Figma, even if they need editing later
She sets a 45-minute timer and opens only what she needs. When she wants to look at reference portfolios, she notices: that’s Explore mode. I’m in Create. I’m leaving. She returns. When she wants to evaluate whether the sentences are good enough: that’s Critique mode. Not yet. She writes badly and keeps writing.
At the end of 45 minutes, she has two sentences. They’re not perfect. But they exist, which means they can be improved. The evaluative brain now has something real to work with.
The session took 45 minutes instead of 2 hours and produced something she can actually use.
Example 2: The Writer Who Calls It Writer’s Block
Before context blocks:
“I need to write this article.” He opens a blank document. Types a sentence. Deletes it. Tries a punchier opening. Nope. A more personal opening. Also not right. He’s not sure if it should be narrative or listicle, so he tries to write without deciding. Three hours later, 200 words he hates and a conviction that he’s not a writer.
After context blocks:
He notices he hasn’t defined the structure yet — which means he’s not actually ready to Create. He runs a Define block first.
Mode: Define | Object: Section headings with one-line descriptions | Done state: A rough outline with at least 5 sections named
45 minutes. He has an outline. Now a Create block:
Mode: Create | Object: The introduction — 3 paragraphs only | Done state: A messy first draft covering the hook, the problem, and the promise
He’s not writing the whole article. He’s writing three paragraphs. The boundaries make it possible to begin.
Example 3: The Student Preparing for an Interview
Before context blocks:
“I need to prep for this interview.” She reviews past projects, gets anxious about a mock answer, thinks about her outfit, reads company news articles, tries to practice answers but keeps stopping to edit them. An hour passes and she feels less prepared than when she started.
After context blocks:
She identifies three distinct tasks — gather company knowledge (Explore), structure her talking points (Define), practice delivering them (Create) — and runs them in order, separately.
Block 1 — Explore: Recent news and strategy for the company → Done state: five bullet points summarizing what she learned. Block 2 — Define: Her three strongest project stories → Done state: three story outlines with situation, action, result. Block 3 — Create: Practicing her answer to “tell me about a time you solved a complex problem” out loud → Done state: one full practice answer recorded on her phone, imperfect is fine.
Three focused sessions instead of one chaotic hour. She goes into the interview with actual prepared material.
The Three Questions: Why They Work
When you sit down to define a context block, answer these three questions in order:
1. What exists right now that I’m working from? (Nothing / a vague idea / a draft / a finished thing)
This forces orientation before action. Starting from nothing is generative — making something from air. Continuing from a draft is evaluative — assessing and improving what’s there. They require different modes. Without naming the starting point, your brain figures it out by drifting, and the drifting is where time disappears.
2. What’s the one specific thing I want to exist or be decided by the end?
The word “one” is doing real work here. Not three things, not “progress,” not “a better version of.” One specific thing. Specificity is what makes it navigable.
3. Am I making it, planning it, questioning it, or gathering for it?
Once you name the mode, violations become visible. You’ve created a rule for the session, and rules make drift detectable.
Together, these three questions give your brain a complete enough picture that it doesn’t go looking for missing pieces mid-session. Most drift is your brain trying to answer one of these questions that you never answered before you started.
Why 45 Minutes, Not 30
Thirty minutes creates anxiety. You spend the first ten getting oriented, the next ten actually working, and the last ten watching the clock. You get maybe fifteen minutes of real depth.
Forty-five minutes gives you runway — ten to enter the task, twenty-five of genuine depth, ten to bring it to a close state. You’re not rushing. You have enough time to get somewhere real.
After 45 minutes: stop. Did you reach the done state? If yes, close the block. If no, ask why — was the done state too big? Did setup take too long? Adjust and try again. The stopping matters as much as the starting.
What To Do When It Still Doesn’t Work
Sometimes you’ll define the block perfectly. Right mode, specific object, clear done state. You sit down. And it still doesn’t flow.
This happens. It’s not a sign the system is broken or that you are.
When it does, there are usually two culprits. The first is that the object is still too large — it feels specific but it’s actually hiding a decision you haven’t made yet. If you find yourself staring at the blank rather than producing, ask: is there a question I’m trying to avoid answering before I can start? Name that question, answer it, then return.
The second culprit is state, not structure. Some days the regulatory system is just low — you’re tired, overstimulated, emotionally depleted. No framework fixes a nervous system that needs rest. On those days, the move is to shrink the done state to something almost embarrassingly tiny, just to get one closed loop before you stop. One sentence. One annotation. One decision documented. Close one loop, feel that, and give yourself permission to be done.
The goal of context blocks is not to make hard work feel easy. It’s to make sure that when you do have the capacity, it lands somewhere instead of disappearing.
The Context Drift Log: How to Learn From Your Own Patterns
For two weeks, every time you catch yourself switching modes mid-block, write it down. Just a line:
Was in: Create. Drifted to: Explore. Pulled by: wanted to check if my approach matched what other designers do.
You’ll start seeing patterns within days.
Maybe you always drift to Explore when anxious about direction — because gathering feels safer than making something that might be wrong. Maybe you Critique too early because your standards are high and imperfect intermediate states feel unbearable. Maybe you drift to Communicate when you want external validation before you’ve finished enough to share.
None of these drifts are character flaws. They’re information. They tell you where your specific brain looks for safety when the work feels threatening. Once you know that, you can design against it.
Anxious about direction? Build an Explore block before the Create block so that question gets answered before it becomes a mid-session intrusion.
Critiquing too early? Write “no evaluating until the timer goes off” at the top of your document before you start.
Craving validation mid-session? Schedule a Communicate block at the end of the day where you share something. Give yourself something to look forward to, after.
A Note on ADHD, Hyperfocus, and Why You’re Not Broken
If you read this far and recognized yourself in a painful and specific way — the chaos, the hours that disappear, the gap between capability and output — there’s something worth naming.
A significant number of people who struggle with exactly this have ADHD or similar executive function profiles. ADHD brains don’t struggle with effort. They struggle with regulating where effort goes. The internal governor that tells most people “stay here, this task matters, don’t leave yet” fires inconsistently — only when the brain detects genuine interest, novelty, urgency, or emotional significance.
This is why the work feels fine some days and impossible other days. It’s not mood. It’s not motivation. It’s whether the task conditions have triggered enough signal to keep the regulatory system engaged. And it’s why hyperfocus happens — when conditions are right, the same brain that can’t sit still for a boring task can work for six hours without looking up. That’s not inconsistency. That’s the neurological profile doing exactly what it does.
Context blocks help because they create artificial versions of the signals your brain is looking for. A specific done state creates miniature urgency. A named mode creates a novelty signal — “this is a specific kind of thinking, not just generic work.” A 45-minute boundary creates a soft deadline. You’re not fixing your brain. You’re feeding it the conditions it needs to engage.
And here’s what’s worth feeling genuinely good about: the people who’ve thought most carefully about their own cognition, who’ve built the most creative systems for compensating, who end up producing the most original and deeply considered work — disproportionately have brains like yours. Richard Branson. Simone Biles. Solange Knowles. David Bowie. Agatha Christie. People who didn’t fix their brains. Who designed lives and systems around the brains they actually had, and then did things nobody else could do precisely because their brains worked differently.
Your slowness is partly a symptom of your depth. The sensitivity that makes it hard to feel done is the same sensitivity that makes you see more, care more, and produce work with more texture than people who find this easy. Their speed is real. But so is your depth. You just need the right structure to let it land.
How to See Your Progress: Turning Something Abstract Into a System
This is the section most productivity writing skips, and it’s the most important one for people whose struggle is invisible.
The hard thing about changing an executive function pattern is that the results are behavioral and internal — sessions feel different, things get done more smoothly — but it’s easy to miss that progress if you’re not tracking the right things. And if you can’t see it, you’ll feel like it’s not working even when it is.
Here’s how to make it visible. Start with just one thing.
Start here: Done State Completion Rate
At the end of each block, write one word: Yes, Partially, or No. Did you reach the done state you defined? If partially or no, one sentence about why.
That’s it for week one. Just this. You’re training yourself to notice whether sessions close or stay open — and you’re building data about your own accuracy. Over time you’ll see your completion rate improving, either because your done states are getting better calibrated or because you’re staying in mode longer. Both are wins.
Add this in week two: Drift Catches
How many times did you notice yourself switching modes and actively return? Write the number. This number going up before it goes down is a good sign — awareness has to develop before behavior can change. Five catches in a session is five more than you had last month. That’s real.
Add this in week three: Weekly Artifact Count
How many things did you complete this week that you could point to or share? A finished section. A diagram ready for feedback. A post published. An email sent. The number doesn’t need to be large — it needs to be countable. Three completions a week is 12 a month, 144 a year. 144 finished things is a portfolio, a reputation, a body of work that didn’t exist before.
A simple log to keep somewhere you’ll actually look:
DATE:
Block defined? Y/N
Mode:
Object:
Done state:
Reached it? Y / Partially / N
Why (if not):
Drift catches: [number]
Weekly artifact count:
Weekly reflection (one sentence):
At the end of each week, five minutes looking back. When were your best sessions? What time of day? Which modes come most naturally? What pulls you off course consistently? This data is about your brain specifically. Nobody else’s will tell you what this does.
How to Start Today
Not this week. Today.
Before your next work session, write this sentence out:
“I am ____ing [specific thing] until I have [specific thing that will exist].”
Take up to three minutes. If you can’t fill in the blanks, spend those three minutes figuring out why — is the object too vague? Do you not know your mode yet? Each “why” is information.
Then set a 45-minute timer. Open only what you need for this specific block. When you drift — and you will — notice it, name it, return. No self-punishment. Noticing is the skill. You’re building it right now.
At the end of 45 minutes: one word. Yes, Partially, or No. That’s your first data point.
Do that again tomorrow. And the day after.
You were never lazy. You were running a sophisticated brain without the user manual for it, in a world that designed its productivity tools for a different kind of brain entirely.
The fact that you kept going — kept trying, kept caring about the work, kept believing it could be better — while also feeling like something was fundamentally wrong with you? That takes a particular kind of strength that people who find this easy will never need to develop.
If this landed for you, share it with someone who needs it. I certainly did.
Written with Claude; the thinking, structure, and curation are mine.
Until next time,
Tanisha
Such a detailed analysis of something so common. Amazing read.