Skip to content

📊 Impact Metrics: Learning and Ecosystem

Measurement Philosophy

We don't measure to control, but to learn. We seek to capture learning velocity, operational reliability, and community growth without falling into vanity metrics.

Cognitive Value Cycle

graph TD
    A[💡 Idea / Challenge] --> B[💻 Local Execution]
    B --> C[🔄 PR & Review]
    C --> D[🚀 Merge & Deploy]
    D --> E[🎓 Lesson Learned]

    style A fill:#e7ae4c,stroke:#333,stroke-width:2px,color:#fff
    style B fill:#37a880,stroke:#333,stroke-width:2px,color:#fff
    style C fill:#e0e7ff,stroke:#333,stroke-width:2px,color:#182232
    style D fill:#f1f5f9,stroke:#182232,stroke-width:2px,color:#182232
    style E fill:#ffffff,stroke:#182232,stroke-width:2px,stroke-dasharray: 5 5,color:#182232

1. 🎓 Learning Metrics (Gamification)

We instrument GitHub Projects to make learning visible and rewarded.

🚀 TTFP (Time to First PR)

The Queen Metric. Time from when a user says "Hello" until their first PR is accepted. If it goes down, our onboarding is world-class.

⚡ Learning Velocity

Number of `learning-task` issues completed per week. Measures the health and curiosity of the active cohort.

Experience System (XP)

We reward real impact, not time in the chair.

Task Level Reward (XP) Example
Level 1 10 XP First analysis, simple fix
Level 2 25 XP New visualization, docs improvement
Level 3 50 XP CI/CD automation, new model
Level 4 100 XP Architecture, governance, mentoring

2. ⚙️ Flow & Reliability Metrics

To ensure sustainable deliveries and prevent burnout.

Cycle Time

Time from In Progress to Done. Goal: Reduce blocks and external waits.

CI Reliability

Percentage of green builds ('Success'). A broken pipeline blocks learning.

Sovereign Adoption

% of PRs that respect the Local-First principle. No hidden cloud dependencies.

3. 🌍 Ecosystem Metrics

Connecting code with territorial impact.

  • ✅ GitOps Coverage: % of components with IaC and reproducible pipelines.
  • ✅ Territorial Impact: Number of community events and active students in target regions (ITI Andalusia, EU, LATAM).

4. 🛠️ Quick Implementation (15 min)

Configure your GitHub Project v2 to start measuring today.

Create the following custom columns: * Status: Backlog, In Progress, Review, Done. * Area: Learning, GitOps, Docs, Backend. * XP (Number): To sum scores. * KPI (Text): Labels like "TTFP", "Reliability".

  • Activate add_to_project.yml workflows.
  • Use labels to assign XP automatically.

Remember: If measured poorly, it destroys culture. We measure to improve the system, never to judge people.