From tool to team
Understand what changes when AI stops only answering and starts executing tasks.
What it is
An AI model (also called LLM, “language model”) is the program that reads text and writes text, like what’s behind ChatGPT or Claude. A tool is something AI can use to act in the real world: read a spreadsheet, send a message, check a calendar. An AI agent is a model that takes an objective and uses tools to execute steps until it reaches a result. The key difference: the chat answers, the agent executes.
Why learn
Confusing answering with executing underestimates the risk. A wrong response in chat is something you read and discard. A wrong action by an agent already happened: the message was sent, the request was changed. Knowing what an agent is is the first step to decide what it can and cannot do on its own.
Key concepts
- Model: the brain that reads and writes text.
- Tool: the hand that acts, like a calendar, a spreadsheet, or WhatsApp.
- Objective: what the agent needs to achieve.
- Result: what’s left in the world after execution.
What it is
Before, the path was: person → executes the process → result. With agents, it becomes: person → defines the intention → organizes the context → delegates → supervises → evaluates. Context is the set of information you give the agent so it can decide well: house rules, examples, history, and the current situation. You don’t leave the process; you just change where you stand in it.
Why learn
Someone who keeps thinking like an executor tends to delegate poorly: they throw the task over the fence and expect a miracle, or redo everything out of distrust. Thinking like a manager means aligning on what good results look like first, and checking afterwards. It’s what you already do with a new employee, now written down.
Key concepts
- Intention: say what you want and why.
- Context: provide the house rules and the current situation.
- Delegate: pass the task with clear limits.
- Evaluate: check the result and correct course.
What it is
Automation is making a task happen without a person performing every step. In classic automation, you design every step: if email X arrives, do Y. In intention-driven automation, you say what: the goal, what a good result looks like, the limits, and when the task is done. The AI chooses part of the route.
Why learn
Describing the intention is faster than drawing each step, but it transfers a decision to the machine. If the intention is vague, the agent carries out the wrong task efficiently. Learning how to write a good intention is the skill that pays off most in this turning point.
Key concepts
- What: the objective in a single sentence.
- What’s good: how to recognize an acceptable result.
- Limits: what it must never do.
- When it ends: the definition of “done.”
What it is
Working with agents follows a flow: Intention → Context → Data → Execution → Evaluation → Supervision → Evolution. The source of truth is the official place where the right information comes from, like the system’s schedule—not the old spreadsheet. Autonomy is how much freedom the agent has to act without asking permission. A guardrail is a constraint that prevents prohibited actions, and a log is the record of what the agent did, so you can check afterwards.
Why learn
When something goes wrong, the flow shows where to look: vague intention, missing context, wrong data, or missing evaluation. Without this map, the common reaction is to switch tools, when the problem was in an earlier step. And the flow doesn’t end at execution: what you learn feeds back to improve the intention.
Key concepts
- Prepare: intention and context before acting.
- Feed: data from the source of truth.
- Execute: the agent acts within its autonomy and guardrails.
- Learn: evaluate via the log, supervise, and evolve.
What it is
Adopting agents in a company is not just a technology issue. Without coordination, each person creates their own agent, their own spreadsheet, and their own rules—so duplicate or conflicting agents appear: two agents responding to the same customer with different information. Management then has to take care of three things at the same time: people, processes, and agents.
Why learn
A well-made agent inside a messy process makes the mess worse—only faster. In a small clinic, if the receptionist and the owner each connect their own WhatsApp robot, the patient receives two different messages. Coordination means knowing who’s responsible for each agent and which process it serves.
Key concepts
- People: who defines, approves, and is responsible for each agent.
- Processes: which routine the agent serves, from start to finish.
- Agents: what each one does and what it does not do.
- Coordination: a single list to avoid duplicates.
What it is
The best way to understand the turning point is to delegate a small, real task—going through the seven questions: intention, context, data, success criteria, autonomy, observation, and supervision. The Agent Sheet (Ficha do Agente) makes you answer these questions and calculates the autonomy level, from N0 (only consults) to N4 (it runs an entire process). You walk away with a ready instruction, three tests, and a checklist.
Why learn
Reading about agent management changes nothing; filling out a sheet changes things. The calculated level shows the central rule in practice: if the task involves money, irreversible action, or people from outside, the agent stays at N2—and nothing goes out without your OK. Starting small and low is the safe path to scaling up later with evidence.
Key concepts
- Choose: a small, repeated task.
- Answer: the seven questions with real examples.
- Calculate: the level comes from the rule, not from preference.
- Test: run the three tests before trusting.