The signal
Customer-facing work needed a consistent way to become a useful success story. A record of activity alone did not explain the customer’s problem, what the CSM contributed, or what changed. The capture process needed to make those distinctions explicit.
The dig
The intake included organizational context and account-team information, then the essential narrative: customer problem, CSM actions, and outcome. Stories also mapped to leadership reporting categories so the output was organized for its intended audience.
The response
I created the intake, Power Automate workflow, PowerPoint template, and SharePoint site and folder structure. An engineer helped connect the automation output to the presentation template.
The point was not to create another reporting chore. It was to give field contributions a repeatable structure and turn submitted information into a consistent presentation format.
What changed
Submitted information could become a templated customer-success slide, with a repository for organizing the material. The practical result was a repeatable capture-and-output process: a consistent way to describe the customer problem, credit the work, and preserve the outcome for later use.
What this case teaches
Make the customer’s change the center of the story. Record the action, the evidence, and the contribution clearly enough that someone else can understand them later.