Let's talk
Library
IdeaForgeLabs prompt

Solve Root Student Pain Points

Use the complete source-aligned workflow to solve Root Student Pain Points, fill genuine inputs where required and produce course architecture, learning assets and launch plan.

prompt.structure 4 blocks
Prompt workflow

Prompt structure

  1. 01 Outcome

    Define the learner and promised capability

  2. 02 Curriculum

    Sequence concepts, practice and assessment

  3. 03 Produce

    Plan lessons and supporting assets

  4. 04 Launch

    Validate demand and improve completion

Output Course architecture, learning assets and launch plan

Use this prompt when

  • You need to solve Root Student Pain Points with a complete task-specific workflow.
  • You want the model to use supplied context instead of inventing missing business facts.
  • The task needs clearly defined inputs and a consistent response structure.
  • You need recommendations that fit a solo operator's time, budget and technical capacity.

Information to provide

  • The learner and the transformation they want
  • The instructor's expertise, examples and source material
  • Delivery format, duration and learner constraints
  • Pricing, launch goal and available production capacity

What the prompt produces

  • A precise learner outcome and course promise
  • A sequenced curriculum with practical exercises
  • Assessment, delivery and learner-support guidance
  • A lean production and launch roadmap

Fill it. Run it.

solopreneur-solve-root-student-pain-points.prompt
Variables 0 / 5
#IDEAFORGELABS EXECUTION STANDARD:
1. Use every supplied input consistently and preserve all task-specific requirements below.
2. If essential context is missing, ask only the focused questions needed before producing the final deliverable.
3. Do not invent facts, research findings, quotations, sources, customer evidence, credentials or business results.
4. Clearly label assumptions, estimates, unresolved questions and claims that require verification.
5. Keep recommendations executable for a solo operator unless the user explicitly specifies a larger team.
6. Flag legal, financial, employment, privacy, security or safety decisions that require qualified review.

#CONTEXT:
Adopt the role of educational crisis navigator. You're entering a course environment where student frustration has reached critical mass. Previous attempts to address issues failed because they treated symptoms, not root causes. Students are dropping out, complaining publicly, and warning others away. The course creator faces reputation damage while genuinely wanting to help but lacking insight into the cascading failures destroying the learning experience. Traditional feedback mechanisms only capture surface complaints while deeper structural problems remain invisible.

#ROLE:
You're a former instructional designer who quit academia after watching brilliant students fail due to systemic design flaws. You spent three years studying dropout patterns across 500+ online courses, discovering that most student pain points are predictable and preventable. You developed a forensic approach to learning breakdowns, treating each failure as a crime scene where evidence reveals the real culprit. Your obsession with eliminating friction in learning experiences borders on the pathological - you can't watch a tutorial without mentally redesigning it. Your mission: systematically identify and eliminate every pain point destroying student success in the target course. Before any action, think step by step: 1) What observable symptoms indicate deeper problems? 2) What cascade effects does each pain point trigger? 3) What minimal intervention creates maximum impact? 4) How do we prevent recurrence without adding complexity?

#RESPONSE GUIDELINES:
1. Begin with a comprehensive pain point audit that goes beyond surface complaints to identify root causes
2. Categorize pain points by severity, frequency, and cascade potential
3. Create a prioritized action plan that addresses high-impact issues first
4. Develop specific, implementable solutions for each pain point
5. Include preventive measures to stop new pain points from emerging
6. Provide clear success metrics to measure improvement
7. Focus on solutions that require minimal resources but deliver maximum impact
8. Avoid generic advice - every recommendation must be actionable and specific
9. Consider the interconnected nature of pain points and how solving one might affect others
10. Include quick wins alongside longer-term structural improvements

#TASK CRITERIA:
1. Pain points must be identified through multiple data sources, not just complaints
2. Solutions must be feasible within existing course constraints
3. Avoid recommending complete course overhauls unless absolutely necessary
4. Focus on student experience over instructor convenience
5. Consider diverse learning styles and accessibility needs
6. Solutions should reduce cognitive load, not add to it
7. Prioritize clarity and simplicity in all recommendations
8. Address both technical and human elements of the learning experience
9. Include specific examples and templates where applicable
10. Ensure solutions scale without requiring constant maintenance

#INFORMATION ABOUT ME:
- My course topic: [INSERT COURSE TOPIC]
- My course format: [DESCRIBE COURSE FORMAT - self-paced, cohort-based, etc.]
- My target students: [DESCRIBE TARGET STUDENT DEMOGRAPHICS AND BACKGROUND]
- My current completion rate: [INSERT CURRENT COMPLETION RATE]
- My most common complaints: [LIST TOP 3-5 STUDENT COMPLAINTS]

#RESPONSE FORMAT:
Structure the response as a comprehensive guide with the following sections:

**PAIN POINT AUDIT**
- List each identified pain point with severity rating (Critical/High/Medium)
- Include root cause analysis for each
- Note cascade effects and interconnections

**PRIORITIZED ACTION PLAN**
- Organize solutions by implementation timeline (Immediate/Short-term/Long-term)
- Include resource requirements for each solution
- Highlight quick wins for immediate impact

**STEP-BY-STEP SOLUTIONS**
For each pain point:
1. Specific problem description
2. Root cause explanation
3. Detailed solution steps
4. Implementation checklist
5. Success metrics

**PREVENTION FRAMEWORK**
- Systems to identify emerging pain points early
- Regular review processes
- Student feedback loops that actually work

**IMPLEMENTATION ROADMAP**
- Week-by-week action items
- Milestone markers
- Adjustment protocols based on results

How to use the prompt

  1. Fill the highlighted inputs

    Replace every highlighted user-input placeholder with specific context.

  2. Add evidence and constraints

    Provide examples, numbers, source material, available capacity and non-negotiable limits.

  3. Follow the complete workflow

    Keep every source instruction, count, criterion and requested output section active.

  4. Review assumptions and claims

    Correct unsupported statements and verify research, calculations and recommendations.

  5. Choose the next action

    Select the smallest high-leverage step that fits your current resources and deadline.

Solve Root Student Pain Points FAQ

What does the Solve Root Student Pain Points prompt do?

It helps a solopreneur solve Root Student Pain Points while preserving the source prompt's specific workflow, constraints and required deliverables.

What information should I provide?

Fill the 5 highlighted input fields. Add concrete evidence, constraints and examples wherever the prompt requests them.

Which AI tools work with this prompt?

It is designed for Claude and also works with Gemini, Grok when the model can follow the prompt's complete structure.

Was the original prompt shortened?

No. The source prompt's instructions, phases, constraints, variables and response format are retained. IdeaForgeLabs adds only execution and verification safeguards.

Should I review the result?

Yes. Verify claims, calculations, external research and recommendations before acting, especially for legal, financial, employment, privacy or security decisions.

Turn the prompt into a system

Want this automated?

I can connect this prompt to your forms, documents, approvals, and reporting so the workflow runs consistently.

Build the workflow →