CATS Hackathon Teams

Welcome to the team documentation hub for the CATS Hackathon organized by Next Trend Hub as a local partner in Lagos State. This hackathon brings together 9 innovative teams, each with 5 members, working on unique projects to solve real-world problems.

About the Hackathon

Next Trend Hub is proud to host 9 teams participating in the CATS Hackathon program. Each team follows an action-learning journey to discover, research, and build solutions that address challenges in their local communities.

The Action-Learning Journey: Four Quadrants

Every team must document their journey through four mandatory quadrants:

1. Ground Truth

Evaluate findings within your local community by observing issues or interviewing people about problems. Voice notes are mandatory to record questions and responses, serving as verifiable evidence of the discovery process.

2. Formulate Insight

Derive common themes and superior interests from collected feedback. Identify patterns and root causes from your research.

3. Formulate Hypothesis

Develop an initial thesis or problem statement based on your research and derived insights.

4. Define Opportunity

Identify and document multiple feasible solutions that address the discovered problems before selecting a final project path.

Participating Teams

Browse documentation by team (9 teams total, 5 members each):

Documentation Structure

Each team has 7 pages to document their complete hackathon journey:

1. Team Overview - Introduction, team members, and project summary
2. Ground Truth - Community research, interviews, and voice notes
3. Formulate Insight - Common themes and insights from research
4. Formulate Hypothesis - Problem statement and thesis
5. Define Opportunity - Multiple solution options explored
6. Journey Stories - Additional reflections and learning stories
7. Final Solution - Selected solution and implementation details

How to Contribute

Team members can update their documentation by editing files in content/team/<team-name>/:

• Navigate to your team’s folder
• Edit the relevant MDX file
• Commit your changes to the repository
• Your updates will appear on the live documentation site