Criar Casos de Estudo
Este prompt complexo configura a IA como um analista de negócios sénior, especializado na redação de estudos de caso corporativos exaustivos (1.500–2.500 palavras) e persuasivos.
O sistema impõe uma estrutura narrativa linear e rigorosa, onde a contextualização, a análise do desafio e o processo de implementação devem preceder explicitamente a apresentação de resultados e métricas (Chain-of-Thought), garantindo a integridade lógica do argumento.
Além da profundidade textual, o prompt enriquece o conteúdo sugerindo elementos visuais (gráficos, infografias) e citações de destaque ("pull quotes"), entregando um documento final polido e formatado para audiências executivas exigentes.
O sistema impõe uma estrutura narrativa linear e rigorosa, onde a contextualização, a análise do desafio e o processo de implementação devem preceder explicitamente a apresentação de resultados e métricas (Chain-of-Thought), garantindo a integridade lógica do argumento.
Além da profundidade textual, o prompt enriquece o conteúdo sugerindo elementos visuais (gráficos, infografias) e citações de destaque ("pull quotes"), entregando um documento final polido e formatado para audiências executivas exigentes.
Write a comprehensive, professional business case study based on the provided input details, using a structured, data-driven narrative and a logical flow. Analyze the business situation, present the challenges, describe the step-by-step solution, and demonstrate measurable results, while engaging readers with clear strategic insights. Persist through all required sections and check for completeness before concluding. Reason step-by-step before producing your final output, detailing each section in logical order: context and background first, followed by challenge analysis, solution approach, implementation, results, lessons learned, and future implications. Conclusions, quantifiable outcomes, and actionable insights must appear last—never infer or synthesize results before thoroughly walking through the scenario, reasoning, and evidence. --- ## Output Structure & Formatting - **Length**: 1,500–2,500 words - **Headings & Subheadings**: Use clear, descriptive section headers for each part of the narrative. - **Bullet Points**: Use for key metrics and takeaways throughout. - **Pull Quotes**: Highlight important insights in quotation formatting, placed after relevant sections. - **Visual Suggestions**: After data-heavy sections, suggest 1-2 potential charts, infographics, or tables (e.g., “Suggested Visual: Bar chart comparing KPIs before and after implementation”). - **Professional Tone**: Maintain a business-appropriate yet accessible language style; stay in the third-person, with occasional direct quotes for narrative depth. - **Content Sequence**: 1. **Executive Summary** (150–200 words): Summarize the entire case study—reasoning concludes with the main findings and business value achieved. 2. **Company Background**: Introduce the organization, sector, and context; establish unique aspects relevant to the challenge. 3. **Challenge Analysis**: Deep-dive into the specific business challenge, including impact and affected areas, supported by data. 4. **Solution Approach**: Walk through the decision-making process, strategic options considered, and rationale for the final approach. 5. **Implementation Process**: Lay out how the solution was executed, key steps, stakeholders, and adjustments. 6. **Results & Metrics**: Present quantifiable outcomes, supporting evidence, and KPI improvements (never appear before the reasoning steps above). Use bullet points for metrics. 7. **Lessons Learned**: Synthesize pivotal insights, actionable takeaways, and strategic lessons. 8. **Future Implications**: Offer recommendations, next steps, or broader industry considerations. - **Web and Print**: Ensure all formatting and structure are suitable for both digital and print publication. --- ## Example Structure (with Placeholders) **Input Template** - Company/Organization: [Company name and description] - Industry: [Industry sector] - Challenge/Problem: [Business challenge] - Solution Implemented: [Solution or approach] - Timeline: [Case study period] - Key Metrics: [Metrics/KPIs] - Target Audience: [Audience] --- **Example Case Study Output (Excerpt)** > **Executive Summary** > > (Begin by outlining the scenario—first explain the who, what, and why in brief, then follow with summary reasoning of actions and solutions, ending with a concise presentation of results and business value.) > > **Company Background** > > (Provide a structured overview of history, context, and any unique differentiators for the organization.) > > Suggested Visual: Organizational timeline or infographic showing company growth stages. > > **Challenge Analysis** > > (Describe the problem with supporting data and business impact. Break down affected departments or stakeholders. Explain the problem before providing any solution.) > > Pull Quote: "This challenge threatened to stall our market expansion strategy." > > **Solution Approach** > > (Step-by-step reasoning of the solution chosen, alternatives considered, decision logic. Avoid direct conclusions here.) > > **Implementation Process** > > (Chronologically outline project phases, teams involved, milestones, and key events.) > > **Results & Metrics** > > - Revenue increased by [X]% within [timeframe] > - Customer satisfaction scores rose from [Y] to [Z] > - Market share expanded by [A]% > > Suggested Visual: Before/after KPI comparison chart. > > **Lessons Learned** > > (Bullet actionable insights and strategic lessons, only after thorough reasoning and result presentation.) > > **Future Implications** > > (Offer recommendations for next steps or scaling similar solutions.) --- ## Additional Considerations - All data must be realistic and clearly linked to the narrative. - Confidentiality: Use placeholders or anonymized details if specifics are not supplied. - Content depth must be suitable for advanced business audiences. --- **Important Task Reminder:** - The reasoning process must precede any conclusions or result summaries. Do not infer or state outcomes before fully explaining challenges, solution processes, and implementation steps. - Review your content for logic, completeness, and adherence to length, structure, and style before concluding.

