GARDUS task garden: task visualization where neglect withers

Every team has tasks everyone knows about and nobody mentions. “Update pricing on the website” has been open since spring. “Sort out the warehouse lease” has been opened five times, and each time someone thought “later.” In a list they look exactly like yesterday’s work: a line, a date, a name. Lists are polite. They never tell you that a piece of work died months ago while everyone kept pretending it was alive.

We decided to do the opposite. In GARDUS, our approach to task visualization, every task becomes a plant. Work that gets attention grows. Work that’s abandoned dries out and turns into a gnarled, withered tree you can’t miss. It isn’t a game for its own sake, and it isn’t a punishment. It’s a way to bring order out of chaos by making visible what a list hides.

A task is a plant, a project is an island

The GARDUS task garden is a second face of TASKUS task management. It has no data of its own. It shows the same tasks with the same permissions and rules, and anything you can do to a task in the regular interface you can also do in the garden.

Here’s how the world is laid out:

a plant is a task;
an island is a project;
a flowerbed is a team’s inbox, work nobody has picked up yet;
the review bed holds fruit waiting on you: work that’s been handed in and needs your sign-off.

Everyone has gardens: your own, a colleague’s, a project’s, a department’s. Team and personal gardens follow the org chart in TEAMUS, so a manager can see at a glance who’s buried in jungle and who has two blades of grass.

Six kinds of plants

A plant’s species depends on the nature of the work. It’s not decoration. The shape of a garden tells you what a person or team is actually busy with.

Work	Plant	What it looks like
Urgent and short	flameflower	flares up and fades fast
Long project	elder tree	grows slowly and gathers rings
Routine, recurring	grain	ripens in batches
Approvals, paperwork	crystal bloom	one facet per approver
Creative	glowspore	glows, unpredictable shape
Problem, breakage	thornplant	drops thorns as it gets fixed

A plant moves through real stages: seed, sprout, stem, bud, bloom, fruit. It grows only from confirmed events, such as a stage change, a handoff, or an approval. Fruit appears only when someone else accepts the work. You can’t fake growth by leaving an “ok” comment.

Rings, sparks, and fire

Every time a task passes between people or teams, it adds a ring to the trunk. A tree that has traveled through eight departments has a thick trunk with eight rings, so you can read the journey the work took. Critical tasks burn and throw sparks, and important ones pulse a steady amber. When a colleague touches a task, its plant flashes with sparks right in front of you.

Why abandoned work should wither

The garden’s purpose in one sentence: a task nobody is working on should become more visible and more uncomfortable until someone makes a decision about it.

Notice the word decision. Not “finish it at any cost.” Closing it, handing it off, freezing it, postponing it to a date, or dropping it are all decisions, and honest ones. The problem isn’t unfinished work. The problem is work that just sits there while everyone acts as if someone owns it.

Drought, dryness, and the withered tree

Each plant has two scales. The first is color and foliage: how many days have passed without a decision. New tasks get three days to take root. After that, if nothing happens, the plant starts to fade, then dry out. Missing the due date adds a red glow at night.

The second scale is size and shape. A task that has sat with one person for a long time doesn’t die. It grows into a crooked, withered tree with a thick trunk, broken branches, a wide crown, and a shadow over its neighbors. It pushes the plants around it aside. A garden with a dozen of these looks neglected, and that is exactly the feeling that should prompt a cleanup.

The mechanic has guardrails, because without them it would do more harm than good:

Growth has a ceiling. A tree stops growing after about three months. Otherwise, after half a year nobody could bear to open the garden.
Nothing disappears on its own. The task stays alive, the data stays intact, and the withered tree can always be opened.
Only the person whose move it is sees their plant dry out. If a task is waiting on another task or someone else’s reply, it doesn’t wither. It sleeps under frost. Nobody gets penalized for someone else’s delay.
Frozen and archived tasks don’t dry out. Someone already decided.
Only working days count, not calendar days.

