Before you ask

Frequently asked questions

Usage is not capability.

Individual wins that stay local do not become a reliable way of working, which is the question underneath most of the ten below.

  1. We already have AI tools and people using them. Why do we need this?

    Usage is not capability. Individual wins that stay local do not become a reliable way of working. This work builds the ownership, documentation, evaluation, and measurement that turn scattered activity into an organizational capability.

  2. Is this training, consulting, or implementation?

    All three, in sequence. Act 1 reads the whole company. Act 2 builds alongside one function: real automations, real documentation, real skills. Act 3 hands the rhythm to your organization so it can continue without an external push.

  3. We already appointed someone to own AI. Where do you fit?

    Good. A named owner is one of the six conditions. The work equips that owner with visibility, a method, and a measurement rhythm rather than replacing them.

  4. Do we need to document everything before we begin?

    No. Nothing needs to be prepared for Act 1. Documentation happens in Act 2, only for the work being redesigned, and only to the level a person or an agent needs to execute it.

  5. What is an Automated Operating Procedure?

    A standard operating procedure rewritten around the real process, exceptions and failure paths included, and structured so AI can execute the work without relying on unwritten background knowledge, with human-review rules attached.

  6. How technical does our team need to be?

    Not very. Nontechnical builders learn testing, troubleshooting, token costs, edge cases, and maintenance in plain language, then make the next build themselves.

  7. How do you handle risk, quality, and human review?

    Every task gets the right level of automation, with human-review rules written into the automation map. Managers get a rubric and an evaluation method for judging AI-assisted work, and every build is registered with an owner.

  8. How much time does this require from our team?

    Act 1 is mostly interviews and an assessment. Act 2 asks real time from one function. That is where the capability is built. Act 3 folds into existing leadership rhythms.

  9. How long does the work take?

    Four weeks for the Diagnostic, twelve weeks through one function, eighteen weeks end to end. A half-day workshop is the smallest starting point.

  10. Where should we begin?

    With a conversation. The first call establishes which starting point is proportionate to the problem.

Book a conversation

Last updated August 5, 2026