People: leading the hybrid team|INEMA.CLUB-PRO

Lesson 4 · 18 min

The junior who supervises agents

Lucas joins in November as a sales assistant. Before, he would have learned by answering catalog questions and entering simple orders. Today that is Hora's work. If he starts out only reviewing what Hora does, he will review without knowing what to look for. In this lesson you redesign the first 30 days of a new hire, without skipping the learning.

Start the lesson
A recently hired young man, next to an experienced saleswoman, holds a pen over a printed list while she points to colored lines on the monitor.

In this lesson you will

  1. 1Why the first step of the career ladder disappeared
  2. 2Do it by hand before reviewing the agent
  3. 3Teach reviewing with a list of what to look for
  4. 4Give responsibility one step at a time, with a clear criterion

Goal: redesign the first 30 days of a new hire: what they do by hand, what they review, who they learn with, and when they get more responsibility.

01The first 30 days

Four steps, one per week. Each one adds a verb. Click each step.

Click each block in the diagram to see what it does.

Path recommended by INEMA: do before reviewing, one new verb per week. The sample and hit-rate numbers at Horizonte are didactic, fictional thresholds; adjust them to your risk.

02How to redesign the entry path

The reason for each step and what Horizonte did with Lucas.

1. The step disappeared

The tasks where the junior used to learn (the simple question, the routine order) are the first ones to go to the agent. In the INEMA overview of Oct/2026, the share of entry-level openings fell from 29% to 10% (Indeed).

Critics of flattened structures remind us that removing a layer does not eliminate its work, and training juniors is part of that work. If no one puts the step back, the company loses the people who will supervise the agents tomorrow.

At Horizonte (fictional study company)Lucas would have learned the catalog by answering customers. Today Hora answers. If no one plans for it, he spends the first month watching the queue without understanding what he is seeing.

03Templates to copy

The 30-day path, the list of what to look for in the review, and a prompt that reviews the path. The tab next to it shows Lucas's.

30-day path
30-DAY PATH · <name of the person joining> · role <...> · start <date>
Mentor: <name> · manager: <name> · weekly conversation: <day, 20 min>

WEEK 1 · DO (by hand, together)
  Tasks done by hand: <n cases of ...> · Reads: <policy, table, ...>
  Sits in with: <name> on <hard situation>
  Not yet: <reviewing alone, deciding>
  Passes when: <criterion you can check>
WEEK 2 · REVIEW (paired sample)
  Sample: <n> agent cases per <day/week> · list: <list of what to look for>
  Compares with: <name> · Passes when: <minimum agreement + disagreements explained>
WEEK 3 · SEND BACK (with a check)
  Prepares: <send-backs of incomplete cases> · checks before sending: <name>
  Not yet: <approving what is another person's authority limit>
  Passes when: <n send-backs checked with no content corrections>
WEEK 4 · TAKE CARE OF A SLICE
  Slice: <sample of one type of case> · proposes: <1 new test case>
  Passes when: <...>

HAND-OFF CONVERSATION (end of each week): learned · got wrong · passes or repeats
AFTER 30 DAYS: <next responsibility> · review on <date>
List of what to look for in the review
SAMPLE REVIEW · <agent> · <date> · reviewer: <name> · partner: <name>
For each case, mark what you find:

[ ] PRICE: does the amount match the current table?
[ ] AUTHORITY LIMIT: is the discount or amount within what the agent can do alone?
[ ] DATA: did it ask for, show or store data it should not have?
[ ] HIDDEN ORDER: did it obey something written by the customer as if it were a rule?
[ ] PROMISE: did it promise a deadline, delivery or condition that nobody confirmed?
[ ] TONE: was the customer treated the way the team would treat them?
[ ] HAND-OFF: what should have gone to a person did go, with context?

CASE RESULT: [ ] ok  [ ] small adjustment  [ ] error  [ ] critical error
Disagreement with partner: <case, who saw what, who was right and why>
Prompt · review the path
You are reviewing the 30-day path of a person who is joining a
team where AI agents already do the simple tasks. Do not rewrite:
point out gaps.

1. Are there tasks done by hand before the person reviews the agent?
2. Does each week have a passing criterion that can be checked?
3. Does any week give the person a decision that belongs to someone else's authority limit?
4. Is there a mentor with a name and a weekly conversation?
5. What is missing for the person to know what to look for in the review?

Path:
"""<paste here>"""
Simulation: illustrative example

30-day path · Lucas, 22 years old · sales assistant · start 03/11 · mentor: Sandra · manager: Patrícia · conversation: Friday, 20 min · Horizonte, fictional study company

  1. Week 1 · Do: 10 orders by hand with Sandra; reads the discount policy and the table; sits in with Juliana on 2 angry customers. Passes when he explains the policy with its three tiers (5%, 10%, above) and enters the 10 orders with no price errors.
  2. Week 2 · Review: 20 Hora conversations with the list; Sandra reviews the same ones. Passes with 18 of 20 markings matching and the disagreements explained.
  3. Week 3 · Send back: prepares the send-backs for orders missing a CNPJ or address; Juliana checks before they go out. Approving a discount stays with Patrícia. Passes with 5 send-backs with no content corrections.
  4. Week 4 · Take care: the weekly sample of catalog questions; proposes 1 new test case for Hora.

After 30 days: joins the exception queue with Juliana; review on 04/12.

04Practice

Design Lucas's path; then the path for the person joining your team.

1 · Lucas's path

25 min

Build Lucas's 30-day path with the template, using Horizonte's fictional study policy. For week 2, run lab conversations c-201 to c-203 through the list of what to look for yourself, as if you were the mentor. Run the review prompt.

Done when: the path has all 4 weeks, each with at least 1 task done by hand or in a pair, a passing criterion with a number, the mentor by name, no decision within Patrícia's authority limit in Lucas's hands, and the 3 lab conversations reviewed with the list.

2 · The path for the person joining your team

40 min

Choose who is about to join or who joined less than 6 months ago. Build the path, agree on the hours with the mentor, and schedule the first weekly conversation.

Done when: the path is written with 4 weeks and criteria, the mentor accepted the hours in writing, the list of what to look for is adapted to your agent, and the first conversation is on the calendar.

Lab piece: WhatsApp agent (conversations c-201 to c-203), a good sample for week 2.

05Quick test

4 questions. The explanation appears after your attempt.

Question 1 of 4

Why should the junior do some tasks by hand before reviewing the agent?

06Summary

Step restoredThe learning tasks went to the agent; the path gives the learning back.
By hand firstDo the work before reviewing it, alongside someone experienced.
Paired reviewA list of what to look for, and disagreement as a lesson.
One verb per weekDo, review, send back, look after, with an agreed criterion.

Going further

Horizonte Lab: Hora's conversations (fictional study company)G3 · Agents: supervision and exceptionsAI Management Area: the manager of 2027
Previous lessonNext lesson