Project Planning with Free Tools: Kanban, Decision Matrix

Most solo makers and small teams do not need project management software. They need a clear next action, a short list of what is blocked, and a way to stop arguing about what to do next. Heavyweight enterprise tools — with dependencies, burn-down charts, resource allocation — exist because big teams genuinely need them. Small teams that adopt them too early spend more time maintaining the tool than shipping the work.

This guide walks through a lightweight project planning stack built from free browser tools: a kanban board for active work, a decision matrix when you have too many options, time blocking for heads-down execution, and the handful of planning practices that actually move projects forward.

Kanban, the simplest viable board

Kanban started in Toyota factories and was adapted for software by David J. Anderson in the mid-2000s. The core idea is three columns: To Do, In Progress, Done. Cards move left to right as work progresses. That is the whole system.

Two rules make kanban actually useful:

• Work in progress limit. Cap the number of cards in the In Progress column. Two or three for a solo maker, maybe five for a small team. When the column is full, you cannot start new work until you finish something. This forces focus.
• Pull, do not push. Work moves into In Progress because someone has capacity, not because someone else has capacity to delegate. This prevents the "I assigned it to you two weeks ago and you never picked it up" failure mode.

Use Kanban Board for a browser-based board that you can share via URL. Everything stays in your session — no signup, no cloud, no "which workspace is this in" confusion. If the project grows to the point where you need assignees, due dates, and comments, a dedicated tool becomes worthwhile. Until then, a simple board is enough.

The Scrum Guide and Atlassian's agile overview are good independent references if you want to understand where kanban fits alongside scrum, sprints, and other agile practices.

Decision matrices for paralyzing choices

Every project has decisions where you have several options, each with different pros and cons, and you cannot tell which is best by staring at them. A decision matrix forces the comparison to be explicit. You list the criteria that matter, weight them by importance, score each option on each criterion, and total the weighted scores.

The output is rarely a clear winner — if it were, you would not have been stuck. What the matrix gives you is one of two things:

1. The highest score is genuinely the best option, and you can move forward with confidence.
2. The highest score feels wrong, and that discomfort tells you a criterion is missing or miscalibrated. Adjust the matrix and run it again.

The second outcome is the more useful one. A decision matrix surfaces hidden preferences — the ones you feel but had not named. That is often the real work of making the decision.

Use Decision Matrix for quick weighted-scoring comparisons. It is most useful for decisions with three to seven options and three to six criteria; beyond that, the matrix gets harder to read than the decision deserves.

Time blocking the week

Kanban tells you what to work on. Time blocking tells you when. Without a time block, the most urgent-feeling work wins, which is rarely the most important work. With a time block, you reserve specific hours for specific categories of work and defend them against incoming interruptions.

A simple time block week:

• Mornings: deep work. Two 90-minute blocks of single-topic focus, no meetings, no messaging.
• Early afternoon: shallow work. Emails, small tasks, administrative cleanup.
• Late afternoon: meetings and collaboration. Batched, not scattered through the day.
• One "maker day" per week. A full day reserved for sustained work on a single hard problem.

The trade-off is obvious: time blocks feel rigid, and the modern messaging-driven workday resists them. The reward is also obvious: sustained focus on real work, not reactive firefighting.

Use Time Blocking Planner to draft a block structure for your week, or Weekly Planner for a less structured list that still captures commitments across the week. For the execution phase inside a block, Pomodoro Timer gives you the 25/5 cycle that keeps focus from decaying mid-block.

The weekly planning ritual

A project planning system works only if someone reviews it regularly. The weekly ritual is a thirty-minute meeting with yourself (or your team) at a fixed time each week. You look at the kanban board, clear done items, update the status of in-progress items, and pull new items from the backlog. You re-check the priorities against the next week's goals.

A typical weekly review:

• What did we finish this week? Move to Done.
• What is in progress? Is it still on track?
• What got blocked? Why? What is needed to unblock it?
• What are the top three things next week?
• What are we saying no to?

The last item is the one most teams skip. A project plan without explicit "not this week" decisions will gradually accept every request and ship nothing well.

Controlling scope creep

Scope creep is the gradual expansion of a project's work beyond what was originally planned. Someone suggests a nice-to-have, you agree, and two months later the project is twice as big as intended and still not done.

The cheap scope-control techniques:

• Maintain a "next version" list. Every new idea goes on this list instead of into the current scope. Revisit after shipping.
• Time box decisions. Spend fifteen minutes on a small decision, two hours on a medium one. When the box is up, commit and move on.
• Ship the smallest useful thing. Launch version 0.1, then improve. Scope creep thrives on "let me just add one more thing before launch."
• Define "done" up front. A task with an ambiguous completion criterion never finishes.

Formal project management bodies like the Project Management Institute publish detailed guidance (the PMBOK Guide) on scope management for larger projects. For a solo maker, the techniques above are usually enough.

Adjacent tools worth bookmarking

Related productivity tools worth knowing: Habit Tracker for the daily habits that make weeks add up, Countdown Timer for deadlines that need to feel real, Meeting Time Planner when collaborators are in multiple time zones, Time Zone Meeting Planner for finding windows that work for distributed teams, Note Taking for capturing ideas during reviews, and Meeting Cost Calculator to put a price tag on every meeting and discourage the unnecessary ones.

Related pillar guide

This cluster is part of the productivity track. For the broader reference on browser tools, see The Complete Guide to Free Online Tools in 2026.

FAQ

When does a project outgrow a lightweight kanban board?

When you need shared accounts, due-date tracking, assignees, comments, or integrations with other systems. For a team of one to three working on a focused project, a simple board is usually fine for months.

How many items belong on a kanban board?

The backlog can be long. The In Progress column should be tightly limited (two to five items). The Done column can accumulate and be archived weekly.

Is time blocking compatible with meetings-heavy work?

Yes, but you have to defend the blocks. If your calendar is open for anyone to book any time, your time blocks dissolve. Mark blocks as busy and treat them as meetings with yourself.

Do I need different tools for personal and work projects?

Not necessarily. Separate boards or separate sections within the same tool usually work. Mixing them is tempting for simplicity and usually fails because the priorities compete.

How do I handle interruptions to a time block?

Distinguish between real emergencies (rare, worth breaking a block for) and urgent-feeling requests (common, not worth it). Log everything that interrupts you for a week and you will see which category most interruptions fall into.

Closing thought

A project plan is not the deliverable. The deliverable is the work the project ships. Any planning tool that gets in the way of shipping is worse than no tool. Start with the minimum viable plan — a kanban board, a weekly review, and time blocks for focused work — and add complexity only when the minimum stops working.