This video introduces Pipeline and Stacks – the tools that turn prioritized tickets into a concrete weekly plan for your team.
The Pipeline is essentially a weekly calendar where each row represents a team member and planned tasks appear as colored cards on the timeline. Tickets can be scheduled via dialog or by dragging time blocks directly – in 15-minute increments. Importantly, the card length represents the planned work step for this week, not the entire ticket estimate.
Two view modes support the planning process: Overview shows compact 8-hour blocks per day – ideal for weekly meetings. Spacious view with its 15-minute grid is designed for fine-tuning. The Reality toggle places plan and actual logged hours side by side, allowing you to continuously improve your estimates.
Once the planning is complete, you activate the week. All planned tasks then flow automatically into the respective team members' Stacks – their personal Kanban board with columns for To Do, Give Feedback, Get Feedback, Done, and Backlog. Every employee sees exactly what's on their plate each morning and in what order – no follow-up questions, no self-prioritization needed.
The result is a continuous planning chain: Big Picture → Pools → Pipeline → Stacks. Each step builds on the previous one, and at the end of the chain is focused, uninterrupted work.
Setting priorities is the first step. But at some point, "this is important" needs to become "Max does this on Tuesday".
In this video, I'll show you the Pipeline, the tool for weekly planning. You distribute tickets across your team, see at a glance who has capacity, and by the end, everyone knows exactly what to do this week.
I open Planning, then Pipeline.
What you see here is essentially a weekly calendar for your team. On the vertical axis, you have your team members, one row per person. On the horizontal axis, you see the weekdays, divided into time blocks.
The colored cards on the timeline are planned tasks. Each card is a ticket, assigned to a specific person at a specific time.
In the top right, you can navigate between weeks using the arrows. And you can see the status of the week, whether it's active or still being planned. More on that in a moment.
The basic principle: you take the prioritized tickets from the pools and distribute them here to specific people and time slots. "Important" becomes "who does it when".
There are two ways to add tasks to the pipeline.
The first way: I click "Add task to pipeline". A dialog opens where I select the ticket, assign the team member, and set the start and end date along with the times.
The second way is even faster: I drag directly in the week view to create a time block on the desired row. The system automatically suggests the person and the time range. Then I just select the ticket, and it's done.
Important: the length of the card in the pipeline corresponds to the planned working time for this step. This doesn't have to be the full estimate of the ticket. If a ticket is estimated at 20 hours total, but you only plan 4 hours for it this week, then the card is 4 hours long. The pipeline shows the next concrete work step, not the entire ticket.
The time grid is divided into 15-minute blocks. So you can plan very precisely.
The pipeline offers two view modes, and they're incredibly useful depending on the situation.
Overview shows each workday as an 8-hour block. Compact, clear. Perfect for the weekly meeting when you want to quickly see how the week looks overall. Who's fully booked, who still has room?
Spacious shows each day in 15-minute increments. Detailed, precise. Here you can place and adjust individual tasks exactly. This is the mode for fine-tuning.
You switch as needed: first use the overview to roughly distribute the week, then switch to spacious view to adjust the details.
And then there's the Reality toggle. When you activate it, you see not only the planned tasks but also the actual logged working hours. Plan and reality side by side.
This is extremely helpful for improving your planning. How long did tasks actually take? Where did we underestimate, where did we overestimate? These insights make each following week a bit more realistic.
When the planning is ready, you click "Mark as active". This publishes the week.
And now something crucial happens: all planned tasks are automatically transferred to the stacks of the respective team members. In exactly the order you set.
This means no employee needs to ask what comes next. No team lead needs to distribute tasks one by one. The planning flows automatically into each person's personal work list.
As long as a week isn't active yet, it's a draft. You can plan, rearrange, discuss in peace, and only when everything fits, you activate it.
I open Planning, then Stack.
The stack is each team member's personal Kanban board. Here every developer, every specialist sees exactly what needs to be done this week, and in what order.
The view is divided into columns.
To Do: the tasks for this week, sorted by priority. The top task gets worked on first.
Give Feedback: tasks where the developer should provide feedback to others. These should be handled first, because they're usually quick and can unblock other colleagues.
Get Feedback: tasks waiting for a response from someone else. The responsible account manager gets notified automatically.
Done: completed tasks.
Backlog: tasks that aren't planned for this week but can be earmarked for upcoming weeks.
The workflow is simple: the developer starts in the morning with the top task in To Do. Finishes it, moves it to Done, takes the next one. If a question comes up, they move the ticket to Get Feedback and continue with the next ticket. No standstill, no waiting.
The goal of Stacks is this: no employee needs to prioritize on their own. No follow-up questions needed. Focused, uninterrupted work.
You've now seen the complete planning chain.
Big Picture for prioritization within a project. Pools for the cross-project view. Pipeline for weekly planning at the person level. And Stacks as a personal, prioritized work list.
Each step builds on the previous one. And at the end, everyone on the team knows exactly what to do this week. No follow-up questions, no uncertainty.
In the next video, we'll look at the billing system, how you turn the work that's been done into invoices.
