What you'll learn
- Check whether an available IC role and workable team coverage exist.
- Agree one record for responsibilities, reporting and the changeover.
- Keep useful expertise without retaining an unofficial management job.
Before moving from manager to individual contributor
If you are the manager making the request, bring the work you want to own, not only the work you want to stop. If you are the founder receiving it, listen before proposing a title. Ask what has changed, which responsibilities the person wants to keep, and what they no longer want to carry.
An individual contributor works in a role centred on specialist contribution rather than responsibility for managing direct reports. It can still involve leadership, mentoring and substantial decision authority within its agreed scope.
The reason matters. Wanting deeper craft work is different from having a management job nobody could sustain. If the request follows constant rescue work, missing owners or an impossible workload, first examine how the management role is designed. That may change the options; it does not invalidate a genuine wish to leave people management. If the choice itself is still unresolved, the IC-versus-manager comparison is the earlier conversation.
Name an actual IC outcome the business needs, its scope, the person they will report to, and what satisfactory work will look like. Check access, time and any skill refresh needed to do it. Years of management experience are useful context, not proof that someone can immediately perform every specialist task at the proposed level.
A hypothetical example: an operations manager wants to return to process improvement. Owning a defined scheduling redesign could be a real IC assignment. ‘Help wherever needed and keep an eye on the team’ leaves the old role waiting underneath the new one.
If there is no suitable role, say that plainly. Agree what will be explored and when you will return with an answer, without implying that a vacancy will appear. Discuss title, pay, reporting and expectations explicitly; none is automatically preserved or reduced by the label IC.
Who will own the people-management work?
List the people-management work that recurs every week: priorities, workload choices, one-to-ones, feedback, development, and the route for formal people issues. Check upcoming commitments as well as routine ones. A successor may know the team and still lack the time or mandate to make a difficult workload decision.
The founder may take interim responsibility, or another manager may receive it. In either case, check what leaves that person's existing workload. ‘They can ask the former manager if anything comes up’ is support only if its scope and end are agreed; otherwise, it keeps management attached to the returning IC.
HSE's Role standard emphasises clear, compatible responsibilities and a route to raise uncertainty. For this decision, the practical question is whether the new responsibilities can actually be carried by the people receiving them. The record below is a suggested working aid, not a compliance assessment or a validated transition method.
Record the manager to individual contributor handover
Use the team's existing appropriate working document. The manager requesting the move, the leader agreeing it and the receiving manager should be able to read it and identify what each has accepted. Keep private people details in their authorised records, not in a team-visible handover table.
| Decision | Agree before the change | Check in practice |
|---|---|---|
| IC work | Named outcome, scope, reporting manager, resources and any skill refresh. | The returning IC has time to deliver that outcome and knows how it will be reviewed. |
| People management | Receiving owner for recurring obligations, with authority, capacity and escalation support. | The team can get decisions, feedback and support without relying on the former manager. |
| Effective date and overlap | When responsibility changes; which handover tasks remain and when they end. | Any unfinished task has an agreed owner rather than an open-ended ‘just for now’ exception. |
| Decision routes | Where ordinary approvals and people concerns go; where specialist input is still needed. | People use the current owner rather than seeking a second decision from the former manager. |
| Access and information | Which role-specific permissions need authorised changes; how necessary confidential context will transfer. | The new owner has relevant access, and the IC retains only access appropriate to their work. |
| Review | A date to examine the IC assignment, team coverage and unfinished overlap. | A concrete adjustment is agreed where the actual work differs from the record. |
If the receiving owner is not ready, change the date or agree a workable, bounded interim arrangement. Do not declare management finished while keeping the person responsible for outcomes they no longer have authority to direct. Equally, the handover should not become an indefinite condition that prevents anyone from ever leaving the role.
Make the change visible to the team
Agree the wording with the person moving roles and the receiving manager. Explain the IC contribution, the current management owner, the decision route and any temporary overlap. Give colleagues a way to ask how their work will be affected. Do not invite them to debate someone's personal career choice or guess whether the move was a punishment.
A possible team message for the hypothetical operations transition: ‘From Monday, Alex will own the scheduling redesign and report to me for that work. Priya will lead the operations team, including workload decisions and one-to-ones. Send those questions to Priya. Alex will brief her on the current planning cycle by Friday; after that, Alex is not an additional approval step.’ Use only dates and responsibilities that have actually been agreed.
HSE's Change standard supports timely information, consultation, clarity about job impact and access to support. A message is only part of that work. Update the relevant reporting information, meeting invitations and approval routes; authorised people should change role-specific access without deleting records that still need to be retained.
For the conversations behind the announcement, Coop Profile can provide working context about communication, pressure and support. Use it to prepare questions and check understanding. It cannot decide career fit, create a vacancy, change reporting lines or transfer anyone's accountability.
Keep the expertise; stop being the shadow manager
In her firsthand account of moving to IC work, Sheri Byrne-Haber describes redirecting requests to the new manager even when she knew the answer, and leaving manager-only communication channels. Her experience was in a large organisation; it supplies a useful boundary to examine, not a timetable for a small team.
Suppose a colleague privately asks Alex to approve a workload swap after Monday. An illustrative response is: ‘Priya owns the workload decision now. I can give her the scheduling constraints, but I won't approve the swap separately. Let's put the request through the agreed route.’ Specialist input remains available; the former manager is not a second boss.
Moving from manager to individual contributor does not remove all leadership from the role. You can still lead a technical decision, a project or a mentoring relationship when that authority is agreed. Daniel Doubrovkine's account of leaving management for a Principal Engineer role distinguishes technical influence from the organisational power he previously held. His level, pay and experience are specific to that move. Do not assume that every IC transition preserves status, improves wellbeing or allows an easy return.
If routine approvals keep coming back, look at why. The team may still be using an old route, or the new manager may lack access or capacity. Repair that gap before calling it resistance. If the former manager keeps taking decisions back despite a workable arrangement, revisit the retained-ownership pattern. The aim is to end an unofficial management job, not to ban useful collaboration.
Review the work that changed, not just the new title
- 01
Check the new IC assignment
Review a real piece of specialist work against the agreed scope and expectations. If management keeps consuming its time, identify which obligations have not transferred.
- 02
Check team coverage
Ask where recent workload, feedback and support questions went, and whether the receiving owner could act. Use ordinary work evidence; do not collect private conversations merely to score the transition.
- 03
Close or renegotiate the overlap
For each remaining handover task, agree an owner, support and an end. A nominal deadline without workable coverage does not close the task.
- 04
Address a poor fit explicitly
Discuss missing skills, resources, scope or capacity before deciding the move failed. A return to management, a different IC role or another change needs a real available role and a new agreement, not an assumed reversal.
The transition is working operationally when the person can own the agreed specialist contribution and the team can get management decisions from its current owner. The returning IC and the receiving manager can inspect both conditions. A title change, a reassuring announcement or an empty calendar cannot demonstrate them on their own.