Skip to Content
TeamOverview

Teams — Progress Tracker

Purpose: Track team stage, responsibilities, and what to present at each stage.

📂 Navigation

📅 Key Dates

  • Dec 03: Team Formation (The Insight Lab)
  • Dec 06: The Builders’ Assembly (Coding Session)
  • Dec 09: The Refinery (Mid-way Review)
  • [TBD]: Grand Finale

🎯 Team Development Stages

Every team progresses through five stages. Each stage has specific deliverables and check-in requirements.

Stage 1: Ground 🔍

What you’re doing:

  • Field research and problem discovery
  • Interviewing stakeholders
  • Gathering evidence (photos, quotes, videos)

Deliverables:

  • Minimum 3 photos + 3 quotes
  • Individual sensing entries
  • Initial problem statement

Duration: 1-2 weeks

Stage 2: Define 📝

What you’re doing:

  • Synthesizing research findings
  • Defining root cause
  • Creating team problem statement
  • Identifying solution approach

Deliverables:

  • Team discovery log
  • Clear problem statement (who, what, where, why)
  • Preliminary solution idea
  • Updated submission.md

Duration: 3-5 days

Stage 3: Prototype 🛠️

What you’re doing:

  • Building first version of solution
  • Creating testable prototype
  • Preparing for user testing

Deliverables:

  • Working prototype (can be low-fidelity)
  • Prototype photos/videos
  • Testing plan
  • Updated team discovery log

Duration: 1-2 weeks

Stage 4: Test 🧪

What you’re doing:

  • Testing with real users
  • Gathering feedback
  • Iterating based on learnings
  • Documenting results

Deliverables:

  • Minimum 3 user tests documented
  • Testing results (quotes, photos, numbers)
  • Iteration evidence (before/after)
  • Updated prototype

Duration: 1 week

Stage 5: Reflect 💭

What you’re doing:

  • Documenting complete journey
  • Preparing final presentation
  • Planning next steps
  • Completing submission

Deliverables:

  • Complete submission.md
  • Final video (3-5 minutes)
  • Impact evidence
  • Sustainability plan

Duration: 3-5 days

Confirmed Teams

Team NameDomainSolution One-LinerCurrent StageStatus
[Team Alpha]AgricultureSMS-based inventory for onion farmers🛠️ PrototypeActive
[Team Beta]FinanceRosca (Adashi) management on blockchain🧪 TestActive
[Team Gamma]TransportRide-sharing coordination for students📝 DefineActive

📊 Team Progress Tracking

Each team must update their status weekly. Use this format:

Required Information

For each team entry, include:

  1. Current stage — Ground, Define, Prototype, Test, or Reflect
  2. Short 1-line status update — What did you do this week?
  3. Required deliverable for next check-in — Specific items needed
  4. Next meeting date/time and contact — When and how to reach you

Example Status Updates

Team Waste-to-Value

Stage: Prototype
This week: Installed one collection drum at Sabon Gari Market Block A, tested for 48 hours with 15 vendors
Next deliverable: 48-hour weight log + 3 photos of vendors using drum + minimum 2 user quotes
Next check-in: Dec 08, 2025 @ 3:00 PM — Contact: [WhatsApp Link]

Team Edu-Connect

Stage: Test
This week: Tested offline resource sharing with 20 students, gathered feedback, identified 3 key improvements
Next deliverable: Updated prototype with improvements + 5 user testimonials + before/after comparison
Next check-in: Dec 07, 2025 @ 2:00 PM — Contact: [WhatsApp Link]

Team Medi-Record

Stage: Define
This week: Interviewed 8 clinic staff, identified root cause (paper records get lost), drafted problem statement
Next deliverable: Complete team discovery log + preliminary QR system design + stakeholder feedback
Next check-in: Dec 06, 2025 @ 10:00 AM — Contact: [WhatsApp Link]

✅ Weekly Check-In Requirements

What Teams Must Submit Weekly

Every Friday by 6:00 PM:

  • Status update using the format above
  • Evidence upload to your team Drive folder
    • Photos from this week’s work
    • Updated documentation
    • Any new quotes or testimonials
  • Updated team discovery log in GitHub (if applicable)

How to Submit

  1. Update your team page (if you have one)
  2. Upload evidence to Drive in your team folder
  3. Post status in community channel (optional but encouraged)
  4. Tag Hub Lead if you need urgent support

🚨 Deliverable Requirements by Stage

Ground Stage Deliverables

  • Minimum 3 photos showing problem context
  • Minimum 3 direct quotes from affected people
  • 60-120 second video or audio evidence
  • Individual sensing entries from each team member
  • Consent documentation

Define Stage Deliverables

  • Team discovery log with synthesized findings
  • Clear problem statement (who, what, where, why)
  • Root cause analysis
  • Preliminary solution idea
  • Updated submission.md with problem section complete

Prototype Stage Deliverables

  • Working prototype (can be low-fidelity)
  • Minimum 3 photos of prototype
  • Video demonstration (1-2 minutes)
  • Testing plan documented
  • Updated team discovery log

Test Stage Deliverables

  • Minimum 3 user tests documented
  • Testing results with quotes and photos
  • Evidence of iteration (before/after)
  • User feedback incorporated
  • Updated prototype

Reflect Stage Deliverables

  • Complete submission.md
  • Final video (3-5 minutes)
  • Impact evidence (quantitative + qualitative)
  • Sustainability plan
  • All assets uploaded with proper naming

💡 Tips for Effective Progress Tracking

Keep Status Updates Specific

✅ Good:

“Tested payment system with 15 vendors. 13/15 successfully sent ₦50 via SMS. Learned we need clearer instructions.”

❌ Too vague:

“Did some testing. It went well.”

Document Everything

✅ Good practice:

  • Take photos during every field visit
  • Record quotes immediately
  • Upload evidence same day
  • Update discovery log weekly

❌ Poor practice:

  • Wait until deadline to document
  • Rely on memory for quotes
  • Skip photo documentation

Be Honest About Challenges

✅ Good:

“Prototype failed during testing. Users couldn’t understand SMS codes. Pivoting to simpler number system.”

❌ Poor:

“Everything is perfect!” (when it’s not)

📞 Team Support Channels

Need Help?

Technical issues:

  • 💬 Support channel (Telegram/Discord)
  • 👨‍💻 Hub Git operator (Kamal)
  • 📚 Documentation Guide

Project guidance:

Team dynamics:

  • 🤝 Event organizers (private message)
  • 👥 Team retrospectives
  • 🎯 FAQ

🏗️ Team Resources

Essential Templates

Guides

🔗 Quick Links

Update your status: Post your weekly update in the community channel every Friday!

Need teammates? Filled the Pod Sign-Up Form  to list your open positions.

Last updated on
TeamsOverview