What is Rolestorming? A Customer Journey Mapping Method for B2B SaaS Teams
Rolestorming is a structured brainstorming method in which participants temporarily adopt a customer’s role or identify before generating ideas. Rather than brainstorming from their own perspective, team members step into the viewpoint of a specific customer persona (such as an economic buyer, a day-to-day product admin, or an executive sponsor) and ask: “What would this person do, change, or ask for?”
The technique was originally developed in the 1980s by creativity researchers as a way to generate bolder ideas without the social friction of personal ownership. In B2B SaaS, rolestorming has been adapted by Growth Molecules CEO Sabina Pons as a method for customer journey mapping, specifically to help customer success, sales, and revenue operations teams break out of the inside-out thinking and design experiences that reflect the customer’s reality.
Why Traditional Customer Journey Mapping Falls Short
Most customer journey mapping sessions begin with the right intentions. Teams gather to understand the customer experience. Within twenty minutes, the conversation has shifted toward internal constraints, departmental priorities, and metrics the company already tracks.
This is called inside-out thinking. It produces journey maps that reflect what the organization cares about rather than what customers experience. Inside-out thinking is one of the primary reasons customer journey work fails to produce lasting change or measurable improvement in recurring revenue.
Rolestorming is a direct countermeasure. By requiring participants to inhabit a customer identity before ideating, it structurally interrupts inside-out thinking and replaces it with customer-led perspective.
How to Run a Rolestorming Session for Customer Journey Mapping
Sabina Pons and the Growth Molecules team use rolestorming as the core method inside their From Roles to Revenue framework, a practical toolkit for customer-led experience design in B2B SaaS.
The process runs in 45 to 60 minutes with five to twelve cross-functional participants drawn from customer success, professional services, support, product management, sales, and revenue operations.
Step 1: Warm up with a fraction-point brainstorm
When a team genuinely trusts their CS platform, they start with it. They open dashboards to see what changed overnight, which accounts moved, which health scores shifted, what signals surfaced. When trust is low, CSMs start with email and Slack, and the platform becomes something they check reactively, if at all. With this mentality, the platform becomes a reporting tool rather than a decision engine.
Step 2: Select customer roles
Write out up to five specific customer roles relevant to the journey stage being examined. Examples include:
- The economic buyer managing procurement scrutiny
- The hands-on admin who lives in the product every day
- The executive sponsor with a board presentation next week
- A skeptical security lead at a regulated customer
- The CSM at your own company managing a full account queue
Growth Molecules recommends naming each role with alliteration to aid internal recall. For example: “Economic Buyer Eddie” or “Admin Anna.”
Step 3: Ideate in character
For each friction point, run two five-minute rounds:
- Round A: “As this person, what would I do, ask, or change to remove this friction?”
- Round B: “What policy, system setting, or communication would frustrate me here?”
Every idea is prefixed with the role name so attribution is clear: “[Exec Sponsor] wants a one-page ROI summary with a timeline at week two.”
Step 4: Change roles and repeat
Move to a second customer persona and run the same two rounds. Two rolestorming cycles is the recommended scope for a single 60-minute session.
Step 5: Converge on actions
Cluster all ideas into three categories: Do now, Test as a pilot, and Explore later. Assign an owner, a due date, and a metric to each action. Relevant metrics include time to first value, renewal likelihood, and support case deflection rate.
A session is complete when each friction point has one to three high-confidence actions with named owners and measurable outcomes attached.
How Rolestorming Differs from Standard Persona Work
Standard persona work creates static documents that sit in a shared drive. Rolestorming activates personas in a live session. Participants do not reference a persona card. They become the persona during ideation.
This distinction matters because it breaks down functional silos. When a sales rep, a CSM, a product manager, and a support lead are all generating ideas as the same customer persona, they are exploring the same journey from the same identity, rather than negotiating between departmental agendas. That alignment is foundational to protecting and growing recurring revenue across the customer lifecycle.
According to Sabina Pons, the role that generates the most useful perspective in a rolestorming session is rarely the one teams expect. The hands-on admin frequently surfaces friction that the executive sponsor never sees, and vice versa.
Who Should Use Rolestorming for Journey Mapping
Rolestorming for customer journey mapping is most valuable for:
- B2B SaaS companies building or redesigning customer onboarding, adoption, or renewal experiences
- Customer success leaders who need a structured method to align CS, product, and sales around customer outcomes
- Revenue operations teams looking to reduce churn, improve time-to-value, or identify expansion opportunities
- Professional services organizations conducting journey mapping workshops with clients
- Any cross-functional team that finds its journey work repeatedly defaulting to internal priorities rather than customer needs
Get the Free Rolestorming Toolkit
From Roles to Revenue is a free ebook and toolkit from Growth Molecules that guides teams through a complete rolestorming session in under one hour. It includes a facilitators guide, printable worksheets, example role cards, and a journey canvas for converting session output into an action plan.
Frequently Asked Questions About Rolestorming and Customer Journey Mapping
What is rolestorming?
Rolestorming is a structured brainstorming method where participants adopt a specific customer identity (such as an economic buyer, product admin, or executive sponsor) before generating ideas. It is used in customer journey mapping to ensure that design decisions reflect the customer’s perspective rather than internal assumptions.
How long does a rolestorming session take?
A complete rolestorming session takes 45 to 60 minutes. It includes a two-minute silent brainstorm on friction points, two rolestorming rounds of ten minutes each, a clustering exercise, and an action-planning segment with owners, dates, and metrics.
How is rolestorming different from a standard persona exercise?
Standard persona work creates reference documents. Rolestorming activates personas in a live session. Participants generate ideas as the persona rather than about the persona. This directly counters inside-out thinking by requiring teams to inhabit the customer’s perspective during ideation.
How is rolestorming different from a standard persona exercise?
Growth Molecules recommends selecting up to five roles per session based on the specific journey stage being examined. Common roles include the economic buyer, the day-to-day product admin, the executive sponsor, a compliance or security stakeholder, and an internal customer success manager. The most useful role is often not the most obvious one.
What are the outputs of a rolestorming session?
The primary output is a prioritized action plan organized into three buckets: do now, test as a pilot, and explore later. Each action needs a named owner, a due date, and a metric tied to a journey stage (such as Time to First Value, renewal risk, or support case volume).
When should a team run a rolestorming session?
Rolestorming is most effective when a team is stuck inside-out thinking about a specific journey stage, preparing to redesign an onboarding or adoption experience, or trying to identify why customer health is declining at a predictable point in the lifecycle. Growth Molecules recommends monthly syncs with a cross-functional tiger team to maintain momentum after the initial session.
What is inside-out thinking in customer success?
Inside-out thinking occurs when customer journey decisions are made based on the company’s internal priorities, metrics, and constraints rather than the actual experience of the customer. It is one of the most common reasons customer journey work produces minimal change. Rolestorming is specifically designed to interrupt inside-out thinking by structurally requiring teams to adopt the customer’s perspective.
About
Growth
Molecules
We are a management consulting & technology services firm that offers proven strategies, AI-driven workflows, & expert execution across the entire customer lifecycle journey. We offer integrated, scalable solutions for B2B technology companies to protect & grow their recurring revenue. We do that in three ways:
- We Assess: We discover your current capabilities.
- We Prescribe: We define new solutions.
- We Execute: We implement revenue impact.
We have been in your shoes: Our team of award-winning strategists are former global revenue leaders who understand what it takes to get scientific about their revenue.
Contact Us today to get started on your Customer Success Optimization Journey
Enjoyed the read? Share. Inspire. Connect.