How does this differ from defect management and knowledge preservation?

Defect management fixes an existing fault (“The material counter is damaged.”). Idea management improves a process or condition (“A different layout would speed up the material counter.”). Knowledge preservation keeps proven practice (“This is how we run the material counter reliably.”).

Are there votes, scoring or rewards?

No. Team-Tasks is not a specialised innovation management system. The focus is on feedback, decision and implementation of suggestions in the tool your team already uses.

Do all employees see all suggestions?

You decide per project: members see either all tasks or only their own.

Can suggestions be submitted with a photo?

Yes. Photos, documents and links can be attached directly to the suggestion – from a smartphone too.

All use cases

Idea management: collect employee ideas and implement improvements

Employees are often the first to see what could work better. But a suggestion made in passing or in a chat is quickly lost, and the person who made it never learns what happened to it. With Team-Tasks, every idea becomes a traceable process: capture, review, decide, implement. The focus is not on collecting but on feedback: my suggestion is heard, decided and followed up.

Start for free

High ropes course employee photographing a post where new signage should be mounted

Why good ideas get lost in daily work

Suggestions are made verbally or in a group chat and then forgotten.
Nobody is clearly responsible for reviewing a suggestion.
Whoever made a suggestion never learns whether and why it was accepted or rejected.
Accepted ideas have no owner and no due date.

How it works in Team-Tasks

1
Capture the suggestion
Employees create a task in a dedicated ideas project: observation, suggestion and, if needed, a photo or link. Project settings decide whether all suggestions are visible or only one's own.
2
Review the suggestion
A responsible person reviews the suggestion and clarifies questions by comment directly on the record.
3
Document the decision
Custom status values such as “Under review”, “Accepted”, “Rejected” or “Implemented” show the state. The reason is added as a comment; the submitter is notified.
4
Plan the implementation
Accepted ideas get owners, steps and a due date – or are moved to the relevant work project.
5
Follow the result
Implementation, photos and history stay visible to those involved. If a process changes as a result, update the related instruction.
6
Schedule a fixed review
A recurring task such as “Review new suggestions” ensures no idea is left lying around. This fixed slot matters more than any extra feature.

Practical example

At Actionpark Hirschhagen, improvement suggestions come straight from operations. Three examples: staff noticed that a step in a Team-Tasks instruction was missing or incorrect – the note was reviewed and the instruction updated for everyone. In the high ropes course, missing signage was spotted; after the decision it was implemented as a task with an owner. The restroom containers lacked an unobtrusive storage spot for toilet paper: the suggestion came with a photo of the intended spot and a link to a suitable product, was accepted and implemented.

From practice

At Actionpark Hirschhagen, improvement suggestions are submitted with a photo, reviewed and implemented – such as missing signage in the high ropes course or a storage spot for toilet paper in the restroom containers.

Read the Actionpark Hirschhagen case study