Implementation intentions for freelancers: the simple swap

It's Thursday afternoon. "Finish the proposal for Lars" has been on your list since Monday. You've shipped four other things, billed two invoices, replied to seven emails. Every time your eye landed on that line you thought "later" and scrolled past. You're not lazy. The task is just badly written.

"Finish the proposal for Lars" is a goal. Goals don't tell your hands what to do at 9:14 on a Tuesday. An if-then plan does: "if it's 9am Tuesday and I've poured coffee, I open proposal-lars.docx." That's the whole trick.

What's the difference between a goal and an if-then plan?

A goal names the outcome you want. Finish the proposal. Close the books. Edit the post. Useful for sorting your week. Useless at the moment of starting.

An if-then plan names two things: a trigger you can actually notice, and the first physical move you'll make when you notice it. The trigger can be a clock time, a place, or the end of a previous task. The first move has to be small enough that you can do it without thinking. Open the file. Read the brief.

Behavioural researchers call this implementation intentions, sometimes shortened to if-then planning. The plain-English version: you decide in advance what cue will make you start, so you don't have to decide again in the moment.

Why "finish the proposal" never gets finished

Every open-ended task demands three decisions every time you read it: when do I start, where do I start, how do I start. A salaried designer at an agency has a project manager and a calendar block handling at least two of those. A solo freelancer has none of that. You make every starting decision yourself, all day, for every task.

Most freelancers I've talked to underestimate how much of their day goes to that. It's not the writing or the wireframing that's tiring, it's deciding when to begin the writing, twelve times before lunch. By 14:00 there's nothing left for the proposal. So it slides to tomorrow.

If-then planning moves the decision earlier in time, when you have more bandwidth. You decide on Sunday what Tuesday looks like. Tuesday just executes.

The cue does the work, not the motivation

A reliable cue replaces willpower. You don't need to feel like opening Figma if your "end of Bravo standup" trigger is right there in front of you, written down, sitting on the task itself. The eyes see the cue, the hand opens the file. No internal debate.

Cues that work share a few traits: they happen on a predictable schedule, you notice them without trying, they're visible from the outside, and they don't depend on how you feel. Coffee being poured works. A clock hitting 9am works. The end of a recurring meeting works. "When I have energy" doesn't.

If the cue lives only inside your head ("when I'm in the right headspace"), it isn't a cue at all.

How to rewrite five typical freelancer tasks

Here are the most common backlog items I see in freelancer planners, and the if-then version that actually gets executed.

Proposal writing. Lars is a freelance UX designer. "Wireframes for Bravo" has sat on his list for four days. Rewrite: if it's 14:00 and my standup with Bravo is done, I open Figma file "bravo-onboarding".

Content editing. Noor writes for SaaS companies. "Edit blog post for Tom Tom" has been pending since Friday. Rewrite: if it's the first slot of my Wednesday morning, I open the Google Doc and read it from the top before I open anything else.

Invoicing and admin. Roos is a freelance bookkeeper. "Send Q1 BTW reminder to Mees" sits there for a week. Rewrite: if it's Friday 16:00 and I've closed my last client task, I open the BTW reminder template.

Code review. Tom is a developer working with one main client. "Review Lena's PR" is pending. Rewrite: if I open my laptop after lunch, I open the PR before email.

Client follow-up. Every freelancer has at least one "ping Jelle about the contract" task that's lived three weeks. Rewrite: if I sit down for my Monday morning planning slot, I send the Jelle message before I plan anything else.

Notice what the rewrites have in common. The cue is something the freelancer was already going to do. The first move is one action, not the whole task. "Open the file" is the rewrite, not "finish the wireframes." Starting is the bottleneck, so starting is what the plan handles.

This is also where a planner that ties tasks to time slots earns its keep. If you pin each task to a real time slot instead of leaving it floating in a backlog, the cue is already there. You just need to write the "then" half on the task itself so future-you sees the actual cue next to the task, not just the goal.

Where this fails (and what to do instead)

Two honest limits.

Once Lars opens the Figma file, he still has to draw the wireframes. If-then plans solve the start problem, not the finish problem. For finishing, you need shorter sessions, a deadline that bites, or a client check-in. The plan got you to minute zero. Minutes one through ninety are still yours.

The other limit is cue reliability. "When the kids are at school" only works if that's actually consistent. If half your school weeks get disrupted by sick days and dentist appointments, that cue won't fire often enough to build the habit. Pick cues that survive a normal bad week, not just an ideal one. Event-based cues ("after my Bravo standup") beat clock times when the event itself is reliable.

If you try this for a week and the cues keep missing, it's usually one of two things. Either the cue isn't as predictable as you thought, or the first move is too big. "Write the proposal" is too big. "Open proposal-lars.docx" is the right size. If even that's too big some mornings, shrink it again. Smaller is fine.

The proposal for Lars isn't going to write itself. But it's also not going to write itself with "finish the proposal for Lars" sitting on your list. Pick a cue you'll actually notice tomorrow. Write the if-then version. See what happens by Friday.