All work

Mini Kit Framework — 1 hour to 3 minutes of kit-build time

~95% reduction in kit-build time · 60+ kits launched · thousands of sessions

Every Mini Kit took an hour to build. After this framework, three minutes. The bottleneck wasn't what we thought.

The problem

Every team-building Mini Kit at Rising Team used to take about an hour to build by hand. Each kit needed its own warm-up, exercise, reflection block, post-session survey, and persistence wiring — and every author re-implemented those pieces slightly differently.

The bottleneck wasn't the editor. It was the survey wiring — connecting the post-session pulse questions to the right insight stream, the right team dashboard, and the right downstream AI signals.

The approach

I spearheaded the Mini Kit Framework — a build system that abstracts kit scaffolding into composable blocks:

  • Block library. Warm-up, prompt, reflection, dyad/triad split, vote, free-form, survey. Each block owns its own state machine, persistence, and signal emission.
  • Config-driven. Authors describe a kit as a list of blocks with content; the framework handles timing, transitions, surveys, and analytics.
  • Survey-as-first-class. The hardest re-used piece is now declarative: a kit's pulse questions wire automatically into the platform's insight pipeline, no glue code.
  • Live-session aware. Built for hybrid and remote teams: synchronous facilitation, multi-participant state, network resilience.

Stack

React · TypeScript · Django · PostgreSQL · WebSockets

Outcomes

  • 1 hour → 3–5 minutes of kit creation time (~95% reduction).
  • 60+ kits launched on the framework.
  • Powers thousands of live 10–20 minute sessions for hybrid and remote teams.
  • Unblocked content velocity for the whole platform.

What I learned

  1. The bottleneck is rarely the part you're staring at. The editor felt like the problem. The survey wiring was. Profiling a real authoring session — not the assumed one — was the unlock.
  2. Frameworks fail when blocks aren't composable. Early versions had blocks with implicit ordering assumptions. Forcing every block to work in any position made the API smaller and the kit catalog grow.

Hiring for something like this?

Tell me what you're building