Map One Marketing Workflow

It is not a flow diagram built for a presentation. Before you automate a buyer path, you need to know what the path does on a Tuesday, including the step nobody owns and the failure that makes no sound. Most teams automate the breaks along with the work, because they never wrote the path down.

Forrester's Revenue Operations Survey 2024 found that 46% of revenue operations leaders say their processes are mostly manual, 49% say the processes are not flexible enough to respond when conditions change, and 38% name data accuracy as a top challenge. These teams are not refusing new tools. Wharton's 2025 AI Adoption Report found that 82% of enterprise leaders use generative AI at least weekly, and 75% report positive returns. The gap is that the process was never documented, so the automation copies the handoff as it actually is. The sequence from a map to a running path is in workflow orchestration.

Which path should you map first?

Map the path that fails in public. Not the most complex one. The one people can describe in plain words: a customer waiting, a late follow-up, a missed handoff that shows up in a support note, or a metric that has been flat for months with no explanation. If the team cannot say what goes wrong today, you do not have a path you can map in an hour. You have a debate.

Where does the failure already show up?

Useful first maps include the form to the first sales reply, a demo request to a calendar booking, a webinar signup to the follow-up, a qualified lead to an assignment, a trial start to the first onboarding touch, a churn signal to a retention action, or a quote request to a proposal. Any of those works if the team can say what goes wrong today. Pick the one where a buyer has already waited, because that wait is evidence you will not have to invent in the room.

Why is the longest path the wrong first session?

A ten-step sequence that touches six systems and runs for 30 days is the wrong first session. Too many owners, and the hour turns into a debate about how it should work. Three to five steps is enough. The blank cells will show you the complexity without you having to map the whole month. Keep the scope of the hour to that one path.

What does a blank cell tell you before you sit down?

If you cannot fill every field for every step before you sit down, that is the path to map. A blank owner means whoever happens to look. A blank failure path means the step fails and nobody knows, which means the buyer waits and the lead ages with no alert. You cannot rank a failure you have not named, and you cannot name it until the cell exists on the page.

The five fields.

The five fields are the whole map. A blank in any of them is a finding, not a formatting gap. Write them for the path as it runs today. If you write them for the path you wish you had, the hour produces a poster.

What does each field have to name?

• The trigger is the specific event that starts the step, such as a form submit, a CRM field change, a calendar event, a score threshold, or time elapsed. "When a lead comes in" is not a trigger, because nobody can automate a phrase that vague.
• The owner is one named person or one named system. A team name, or "whoever is free," means the step has an ownership problem, and you will feel it the first week someone is out.
• The tool is the system used for the step, or "manual" when a person does it with no system help. Manual is a complete answer. It tells you which steps are candidates to automate later, after the map exists.
• The output is the field written, the task created, the message sent, the route taken, or the decision recorded that the next step needs before it can start. "The lead is passed" is not an output.
• The failure path is what happens when the step does not finish: a retry, a review list, an alert to the owner, or nothing. Nothing is a valid answer, and it is usually the answer you act on first.

Why does the output field show the handoff?

The output field is the diagnostic. The trigger tells you how the step starts. The output tells you what the next step is waiting on. When the output is "the rep gets the lead," the handoff is a promise, and the next step starts on an assumption. When it is "a CRM task with the source, the company, and a reason in the notes," the next step has something to start from. A flowchart shows sequence. This map shows what moves between steps, and who is accountable when it does not arrive.

Why do teams leave the failure path blank?

The failure path is the field most teams skip, because writing down a failure feels like admitting a design flaw. A failure path of nothing means the buyer waits and the lead ages until someone happens to look. Naming it is not the same as fixing it in the hour. It is how you rank it later, on purpose, instead of discovering it in a stage conversion drop three months from now.

How do you run the 60 minutes?

Who belongs in the room?

Three people. The person accountable for the outcome, the person who does the work daily, and one person who can ask plain questions without a stake in the answer. A fourth can join if you need someone who knows the systems. More than four and the session becomes a debate about the ideal state. The ideal state is not the agenda. Current state is. If the person who does the work cannot attend, reschedule. A map built from memory of the work is how the blank owner stays blank.

How do you spend the four blocks?

1. Minutes 0 to 10: name the path and the first trigger as the exact event, such as "the demo form is submitted and a CRM entry is created." No summaries and no "usually."
2. Minutes 10 to 35: walk every step as it happens today, and fill all five fields before you move on. Do not skip the failure path, and do not describe how the step should work.
3. Minutes 35 to 50: mark the gaps. Unclear owners, manual relays, vague outputs, missing failure paths, and systems that do not pass data on their own.
4. Minutes 50 to 60: pick one break. Name it, assign one owner, and write one next action with a date.

What sentence keeps the session on today?

Open with one instruction, and expect to repeat it: "We are mapping how this path works today, not how it should work." When someone says what you are planning to do, write it in a side column and come back with "For the map, what actually happens today?" Ideal-state notes are useful, and they cannot share the cells with current state. If they do, the map becomes a wish, and a wish cannot show you the break.

