“Estonian” workflow

Author: Jan Trawiński

Art. 15zzzzzu. 1. The restrictions referred to in Art. 15zzzzzo paragraph. 2 pt. 2… something about the Estonian workflow

When we think about the intricacies of Polish regulations, we feel terrified. VAT, PIT, CIT, COVID – it’s a pity to talk. I have not heard anyone say they are in favor of complicating them further – rather, we only hear voices for simplification and rewriting.

On the other hand, whenever we have the opportunity, we complicate ourselves as much as possible. The implementation of document and case workflow processes is a good example of such an action. The emergence of an electronic system sometimes even encourages to confuse the procedures that exist before implementation – because such an opportunity arises. As a result, monster processes are created, of such a complexity that even reading their maps requires a lot of determination and experience.

Can it be otherwise?
I believe so. I think that if the maximum simplification of processes was one of the basic goals of the implementation, this would be the case.

I’ve found that one way to do this is to divide large processes into several smaller ones. To illustrate this example, let’s take such a holiday request process. It usually combines various types of absences: vacation leave, occasional, on demand, child (maternity, paternity – parental and child-care), training, unpaid and all forms of paid and unpaid absence of service providers.
Now let’s think about the map of such a process and its complexities – actors, types of decisions, conditions, etc. To design something like this, you need an expensive analyst (and it’s still quite a simple process, comparing it, for example, to some invoice workflows).
Meanwhile, if each case was designed separately, then “clicking” one of them (forms and flow) without drawing a map at all would probably take several minutes. Moreover, filling out simpler forms would also be much more convenient for later users.

Of course, we, the suppliers of workflow systems, are also to blame for this state of affairs. Why?
First of all, we do not all agree with my thesis that simpler is better.
Secondly, the implementation should be shrouded in a fog of secret knowledge, reserved only for initiates.
Thirdly – we license per process and / or earn money on implementations.

With this in mind, I leave you reflecting, dreaming about an “Estonian” workflow.

Flow BlueDew


BlueDew Sp. z o.o.


ul. Małachowskiego 5
80-262 Gdańsk


ul. Szafarnia 11/F8
80-755 Gdańsk

Contact form

    By sending the form you accept Privacy policy

    Other services