▸case-01 We've been trying to reduce customer churn for three quarters using various loyalty discounts and feature additions, but nothing seems to work. I feel like our team is trapped in a specific mindset about this problem. Can you help us uncover the underlying assumptions we're taking for granted and suggest a fresh, completely out-of-the-box strategy to address churn? | fail→fail | 20,111 | 32,524 | +62% | 1 | 1 | 0% | 2,666 | 3,345 | +25% | 0 | 0 | — |
▸case-02 I've been designing this software architecture for weeks, continually tweaking microservices boundaries, but I keep hitting the same complexity bottlenecks. I suspect I'm stuck in a dogmatic design pattern without realizing it. Please analyze my current approach, pinpoint the dominant mental model driving my decisions, and present an alternative frame that breaks away from it. | fail→fail | 17,297 | 21,196 | +23% | 1 | 1 | 0% | 2,270 | 3,004 | +32% | 0 | 0 | — |
▸case-03 Our marketing strategy for launching our new AI developer tool has stalled. Every idea we generate feels like a slight variation of standard SaaS product-led growth playbooks. We need an objective evaluation to spot the subtle cognitive traps anchoring our brainstorming and provide a reframed action plan that breaks out of those default assumptions. | fail→fail | 24,912 | 29,189 | +17% | 1 | 1 | 0% | 3,306 | 2,887 | -13% | 0 | 0 | — |
▸case-04 Our database engineering team has spent six months optimizing indexes and partitioning tables for PostgreSQL to handle high write volume, but we still hit throughput walls. Provide an evaluation that breaks us out of our current query-tuning mindset with an alternative paradigm. | fail→fail | 21,653 | 25,628 | +18% | 1 | 1 | 0% | 2,970 | 3,629 | +22% | 0 | 0 | — |
▸case-05 We are pricing our B2B SaaS product per active seat, but enterprise buyers keep capping user counts to stay under budget. Provide a strategic assessment of our pricing assumptions and propose an alternative monetization frame. | fail→fail | 20,858 | 26,056 | +25% | 1 | 1 | 0% | 2,673 | 3,574 | +34% | 0 | 0 | — |
▸case-06 Our cybersecurity team is constantly updating firewall rules and VPN configurations to secure our hybrid cloud infrastructure, yet lateral movement risks remain high. Deliver an evaluation that pinpoints our implicit security mindset and outlines a non-traditional defense model. | fail→fail | 20,688 | 26,856 | +30% | 1 | 1 | 0% | 2,891 | 917 | -68% | 0 | 0 | — |
▸case-07 Our e-commerce design team has run 15 A/B tests tweaking button colors, form fields, and step indicators on our multi-page checkout flow, resulting in negligible conversion gains. Provide an analysis that uncovers our design assumptions and outlines a completely reframed user flow. | fail→fail | 24,170 | 20,998 | -13% | 1 | 1 | 0% | 3,301 | 2,855 | -14% | 0 | 0 | — |
▸case-08 We are building an API for mobile clients and keep adding custom endpoints to aggregate nested backend resources, leading to continuous API maintenance pain. Evaluate our API architecture assumptions and present a fresh design paradigm. | fail→fail | 21,640 | 22,362 | +3% | 1 | 1 | 0% | 2,993 | 3,432 | +15% | 0 | 0 | — |
▸case-09 Our DevOps group keeps adding retry steps, parallel build nodes, and caching layers to speed up our monolithic Jenkins pipeline, but builds still take over 45 minutes. Provide a diagnostic that breaks down our pipeline assumptions and offers an alternative execution frame. | fail→fail | 23,354 | 19,115 | -18% | 1 | 1 | 0% | 3,127 | 2,644 | -15% | 0 | 0 | — |
▸case-10 Our content team publishes 20 keyword-optimized articles per week to boost organic search traffic, but total domain authority and conversion rates have stagnated. Evaluate our content growth strategy assumptions and suggest an alternative content engine. | fail→fail | 21,195 | 28,106 | +33% | 1 | 1 | 0% | 2,902 | 4,083 | +41% | 0 | 0 | — |
▸case-11 Our sales force spends weeks responding to enterprise RFPs, achieving a low 12% win rate while locking up our technical pre-sales resources. Provide an evaluation that uncovers our sales process assumptions and reframes our enterprise go-to-market approach. | fail→fail | 20,869 | 39,340 | +89% | 1 | 1 | 0% | 2,820 | 4,059 | +44% | 0 | 0 | — |
▸case-12 Our mobile game relies on daily login rewards and energy timers to drive retention, but long-term player churn remains high after 30 days. Analyze our player retention assumptions and propose an alternative engagement model. | fail→fail | 21,211 | 24,426 | +15% | 1 | 1 | 0% | 2,683 | 3,351 | +25% | 0 | 0 | — |
▸case-13 Our engineering organization requires candidate screeners to look for 5+ years of specific framework experience, resulting in a thin candidate pipeline and high rejection rates. Provide an assessment that breaks our hiring assumptions and proposes a reframed talent acquisition framework. | fail→fail | 21,528 | 19,690 | -9% | 1 | 1 | 0% | 2,976 | 2,857 | -4% | 0 | 0 | — |
▸case-14 Our product engineering teams keep tweaking story point estimation rules and sprint retro formats to boost velocity, but feature throughput has remained flat for a year. Provide an evaluation that pinpoints our team's structural assumptions and offers a reframed delivery model. | fail→fail | 22,036 | 30,400 | +38% | 1 | 1 | 0% | 2,962 | 3,205 | +8% | 0 | 0 | — |
▸case-15 Our data team runs nightly ETL batch jobs to power our analytics dashboard, but business stakeholders now demand real-time insights and our jobs keep failing during batch windows. Provide an evaluation that challenges our batch data mindset and outlines a reframed data processing model. | fail→fail | 23,279 | 25,818 | +11% | 1 | 1 | 0% | 3,246 | 3,682 | +13% | 0 | 0 | — |
▸case-16 Our product management team builds quarterly roadmaps by copying competitor feature matrices, but customer sentiment remains neutral. Provide an analysis that exposes our product planning assumptions and suggests an alternative roadmap strategy. | fail→fail | 23,447 | 18,803 | -20% | 1 | 1 | 0% | 3,033 | 2,704 | -11% | 0 | 0 | — |
▸case-17 Our logistics team continually increases safety stock levels across regional warehouses to prevent stockouts, raising holding costs without fixing delivery delays. Provide an assessment that identifies our supply chain assumptions and proposes a reframed inventory model. | fail→fail | 20,159 | 24,140 | +20% | 1 | 1 | 0% | 2,736 | 3,414 | +25% | 0 | 0 | — |
▸case-18 Our credit risk team keeps adding manual review rules and credit score thresholds to reduce default rates, but approval rates have plunged while defaults remain steady. Analyze our underwriting assumptions and suggest a reframed risk assessment model. | fail→fail | 20,279 | 20,652 | +2% | 1 | 1 | 0% | 2,835 | 3,066 | +8% | 0 | 0 | — |
▸case-19 Our customer success team continues building larger FAQ articles and chatbot decision trees to reduce ticket volume, but resolution time and customer satisfaction scores continue to drop. Provide an evaluation that breaks our support strategy assumptions and offers a reframed support model. | fail→fail | 20,296 | 21,083 | +4% | 1 | 1 | 0% | 2,745 | 2,576 | -6% | 0 | 0 | — |
▸case-20 Refactor this Python function converting a standard for loop accumulating numbers into a clean list comprehension. | pass→pass | 5,703 | 16,972 | +198% | 1 | 1 | 0% | 921 | 2,837 | +208% | 0 | 0 | — |
▸case-21 Calculate the net present value (NPV) for an initial investment of $100,000 with annual cash inflows of $30,000 for 5 years at a discount rate of 8%. | pass→pass | 8,597 | 11,510 | +34% | 1 | 1 | 0% | 1,808 | 2,290 | +27% | 0 | 0 | — |
▸case-22 Summarize the primary administrative features introduced in PostgreSQL 16 based on public release documentation. | pass→pass | 17,988 | 21,072 | +17% | 1 | 1 | 0% | 2,371 | 3,202 | +35% | 0 | 0 | — |