Research teams wasted hours recreating questions. Built reusable library driving 37% team adoption in 30 days.
Research teams were recreating the same screening questions across multiple studies—wasting time and introducing inconsistencies. More critically, we needed to support an enterprise client renewal worth $70K ARR, and the Question Bank was a key feature in their decision.
Beyond the immediate sales need, our product goal was clear: create feature stickiness and switching costs. Teams with well-built, widely-adopted question libraries would find it painful to migrate to competitors.
I designed an end-to-end Question Bank and Screener Mapping system that allowed researchers to build, share, and reuse question components across their teams—streamlining setup while creating strategic lock-in.
The Question Bank exceeded adoption targets within 30 days and continued growing post-launch.
Centralized library where teams can create, organize, and manage reusable screening questions. Designed with tagging, search, and team-level sharing for scalability.
Intelligent mapping system that connects bank questions to study screeners, maintaining data consistency and reducing setup time. Handles complex logic and branching.
Permission controls and sharing mechanisms allowing teams to build shared libraries while maintaining appropriate access levels.
User Research: Conducted interviews with 8 research teams to understand current workflows, pain points, and mental models around question reuse.
Competitive Analysis: Studied how Qualtrics, SurveyMonkey, and Rally handled question libraries to identify best practices and gaps.
Cross-Product Thinking: Designed for both Research Hub and Recruit products simultaneously, ensuring consistent experiences across platforms while respecting each product's unique workflows.
Scalability Planning: Collaborated with engineering to ensure the architecture could support enterprise teams with hundreds of questions and complex organizational structures.
Marketing Collaboration: Worked with marketing to position the feature correctly in sales conversations and customer communications.
Feature Stickiness is Strategic: This project taught me how to design for lock-in without compromising user value. The question bank genuinely saves time while creating switching costs—a win-win.
Adoption vs. Usage Depth: While project-level usage remained low (5%), team-level adoption was strong (37%). This taught me to focus on the right success metrics—teams were keeping the feature in their toolbox even if not every project needed it.
Cross-Product Design Challenges: Designing for Hub and Recruit simultaneously revealed subtle workflow differences that required thoughtful abstraction without over-generalizing.
Sales Escalation Pressure: Delivering under a renewal deadline taught me to prioritize ruthlessly—we shipped an MVP that met the core need, then iterated based on usage data.
What I'd Do Differently: I would have invested more in onboarding and education. The feature's power wasn't immediately obvious to new users, leading to slower initial adoption than we hoped.