Stop Holding the Whole Project in Your Head: A Work System for Tiny Teams

Your memory should not be the project system

A founder described a familiar source of friction: larger solo projects lasting a month or more lacked structure, leaving them carrying the entire project in their head. In a tiny team, that same pattern makes the founder the default source of context, priorities, and next steps.

The answer is not necessarily more software or more meetings. It is a small, shared system that answers four questions: What are we trying to achieve? Who owns what? What happens next? Where are we stuck?

Your leadership task is to make the work understandable without making yourself essential to every update.

1. Start with a one-page project brief

Before creating a task list, write down the project's purpose and boundaries. For a month-long effort, a short document is usually enough to start.

Include:

• Outcome: What should be different when this is finished?
• Definition of done: What observable evidence will show completion?
• Scope: What is included, and explicitly excluded?
• Constraints: What deadlines, budget limits, or dependencies matter?
• Project owner: Who keeps the overall work moving?

For example, “improve customer onboarding” is a direction, not a finish line. A clearer outcome is: “Publish a revised onboarding flow, test it with three customers, and resolve any issues that prevent completion.” This is an illustrative target, not a universal benchmark.

If you are working alone, write the brief anyway. It gives you somewhere to return when urgent requests interrupt your thinking.

2. Empty your head, then organize the work

Set aside 30 minutes to capture everything you currently remember: tasks, questions, risks, promises, dependencies, and unfinished decisions. Do not try to organize it while capturing it.

Then separate the list into:

• Deliverables: Things the project must produce.
• Actions: Specific steps someone can take.
• Decisions: Choices needed before work can continue.
• Later: Ideas that do not belong in the current scope.

This distinction matters. “Choose a payment provider” is a decision; “configure the selected provider” is an action. Combining them hides the real reason work cannot move forward.

Record important decisions with a date and a sentence explaining why. Future you should not have to reconstruct the reasoning.

3. Break the project into visible milestones

A long task list can still leave you unsure whether the project is progressing. Group the work into a few milestones that produce something reviewable.

For an onboarding project, those might be:

1. Current problems documented and priorities agreed.
2. Revised flow ready for testing.
3. Customer testing completed and findings reviewed.
4. Changes released and handoff completed.

Work backward from any genuine deadline, noting dependencies. Detail the next week or two; keep later work broader until you know more.

Each active task should describe a concrete next action. Replace “work on onboarding” with “draft the welcome email and send it for review.”

4. Use one shared board with clear ownership

Use a tool your team will actually open. A spreadsheet or simple task board is enough. Start with four statuses: Next, Doing, Blocked, and Done. Keep later ideas outside the active queue.

For each active item, record:

• One accountable owner.
• The expected output.
• Its milestone.
• A due date or next review date.
• Any dependency or decision needed.

Multiple people can contribute, but one person should be responsible for moving the item forward. Agree on what they can decide independently and when they should involve you.

Limit simultaneous work. Start with one main active task per person and adjust for your reality. If everything is “Doing,” the board cannot show what deserves attention.

5. Create a rhythm that replaces chasing

Hold a short weekly review using the board, not a separate presentation. Ask:

• What finished, and does it meet the definition of done?
• What is blocked, and who will unblock it?
• Has the next milestone or forecast changed?
• What are we committing to next?

Owners should update their items before the review and flag urgent blockers when they arise. Do not wait a week to surface a dependency that stops today's work.

For solo projects, keep the same appointment with yourself. End each work session by recording your next action so restarting does not require rebuilding the entire project mentally.

6. Check whether the system reduces dependence on you

After two weeks, ask whether someone can understand the project's status without messaging you. Can they find the next milestone, current owners, and unresolved decisions?

If not, fix the missing information before adding more process. Remove fields nobody uses. Clarify ownership where updates still depend on your reminders. The goal is reliable shared visibility, not perfect documentation.

The Leadership Reset Workbook creates space to reflect on your leadership, priorities, and personal development while your company scales. For leaders who want personal support turning that reflection into clearer ownership and sustainable working habits, consider a coaching call with Jessica Hill Holm.