Back to all updates

12 months ago

Crafting Your Winning Project Report: A Guide

Africa Deeptech Challenge 2025: Your Project Report Guide

 

Hello innovators! Your project report is crucial for the Africa Deeptech Challenge 2025. It's your project's storyboard and technical blueprint, showcasing your vision, technical prowess, and solution viability to judges (investors, academics, experts).

 

Judges' Expectations: Section Breakdown

  1. Problem Definition and Context: Clearly define and narrate the problem, emphasizing its relevance and scale in an African context. Use data or anecdotes to illustrate the pain point.

    • Tip: Frame it as a story. What challenge does your target community face daily?

  2. Identified Constraints: Provide a detailed, quantified analysis of specific resource constraints (e.g., power, data, compute, connectivity).

    • Example: "Our solution for precision agriculture in rural areas operates with less than 5W peak power consumption, relies on intermittent 2G connectivity for data offload, and utilizes local on-device processing due to unreliable cloud access."

    • Tip: Show, don't just tell. Quantify your constraints wherever possible.

  3. Documentation of Design Alternatives and Final Decisions: Show your engineering thought process. Discuss alternatives considered, why they were discarded, and the rationale for your final design choice, linking it back to constraints.

    • Example: "We initially explored a cloud-based AI model but pivoted to an on-device TensorFlow Lite solution because of the unreliable internet access identified in our target communities, reducing data transmission needs by 90%."

    • Tip: Use flowcharts, diagrams, or simple tables to illustrate your design options and decision matrix.

  4. Tools Used (AI, IoT, etc.) and Why: List key technologies and tools, explaining your rationale for each choice, connecting them to your problem, constraints, and design.

    • Example: "We integrated a LoRaWAN module for long-range, low-power data transmission, as Wi-Fi range was insufficient and cellular data too costly for our target application. For local data processing, we used a lightweight Python script leveraging MicroPython on the ESP32, chosen for its low power consumption and robust community support."

    • Tip: Connect tool choices directly back to your problem, constraints, and design decisions.

  5. Performance Tests and Benchmarks: Prove your solution works with data. Describe methodology, present results (charts/graphs), and compare performance against benchmarks or existing alternatives.

    • Example: "Our power consumption tests showed an average draw of 450mW during active operation, allowing for 72 hours of continuous use on a standard 18650 battery, exceeding our target of 48 hours."

    • Tip: Be honest about limitations too. Transparency builds trust.

  6. Screenshots or Short Videos Showing Your Build in Action: Provide clear, relevant visual proof of key functionalities. A 30-60 second video is often impactful.

    • Tip: A 30-60 second well-edited video demonstrating your core functionality is often more impactful than multiple screenshots.

General Tips for a Great Report

  • Be Clear and Concise: Get straight to the point.

  • Structure and Readability: Use headings, bullet points, and images for easy navigation.

  • Tell a Coherent Story: Ensure logical flow between sections.

  • Proofread Meticulously: Avoid typos and grammatical errors.

  • Emphasize Impact: Reinforce your solution's potential impact in an African context.

 

Conclusion

Your report is your chance to shine. It demonstrates your understanding, rigorous approach, and passion for solving real problems with innovative deep tech in a resource-constrained environment. Invest time in it; it's a critical part of your submission.


Good luck with the Africa Deeptech Challenge 2025! For more inspiration, check out this info session by Guinness World Record holder Oluwatobi Oyinlola on Documenting Hardware Projects the Open Source Way.

Questions?

If you have any questions about the hackathon or this topic, please post in the Telegram Channel.