What transfers from managing people?
Most of the fundamentals of managing people transfer to managing Digital FTEs without modification. A clear remit, measurable targets, a regular review rhythm, specific feedback, and autonomy earned through demonstrated judgement all work exactly as they do with a human team.
This is the single most useful thing to know before hiring a second Digital FTE. The instinct to treat it as a technical deployment rather than a management relationship is what produces vague remits and unmeasured outcomes. Managers who already run teams well tend to run digital ones well.
What does not transfer?
The main thing that does not transfer is inference. A capable human employee fills gaps in an instruction from context, precedent, and a read of what you actually meant. A Digital FTE follows the remit it was given, which means every implicit expectation has to be made explicit.
The practical consequence is that the remit document does more work than a job description would. If a topic is off limits, say so. If a tone is expected, describe it. If something must always escalate, name it. Gaps do not get filled by good judgement; they get filled by whatever the instruction literally permitted.
How do you prevent two Digital FTEs duplicating work?
Preventing overlap between Digital FTEs requires explicit boundaries, because they will not negotiate territory the way colleagues do. Two humans covering adjacent ground notice the overlap in a corridor and sort it out. Two Digital FTEs will both produce the work.
Draw boundaries by property and by surface rather than by topic, since topics blur. The Social Growth FTE owns the social accounts; the Search Visibility FTE owns the website. Where a genuine handoff exists, name the handoff explicitly in both remits: which one produces, which one adapts, and who approves.
How does elastic capacity change prioritisation?
Elastic capacity changes prioritisation from triage to sequencing, and most managers underuse it at first. With a human team the constant question is what to drop, because hours are fixed. With Digital FTEs the constraint moves to review time and budget, so the question becomes what order to do things in.
The failure mode this creates is sprawl: because more work is possible, more work gets started, and the approvals queue becomes a backlog nobody clears. The discipline is to keep the number of active targets small even though capacity would allow more, and to let the queue length be the signal that you have over-committed your own attention.
What does a weekly management rhythm look like?
A workable weekly rhythm for a team of Digital FTEs has three parts: a daily pass over approvals, a weekly look at targets and exceptions, and a monthly review of autonomy levels. That is enough structure to stay in control without supervising continuously.
The daily pass is short by design: clear the queue, send back what is wrong with a specific reason, and note recurring send-backs. The weekly look asks whether the targets still matter and what the exceptions are telling you. The monthly review asks which classes of action have earned promotion and which should step back down.
- Daily: clear the approvals queue, send back with specific reasons
- Weekly: review targets, exceptions, and spend against budget
- Monthly: adjust autonomy levels up or down per class of action
- Quarterly: re-confirm remits and check for overlap between roles
How many Digital FTEs can one manager run?
The limit on how many Digital FTEs one manager can run is set by review time rather than by the number of systems, which is why the autonomy ladder matters so much for scaling. At Level 0, where everything is proposed, a manager is reviewing every item and the ceiling is low.
As classes of action are promoted, review shifts from items to exceptions and the same manager can hold more roles comfortably. The honest answer is that the number depends on how much of the work has earned autonomy, which is why promoting deliberately is a scaling strategy rather than a convenience.
What does the workforce view show, and how do you use it?
The workforce view on ftes.ai lists every Digital FTE the organization runs, with its role, status, manager, and the count of items waiting on someone. It is the place a manager running several roles starts the day: one combined list of what blocks the most, ordered so that the finance exceptions waiting on the controller and the shortlist waiting on the hiring manager appear before the routine approvals a team member will clear.
Use it to spot three things. An FTE whose waiting count keeps growing has an approver who is not approving, which is a routing fix. An FTE whose approval rate is falling across categories is drifting, which is a remit or source fix, found in the send-back reasons. And two FTEs whose targets overlap are duplicating work, which is a remit boundary fix. The view does not replace each FTE's own workspace; it is the roll-up that makes managing several of them a single daily habit rather than several.