▸case-01 I'm running a SaaS company and our monthly churn is stuck at 15%. Right now, I keep viewing this as a product completeness issue—thinking customers leave because we lack features. We've tried adding new capabilities and running exit surveys, but nothing changed. I want to bring churn under 5%. Can you help me look at this from totally different perspectives—like how an outsider or child might view it, what reversing the premise looks like, or pushing it to the limits? Show what each view reveals, then highlight the single best angle and a concrete action item I should take next. | fail→pass | 21,267 | 24,213 | +14% | 1 | 1 | 0% | 2,829 | 3,215 | +14% | 0 | 0 | — |
▸case-02 Our team's pull requests take almost five days to get reviewed. I've been treating this as an accountability issue, assuming reviewers are just procrastinating or overly busy. I've tried sending automated reminders and setting aside review blocks on calendars, but the lag persists. My goal is to get average review turnarounds down to 24 hours. Break down this problem through distinct alternative lenses—such as a simple novice perspective, an outside domain's approach, an inverted view, and an extreme limit case. Explain the insight each frame uncovers, pick the most effective perspective for my situation, and suggest a specific next step. | fail→pass | 29,263 | 14,716 | -50% | 1 | 1 | 0% | 3,202 | 2,816 | -12% | 0 | 0 | — |
▸case-03 I'm designing a personal finance app, but users stop opening it after their first three days. I currently see this as an engagement design flaw, thinking the interface isn't fun enough. I've built streak trackers, added badges, and redesigned the dashboard, yet drop-off remains high. I want users logging expenses consistently for at least a month. Could you re-examine this issue using several unique viewpoints—such as how a kid sees it, how a completely different industry handles an equivalent issue, the opposite perspective, and an extreme scenario? Outline what each shift uncovers, tell me which frame is most useful, and give me a clear action step to execute. | fail→pass | 23,609 | 20,938 | -11% | 1 | 1 | 0% | 2,902 | 3,238 | +12% | 0 | 0 | — |
▸case-04 Our checkout service keeps failing due to database connection pool exhaustion during peak hours. Perform a 5 Whys root cause analysis to trace this issue back to infrastructure configuration. | pass→fail | 21,536 | 23,305 | +8% | 1 | 1 | 0% | 2,168 | 3,155 | +46% | 0 | 0 | — |
▸case-05 Draft a formal status update email for executive stakeholders regarding our delayed AWS cloud migration project, highlighting current progress, budget status, and revised milestones. | pass→fail | 21,440 | 35,061 | +64% | 1 | 1 | 0% | 2,006 | 5,316 | +165% | 0 | 0 | — |
▸case-06 List 10 specific product feature ideas to improve item recommendations on an e-commerce website, such as collaborative filtering upgrades or personalized email digests. | pass→fail | 23,934 | 35,244 | +47% | 1 | 1 | 0% | 3,049 | 5,276 | +73% | 0 | 0 | — |
▸case-07 Our customer success team is overwhelmed by tier-2 technical ticket escalations, causing average response times to jump to 48 hours. We currently view this as a staffing shortage—assuming we need to hire three more support engineers. We've tried overtime pay and routing tickets to developers, but backlogs keep growing. Our target is a sub-4-hour response window. Reframe this challenge using distinct angles like a child's simplicity, a non-tech industry model, inversion, and physical limits, detailing what each exposes and recommending a concrete action. | pass→fail | 26,751 | 16,465 | -38% | 1 | 1 | 0% | 3,340 | 2,965 | -11% | 0 | 0 | — |
▸case-08 We cannot find qualified senior Rust developers for our cryptography startup, with positions remaining open for over six months. We frame this as a talent scarcity problem in the labor market. We've increased referral bonuses and hired third-party recruiters without success. We want to fill three open engineering roles within 30 days. Help us reframe this using naive, outside-industry, inverse, and extreme perspectives to discover new insights and a concrete next move. | fail→fail | 26,451 | 20,510 | -22% | 1 | 1 | 0% | 3,017 | 3,051 | +1% | 0 | 0 | — |
▸case-09 Our internal dev team newsletter has a 12% open rate among engineers. We frame this as a delivery channel failure, assuming emails are getting buried in inboxes. We tried changing subject lines and sending on Tuesday mornings, but engagement hasn't moved. We want at least 50% of engineers reading our updates. Analyze this challenge through a novice view, a non-software domain approach, an inverted goal, and an extreme limit case, identifying what each reveals and pointing to a primary action. | pass→pass | 29,984 | 27,424 | -9% | 1 | 1 | 0% | 3,068 | 3,497 | +14% | 0 | 0 | — |
▸case-10 Our enterprise sales cycle takes 9 months from initial demo to signed contract. We frame this as a buyer procurement bureaucracy problem. We tried offering early-bird discounts and shortening pitch decks, but procurement timelines remain unchanged. Our goal is closing deals within 60 days. Reframe this challenge across naive, external sector, inverted, and extreme lenses, detailing what each uncovers and defining the top next step. | pass→pass | 25,977 | 15,858 | -39% | 1 | 1 | 0% | 2,887 | 3,021 | +5% | 0 | 0 | — |
▸case-11 Our developers never update project documentation, leading to long onboarding times for new hires. We frame this as a discipline and culture issue. We've tried mandatory pull request checklists and documentation Fridays, but docs remain outdated. We want documentation kept current after every sprint. Reexamine this using naive, cross-domain, opposite, and limit perspectives, outlining the insight from each and choosing the best action item. | pass→fail | 27,854 | 18,703 | -33% | 1 | 1 | 0% | 3,182 | 3,377 | +6% | 0 | 0 | — |
▸case-12 Our GPS tracking app drains smartphone batteries within 3 hours of continuous use. We frame this as an algorithm optimization problem, assuming our location polling code is inefficient. We've rewritten background threads and reduced location ping frequency, but users still complain. We need 12-hour continuous battery life. Breakdown this issue using a child's view, a non-tech domain solution, an inverted concept, and an extreme scenario, providing the insight from each and a single next move. | fail→pass | 23,356 | 20,049 | -14% | 1 | 1 | 0% | 2,677 | 2,966 | +11% | 0 | 0 | — |
▸case-13 40% of enrolled students drop out of our web development bootcamp before week 4. We frame this as a student motivation problem, believing students lack perseverance. We tried adding motivational coaching emails and peer study groups, but dropouts persist. We want a completion rate above 90%. Examine this through naive, outside industry, inverted, and extreme lenses, detailing what each reveals and identifying the best next step. | pass→pass | 29,589 | 14,031 | -53% | 1 | 1 | 0% | 3,186 | 2,696 | -15% | 0 | 0 | — |
▸case-14 75% of visitors leave our SaaS pricing page without clicking Start Free Trial. We frame this as a pricing tier complexity issue. We reduced our plans from five to three and added comparison tables, but bounce rates haven't changed. We want conversion rates above 15%. Reframe this using a naive lens, an outside domain example, an inverted approach, and an extreme condition, showing what each reveals and recommending the top action. | fail→pass | 27,982 | 19,693 | -30% | 1 | 1 | 0% | 3,276 | 2,995 | -9% | 0 | 0 | — |
▸case-15 Our commercial building projects exceed their budget by an average of 20%. We frame this as an unexpected material cost inflation problem. We tried renegotiating supplier contracts and adding 10% contingency funds, but overruns continue. We need projects delivered strictly on budget. Reexamine this challenge through a child's view, another industry's method, an opposite framing, and an extreme scenario, noting the insights and selecting a primary next step. | fail→pass | 24,802 | 19,764 | -20% | 1 | 1 | 0% | 2,770 | 2,697 | -3% | 0 | 0 | — |
▸case-16 New users register on our developer forum but rarely post a second message. We frame this as a lack of welcome incentives. We tried automated welcome badges and gamified reputation points, but user retention remains flat. We want 40% of new users returning weekly. Reframe this using naive, cross-industry, inverted, and extreme perspectives, detailing the insight from each and defining the immediate next move. | fail→pass | 28,384 | 14,348 | -49% | 1 | 1 | 0% | 2,926 | 2,824 | -3% | 0 | 0 | — |
▸case-17 Company meetings routinely run over their scheduled 60-minute duration. We frame this as poor agenda time management. We tried setting timers and appointing meeting facilitators, but overruns happen daily. We want all meetings capped at 30 minutes and ending on time. Reexamine this issue across naive, external field, inverse, and extreme lenses, detailing what each uncovers and offering a clear next step. | fail→pass | 20,849 | 20,162 | -3% | 1 | 1 | 0% | 2,711 | 3,001 | +11% | 0 | 0 | — |
▸case-18 Our retail branch experiences 60% annual staff turnover. We frame this as a compensation competitiveness issue. We increased hourly wages by 8% and offered flexible scheduling, but staff continue leaving after six months. We want annual turnover below 20%. Reframe this problem using naive, non-retail domain, inverted, and extreme viewpoints, explaining what each exposes and detailing the top action step. | fail→pass | 25,442 | 18,803 | -26% | 1 | 1 | 0% | 2,821 | 2,776 | -2% | 0 | 0 | — |
▸case-19 We have pitched 40 venture capital firms for our Series A round without securing a lead investor. We frame this as a pitch deck storytelling issue. We redesigned our slide deck three times and hired a pitch coach, but pitch rejections persist. We want to secure $5M in funding within 60 days. Reexamine this challenge through naive, outside industry, inverse, and extreme frames, outlining the insight each provides and suggesting the key next action. | pass→fail | 25,433 | 18,084 | -29% | 1 | 1 | 0% | 3,249 | 2,816 | -13% | 0 | 0 | — |
▸case-20 Deploying a release to production takes our infrastructure team 14 hours. We frame this as a manual testing slowdown. We tried parallelizing unit tests and upgrading build servers, but release time remains over 12 hours. We want automated deployments completing under 30 minutes. Reframe this using a naive angle, an outside industry approach, an inverted target, and an extreme limit case, showing what each reveals and recommending a next step. | fail→fail | 19,657 | 22,574 | +15% | 1 | 1 | 0% | 2,841 | 3,510 | +24% | 0 | 0 | — |
▸case-21 Only 10% of employees participate in our corporate wellness challenge. We frame this as an awareness and marketing problem. We sent weekly company-wide emails and posted flyers in breakrooms, but participation hasn't improved. We want 60% employee engagement. Reframe this challenge using naive, cross-domain, opposite, and extreme lenses, describing the insight from each and detailing the primary next action. | fail→fail | 23,528 | 18,633 | -21% | 1 | 1 | 0% | 2,711 | 2,601 | -4% | 0 | 0 | — |
▸case-22 68% of users who add items to their cart abandon the site before completing checkout. We frame this as unexpected shipping cost friction. We added a free shipping threshold banner and displayed estimated taxes early, but cart abandonment remains high. We want checkout completion rates above 50%. Reframe this problem through a simple child's lens, an outside domain model, an inverted premise, and an extreme boundary, outlining what each exposes and specifying a concrete next move. | fail→pass | 32,240 | 22,871 | -29% | 1 | 1 | 0% | 4,064 | 3,555 | -13% | 0 | 0 | — |