Sales Process Mapping Workshop: Getting the Real Process Onto One Page

Two reasons, and only two. First, so the pipeline data means something, which requires everyone to agree what each stage represents and what evidence is needed to enter it. Second, so improvement has a target: you cannot fix a leak in a process you have not described. Everything else that gets attached to these exercises, alignment, visibility, standardisation, follows from those two.

The failure mode is a session that produces the process management already believed in, drawn neatly. That document has no relationship to what happens on Tuesday afternoon, and within a month everyone is back to the real process, which remains undocumented.

State the rule at the beginning: we are documenting what happens, not what should happen, and nobody is in trouble for describing a workaround. Then behave consistently with that for the whole session, because the first time someone is corrected for admitting a shortcut, the honest information stops.

Bring specific deals rather than abstractions. Print the details of the last three deals won and the last three lost, and walk through each one chronologically. People describe processes inaccurately and describe events accurately, so anchoring in real cases is the single most effective facilitation choice available.

Write each stage as a state the deal is in, entered on observable evidence. Qualified means a stated requirement, an identified budget holder and an agreed next step, not a good feeling after a call. Proposal means a document sent covering scope and price. Negotiation means terms are being discussed with the person who can agree them. If two people in the room would place the same deal in different stages, the criteria are not specific enough yet.

Test each proposed stage against a simple question: what did the buyer do to cause this transition? Stages that correspond to something you did, such as sent brochure, are activities dressed as stages, and they inflate pipelines without telling you anything.

Handovers

Map every point where the deal passes between people or teams, and name the owner on each side and the artefact that passes with it. Work is lost at boundaries far more often than within them. The handover from sales to delivery deserves particular attention, since that is where customer disappointment is most often manufactured.

Exceptions

Ask what happens with an unusual discount request, an urgent order, a customer with an unpaid invoice, a request outside your normal scope. These consume a surprising share of the week and appear in no documented process. Even a rough rule agreed in the room saves repeated escalations.

Publish the one page map within two days while the discussion is fresh. Reconfigure the CRM to match: stage names, entry criteria as required fields at transition, and the handover as an actual assignment rather than an email. This step is what makes the map real, because the tool people use every day is a stronger teacher than any document.

Then review after a month. Are deals sitting in the stages the map predicted? Are the required fields being completed or worked around? Has anyone reverted? A short review at that point catches drift while it is still a conversation rather than a rewrite.

Configuring the agreed process is straightforward in HelloGrowthCRM, where stages, entry requirements and handover ownership are set once and then applied to every deal, which mostly matters because a process that only exists on a wall is a process everyone is free to ignore.

Related reading on process and pipeline design: sales automation, lead management software, what a CRM does, CRM for small business, features, and use cases.