Reconstruct a recent customer workflow
Use one recent customer example to map the workflow from start to finish, including difficult moments and workarounds.
- Preparation
- One interview round plus evidence review
- Steps
- 6
- Difficulty
- Moderate
- Task
- Map the current customer workflow
Requires: Choose the customer job and a recent instance to reconstruct. Prepare participant codes and an approved evidence register.
Uses: Google Sheets
Back to the Task: Map the current customer workflowBefore you start
Prepare
- Choose the customer job and a recent instance to reconstruct.
- Prepare participant codes and an approved evidence register.
Steps
Work through the method
Use the listed inputs and tools. Check the evidence when you need to verify a step.
Select one recent instance
Ask the participant to choose a completed or attempted example they can reconstruct.
Step details and sources
Why it matters: A specific instance limits speculation about typical behaviour.
- Input
- The target customer job.
- Output
- A dated or bounded example.
Tools in this stepGoogle SheetsEvidence for this step
A practitioner recommends reconstructing a recent workflow from start to finish before evaluating solutions.
First Round Review: EARLY EXPLORATION; workflow script beginning “walk me through the last research project you did”The examples come mainly from software product research.Vanta’s founder describes using recent calendars to reconstruct customer work after solution-first ideas failed.
First Round Review: Zeroing in on the Right Problem to PursueThis is a retrospective founder account from one company.
Trace the sequence
Walk from the trigger to the final outcome and record each action in order.
Step details and sources
Why it matters: The full sequence shows work around the proposed solution.
- Input
- The recent example.
- Output
- An ordered action list.
Tools in this stepGoogle SheetsEvidence for this step
A practitioner recommends reconstructing a recent workflow from start to finish before evaluating solutions.
First Round Review: EARLY EXPLORATION; workflow script beginning “walk me through the last research project you did”The examples come mainly from software product research.
Record tools and hand-offs
For each action, record the tool, person, information, and hand-off involved.
Step details and sources
Why it matters: Tools and hand-offs reveal dependencies within the current workflow.
- Input
- The ordered action list.
- Output
- A workflow table with dependencies.
Tools in this stepGoogle SheetsEvidence for this step
A practitioner recommends reconstructing a recent workflow from start to finish before evaluating solutions.
First Round Review: EARLY EXPLORATION; workflow script beginning “walk me through the last research project you did”The examples come mainly from software product research.
Find the difficult moments
Ask which step took the most effort, caused delay, introduced risk, or required rework.
Step details and sources
Why it matters: The difficult moment must come from the participant’s account.
- Input
- The workflow table.
- Output
- Evidence-linked difficult moments.
Tools in this stepGoogle SheetsEvidence for this step
Vanta’s founder describes using recent calendars to reconstruct customer work after solution-first ideas failed.
First Round Review: Zeroing in on the Right Problem to PursueThis is a retrospective founder account from one company.The Forces of Progress framework defines push, pull, anxiety, and habit around a concrete struggling moment and switch.
Jobs to be Done: The Forces of Progress; The Struggling MomentThe framework does not establish any candidate’s forces by itself.
Capture the workaround
Record what the participant does today and why that option remains acceptable or necessary.
Step details and sources
Why it matters: The current workaround shows the existing alternative and its constraints.
- Input
- The difficult moments.
- Output
- A current-workaround record.
Tools in this stepGoogle SheetsEvidence for this step
A practitioner recommends reconstructing a recent workflow from start to finish before evaluating solutions.
First Round Review: EARLY EXPLORATION; workflow script beginning “walk me through the last research project you did”The examples come mainly from software product research.
Compare without erasing differences
Align common steps across interviews and retain exceptions, missing steps, and contrary cases.
Step details and sources
Why it matters: A shared pattern should remain traceable to individual evidence.
- Input
- Several coded workflow tables.
- Output
- A comparison with common and divergent steps.
Tools in this stepGoogle SheetsEvidence for this step
A practitioner recommends preserving transcripts and pressure-testing early themes before choosing a solution.
First Round Review: FIGURING OUT WHAT TO GO AFTER; Mistake #1: Chasing themesThe source is an edited practitioner interview.
Success checks
Check the result
- Every step comes from a recent participant example.
- Difficult moments and workarounds link to source evidence.
- Differences between workflows remain visible.
Failure modes
What could go wrong
- Return to the interview when the workflow contains guessed steps.
- Separate the maps when distinct segments use materially different workflows.
- Do not let an automatic transcript summary replace source checking.
Tools
Choose tools
Google Sheets
A shared spreadsheet for source-linked research, decisions, and operating records that people can inspect and correct.
Check fit, limits and pricingSources
Check the sources
Check what each source supports and where the advice has limits.
- First Round Review: Vanta's Path to Product-Market FitEdited founder interview · Publication date unavailable
- First Round Review: A UX Research Crash Course for FoundersEdited practitioner interview · Publication date unavailable
- Jobs to be Done: The Forces of ProgressTraining-provider framework · Publication date unavailable
- Google Workspace: Share files from Google DriveOfficial help documentation · Publication date unavailable