The Heirloom Platform

One improvement record from first observation to what happened next.

The workspace operates, records, and strengthens an employee-powered improvement program. It keeps development, decisions, experiments, ownership, evidence, and follow-through connected.

The product in context

Built around the lifecycle, not a generic feature grid.

The workspace does not create participation by itself. It supports a program with clear roles, facilitation, decision pathways, and manager follow-through.

Low-stock replenishment

Illustrative improvement record

Experiment in progress

  1. 1

    Observation

    Pickers lose 20 to 30 minutes waiting when low-stock bins are not flagged.

  2. 2

    Development

    Employees and the warehouse lead shape a two-stage stock signal and scheduled sweep.

  3. 3

    Leadership decision

    Approve a bounded low-stock replenishment experiment.

  4. 4

    Experiment

    Two weeks · one warehouse zone · before peak picking · named owner

  5. 5

    Tasks + evidence

    Track stockouts · picker idle time · replenishment labor · employee feedback

  6. 6

    Implementation

    Expand, revise, or stop · record the decision · share the reasoning

Available now

The core operating path is supported today.

  • Employee idea or observation submission
  • Basic organization and categorization
  • Discussion and collaborative development
  • Stage-based workflows and leadership decisions
  • Requests for revision
  • Experiment planning
  • Tasks, owners, and deadlines
  • Recording results and evidence
  • Implementation tracking
  • Participation and pipeline visibility
  • Employee updates and notifications
  • Visibility controls for different groups or units

Supported through configured workflows

A workspace shaped around the pilot.

Heirloom configures stages, group visibility, roles, decision responsibilities, experiment records, and reporting practices around the selected unit and priority. Some operating practices depend on facilitation and organizational process, not automated software behavior.

Future product direction

Deeper organizational learning over time.

The longer-term direction is to make improvement knowledge easier to reuse across programs and units. This is direction, not a public feature commitment. The current platform does not claim automated duplicate detection, sophisticated scoring, predictive analytics, or automated impact measurement.

Program and platform

Software preserves the path. People make the path credible.

Begin with a practical improvement cycle and a workspace configured to support it.