How specialists work with their stack
🟥 The stack view clearly structures tasks for specialists according to priority, enables concentrated work and fast feedback processes.
This text is a reference. What types of text are there?
The stack view shows the individual task list of each specialist and follows the order defined by the pipeline planning. At the beginning of the week, all tasks appear in the "To do" column, sorted according to their priority in the pipeline. The specialist works through the tasks in sequence and has two main options:
- Complete task: If the specialist can complete the task, they set the status to "Completed" and return the task to the creator. The task then disappears from the "Completed" column and appears in "Completed".
- Feedback required: If there are problems or queries, the specialist changes the status to "Obtain feedback" and assigns the ticket to the person responsible. The task is then moved to the "Obtain feedback" column and the specialist can immediately move on to the next task.
- Giving feedback: In the stack view, there is also the "Give feedback" column, into which tasks are moved if the specialist is to give feedback themselves. It makes sense to agree that these tasks have priority over those in "Complete". As giving feedback usually only takes a few minutes, the specialist can process such tasks quickly so as not to delay the workflow of other team members.
The predefined order ensures that the specialist completes the most important tasks first. This clear structure enables continuous, disruption-free work and increases efficiency. The stack view guides the specialist through the tasks in a targeted manner, without the need for queries about priority.