How to plan a big project when you don't have a project team

A person in a cream cardigan sits on the floor over a painted map, tracing a dotted route between six small flags with one finger and holding a magnifying glass.

Here's how to plan a big project with no project team: get every piece onto one list, then draw its edges. Make the decisions that block everything else, agree how changes get in, and decide how it ends.

It might be one line that has sat on your list for a while: "Rebrand," "New CRM," or "Launch the new service."

You know what it should look like when it's done. But every time you sit down to start, you can't tell which piece comes first, so nothing does.

Work through those moves and this project ends up on paper, in a plan someone other than you could pick up.

It works whether you run the project yourself or hand it to someone else. And if this one feels heavier than your normal work, here's why one-time projects are harder than they look.

Get the whole project out of your head and onto one list

Start with what has to exist when the project is finished. Not the tasks yet, the things: the new pages, the updated documents, the system your people log into, and the announcement your customers receive.

Then break each of those into smaller pieces. Keep going until every piece is something one person could do, and you could tell when it's finished. "Switch to the new name" isn't a piece yet. "Order business cards with the new name on them" is.

Now check the list two ways. Is everything the project needs on it? And is anything on it twice? A missing piece turns up later as a surprise. A piece listed twice gets done twice, or argued about.

Before you call the list finished, show it to the people who will do the work. They'll see pieces you can't see from where you sit. The person who sends the invoices knows the invoice template still has the old logo on it.

I'm autistic and ADHD, diagnosed late. A plan that lives only in my head is a plan nobody else can run. So the list goes on paper before anything else happens. Maybe you can see the whole project at once and keep stalling on the follow-through. If that's you, the list does the same job for you. The project stops living in your head.

Draw the edges: what's in, what's out, and what "done" means

A list tells you what the project contains. It doesn't tell you where the project stops. So write that down too, in two columns: what's in, and what's out.

The out column is the one people skip. It feels odd to write down work you've decided not to do. It's also the column that keeps the project the size you agreed to. Say you're moving to a new system. Is cleaning up the old records in, or do they move across as they are? Is the old report getting rebuilt, or retired? Either answer can be right. The trouble starts when there isn't one.

A big project with no written out list keeps growing. Nobody decides to make it bigger. Each addition seems reasonable on its own, so it gets a yes. The small yeses add up to a different project from the one you planned.

Next, write down what the plan is counting on. Maybe it assumes the new name is final, or that the person who knows the old system will be around to answer questions. Write down what limits the plan, too: the money you've set aside and the busy stretch of the year you can't touch. When an assumption turns out wrong, you'll know which parts of the plan it moves.

Then go down the list and write what "done" means for each piece, and who says it's done. "The new pages are live" isn't done. "Live, read through, and approved" is. Without a named person to say yes, a piece can sit at almost finished for a very long time.

Make the decisions that block everything else, first

Look down the list now. Some pieces can't start yet, because they're waiting on a decision. Mark each of those decisions, write down who makes it, and make them before anything else begins.

A rebrand shows it most clearly. The new name has to be settled, and checked that you can protect it, before anyone designs anything. Every design choice depends on the name, so a design started early gets done again. The rebrand rollout plan covers everything that changes after that, and who changes it.

Some of these decisions can only be yours. What the business is called. What it offers. How much you're willing to spend getting there. Make those early, because every piece behind them waits until you do.

Once the edges and the blocking decisions are set, every change on the list needs a finish line and one person who owns it. That's the job of a business implementation plan. Who runs the whole thing is a separate question, and do you need a project manager? works through it.

Agree how changes get in before the first one arrives

Changes will come. Someone sees the new pages and wants one more. A supplier changes something you were counting on. None of that is a problem if there's an agreed way in.

So decide it now, in writing. How does someone ask for a change? Who can say yes? What does the change do to the rest of the plan? Keep one list of changes that everyone can see. A new page might move the launch, or push something else out of scope, and the list is where that gets said.

One rule holds the rest together. A yes in conversation doesn't count until it's on the list. The quick yes at the end of a call, or in a text, is how a project grows without anyone agreeing to it.

Two more things get missed often enough to name here. Launch day isn't the end, because your people still have to start using the new system day to day. And whatever the project leaves behind has to be written down so someone can run it. A project handover checklist covers what that should include.

Decide how your project ends

The last thing your plan needs is its end. Write down where this project stops, and what's true when it does. If you can't say yet, write down when you'll decide. Without a named end, a one-time project slowly becomes permanent work, and nobody remembers agreeing to that.

A one-time project can end in one of three ways. If you already know yours, pick it now and put it in the plan:

  • Whoever runs it finishes it. They take the work to completion, and that's where it stops.
  • Whoever runs it hands it back to you. They build the new process and keep it going until your team is ready for it. Then you take it over, with everything written down.
  • Whoever runs it keeps it going. Choose this if you'd rather not take it back in-house at all.

Not sure yet which end fits? If someone else runs it, you can choose now or decide along the way. Sparkitive can take a list bigger than your team has time for, plan it, and run it to whichever end you pick.

Your list doesn't have to be tidy for a free 30-minute discovery call with me. Bring it as it is, and walk away with your next step.

Book a discovery call

A glowing firefly carries a sealed letter through the night sky

Get The Spark Post, Sparkitive's newsletter

Practical strategies for the big projects, the run of small ones, the processes worth rebuilding, and the work you'd rather pass on, plus the occasional magical blueprint, delivered to your inbox with a spark. You can unsubscribe at any time.

Privacy and terms

You're on the list. Thanks for joining.