Overview
StoryJam started as a create-a-thon fix for remote story pointing. Research revealed a bigger problem: participation imbalance appeared across every ceremony type, and facilitation couldn't fix it. I advocated for expanding scope to a general-purpose participation platform, set the MVP constraint, and led from research through shipped product. My contribution was problem framing, research direction, design requirements, and delivery tradeoffs, not UI design itself.
Activities Led
Role
End-to-end PM: problem framing, scope, research direction, and delivery across a cross-functional team
Team
3–4 engineers, 1–2 designers, embedded throughout
Status
Shipped & Scaled
Duration
~8 months (discovery → build → launch → iteration)
FROM PAIN POINT TO PLATFORM
Started as a team's frustration with remote story pointing. Research showed participation imbalance was structural and cross-ceremony. Expanded scope to a general-purpose participation platform, scoped tightly to learn from adoption.
DESIGNED FOR HOW MEETINGS ACTUALLY WORK
The create-a-thon prototype broke in real meetings. Defined the minimum flexibility threshold before building the MVP: anything that would prevent a session from continuing had to be handled.
The problem
The team's pain point was real, and bigger than they thought
StoryJam started in a FordLabs create-a-thon. Remote story pointing on Webex and Slack wasn't working because responses appeared in real time and influenced whoever hadn't weighed in yet. Existing tools felt clinical. The designers chose a fruit-themed concept that made sessions feel warm and playful, and when we tested it, participants responded immediately.
Leadership asked whether there was a wide enough audience to justify building and scaling it, and whether it could demonstrate the quality of product FordLabs' process could produce. The answer would determine whether this remained a one-team prototype or became a real investment.
Early prototype, the fruit-themed interface from the create-a-thon
Research insights
Participation looked open. The mechanics said otherwise.
Across 9 interviews and 13 observed sessions spanning planning, retrospectives, and prioritization, five insights reshaped what we built.
Insight 1
Visibility timing, not culture, drove the imbalance.
Early submissions anchored later responses. Vote distributions narrowed. Senior input disproportionately shifted direction. These effects appeared regardless of facilitation quality.
Insight 2
Intent couldn't overcome mechanics.
PMs actively encouraged equal participation. It didn't matter. Quieter participants, especially junior team members and non-native English speakers, withheld input regardless. The tools determined who influenced the outcome, not the effort.
Insight 3
The problem crossed every ceremony type, and story pointing was declining.
Participation imbalance appeared in planning, retrospectives, and prioritization. Story pointing itself was losing traction. If the tool only served one ceremony, the audience wasn't there.
Insight 4
The prototype broke under real meeting conditions.
Late joins altered vote distributions. Multi-round discussions were common. Participants dropped off. I defined the minimum flexibility threshold: anything that would prevent a session from continuing had to be handled.
Insight 5
Facilitators were stuck in a lose-lose — and they controlled adoption
Participate and bias the outcome, or disengage and lose control. No mode let them do both. We also found facilitators held informal influence over tool adoption. Any approach requiring training wouldn't survive. I defined the requirement for a facilitator role that could manage sessions without submitting input.
Before: Open Visibility
Open session begins
All responses visible in real time
Early responses appear
First input sets the reference point
Anchoring takes hold
Subsequent responses cluster around the anchor
Decisions narrow
Group converges before independent thinking surfaces
After: Protected Independence
Private input collected
Each participant responds independently
Responses remain hidden
No visibility until everyone commits
Simultaneous reveal
All perspectives surface at the same moment
Independent perspectives surface
Teams converge with genuine diversity on the table
The core mechanic: changing when visibility enters the system changes what teams have to work with.
Synthesized from 9 interviews and 13 observed sessions into the scope and sequencing for the platform.
Strategic decisions
Two calls that defined the scope and the constraint
I did not design the UI. The designers created the visual design, interaction patterns, and fruit concept. My contribution was defining the problem, directing research, facilitating design direction, and making the strategic calls that shaped what got built.
Decision
Scope reframe: participation platform, not pointing tool
Story pointing was declining, but participation imbalance appeared across every ceremony type. I advocated for expanding scope to a general-purpose platform — no tailored affordances for any specific meeting type.
Tradeoff
Risks being too generic.
Why It Held
Addressing the systemic failure mattered more than optimizing one declining ceremony, and post-launch usage confirmed teams used it across contexts.
Decision
MVP constraint: ship to learn, not to finish
The team was divided on whether to build beyond story pointing. I advocated for the broader scope but constrained the build to MVP. Don't overbuild. Let adoption signals guide what to build next. When a valid feature request came in, I held it until usage data confirmed the need was widespread.
Tradeoff
Delayed features teams were asking for.
Why It Held
Building without adoption data risks investing capacity in edge cases.
The solution
Protect independent input. Reveal simultaneously. No instructions needed.
The core mechanic was private input → hidden signals → simultaneous reveal. The interface enforced the sequence. Participants could not see others' input before commitment. Facilitators could not override the order.
The warm visual tone reduced social anxiety through design. The mechanic reduced it through structure.
No facilitation guides. No training materials. No moderation rules. If the design is right, it should not require instructions.
Accessibility was embedded from day one through WCAG 2.1 AA user stories, testing, and engineering collaboration.
Results
Teams could diverge before they converged
By protecting independent input before visibility, senior voices no longer set the anchor. Quieter participants no longer self-censored. Teams arrived at convergence with genuine diversity already on the table.
The tool didn't change how teams made decisions. It changed what they had to work with when they did.
Measurement was built in from day one. Instrumented with Amplitude, A/B tested launch CTA — both variants exceeded internal benchmarks by 2–3×. Leading and lagging indicators were defined before launch.
612
Monthly active users
2–3×
Launch engagement vs. internal benchmarks
4.3 / 5
Satisfaction rating
"A tool I am using to build psychological safety is StoryJam. It builds psychological safety because people get to state their opinion without being biased by other people's answers first. Everyone on the team participates and hopefully feels valued. This greatly improves the quality of our discussions and encourages challengers to open up in a safe way."
"It changed our story pointing sessions. I used to dominate discussion — now more people speak up."
After launch
Set up the next team to make their own decisions
After scope expanded, three design concepts were on the table. I facilitated the team through evaluating each concept against its riskiest assumptions. The goal wasn't consensus — it was structured evaluation: identifying which unknowns would kill a concept if they turned out to be wrong, and which could be tested cheaply. The team decided together. My role was structuring the conversation so direction was evidence-driven.
While waiting for adoption data, I led the team through a continuous discovery framework: identify the problem, generate distinct solutions, prioritize assumptions, test to decide. This became a handoff artifact — not a feature backlog, but a decision framework for the team continuing after I rolled off.
The team decided together. I brought the structure.
What This Taught Me
Mechanics scale. Intent doesn't.
What looked like a facilitation problem turned out to be a sequencing problem. Once visibility entered too early, influence was already shaping group judgment before real discussion began.
That changed the real design task. The highest-leverage move was not refining a better story pointing flow, but reframing the brief entirely. By redefining the problem before build, we avoided shipping a polished tool for the wrong scope.
The broader lesson is one I now look for across product work: when a pattern survives across teams, ceremonies, and facilitators, the failure is usually structural.
Transferable Principle
When the problem is structural, change the structure.