When It’s Faster to Do It Myself
AI made a familiar task quicker to do myself. That left me wondering what I would be giving up by keeping it.
In this essay
I recently completed a task with AI that would be suitable for an intern.
I understood the context and the main problem. I wasn’t sure of the solution, but I had a clear goal. With recent LLM models, I could investigate the code, make changes, and test them without doing the implementation myself. I was still deciding what to try and whether the results were good enough.
AI helps both of us work faster. But if doing the task myself now takes half the time, while explaining and reviewing it takes almost as long as before, I save less time by delegating. For example:
Illustrative example · senior engineer’s time only · same task
Before AI
By delegating, I save4 hours
With AI
By delegating, I spend1 extra hour
Both pairs use the same 0–12 hour scale. Support includes explaining, answering questions, and reviewing. The intern’s own working hours are excluded. These numbers show how the tradeoff could change, not how often it happens.
That makes doing it myself tempting. But if I keep making the decisions, when does someone else get to learn how?
Part of what I want to help an intern learn is to bring an approach, explain why they chose it, and show what they checked. I want to review their reasoning instead of supplying it. That takes time together, even when doing the current task myself would be quicker.
AI can reduce that support time too: the engineer may use it to find context, investigate alternatives, and catch mistakes before review. That changes how much time I save by delegating. It doesn’t settle whether the assignment is worthwhile. An intern can learn something valuable even if it never saves me time during the internship.
The work can get done, and someone can learn from it, while I still need to direct the next task. That made me wonder what changes this over time.
The same task, four settings
Imagine an integration with an external service: someone needs to investigate, implement, and test it. Here are four combinations of support, time together, and room to make decisions, with AI available to everyone.
01A startup intern, for ten weeks
The CTO could finish the integration with AI in six hours. Helping the intern takes eight. The integration works, but the CTO has spent two extra hours. With a ten-week internship, there are fewer future assignments where that learning can save the CTO time.
02The same startup, a permanent hire
The first integration costs just as much attention. On the next one, the CTO asks the engineer to propose the approach and explain the tests, then reviews their reasoning. Repeated assignments give them context; being trusted to choose an approach gives them practice making decisions. Hiring them for longer doesn’t make that happen on its own.
03A company intern, for ten weeks
A working example, tests, and a mentor make the first integration easier to start. The mentor still spends time reviewing it, but does not have to explain the system from scratch. Those existing resources, rather than the company’s size itself, make the short engagement less costly.
04The same company, a permanent hire
The lead keeps breaking every problem into steps and choosing what to investigate. The engineer gets faster with AI, but has little reason or room to propose the next step. Six months of completed tasks need not change that relationship. The dependency here is partly in how the lead assigns the work.
Who is directing the investigation?
A task can be completed correctly while the lead still chooses what to investigate, what to try, and what evidence is enough. The work has moved to someone else; directing it has not.
I may still review every significant decision, especially when the consequences demand it. That alone does not tell me whether delegation is working. What matters is whether I am reviewing someone else's reasoning or still doing the reasoning for them. I remain accountable in either case.
Knowing when to ask for help is part of that judgment. Fewer questions are useful only when the person can recognize what needs escalation.
A review I remember
In one review, an intern brought examples of incorrect answers that our matching rule had counted as correct. That made our earlier accuracy results look less reliable. I asked what that meant for our evaluation and which earlier conclusions we needed to revisit.
Finding the problem was useful. The next step was understanding which conclusions might no longer hold and how to test them. I could help by asking questions without supplying the answers. What I wanted them to bring next time was their view of the “so what?”: what the findings changed, what they would do next, and where they were unsure.
Different parts of the work can change at different times. Someone might lead the validation while continuing to frame the problem with their mentor.
| Decision | Initially | Developing | More independent |
|---|---|---|---|
| Frame the problem | Mentor-led | Shared | Intern-led |
| Propose experiments | Mentor-led | Intern-ledwith review | Intern-led |
| Choose metrics | Mentor-led | Shared | Intern-led |
| Validate results | Shared | Shared | Intern-led |
| Recommend a decision | Mentor-led | Shared | Intern-led |
Ask for help, flag uncertainty, and escalate decisions beyond the agreed scope.
An illustrative progression within one area of work, not a fixed timeline or a scorecard. Different responsibilities can develop at different rates. “Intern-led” means leading the reasoning, with support and review available.
I would still expect questions, reviews, and disagreements. The change I am looking for is having an approach to discuss, rather than having to supply one. That can happen in one familiar part of a system long before it happens elsewhere.
What I would do differently
What we need to consider is how easily I could make the same decision on the next task, and the next, because each looks cheaper to do myself.
I would now ask what I am leaving for someone else to learn to decide. If I keep the unfamiliar problems and delegate only the steps I have already worked out, I should not be surprised when I am still needed to work out the next one.
I would look for work where someone can make real decisions, but a mistake or delay is manageable. I would ask for their approach before breaking the problem into steps myself. They could use AI to explore options and check their work before we talk.
This may take more of my attention today, not less. In a small team, that investment competes with work that needs to get done now. Doing the task myself may be faster today; delegating it may create more capacity later. The difficulty is knowing which investment I am making.
Optional: put numbers to the time tradeoff
I kept the model below for exploring how long an initial time cost might take to recover. It assumes how supervision changes; it does not explain how someone learns, or tell us what usually happens. It measures the existing team’s time, not the full economics of hiring.
Illustrative time model
The comparison is against the existing team doing the work directly with AI. Change the support time as well as the time saved: AI may reduce both.
Existing team’s net time gained = work avoided − onboarding − supervision
All hours refer to the existing team: the CTO, mentor, and reviewers. The intern or new hire’s own working hours are excluded.
Preset assumptions · change any value to explore.
Assumptions and limits
These presets are hypothetical starting points for recurring work, not measured versions of the integration examples. Onboarding uses the existing team’s time at week 0. Time spent supporting includes onboarding and ongoing supervision. Every productive week avoids the same amount of work for the existing team, measured against doing it with AI. Supervision in week w is initial supervision × (1 − weekly decrease)w − 1. Supervision counts attention from everyone providing it, not just the technical lead.
The model assumes suitable work is always available and output has been validated to the required quality. A weekly decrease compounds: 15% means 5 hours becomes 4.25 hours in week 2. It approaches zero over time. There is no explicit allowance for interruptions, minimum review requirements, or new domains that increase supervision. Break-even is the first productive week in which the existing team’s time saved covers its onboarding and supervision time.
This measures attention, not financial return or the value of learning. It excludes compensation, recruiting, retention, and any benefit after the engagement ends. A negative result does not mean a failed internship.