Who passes work to whom, and who owns it next?
When everyone is cc'd or a message lands in a shared channel, nobody clearly owns the next step.
Learn
Get clarity on the people, process and software behind the way you work.
Make work handovers between people, software and process flow better.
The friction point
In a small team of 3 to 10 people, work rarely fails inside a single task. It gets dropped in the handover between people, software and process.
When everyone is cc'd or a message lands in a shared channel, nobody clearly owns the next step.
If moving a deal or onboarding a client relies on memory and copy-pasting between tabs, context will slip when the team gets busy.
Without a simple, agreed rule for what 'ready to hand over' means, every project starts differently.
Every step makes a handover clear, owned and visible.
The learning journey
Pick the phase that matches where you are stuck. Each step focuses on a single question and links to practical field notes as they are published.
Understand how work actually moves today before you shop for tools or build automations.
Where are leads, client details or tasks stalling or getting lost right now?
Who owns each stage of work, and what must be true before they pass it on?
How does work actually travel from enquiry to delivery today — including the side channels?
Is our process clear enough to automate, or will automation just speed up a broken step?
Pick the simplest tool setup that fits your team's real workflow and capacity.
Do we need a CRM, a shared project board, or a cleaner bridge between tools we already have?
How do the shortlisted options handle our exact handovers without extra admin?
What happens when we run one real lead and client handover through the setup before committing?
Set up the workflow cleanly and help the team make it their normal way of working.
How do we build the minimal stages, fields and automations so handovers work reliably?
What day-to-day habits and check-ins stop people from slipping back to old spreadsheets and DMs?
Check what is working in live work and tweak the friction points that remain.
Are leads, opportunities and handovers moving cleaner now, and what needs the next small tweak?
Highlighted pillar
In a 3 to 10 person business, you don't need corporate change-management theatre — but you do need clear ownership, practical habits and follow-through so a new workflow actually sticks.
Check whether the team has the breathing room and clarity to change a workflow right now.
Make sure a founder, partner or ops lead visibly backs the change and unblocks decisions.
Spell out plainly what is breaking today and how the new handover saves everyone headaches.
List who touches the workflow and whose daily routine will change when the new step goes live.
Gather practical input from the people doing the job while keeping one clear owner to decide.
Tell the difference between pushback caused by a clunky form versus unclear rules or habit.
Show each person only the exact steps, fields and handovers they need for their role.
Run weekly pipeline and delivery check-ins from the system itself, not side messages.
Nominate a go-to person on the team who can answer quick 'where does this go?' questions.
Watch two or three simple signals that show whether handovers are happening in the right place.
Review at 30, 60 and 90 days to smooth out rough edges before old workarounds creep back.
Check honestly whether response times, handovers and revenue visibility improved as expected.
Decision checklist
Use these eight questions to test whether a tool or workflow change actually fits a small team.
Does it match the way a lead, client or job actually moves from start to finish?
Is it straightforward enough that the team will use it on a busy Tuesday without friction?
Does it give owners clear sight of leads, opportunities and bottlenecks without chasing people?
Can someone inside the business adjust fields, stages and rules without calling a specialist?
Do we have the time and attention to set this up and learn it alongside client delivery?
Are permissions, client data ownership and error alerts clear and manageable?
What will make the team trust this system more than their old inbox or spreadsheet?
Does the time saved and revenue protected clearly outweigh the subscription and setup cost?
“Where will work get dropped between this tool, your team and your process?”
Next steps
Move at the pace that suits your team — from reading the free notes to running a guided mapping session.
Start with the linked guides, checklists and real-world experiment logs on this site.
Use the handover questions and the Fit Lens above to audit your own pipeline and client handovers.
Walk through your people, process and software together to pinpoint where work gets dropped and what to fix first.
Direct conversation · No mailing list
No newsletter popups or email funnels — just practical notes and direct conversations.