The essentials at a glance

  • Planning creates reliability: It shows which tasks build on one another, where dependencies lie, and which deadlines are realistic.
  • Three questions to get started: Sequence, dependencies, and time – that’s all you need for the initial plan.
  • Kanban and planning go hand in hand: Kanban shows what’s happening right now. A timeline shows when things are supposed to happen.
  • Visual timelines provide orientation: A Gantt chart aligns tasks, dependencies, and milestones on a single line.
  • A shared space helps: Planning stays effective when it takes place in the same space as tasks, context, and coordination.

In day-to-day project work, this becomes apparent quickly. The draft is done, but approval is pending. The concept is in place, yet implementation is waiting on a decision. Tasks get ticked off, yet the deadline draws closer without anyone knowing if it will be met. Progress only becomes reliable when three questions are answered: What happens when, what depends on what, and what needs to be in place by when?

When everything’s moving but nothing’s clear

In the last part of this series, we looked at workflow. With Kanban, teams get moving, tasks are completed step by step, and the workflow becomes visible to everyone. That answers one important question: What’s currently happening? However, as soon as deadlines, milestones, or multiple stakeholders come into play, a second question arises: When will things happen? A timeline answers exactly that. It shows whether a milestone is realistic in three weeks, whether sign-off will come in time, and whether a task can start because the previous one is completed. Kanban keeps work moving. Planning gives that movement a destination and a date.

The real problem: when deadlines rely on gut feeling

Many teams are more structured than they realise. Yet time planning often remains surprisingly vague. That’s when you hear things like:

“We should be able to get this done by the end of the month.”

“The draft is almost finished.”

“Hopefully sign-off won’t take long.”

“If nothing comes up, we’ll be fine.”

These phrases slip into conversations easily, but in project work they are warning signs. They show that the project timeline is based more on experience, hope, and intuition than on any shared plan.

As long as the deadline is far away, this hardly registers. It’s only towards the end that the mood shifts. Follow-up questions become urgent, sign-offs become critical, and minor delays turn into real risks. The real cause sits further back: Time-based dependencies simply become visible too late.

Realistic planning not only creates reliability but also provides relief: Everyone involved knows earlier what is needed and when, and there is far less scrambling at the end.

The shift in perspective: from “what’s been done?” to “what will be achieved when?”

So far, this series has looked at tasks, relationships between tasks, visible progress, and workflow. Now a new question arises: When will each outcome be achieved?

This small shift significantly changes how a project is managed. When planning problems arise, many teams respond with more activity: starting faster, assigning more tasks, increasing coordination. What really helps is asking a different set of questions. What sequence makes sense, which dependencies must be considered, and how much time do the steps realistically require? Once these three points are clear, the team has a plan it can rely on in everyday work.

What constitutes good project planning

Good project planning is simple. Three questions are enough to get started, and they apply to any project – whether it’s a marketing campaign, a rollout, or a product launch:

1. In what order does the work need to happen?

Content needs to be finalised before design is locked in. The technical review runs first, then sign-off follows. Clarifying the sequence early avoids idle time and duplicated effort.

2. What dependencies exist?

Delays usually arise between tasks rather than within the team itself. Someone is waiting for feedback, a department delivers data late, or an external partner needs an internal decision. Knowing these interfaces allows you to build buffers where they’re actually needed.

3. How much time do the individual steps require?

Realistic assumptions beat perfect predictions. If approval typically takes five days, it should be planned as five days. If three rounds of coordination are needed, they should each have a slot on the timeline.

Planning a project means making its structure visible – linking tasks, dependencies, and deadlines. Sequence, dependencies, and time are usually enough as a first planning framework.

When project planning really pays off

For a single task, clear ownership and a deadline are often enough. Project planning becomes essential when multiple teams are involved, fixed deadlines are in place, or external partners come into play.

A launch, a rollout, a client meeting, or a board presentation all carry a hard time expectation. At that point, alongside the question “What needs to be done?” comes another: “When does each interim result need to be in place?” The more people and dependencies converge, the more valuable a shared picture of the timeline becomes.

Kanban and project planning: two perspectives, one picture

