Quick Answer: Finishing feels worse because the last stretch removes every reward the project was giving you. Early knitting delivers fast visible progress, novelty, and the pleasure of an imagined finished object. The end delivers slow visible progress, repetitive finishing tasks, and the risk that the real object will not match the imagined one. The fixes are structural: finish as you go, make the last 10% a separate scheduled activity, and lower the stakes on blocking day.

If you have three nearly-finished projects in a basket, this is the mechanism, and it is extremely common.

Why does progress feel slower at the end?

Because it genuinely is, and because the rewards change shape.

Early rows are short and fast. Cast on a top-down sweater and the first inches fly. Each row is visibly different from the last, and visible change is what your brain registers as progress.

Late rows are long and identical. By the time you are on the body or a second sleeve, each row takes several times as long and produces a change you cannot see without measuring. The same effort now buys visibly less.

Second sleeve syndrome is the pure form of this. You already know exactly how it goes, there is nothing to learn, and completing it produces no new information. Novelty was doing a lot of the work and now it is gone.

Finishing tasks are a different craft entirely. Weaving in ends, seaming, picking up a neckband, and blocking are not knitting - they are a set of fiddly, unrewarding, error-prone tasks that happen to be attached to knitting. People who love knitting are not obliged to love finishing, and pretending otherwise is why the basket fills up.

And the imagined object is at risk. While unfinished, the sweater can still be perfect. Finishing it converts a possibility into an actual garment that might not fit, and that is a real, if unspoken, disincentive.

What is the psychology underneath it?

Three well-documented effects, all pushing in the same direction.

The goal-gradient effect says motivation increases as you approach a goal - and it works beautifully when progress is visible. When the final stretch is measured in unglamorous tasks rather than in centimetres, the gradient flattens and the effect fails to help.

The Zeigarnik effect - unfinished tasks occupy mental space - explains why the unfinished basket is quietly draining. Each unfinished project holds a small amount of attention permanently. Three of them is a noticeable background load, and it is often felt as a vague reluctance to start anything new.

Loss aversion applies to the imagined object. An unfinished sweater is potential; a finished one is a verdict. Not finishing preserves the possibility that it would have been perfect, and that trade is made below conscious awareness.

Novelty drives dopamine, and repetition does not. Casting on delivers a genuine reward hit. The second sleeve delivers none. This is a neurological pattern rather than a character flaw, and treating it as a character flaw is what makes people feel bad about a basket of unfinished knitting.

Which means the solutions are structural, not motivational. You are not going to want to weave in ends. Build a system that does not require wanting to.

5 Mistakes That Guarantee an Unfinished Basket

1. Leaving all the ends until the very end. Twenty ends waiting at the finish line is a genuinely unpleasant hour. Weave them in as you go, at every colour change or joined ball. It costs nothing in the moment and removes the worst single barrier.

2. Knitting sleeves last, and separately. Both sleeves at once on one long circular or two circulars means you finish them together and never face a second sleeve alone. This one change resolves more abandoned sweaters than any other.

3. Casting on something new while the last thing is at 90%. The new project is intensely rewarding precisely when the old one is least rewarding. A rule of one 90%-complete project at a time is arbitrary and works.

4. Treating blocking as a scary final exam. Blocking is reversible for most fibres, it fixes a remarkable amount, and it is not a test. Wet, pat to shape, leave to dry covers the majority of garments.

5. Making the finishing session an evening entertainment. Weaving in ends while watching something is slow and error-prone, which makes it feel worse. Twenty minutes in daylight with good scissors and a proper needle finishes it faster than two hours on the sofa - and once it is done, it is done.

What actually gets projects finished?

Systems that assume you will not feel like it.

Schedule the finishing separately. Put a 30-minute finishing session in the diary as its own activity, not as the tail end of a knitting evening. Finishing is a different craft and deserves its own slot.

Set a visible finish line. Count the remaining rows and write the number down, then cross off as you go. Turning invisible progress into a visible countdown restores the goal-gradient effect that the plain fabric removed.

Use the 10-row rule on bad days. Ten rows, then permission to stop. Most sessions continue past ten, and the ones that do not still moved the project forward.

Finish in company. A knitting group, a video call, or simply someone else in the room. Boring tasks are dramatically more tolerable with ambient company, which is why knit-nights exist.

And know when to let one go. Some projects should be frogged. If a project has sat untouched for a year, does not fit, or was never going to suit you, the yarn is worth more than the guilt. Reclaiming it is a completion of a sort, and it frees the mental space the Zeigarnik effect was quietly charging you for.

The seasonal timing is on your side right now. Late August into September is the natural start of knitting season - evenings lengthen, wool becomes appealing again, and there is a genuine reason to want a finished sweater. Finishing the three near-complete projects before casting on the autumn one is both practical and, unusually, motivating.

FAQ: Finishing Questions, Answered

How do I get through second sleeve syndrome?

Knit both sleeves at the same time on one long circular or two separate circulars. If the first is already done, break the second into scheduled chunks with a written row countdown rather than trying to do it in one sitting.

Should I finish old projects before starting new ones?

A workable rule is one nearly-finished project at a time. Multiple projects at different stages is fine and often helpful - multiple projects all at 90% is what produces the stuck feeling.

Is it normal to lose interest at 80% complete?

Extremely. Novelty drops, visible progress slows, and finishing tasks are a different craft. Nearly every knitter experiences it, and the ones who finish reliably have systems rather than more willpower.

When should I give up on a project?

When it has been untouched for a year, when the fit is wrong beyond rescue, or when you know you will not wear it. Frogging is a legitimate outcome and the yarn is worth reclaiming.

Does blocking really make that much difference?

For most natural fibres, yes - it evens stitches, opens lace, and settles the fabric. It is also largely reversible, which makes it much less of a high-stakes moment than it feels like the first few times.

TL;DR:

• The end feels worse because it removes the rewards: fast visible progress, novelty, and the safely imagined finished object.
• Goal-gradient, Zeigarnik, and loss aversion all push the same way - this is structural, not a lack of discipline.
• Fixes: weave in ends as you go, knit both sleeves at once, one 90%-project at a time, and schedule finishing as its own 30-minute activity.
• Write a row countdown to make invisible progress visible, use the 10-row rule on bad days, and frog what is genuinely dead.

The thing worth internalising is that finishing is a separate craft from knitting, with its own tools, its own pace, and its own slot in the week. Once you stop expecting it to feel like knitting, it stops feeling like a failure that it does not.