Many managers find it hard to get an overview of their department’s activities (especially when they oversee more than one team).
These features are used to automatically create connected cards according to pre-established conditions and after they’re done, move the parent cards.
How does automatic delegation work?
Company XYZ has 150 employees. Customer operations is its largest department. The department’s manager oversees 80 employee’s divided into 5 teams.
Each team uses its own pipe to manage their activities. The department’s manager has access to each of these pipes but he claims to have a hard time keeping track of the progress of the department’s activities as a whole.
How to setup automatic delegation?
The first step is creating the manager’s pipe. It should have 3 phases: backlog, in progress and done as well as color coded labels for each team.
Create connections between the department manager's pipe and each of the team's pipes.
Every time a card entered the “in progress” phase in the manager’s pipe, a new connected card would be created in the:
- Inbound sales pipe, if it had a red label;
- Outbound sales pipe, if it had a blue label;
- Expansion pipe, if it had a green label;
- Customer success pipe, if it had a purple label;
- Customer support pipe, if it had an orange label.
To set it up, they’ve accessed Apps & Integrations > Automations.
They chose the event “when a card is moved” in pipe “customer operations” to phase “in progress” according to this condition: Label > is equal to > inbound sales.
The action was “created a new connected card” in pipe “inbound sales”. They’ve matched the corresponding fields and that’s it, first automation done.
Repeat it four more times using each team’s label in the condition and each team’s pipe in the action.
How to keep track of the delegated tasks?
To make sure the manager would always know when the delegated tasks were done, their consultant suggested they set up a second automation so that way every time a connected card was moved to done, so would the ‘parent’ card.
Here’s how they set it up:
- Event: “When all connected cards are moved to a phase” in pipe “inbound sales” to phase “done”;
- Action: “Move the parent card” in pipe “customer operations” to phase “done”.
They did the same to all other pipes and that was it.
The customer operations manager was now able to check the status of each task by opening the card and viewing the connected card information.