Choose a starting process by looking at its boundaries, decisions and handovers. These questions help turn a broad need for support into a brief you can discuss.
The first process you hand over does not need to be the largest one. It needs to be something you can describe clearly enough for another person to take responsibility for it. Start with a piece of work your team understands, including the parts that do not follow the usual pattern.
Before a scoping conversation, sit down with the person who does that work today. Bring a recent example and follow it from arrival to completion. Use these questions to decide whether the process is ready for a closer look.
“Help with finance” describes a department, not a process. “Check supplier invoices against purchase orders and send exceptions to our finance manager” gives the conversation a starting point. Write down what arrives, where it arrives and what a completed item looks like.
Include the handover at each end. Someone must supply the inputs, and someone must receive or approve the output. If those people disagree about the boundary, resolve that before asking a new team to work within it. A simple example is often more useful than a long process document.
Separate repeatable checks from decisions that require your judgement. A team might identify a mismatch without having authority to approve a payment. Customer support might answer a routine enquiry but need an internal owner for a complaint outside the agreed guidance.
Make a short list of these decision points. For each one, name the person who can decide and explain what information they need. Avoid making “ask the business” the escalation route: it leaves the next person to discover who that means.
Look at the records and instructions the team would actually receive. Are required fields complete? Can someone find the current template? Do people use the same words for the same status? These questions help distinguish delivery work from preparation that should happen first.
You do not need perfect documentation to begin a discussion. You do need to show the gaps honestly. Bring an ordinary example and an awkward one, with personal or confidential information removed where it is not needed for the conversation.
Agree a starting view of the work before deciding what to measure. That might include outstanding items, reasons for rework or the questions waiting for an approver. Choose measures your team can explain and maintain from the records it already uses.
Ask who will read the update and what decision it should support. A report that prompts a useful conversation is more valuable than a collection of fields nobody reviews. Record the baseline and the reporting cadence in the scope.
A new team needs access, context and feedback. Identify who can walk through the process, grant permissions and review the first outputs. Put those responsibilities alongside the work being handed over, rather than treating them as background administration.
Finish with a small working brief: the process boundary, inputs, approvals, reporting and handover owners. Take unresolved questions into the scoping call. The aim is a shared understanding of the work, with a clear next step for each person involved.
A useful brief connects the role to real work, clear selection criteria and an agreed decision process. Here is what to prepare before the search begins.
Use year end to check payroll records, employment documents and the owners of upcoming submissions. Keep a clear record of questions that need specialist advice.
A team lead connects the daily work with the people who make decisions. Clear ownership, useful updates and a shared record keep that relationship practical.
Tell us what is slowing your team down. We’ll come back with a plan, the people, and the next step.
