Quotas & Quota Automations
Enterprise API partners needed automated participant screening. Designed end-to-end quota system in 90 days.
The Challenge
After shipping Multiple Panels, our squad had to rapidly pivot focus to Recruit and Recruit API—our highest-revenue products. New opportunities revealed critical gaps in reporting, fraud prevention, and quota management. Most critically, our growing unmoderated study segment and API partners needed automated participant flow through the research funnel.
I stepped in to lead design and research for the Quotas feature under a high-pressure Q4 timeline. This project required me to:
- Rapidly ramp up on unfamiliar product domains (Recruit API, unmoderated workflows) - Build deep cross-product context while executing at a senior-to-staff level - Coordinate across squads amid constantly shifting priorities - Design for both manual researcher workflows AND API automation
The resulting Quotas solution allows automated movement of participant segments through the research funnel, supporting both enterprise workflows and API integrations.
Business Impact
Quotas directly addressed a critical gap in our product suite, unlocking both immediate sales escalations and long-term API partnership growth.
Key Features Designed
Quota Configuration
Flexible quota setup allowing researchers to define participant segments (demographics, behavior, custom attributes) and target quantities. Designed for both simple and complex quota structures.
Automated Funnel Management
Automation system that moves participants through the research funnel based on quota rules—automatically accepting, rejecting, or waitlisting based on segment availability.
Real-time Quota Tracking
Dashboard showing live quota fill status, helping researchers monitor progress and make adjustments. Critical for time-sensitive research projects.
API Integration
Designed quota management to work seamlessly with Recruit API, enabling external partners to run studies with automated quota enforcement.
High-Pressure Execution
Rapid Domain Learning: This project threw me into unfamiliar territory—API workflows, unmoderated research mechanics, fraud prevention requirements. I had to build context quickly through customer interviews, competitive research, and technical deep-dives with engineering.
Cross-Squad Coordination: Worked closely across multiple teams: -
Shifting Priorities: The Q4 timeline meant constantly re-evaluating scope. I learned to identify the "must-ship" features that unlocked customer value versus nice-to-haves that could wait.
Design Under Pressure: This project tested my ability to maintain design quality while moving fast. I prioritized research on the highest-risk assumptions and used rapid prototyping to validate quickly.
Key Learnings
Rapid Context Building: This project proved I could step into unfamiliar domains and execute at a senior level quickly. The key was asking the right questions early and building relationships with domain experts.
Managing Ambiguity: With constantly shifting priorities, I learned to design flexible systems that could adapt as requirements evolved. The quota configuration system is modular enough to support future use cases we haven't imagined yet.
Balancing Speed and Quality: Under Q4 pressure, I learned which design decisions needed deep research and which could be validated post-launch. Not everything needs to be perfect on day one.
API-First Thinking: Designing for both manual workflows and API automation simultaneously taught me to think in terms of underlying data models and automation rules rather than just UI flows.
What I'd Do Differently: I would have pushed harder for earlier customer validation. We made some assumptions about quota complexity that later proved incorrect, requiring a mid-project pivot. Earlier access to real customer data would have saved time.
Career Growth: This project demonstrated my ability to thrive under pressure, rapidly build context in new domains, and coordinate across multiple teams with competing priorities—all key skills for staff-level design roles.