TenkaTenka
Sign in

Tenka Help Center › People and development › Roles and autonomy

Roles and autonomy

Job title is the employment link; role is the piece of work with purpose, responsibility and expectation. Next to each role lives the pair that is almost always missing: what the person can decide on their own.

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

The screen

The real screen, in the theme you picked above.

Roles and autonomy

What you find on this screen

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

Available actions

New roleRefreshSaveCloseLink personCancelDeclare decision

Form fields

PapelNome do papel na organização. Papel é o que a pessoa faz, e não se confunde com o cargo da folha.
CódigoNúmero sequencial do papel por empresa.
TipoSe o papel é de liderança, de execução ou de suporte.
PropósitoPara que este papel existe, em uma frase. Papel sem propósito escrito vira acúmulo de tarefa.
ResponsabilidadesO que quem ocupa o papel decide e entrega sem precisar pedir permissão.
ExpectativasA régua combinada de desempenho. É o texto que a conversa de avaliação usa.
CargoCargo formal a que o papel se amarra na folha de pagamento.
AtivoPapel inativo não pode ser atribuído a mais ninguém; quem já ocupa continua registrado.

Start here

What it's for
State, in plain human language, what's expected of each role in the company — and how far the autonomy goes for whoever holds it. A person can have several roles, including outside their own position.

Rules

Why role and autonomy are on the same screen
Because kept apart they produce the most common flaw of growing companies: someone is accountable for everything and can decide nothing. Responsibility without autonomy produces an owner who can only be blamed; autonomy without an owner produces chaos. Here both things are declared together, side by side.
The autonomy ladder
Four steps, from freest to least: DECIDES AND ACTS (doesn't even need to notify) · DECIDES AND INFORMS AFTERWARD (mature delegation) · CONSULTS BEFOREHAND (the conversation is mandatory, but the decision is still theirs) · RECOMMENDS (someone else decides). Most day-to-day decisions should be in the first two steps — if almost everything is in the last two, the bottleneck is structural.
A ceiling without an escape route locks more than it unlocks
If you declare a limit ("up to R$5,000") and don't say who it goes to when it's exceeded, the person is left waiting to figure it out. The screen flags this case: every ceiling needs a destination.

Frequently asked questions

Somar mais de 100% não é problema de organização
It is a capacity problem. When the screen warns that someone has accumulated 260% of time in roles, the conversation is not about redrawing boxes — it is about what that person is going to stop doing.
Was this article helpful?

In the same module: People and development24

Tenka Academy

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

Explore the Academy