One Large Creative Project vs Several Small Ones: A Practical Comparison

There is a particular kind of tiredness that comes from a big project. It sits in the shoulders after four hours of the same problem, and it feels oddly satisfying. There is another kind that comes from a week of small projects — five things started, three finished, two hovering in a folder — and it feels less like tiredness than like static. Both are legitimate ways to work. They just ask different things of you, and most creative frustration comes from choosing one shape and expecting the rewards of the other.

What follows is a practical comparison, not a verdict. The useful question is never which approach is better in general, but which one fits the months you actually have.

What a large project demands of your attention

A large project — a book draft, a full collection of work, a documentary edit, a body of illustrations — needs continuity. You have to carry a lot of context in your head: what has already happened, what the tone is, which decisions you made three weeks ago and why. The value of that continuity compounds. By week six you make decisions faster and better than you did in week one, because you are no longer reintroducing yourself to your own material.

The focus advantage

This is the quiet gift of going big. You stop spending the first forty minutes of every session remembering where you were. The work develops a spine. Even on a mediocre Tuesday you are moving the same organism forward rather than tending five separate pots.

The focus trap

The trap is that a large project is very good at absorbing avoidance. You can spend a whole day reorganising files and call it progress, because there is no external checkpoint to tell you otherwise. Large projects also fail silently for long stretches: you can be three months in before it becomes clear that the middle section does not hold. Small projects tend to break loudly and early, which is unpleasant but instructive.

Momentum, and the cost that small projects hide

Working on several smaller pieces gives you frequent wins and frequent feedback. You finish things. Finishing is a skill, and small projects let you practise it weekly instead of annually. That matters more than it sounds: people who only ever work on large projects often have surprisingly little experience with the specific discipline of shipping.

But the switching cost is real, and it is almost always underestimated. Every time you move between projects, you pay a tax in setup and re-entry. If you keep four efforts alive in a fortnight, you may spend more time reloading your own thinking than doing it.

• Context reload. Re-reading notes, reopening files, remembering which version is current.
• Tool shuffling. Different software, different materials, different setups, each needing their own warm-up.
• Emotional re-entry. Getting back into the mood of a piece you last touched nine days ago.
• Decision fatigue. Choosing what to work on becomes its own daily chore.
• Stale endings. Small projects that never get their last ten percent because something new arrived.

None of these are fatal. But if you are running five small projects and feeling busy without feeling productive, the tax is probably the reason.

Deadlines: one long runway versus many short ones

A single large project usually has one distant deadline, if it has one at all. That is a structural problem. A deadline eight months away is not a deadline; it is a mood. The work expands to fill the space, and the last six weeks carry a burden the first six months should have shared.

Small projects give you more checkpoints, more chances to be seen, and more opportunities to correct course. A photographer who shoots twelve small series in a year learns faster than one who spends the year on a single monolithic body of work with no interim review — provided the small series are actually finished and shown to someone.

If a project has no checkpoint between now and the end, it does not have a deadline. It has a hope.

The practical fix for the large project is to manufacture internal deadlines: a first act finished by a certain date, a rough version shown to two people, a section sent to a friend who will actually reply. These are artificial, and they work anyway.

Energy: marathon versus intervals

A big project rewards long, protected blocks. Two or three hours in one stretch will do more for a manuscript than six twenty-minute fragments, because the deep part of the work only arrives after the shallow part is exhausted. This means a large project is expensive in calendar terms: it wants your best hours, not your leftovers.

Small projects are more forgiving. They fit into the gaps — a sketch before work, a paragraph at lunch, an hour on a low-energy evening. They also tolerate interruption better. The cost is that they rarely take you into the deeper, stranger territory that only appears after sustained attention.

So the honest comparison is this: a large project asks for fewer hours but better ones; several small projects accept worse hours but demand more of them. If your weeks are fragmented by caregiving, a day job with unpredictable demands, or health that varies, small projects are often not a compromise but the correct choice. Planning against your real life is not a lack of ambition.

Finding a middle path

Most people do best with a primary project plus something small and regenerative, rather than a pure version of either. Try this sequence:

1. Name one primary project for the next three to six months. One. Write it down with the finish line described in concrete terms.
2. Give it your best hours — the same slots each week, protected in your calendar before anything else claims them.
3. Add one small project that uses a different muscle: something by hand if your main work is on screen, something short if your main work is long.
4. Cap the small projects at one or two. When a new idea arrives, put it in a file labelled "later" rather than starting it immediately.
5. Set a checkpoint at the halfway point of the big project and show the work to someone, even unfinished.
6. Review at the end of the season. Did the big project get the hours it needed? Did the small ones actually ship?

Signs you have chosen badly

If your large project has drifted for a month with no visible progress, the problem is usually the absence of checkpoints rather than the size. If your small projects keep multiplying while nothing finishes, the problem is the absence of a cap. Both are fixable with structure, not with more willpower.

A practical way to decide

Before you commit, answer three questions honestly. How many uninterrupted hours can you protect in a normal week — two, six, fifteen? What do you need most right now: depth, or the experience of finishing? And what has actually worked for you in the past year, not in theory but in your calendar?

If you can protect long blocks and you have something substantial to say, go large, and build checkpoints into it. If your weeks are choppy or you are rebuilding your confidence after a stalled period, go small — but cap the number and finish each one properly before starting the next. Then write the decision somewhere visible, with the date you will review it. The shape of your working months is a choice, and it gets much easier once it is a deliberate one.

Photo: Firmbee / Pixabay