Which questions show the hidden handoffs?

What do you ask about who sees the step start?

• What exact event starts this step, in one sentence, without the word "usually"?
• Who knows the step started, and do they know because of an alert, a task, a field change, or because they check a shared list by hand?
• Is there a named person who notices if the step does not start on time? If there is not, the trigger is invisible to the team.

What do you ask about what the next step receives?

• Where is the CRM entry updated when the step finishes?
• What does the next person or system need, as a specific field, task, or message?
• How would they know if that output was incomplete or late?

What happens if this step fails and nobody notices?

Ask that question on every step with a blank failure path. The common answers are "nothing until someone checks" or "eventually the rep asks marketing." Those mark a silent failure. The buyer waits, and nobody knows they are waiting. Silent failures outrank visible ones, because a visible failure at least creates a ticket. A silent one shows up later as a buyer who went quiet at a handoff nobody was watching. Write the answer in the failure cell even when the answer is embarrassing. An empty cell hides the wait. A cell that says "nothing" lets you rank it against the other breaks before the hour ends.

What breaks does the session usually find?

The same five patterns show up on a first map, regardless of company size or which tools are in the stack. They are what you get when the path grew faster than anyone wrote it down.

What are the five patterns?

1. The trigger is a person checking a shared list, so the step runs when their calendar allows, and it stops when they are out, with no alert.
2. The owner is a team name, which means nobody owns it, and when something goes wrong each person assumes another person has it.
3. The output is a Slack message, an email, or a verbal yes. None of those can start the next step reliably, and none of them can be queried when you need to know whether the handoff happened.
4. The CRM was never updated, so every later step that reads the CRM is working from a stale contact, and attribution breaks when the deal closes.
5. The failure path is nothing, so the sequence continues on incomplete information and the loss shows up later as a stage conversion drop.

Which pattern creates the longest delay?

The silent failure is usually the highest-impact finding, and it is hard to see until the CRM write exists. A step can fail quietly in part because there is nothing clean to query. Fix the write-back, then add the alert. That order is the smallest useful fix from most first maps. An alert on a field that never gets written will sit quiet, and you will think the path is healthy.

What does a finished map look like?

This example is illustrative, not a client result. It covers a demo request through the first sales action, in three steps, so you can see what "filled in" means before you try to fill your own.

How do you read the example?

The owner at step 2 is one named person, not a shared inbox. The output is a reason and a route in a specific field, not "the lead was reviewed." The failure path at step 2 is not silence. It is an alert that fires when four hours pass and the step is still open. That is the difference between a map you can hand to someone and a diagram that ends in a box labeled "sales." Read the row left to right: the trigger has to be an event a system can see, the owner has to be a name, and the output has to be the artifact the next row is waiting on. If any of those three is a mood ("the team handles it"), the row is not finished.

What does the failure column say about the map?

Step 1's failure path is the integration raising an alert. Step 2's is a clock that starts when the entry is created. Step 3's is the manager, who hears about it when the task sits unaccepted for two hours. A useful map has at least one failure path that is not silence. In most sessions, steps 2 and 3 start as "nothing." That is the finding. It is not a problem with the table.

What should you do in the first 24 hours?

Why do you pick one break instead of the list?

The session will surface four to seven findings. Most first maps do. Pick the one break that creates the longest buyer wait, touches the most volume, and can be owned by one person who can move it within ten business days. Everything else goes on a ranked list with the same five fields still attached, so you can come back without rerunning the hour. Ten action items at once means none of them have an owner, and the map goes into a folder. A list of ten breaks feels thorough in the room and produces no change by Friday, because nobody can tell which wait the buyer feels first.

What three rules does the action have to meet?

The action has three rules: one named person, one deliverable (a trigger, a field, an alert, or a manual step removed), and a date. "Next cycle" is not a date. Write it on the map before the session ends. A map without an owner and a date is a description of the problem. The description was the input to the hour. The output is the named fix.

What do you check at 72 hours?

The 72-hour test asks one question: has the named owner done anything concrete? If they have not made one move within 72 hours, the session did not fail. The follow-through did. The usual stall is a correct map with no action, or an action with no date and no one checking. A no at 72 hours means you go back to the map and find which cell is blocked, whether that is a missing login, a field nobody can edit, or an owner who was never actually free to do the work. You do not reschedule the same conversation and hope a second hour creates the accountability the first hour skipped. The path from a clean map to a workflow that runs without a manual relay is in the orchestration debt audit and the data contract between steps.

Map the handoff before you automate it. Get your free Systems Plan. From there we find the buyer path with the clearest break, then turn the map into one owned fix.

How we know this.

Forrester's Revenue Operations Survey 2024 is the source for the 46% mostly-manual figure, the 49% flexibility figure, and the 38% data-accuracy figure. Weekly generative AI use at 82%, and positive returns at 75%, come from Wharton's 2025 AI Adoption Report. The five fields are an operating schema for replacing a manual step, not a client diagnostic. The example map is illustrative, not a client result. The ranking of the five break patterns comes from the gaps these mapping posts keep finding, not from a private dataset of client scores.