Zanatello Acosta
Consulting
Discuss a problem
Menu

Approach

APR.01

Understand the system before changing it.

I start with how the business actually operates, not with a preferred tool. I map the process, make constraints visible and rank the opportunities before designing anything.

Three rules

APR.02

  1. Understand the system before changing it.

    Every engagement starts with the people, decisions, tools and handoffs behind the visible problem.

  2. Build the smallest intervention that matters.

    Not a transformation programme. A useful change with a clear owner and a measurable effect.

  3. Leave capability behind.

    Documentation, transparent tools and a practical handover are part of the work.

The sequence

APR.03

Map. Prioritise. Design. Build. Transfer. Five steps, in this order, each with an output you keep.

  1. Map

    01

    People, decisions, tools and handoffs.

    Output
    Current-state map

  2. Prioritise

    02

    Value, effort and risk, ranked.

    Output
    Opportunity register

  3. Design

    03

    The smallest intervention, specified.

    Output
    Prototype + spec

  4. Build

    04

    Tools, automations and AI where they help.

    Output
    Working system

  5. Transfer

    05

    Documentation, owners, handover.

    Output
    Capability left behind

What you keep

APR.04

No dependency by design.

When the answer includes software, automation or AI, I define it, prototype it and help deliver it. Then I hand it over.

Documentation
How the system works, who owns it and how to change it.
Your tools
Transparent tools you already use or can run without me.
Your repositories
Code and automations live in accounts you own from day one.
Handover
A named owner on your side and a practical session to transfer the work.
Start with an auditSee the four services