Skip to content
English
More support
Contact us
  • There are no suggestions because the search field is empty.

đź“Š System Logic: How Everything is Connected

Understand the system logic of ValueStreamer: how teams, KPIs, lists, process activities, tasks, and deviation management are linked – and how you can use these connections in your work.

.

🔍 Content

  • Basic Principle: Visualize, Cascade, Collaborate

  • Elements in the System: KPIs, Lists, Process Activities, Tasks, and Deviation Management

  • Tips & Best Practices

  • FAQ

🛠️ How it works
ValueStreamer is based on the principle of managing operational collaboration transparently and purposefully. All content in the system is logically connected.

🔄 Basic Principle: Visualize, Cascade, Collaborate

  • Visualize: KPIs, lists, tasks, deviations, and measures are displayed clearly.

  • Cascade: Content can be systematically passed between teams (e.g., tasks from one team to another).

  • Collaborate: Deviations and measures are linked to tasks or KPIs and can be shared across teams.

📸 Screenshot: Example of cascading a task

🧱 Elements in the System: KPIs, Lists, Process Activities, Tasks, and Deviation Management
The system offers several ways to display information. Individually configured KPIs and lists make a team’s current situation transparent. The process board can represent processes such as order processing or development. The task board contains all tasks that team members must complete. In all these areas, it is possible to link deviations and measures as well as top topics, feedback, and Go & See. All these elements in ValueStreamer are always assigned to a team.

  • KPIs: Individually configurable, team-related, and aggregatable (e.g., output quantity as the sum across production areas).

  • Lists: Allow structured entries (e.g., announcing an audit) that can be passed to other teams.

  • Process Activities: Represent defined processes in the process board (e.g., orders or projects), including links to tasks or checklists.

  • Tasks: The smallest plannable unit (e.g., "Plan team event" or part of a larger process).

  • Deviations: Occur when status is “red” (e.g., target not met) and are used to identify problems.

  • Measures: Only linkable to deviations. Managed via PDCA or A3 methodology, including implementation plans as tasks.

  • Top Topics, Feedback & Go & See: Highlight issues before larger measures are taken.

✨ Tip: Content is often visible in multiple team boards – keep the context in mind.

ℹ️ Info: Cascaded tasks are automatically visible in the target team.

✨ Tips & Best Practices

  • Use colors and statuses consciously for prioritization.

  • Clearly define team assignment to ensure accountability and visibility.

  • Avoid redundancy: use cascading intentionally instead of duplicating content.

âť“ FAQ

What is the difference between a task and a measure?
Tasks are planned activities and visible in the task board. Measures always arise in response to deviations and are not plannable. They are found in deviation management.

How does cascading work?
A card is passed to another team. It automatically appears there with a link to the source.

What happens to colors in cascaded content?
The status color remains the same. In the target team, it can be adjusted if needed.