Heirloom’s improvement method

A visible path from observation to organizational learning.

Employee knowledge becomes useful when people can develop it, leaders can evaluate it, and the organization can test and implement what proves valuable. Heirloom makes that operating path explicit.

Six connected stages

Each stage answers a different question.

  1. 01

    Surface

    Employees share observations, recurring friction, customer needs, and opportunities grounded in their experience of the work.

    Employees make the work visible. A facilitator helps distinguish an observation from a proposed solution.

  2. 02

    Develop

    Relevant employees, managers, and stakeholders clarify the problem, test assumptions, and strengthen promising ideas.

    Contributors remain involved. Context, constraints, affected groups, and possible measures are recorded.

  3. 03

    Evaluate

    Ideas move through explicit criteria and a named decision pathway, with a response that employees can see.

    Leadership retains the decisions it is responsible for and explains approvals, revisions, deferrals, or declines.

  4. 04

    Experiment

    Selected ideas become bounded tests with an owner, timeline, measures, responsibilities, and defined limits.

    The team learns before committing to a full rollout. Experiments are practical, not performative.

  5. 05

    Implement

    Evidence is reviewed and an accountable owner carries a successful change into the operating system.

    Tasks, decisions, evidence, and follow-through stay connected to the idea that initiated the work.

  6. 06

    Learn

    Results and lessons remain visible, including when an experiment does not produce the expected result.

    The organization builds reusable knowledge and decides what to repeat, adapt, stop, or expand.

One example workflow

A recurring delay becomes a test the team can learn from.

The same idea retains its context as it moves between employees, facilitators, managers, and the accountable decision-maker.

Illustrative example

01 / Employee observation

“On busy mornings, warehouse pickers lose 20 to 30 minutes waiting for replenishment because low-stock bins are not flagged until they are empty.”

02 / Developed idea

“Create a simple two-stage stock signal and complete a scheduled replenishment sweep before peak picking begins.”

03 / Practical experiment

“Test the process in one warehouse zone for two weeks. Track stockouts, picker idle time, replenishment labor, and employee feedback.”

04 / Decision and next step

“Review the evidence with the participating team. Expand the process, revise it, or stop the experiment, with the decision and reasoning visible to employees.”

Participation

Employees shape the work.

People can contribute observations, develop solutions, understand the decision, and participate in testing - not merely submit an idea into a queue.

Decision pathways

Responsibility stays clear.

Each stage names who facilitates, who contributes, who decides, and who owns the next step. Participation does not erase accountable leadership.

Follow-through

The response remains visible.

Requests for revision, experiment evidence, decisions, and implementation work stay connected so employees can see what happened next.