STRENGTHSTUDIO / by LumenCoreMeet the cohort ↗
TAKEOFF FALL 2026 · EDUCATION

Itty Bitty City at Project Reflect

Project Reflect publicly connects Itty Bitty City early learning with school-age programs and family resources.

Open Itty Bitty City at Project Reflect workspace ↗Visit business source ↗Download free package ↓

A public strength profile and free toolkit from a fellow founder. This is an independent contribution, not a website operated by Itty Bitty City at Project Reflect.

A possible path through the work

PROPOSED FLOW
  1. 01Discover
  2. 02Enroll
  3. 03Prepare
  4. 04Learn
  5. 05Follow up

These stages are a starting point for owner review. The interactive workspace includes a rotatable 3D view of this proposed flow.

Three questions worth exploring

PUBLIC RESEARCH

These are hypotheses to discuss, with current baselines unmeasured. They do not establish that a problem or loss occurs in this business.

01OWNER INPUT NEEDED

Could families need several exchanges to determine which program and application route applies?

An approved-program FAQ and form checklist that drafts routing explanations with source links.

What we could measure together

Measure: Administrative clarification exchanges before routing (exchanges per inquiry).

Review an approved sample of deidentified inquiries and record correct program routing, including unresolved cases.

Acceptance boundary: Staff approves eligibility and enrollment; use synthetic examples first and avoid profiling children.

02OWNER INPUT NEEDED

Could capacity, schedules, and waitlist status be difficult to reconcile between program records?

A read-only reconciliation sheet that highlights conflicting counts and missing timestamps.

What we could measure together

Measure: Unreconciled capacity or schedule entries (entries per weekly review).

Compare the same dated enrollment, schedule, and capacity snapshots using existing staff rules.

Acceptance boundary: No automatic enrollment decisions or changes to staff-to-child constraints; authorized staff resolves conflicts.

03OWNER INPUT NEEDED

Could producing consistent family notices across programs take repeated editing?

A template assistant using approved dates, program policies, and staff-reviewed translation drafts.

What we could measure together

Measure: Staff editing time per approved family notice (minutes per notice).

Time drafting and review of the same notice types; record factual and translation corrections separately.

Acceptance boundary: Staff verifies every notice; exclude student identifiers from general-purpose AI tools.

Your free Luma toolkit

PORTABLE PACKAGE

Make work easier to follow

Use a workboard, acceptance criteria, revision fingerprints and measurement records to define the next useful step.

Prepare and explore

Grant Factory drafts from supplied facts, a public opportunity scout, and fictional-money paper trading tools are included.

Coordinate and learn

LumaCare supports nonclinical coordination practice. Optional AI drafting uses the member's own API account and credits.

Get your package and setup instructionsPlan a measurement ↗

The public workspace stores work in your browser. The downloaded Python app adds local backups and optional hourly public-source scout and paper jobs while it stays open. No shared team accounts, clinical deployment, grant submission or live trading are included.

Public sources and corrections

The strength description and questions come from the reviewed public research below. Owner corrections and actual operating records should guide any next experiment.

Read the complete cohort research ↗