Visual planning tools for the Leadtime ticket system
🟦 Why task organization using only lists reaches its limits once a company reaches a certain size
This text provides background information. What types of text are there?
As a digital service company grows, not only does the number of customers increase, but also their expectations for fast and smooth processing of their tasks and projects. At the same time, the number of internal projects and the number of employees assigned to these projects increases. Even a highly motivated team reaches its limits at some point - not every request can be processed immediately. Management must therefore prioritize. But how do you decide which tasks add the most value to the company?
The problem of complexity and prioritization
Let's imagine the following scenario: A support employee is looking after several customer projects at the same time. Each customer expects their tickets to be handled with high priority. However, the individual tickets differ in their urgency, duration and complexity. A well-trained employee may be able to keep track of the tasks in a project. But what happens if this employee is responsible for several projects and each project has a long list of open tasks?

A simple list of tickets quickly becomes confusing here. Each ticket contains details that need to be taken into account when prioritizing: Are there tight deadlines? Which tasks have the greatest impact on customer success? How long does it take to process? Which ticket is particularly complicated or risky? In a growing company that is constantly managing new customers and projects, it becomes virtually impossible to keep track of all this information and prioritize correctly using just a list view.
The basic problem is that everyone involved has a different view of the situation:
- Customer: the customer sees their project as a top priority and expects their concerns to be dealt with quickly and efficiently.
- Administrator: The administrator wants to ensure that all customers are satisfied. To do this, they must prioritize the customer's tickets and find a balance so that important requests are processed without neglecting other customers.
- Team leader: The team leader has an overarching view and must ensure that the team's resources are used in the best possible way. Their task is to ensure that the most important and valuable tasks for the company are completed first.
- Developer: The developer wants to concentrate on one task and complete it without being interrupted by additional requests. It is important for them to work on individual tickets in a focused and efficient manner.
This reveals a fundamental organizational problem - everyone involved has a different perspective and different priorities.
The solution: Visual planning tools for control and prioritization
To meet these challenges, Leadtime offers four specially developed planning tools: Big Picture, Pools, Pipelines and Stacks. These tools create a visual representation of the workload and make it possible to systematically manage the different perspectives and priorities within the company. They help to maintain an overview not only within a project, but across all projects and to make the right decisions.
Big Picture - the customer-oriented project overview

The Big Picture tool is the first step in the planning chain and provides a project overview at individual customer level. It displays all the tasks of a project as visually organized maps that are divided into task types, such as features and bugs . Within these categories, the tasks can be prioritized according to importance.
- Application example: An administrator consults with the customer and discusses which features or bugs currently have the highest priority for them. This helps the customer to formulate a clear order of their wishes and to focus on the most urgent tasks.
- Goal: Big Picture provides a structured and visual overview of the tasks within a project and facilitates coordination between customers and specialists.

Example: A support employee can work with the customer to determine which tasks need to be completed first in order to offer the greatest added value.
Pools - cross-project prioritization for clerks

Pools extend the Big Picture to the multi-project level. Administrators usually look after several customers at the same time and have to balance the priorities between these projects. The pool is therefore a multi-project dashboard in which the tasks of all supported customers are displayed together. This allows the clerk to keep track of all the tickets relevant to them.
- Application example: A clerk who looks after several customers sees the prioritized tickets from different projects and customers next to each other in their pool. This allows them to decide which tasks will bring the greatest benefit to the company in the coming days.
- In addition: The team leader can intervene in the pools and set strategic priorities, e.g. by highlighting particularly revenue-generating tasks.
- Goal: The pools enable the clerk to prioritize across projects and ensure that the most important tasks are processed first to maximize customer satisfaction and value for the company.

Example: A support employee sees that a ticket in project A is urgent, but project B has a greater long-term impact. With the pool tool, he can decide across all projects which ticket has priority.
Pipelines - resource planning and coordination within the team

Pipeline planning is used for the weekly allocation of tasks to team members, especially developers or specialized experts. The aim here is to use the capacities of the team members efficiently and to define a sensible sequence for completing the tasks. The pipeline distributes the tasks across projects and customers throughout the week and shows how much working time is available to each developer.
- Application example: In a weekly meeting, each clerk brings in their prioritized tickets from their pool. The team leader moderates and decides together with the team which tasks are to be processed in which order and with which resource allocation.
- Visualization: The pipeline divides each day into 15-minute sections and provides an overview of how much capacity is available and how the work is distributed over the week.
- Objective: The pipeline serves as a central planning tool to distribute tasks to the specialists in a sensible order and to make optimum use of the available resources.

Example: The support staff coordinate which customer projects have priority and ensure that the developers focus their time on the most valuable tickets.
Stacks - the personal work plan for specialists

The stack is the final tool in the planning chain and provides the individual task list for each specialist employee. The tasks that have been defined for an employee in the pipeline appear in their stack in the specified order. The stack functions as a personalized Kanban board that clearly structures the workflow and promotes the productive processing of tasks.
- Application example: At the beginning of the week, a developer sees all the tasks assigned to him in the "Done" column of his stack. He works through the tasks one after the other. If he encounters a problem or needs feedback, he can move the ticket to the "Obtain feedback" column and assign it to the person responsible. This interrupts the processing of the task and they can move on to the next task.
- Objective: The stacks reduce the need for queries and enable developers to concentrate on their work without disruption.

Example: A developer can see at a glance which tasks are prioritized for him and can concentrate on processing them without being interrupted by additional requests.
To summarize: An integrated workflow for prioritization and planning
The four planning tools in Leadtime interlock like gears and enable efficient prioritization and task management at all levels:
- Big Picture helps the customer and clerk to prioritize on a project basis.
- Pools expand this view and allow the person responsible to set priorities across several projects.
- Pipelines bundle these prioritized tasks and coordinate them across the entire team, with the team leader providing the global perspective.
- Stacks ensure that developers can complete their work without interruption to be as productive as possible.
This structured workflow not only promotes efficiency in day-to-day work, but also creates a resilient basis for strategic planning and continuous value creation within the company.