byte-n

Try another version of the hidden dependency

A small creative experiment about the hidden dependency.

Original creative challenge · A place for unfinished work

  1. Use this invented starting situation: A small task keeps reappearing because another step is missing.
  2. Name the missing step beside the task instead of copying it again.
  3. Make a small artefact that shows the change: a note, sketch, caption, or three-panel sequence.
  4. Write one sentence describing what the artefact makes clearer. Keep this an experiment; no account, purchase, or public post is needed.

Try a question

What would you keep if this were an experiment rather than a permanent rule?