At first glance, Kanban and project planning may seem like two different approaches. One fluid, the other time-bound. In practice, they work hand in hand.

Kanban shows the current workflow: which tasks are in progress, where work is waiting, and where bottlenecks arise. The timeline adds a second layer: which tasks follow one another, which milestones matter, and whether the planned sequence remains realistic. Together, they create a shared picture of movement and direction.

A real-world rollout example

A cross-functional team is preparing the rollout of a new internal service process. Communication, training, technical adjustments, and approvals all need to interlock before other departments can start using it. The board is set up, responsibilities are clear, and work is underway. Yet one question remains: Does the sequence actually make sense? Can training materials be finalised before the pilot group has given feedback? How long will approval really take?

With a timeline, the perspective on the same tasks changes. The pilot phase moves earlier, technical adjustments gain buffer time, final approval becomes its own milestone, and the communication launch is given a fixed place in the sequence. Individual tasks turn into a structured process that shows what must happen first, what can run in parallel, and where additional time should be planned.

How a simple timeline makes dependencies visible

A good timeline is simple. An axis on which tasks, phases, and deadlines are placed side by side is enough to get started. That’s exactly what a Gantt chart provides: Tasks appear as bars on a timeline, duration and sequence become visible, milestones mark key intermediate results, and dependencies can be mapped.

The real value emerges when the team uses the timeline to make concrete decisions and move the project step by step towards completion.

Looking at the timeline together quickly reveals where clarification is still needed:

  • Can these tasks really run in parallel?
  • Who is waiting on whom?
  • Where is a buffer missing?
  • Which decision is blocking the next step?
  • Is the deadline realistic – or just wishful thinking?

This is where project planning becomes immediately effective in day-to-day work: Instead of talking vaguely about “the end of May”, the team can see exactly which steps need to be completed by then.

A template helps with getting started. In Conceptboard, the timeline is built where the team already works: in the shared project space. The Gantt template directly connects tasks, dependencies, and deadlines. The current state of work becomes a shared timeline that everyone can develop further.

Planning and execution belong in the same space

Plans become fragile as soon as they live in a different place from the work itself. The schedule sits in a spreadsheet, tasks are tracked in another tool, decisions are made in meetings, and feedback is scattered across chats and emails. Anyone who wants to know whether the deadline still holds has to piece together a puzzle first. As a result, plans are often updated only after deadlines have already slipped. The timing lags behind reality.

In a shared visual workspace, the timeline stays connected to its context. Tasks don’t sit in isolation on a timeline – they sit directly alongside decisions, materials, feedback, and responsibilities. When tasks, decisions, and the schedule are all visible in the same context, planning remains usable in day-to-day work.

The next step: updating the plan regularly

A timeline is a shared snapshot of the current situation, not a fixed promise. Once work begins, things shift: Feedback takes longer, a decision comes faster, or a new dependency emerges. Good plans are regularly adjusted whenever new information becomes available.

If you’d like to get started straight away, ourproject timeline guidewalks you through it. It shows you how to build a visual project timeline, how to define sequence, dependencies, and milestones, and how to develop realistic timeframes that hold up in practice.

Outlook: when planning meets execution

With tasks, progress, workflow, and timeline planning in place, the framework is set. In day-to-day work, one final question then arises:

How do you maintain this overview when execution moves deep into operational detail?

In many organisations, the overview lives in the visual workspace while tickets are managed in systems such as Jira.

The next and final part of the series explores how these two worlds work together to make project work scalable.

Conclusion: projects become reliable when progress gets a timeline

Even when tasks are moving forward, the key question remains: Will the deadline be met? A project doesn’t become plannable simply because work is visibly progressing. Only when sequence, dependencies, and deadlines are mapped onto a shared timeline can a team see what needs to happen when – and which decisions enable the next step.

Three questions are enough to get started: What happens when, what depends on what, and which deadlines are realistic? This creates a plan that builds reliability and reduces pressure. The team can spot bottlenecks earlier and has far less need to improvise at the end. Kanban gets work moving. Project planning gives that movement a destination.

Build your first project timeline – get started with the Gantt template in Conceptboard