THE PROMISESTEP METHOD

Refactoring for Kindness, Familiarity, and Visual Metaphor

A practical teaching method for making software kinder, more familiar, and easier to understand—while preserving verified working behavior.

01 / KINDNESS

Design for the person.

Respect boundaries, time, disability access, contribution, and the real conditions in which the work takes place. Make it easier to succeed without unnecessary pressure.

02 / FAMILIARITY

Preserve what people know.

Start with recognizable structures and tested workflows. Change should explain itself, and verified behaviors should not be removed by unrelated refactoring.

03 / VISUAL METAPHOR

Make meaning visible.

Use clear objects, relationships, and spatial metaphors when they improve understanding. Avoid decorative symbolism that confuses the task.

A WORKING EXAMPLE / KEEP THE PROMISE

When saving fails,
the work should not disappear.

This is the kind of practical refactoring the method teaches. The goal is not a prettier error; it's protecting someone's ability to continue.

BEFORE / A BROKEN PROMISE

“Something went wrong.”

The dialog closes. The draft is gone. The person must reconstruct their work and guess what happened.

AFTER / REFACTORED FOR KINDNESS

“Your draft is still here.”

A failed save leaves the content intact, explains the problem in plain language, and offers a safe retry.

KINDNESS

The person's work survives.

FAMILIARITY

Editing stays where it was.

VISUAL METAPHOR

The saved state is understandable.

QUALITY ASSURANCE

Test failure, recovery, keyboard access, and return.

TRY THE METHOD / A SAFE DEMONSTRATION

Keep the work.
Even when the save fails.

This little exercise is interactive. Change the draft, interrupt a save, and see whether your work survives. No account, network request, or permanent storage is involved.

WORKING NOTE / 01

Draft is here. You can change it before testing an interrupted save.

This is a local browser rehearsal, not Nurture and not a real save. Please don't enter private or sensitive material. The note is not stored after you leave this page.

QUALITY IS THE PROMISE

Preserve the baseline. Improve the journey.

Observe

Identify the actual experience and the promised outcome.

Understand

Keep facts, interpretations, and unknowns distinct.

Refactor

Make small, reversible, well-explained improvements.

Verify

Test the whole journey, not only isolated components.

A DISTINCT SERIES

Preventative Care for Human-Centered Design

Each instrument retains its own identity and purpose. These examples are educational descriptions, not claims of legal enforcement.