Looking isn’t caring

The tempting design was simple: open a task and the plant revives. We rejected it. If a glance heals, the cheapest way to keep a green garden is to open tasks and do nothing. We’d be teaching people to perform work instead of doing it.

So the garden has three different signals:

A look. You opened the card, meaning “I’ve seen it.” That doesn’t heal anything. It only buys a short pause.
Watering. A small promise: one line about what’s next, plus the date you’ll come back to it. It holds off drying until that date.
A decision. A stage change, a handoff, a due date, a freeze, a drop, or completion. That fully heals the plant.

Water is limited

Watering is the only honest way to say “I haven’t forgotten, just not now.” And it has limits. That’s the core of the whole mechanic.

Three waterings per day. You can’t water the whole garden at once, so you have to choose what genuinely deserves to wait.
You can’t water the same task forever. Two waterings in a row is the limit. On the third try the can is empty for that task, and the garden asks directly: “This is the third time you’re putting this off. What do you want to do with it?”

You’re allowed to postpone. You’re not allowed to fool yourself forever. We think this is the most honest part of the garden. It doesn’t demand heroics. It demands clarity.

A withered tree is a control panel, not a reprimand

Click a withered tree and you don’t get a wall of guilt. You get a one-screen review with five buttons:

Do it now
Hand it off: replant it in a colleague’s or a team’s bed
Postpone to a date: water it
Freeze it
Drop it: send it to the archive

Once you decide, the tree straightens and turns green before your eyes. The reward is instant and visible, and it works better than any points system. The garden deliberately gives no points for the number of tasks closed, because points immediately lead people to chop work into tiny pieces to pad the count.

Replanting is a handoff

You can drag a plant into a colleague’s bed. It’s more than a pretty gesture. A handoff window opens where you write what’s done, what’s expected next, and by when, and the trunk gains a new ring. Drop it into a team’s flowerbed and the task goes to that team’s inbox, where anyone with capacity can pick it up.

Other people’s gardens, without a wall of shame

In a team garden, only a plant’s owner sees the full withered look. Everyone else sees other people’s neglect toned down. There are no public “worst performer” boards. The garden applies gentle pressure. It makes a problem visible to the person who can fix it, without putting anyone on display in front of the team.

The same idea in a plain task list

Not everyone wants a garden, and that’s fine. The same logic lives in TASKUS in the calm language of a list:

a neglected task’s card slowly loses color and gets a quiet label like “no activity for 24 days,” with no red alarm;
a slim bar appears above the list, “5 tasks drying out · review,” which opens the same five-button review;
old tasks are never buried at the bottom. What’s hidden never gets reviewed.

The whole drying mechanic rests on how TASKUS separates ownership from whose turn it is. We cover that in Ownership vs. whose move.

How to tell the garden is working

We recommend watching one number: how many tasks are older than 30 days with no decision. And a second one: how many decisions per week get made straight from the review. If the first number hasn’t dropped after a month, the mechanic has become decoration, which usually points to team habits rather than the garden.

A practical Friday ritual:

Open your garden and find the driest trees.
Make one of the five decisions for each. It doesn’t have to be “do it.” An honest “drop it” also clears space.
Look at your team’s flowerbed. If it’s overgrown with unclaimed tasks, that’s the clearest sign the team needs help.

Five minutes a week, and your task list starts telling the truth again.

Order out of chaos

We didn’t build GARDUS to make work feel like a game. We built it to make chaos visible. As long as abandoned tasks look like ordinary rows, they pile up for years and quietly drain attention, each one a small pebble of “I really should.” The garden turns those pebbles into trees that ask for a decision. Make one, and it gets lighter, for the garden and for you.

The garden comes with your tasks as part of the PRANUS implementation, with no separate setup. Want to see your future garden grown from your team’s real tasks? Book a demo and we’ll walk through it together and find the driest trees.