Before jumping into building solutions, it’s super important to decode and analyze the Problem Statement (PS) properly. Many teams fail not because their idea is bad, but because they misinterpret the PS, overestimate feasibility, or pick something flashy that doesn’t align with their team’s skills.
👉 Use this prompt to get a detailed, structured breakdown of any PS you’re considering. Just copy-paste it into ChatGPT (or your mentor tool) along with your PS description, and it will analyze across all the key factors you need to know.
The Prompt -
I have a Problem Statement from SIH (or hackathon). Please analyze it in detail across the following factors and give me a structured breakdown.
Make the output visually good with proper formatting, sub-headings, bullet points, and emojis.
Also, wherever possible, add insights from competitor analysis, existing apps, websites, or research papers related to this PS.
- Pain Points & Core Understanding 🔎
- What exact problem is being addressed?
- Why does this problem exist (root causes)?
- Who are the primary stakeholders/users affected?
- What are the current challenges or inefficiencies in solving it?
- Feasibility of Execution ⚙️
- Can a working prototype be realistically built within the hackathon timeline?
- What are the technical requirements (APIs, datasets, hardware, integrations)?
- What could be blockers (data availability, regulations, scaling issues)?
- What MVP (minimum viable product) can be achieved to impress evaluators?
- Impact & Relevance 🌍
- Who benefits from this solution (citizens, govt, industry, students, etc.)?
- What real-world impact can it create (economic, social, environmental)?
- Is it scalable beyond a hackathon (enterprise, state-level, national-level)?
- Why would evaluators find this problem important?
- Scope of Innovation (Existing Solutions) đź’ˇ
- Are there existing products/solutions in this space?
- What are their limitations?
- Provide a short competitor analysis (apps, platforms, or research papers).
- What new/innovative approach can be added here (features, tech stack, process improvements)?
- How can the solution stand out technically (AI, Blockchain, AR/VR, IoT, UX design, etc.)?
- Clarity of Problem Statement 🧩
- What exactly is being asked (clear deliverables)?
- Where can teams misinterpret the PS?
- How should the solution be framed so evaluators see clarity and alignment?
- Evaluator’s Perspective 🎯
- How will an evaluator judge this PS?
- Which criteria matter most (uniqueness, feasibility, sustainability, impact, product completeness)?
- What are the red flags evaluators might notice?
- Strategy for Team Fit & Execution đź‘Ą
- What skill sets are needed in the team (backend, frontend, AI/ML, hardware, design, presentation)?
- What would be the ideal team ratio for this PS?
- Suggest a step-by-step approach to research and ideation before solution building.
đź“Š Output Requirement:
Make the final output visually engaging with: