TenkaTenka
Sign in

Tenka Help Center › Where work gets stuck › Process AS-IS

Process AS-IS

How the process works TODAY, in three layers: the record of what it receives and delivers, the map of who does what and at which stage, and the measured performance of what the operation has already recorded.

🕒 Updated on Aug 31, 2026📖 ~2 min read

What you find on this screen

A portrait of the screen, read from the screen itself — it changes when the screen changes.

Available actions

Export mapSave recordTurn into disruptionAdd

Form fields

Tipo de demandaTipo de demanda que este processo atende. É o elo entre a ficha e o trabalho que chega.
FornecedoresQuem entrega insumo ou informação para o processo começar.
EntradasO que precisa chegar para o processo rodar. Entrada faltando é a causa mais comum de retrabalho.
SaídasO que o processo entrega quando termina bem.
ClientesQuem recebe a saída e reclama quando ela não vem.
Processos envolvidosOutros processos que este toca. É por aqui que se descobre a fila escondida.
IndicadoresComo se sabe que o processo está indo bem, em números.
SistemasOnde o trabalho é registrado hoje, inclusive planilha e caderno.
RiscosO que pode dar errado neste processo e o que acontece se der.
DocumentosNorma, formulário ou instrução que o executor precisa ter em mão.
SLA acordado (dias)Prazo combinado para o processo entregar. É contra ele que o atraso é medido.

Start here

What it's for
Having an honest picture of the process before trying to improve it. Whoever redesigns without measuring the AS-IS trades one opinion for another — and six months later can't say whether it improved.

Rules

The link that changes everything
In the "demand type that represents this process" field, you link the design to the data. From there, lead time, cycle time, rework, SLA adherence and COST PER EXECUTION (hours logged × hourly cost with payroll charges) appear on their own, with no one typing them in. Without this link, the screen states that it hasn't measured — instead of showing zero.
Note the problem right on the activity
The note field on each activity is the most valuable part of the map. When someone notices that "this here happens through informal conversation," they note it right there, in context — and with one click that turns into a fully contextualized pain point, without waiting for a workshop. That's how the map stays alive.
Work is not the same as crossing time
If the team estimates 6 hours of work in the flow but an execution takes 9 days to cross, the difference is wait time: work sitting idle between activities. This number is usually the most uncomfortable and the most profitable one on the screen, because reducing wait time is almost always cheaper than trying to speed up whoever executes.

Frequently asked questions

Do I need to fill in everything for it to be useful?
No. A form that's 40% filled in with the demand type linked already delivers more than a 100%-filled form with no measurement. Start with the outputs and clients (what it's for and for whom), link the demand type, and leave risks and documents for later.
Was this article helpful?

In the same module: Where work gets stuck14

Tenka Academy

Step-by-step learning paths for your industry, inside the platform.

Explore the Academy