Thinking in processes: an introduction to TaskAux

From a single step to a chain – without an implementation project

ProcessesTaskAux
Thursday, July 30, 2026

When people hear “process,” many think of flowcharts, workshops full of colorful sticky notes and a project that takes six months. In everyday office work, a process is something much simpler: whatever happens after the e-mail arrives. Who picks it up? What gets checked? Who signs off, and where does the result go?

Every office answers these questions every day, mostly in people's heads and often by calling across the room. Thinking in processes simply means making these answers visible. Here's what that looks like with TaskAux, using one example.

Three terms, that's all you need

  • Task: a single step with assignees, a due date, attachments and short instructions. Some tasks are done by people, others by the software.
  • Chain: the sequence of tasks that together form a workflow.
  • Case: the specific matter that runs through a chain, for example the NDA review for a particular supplier.

Then there are templates. Every chain, any part of it and even a single task can be saved and reused for the next case of the same kind.

An example: the NDA review

Take a task that comes up constantly in many legal departments: purchasing needs a non-disclosure agreement with a new supplier. So far, the request arrives by e-mail, and “the attachments are usually missing,” as someone told us in one of our conversations. Then come the follow-up questions, a draft, a review, an approval and the signature.

In TaskAux, the chain could look like this:

  1. The request comes in through a form and starts the chain automatically.
  2. Check the details and import the supplier data (automated).
  3. Create the draft from the template.
  4. Review the draft from a legal perspective.
  5. Clarify questions with purchasing.
  6. Approval by the team lead.
  7. Obtain the signature.
  8. File the agreement and notify purchasing (automated).

Whoever works on step four sees their task on the dashboard, with everything they need: the draft, the details from the form and the instructions on what to look out for with this kind of NDA. They don't need to keep the other seven steps in mind. The system knows them.

Week one, two, four: how a chain emerges

Here's what matters most: nobody has to design this chain on the drawing board beforehand. It grows from the people who run it.

  • In week one, a colleague sets up the first steps as a chain, just the way she does them anyway.
  • In week two, questions and approvals are added, right in the middle of a live case.
  • After four weeks, the chain is complete, and the first steps run on their own.

In a sense, the department maps itself along the way, as part of its daily work. The task visualization shows the entire flow as an interactive map at any time.

Who does what? Responsibility and cover

Every task goes to one person, several people or a group, in a fixed order. If the first person is out, say through illness, the task moves to the next in line. If that's a group, everyone in it sees the task. Anyone further down the line with capacity to spare can pick up tasks early. That way, work gets distributed without anyone having to distribute it.

Manual, automated and entered once

Every chain has steps that call for experience and steps that simply need doing. TaskAux takes care of the second kind: pulling master data from other systems, transferring documents to practice software, sending e-mails.

Many fields also fill themselves without any AI. A value someone has entered once is reused in every following task, because TaskAux knows where it came from. That sounds unspectacular, but it ends exactly the kind of retyping many offices describe like this: “We type the same data three times into three systems.”

What changes for staff and management

For staff, the day starts with the dashboard: see what's on, the most urgent first, open it and get going.

For management, the numbers appear along the way. TaskAux shows completion times and time estimates directly. Further reports across all modules – which cases are open, where things get stuck, what's taking longer than usual – will come with StatAux, our statistics module for the whole suite, which is currently in development.

Measure first, then automate

Once a chain has been running for a while, it becomes clear which step costs the most time. Frequent and time-consuming: that's the candidate for the next automation. This is exactly where a small, dedicated module pays off, one that takes over the manual step and runs in its place in the chain. The decision isn't based on gut feeling but on economics.

How to get started

  • Pick one type of case that comes up often and is easy to oversee.
  • Start with a small team that handles it anyway.
  • Set up the chain during the next real case, not in a workshop.
  • Add whatever is missing while the case is running.
  • After a few weeks, look at the numbers together.

We'll support you with installation, setup and the first training sessions. Why this matters right now is the subject of our article When know-how retires. You'll find more about TaskAux on the product page, or you can get in touch with us directly.