The problem behind the process
Events, research, assessments, sales conversations, and consulting offers existed, but the experience needed a clearer path between them. A person could attend an event and still be unsure what happened next. Internally, the team also needed consistent timing, ownership, and decision points.
I helped turn separate activities into a designed journey. Each touchpoint needed to create value for the participant while making the next appropriate action easier to understand.
Every touchpoint answers one question and earns the next.
Start with permission, not pressure
The journey begins when an engaged lead chooses to share contact information through a relevant offer, assessment, or event. This creates a more respectful foundation than treating every audience member as sales-ready.
Make follow-up useful
Post-event communication was designed to offer reflection, diagnosis, and a recommendation package rather than immediately jumping to a proposal.
Design the “no” path too
Declining or not completing an assessment did not make someone a failed lead. The process included lower-pressure nurture and later follow-up paths.
Translate a system into team behavior
Timing, channels, decision points, and next actions were mapped so that the journey could be executed consistently rather than living in one person’s head.
A funnel describes movement. A journey explains experience.
The strongest process was not the one with the most follow-up. It was the one in which each interaction gave the participant a reason to trust the next step.Case-study reflection
Original process documentation.
These files show the actual thinking and sequencing behind the case study. Before a public launch, the organization should approve direct publication; otherwise, the website should show recreated excerpts while retaining the originals for private review.
Process design is experience design. Timing, language, ownership, and decision points determine whether people feel guided through a system or processed by it.