• Explainer
  • Operations
  • 5 min read

Managing a Hybrid Human-AI Team

The Digital FTE does the repetitive work and proposes. The people decide, handle the hard cases, and grow. The manager draws the lines and keeps them honest.

Author
ftes.ai Editorial
ftes.ai Team

The short answer

Managing a hybrid human-AI team means drawing clear lines: the Digital FTE owns repetitive, evidence-based work and proposes; people own judgement, relationships, and every decision about a person; named people approve proposals and receive escalations with a summary; and people's roles shift toward the judgement work the FTE surfaces.

Put a Digital FTE on thisEvery role proposes with evidence and reports to you.

Key takeaways

  • Draw the line between repetitive evidence-based work and judgement work.
  • Name who approves which category of FTE proposal.
  • Escalations reach people with a summary, not a raw item.
  • People's roles shift toward judgement; say so explicitly and early.
  • The FTE is reviewed on targets; people are reviewed on the work only they can do.

What changes when a Digital FTE joins the team?

When a Digital FTE joins a team, the repetitive, evidence-based work gets an owner that does it daily and proposes rather than acts, and the people on the team find their days shifting toward the cases the FTE surfaces: the exceptions, the escalations, the send-backs, and the decisions. The volume of routine work falls; the proportion of judgement work rises.

That is a real change to people's jobs, and it goes better when the manager names it early rather than letting it happen. The Digital FTE is a direct report in the workspace; the people are still the team.

How do you draw the lines?

Draw the lines by listing the function's work and sorting it. Repetitive and evidence-based, with a checkable right answer: the Digital FTE owns it and proposes. Judgement, relationship, and anything that changes a person's outcome: people own it, and the FTE prepares the evidence. Write the sorted list into the FTE's remit and into the team's understanding of their own roles.

Revisit the lines quarterly from the send-back reasons. Work that keeps coming back from the FTE is judgement work that was mis-sorted; work that people find themselves doing by hand is FTE work that was left out.

  • FTE: matching, screening, drafting from sources, monitoring, reporting
  • People: exceptions, interviews, escalations, editing, decisions about people
  • Both: approval, where a person reviews the FTE's proposal in minutes
Digital FTE owns and proposesMatching and reconciliationScreening against a scorecardDrafting from sourcesMonitoring and detectionsReporting against targetsPeople own and decideDeciding exceptionsInterviews and offersComplaints and relationshipsPricing and negotiationAnything about a personApprovalgate
Figure 1Draw the lines before the first proposal: what the Digital FTE owns and proposes, what people own and decide, and the approval gate between them.

Who approves and who receives escalations?

Name an approver per category of proposal. Routine categories can be approved by the team member closest to the work, which is also how they learn the standard; sensitive categories go to the manager or a specialist. The approver's name is in the audit trail for each decision.

Escalations from the FTE arrive with a summary: what was asked, what it found, why it did not resolve, and a suggested next step. Route each escalation category to the person who owns that judgement, and make sure they know to expect the summary rather than a raw item.

How do people's roles change?

People's roles change toward the work only people can do. A finance team member who spent mornings matching now spends them deciding exceptions from evidence. A support agent who answered password resets now handles the complaints the FTE escalated, with the FTE's summary in hand. A junior who did CRM updates now reviews the FTE's hygiene proposals and learns what good data looks like.

Say this explicitly and early, in each person's own terms. The comparison with a junior hire on ftes.ai makes the point: the repetitive work was never what the people were for.

How do you review the two kinds of team member?

Review the Digital FTE on its Targets, its approval rate, its cost per outcome, and its own first-person monthly report, with send-back reasons as the diagnostic. Review the people on the work only they can do: the quality of their judgement on exceptions, their handling of escalations, and their growth into the decisions they now own.

Do not review people on volume the FTE now handles, and do not review the FTE on judgement it is designed to escalate. Keeping the two reviews distinct is most of what makes a hybrid team feel fair to the people in it.

What does a week look like for the manager of a hybrid team?

A week for the manager of a hybrid team starts each morning with the workforce view and the combined brief: what is waiting on whom across every Digital FTE, ordered by what blocks the most. The routine approvals have been routed to team members close to the work, so the manager's own items are the sensitive categories and the escalations that carry a summary. That takes minutes. The rest of the morning is the people: the exceptions someone decided, the interview someone ran from a shortlist, the complaint someone handled from an escalation summary.

Midweek the manager reads the send-back reasons with the team member who approves that category, which is a coaching conversation about the standard as much as a remit review. At the end of the week the workforce view shows each FTE's approval rate and waiting count, and any drift is visible before it becomes an incident. Once a month the FTE reviews happen from the FTEs' own reports and the people reviews happen on judgement and growth, kept apart. The manager's job is the lines, the routing, and the people, and the workspace is what keeps the first two from consuming the third.

Frequently asked questions

How do you manage a team with people and AI employees?

Draw the line between repetitive evidence-based work, which the Digital FTE owns, and judgement work, which people own. Name approvers, route escalations with summaries, and shift people's roles toward judgement explicitly.

Who approves the FTE's proposals?

A named person per category: team members close to the work for routine categories, the manager or a specialist for sensitive ones.

How do people's jobs change?

Toward exceptions, escalations, editing, and decisions, which the FTE surfaces with evidence. Say so early and in each person's terms.

How is the FTE reviewed differently from people?

The FTE on targets, approval rate, and cost per outcome. People on judgement, escalation handling, and growth. Keep the two distinct.

How often should the lines be revisited?

Quarterly, from send-back reasons and from any work people find themselves doing by hand.

  • Operations
  • Hybrid team
  • Management
  • Team design
  • Digital FTE
Further reading

Keep going.

Related guides on hiring and managing Digital FTEs.

Explainer · Operations · 5 min

Team Structure With Digital FTEs: Three Patterns That Work

Where do Digital FTEs sit in an org chart? Three patterns that work: one FTE per function reporting to that function's lead, a pod of FTEs under one operations manager, and an FTE paired with a junior as apprentice manager. When to use each.

Read

Ready to hire your first Digital FTE?

Pick a role, connect the tools it needs, and review its first proposals this week.