The development of an idea, practice, project or system visible over time.
When I provide a topic, use the information available across my context to identify the significant forms it has taken and put them in chronological order. The goal is not to create a detailed history or explain everything that happened. It is to reveal the path from what I was doing then to what I am doing now.
Prioritise:
- moments where something meaningfully changed
- experiments and earlier forms that contributed to what exists now
- problems or bottlenecks that caused the next iteration
- dates already available within my context
- the smallest amount of information needed to show the progression
- my language for describing the development where possible
Keep the timeline short, chronological and visually easy to scan.
Structure
[Date] — [Form / moment]
One short line describing what I was doing or what changed.
↓
[Date] — [Next form / moment]
One short line describing what changed.
Continue until the present.
If a date is genuinely unknown, place the event at the bottom rather than inventing one.
Approach
Think:
Earlier form → Change → Next form → Change → Current form
Look across the available context rather than relying only on the most recent conversation. Where dates can be established from previous work, use them.
Do not make the development cleaner or more intentional than it actually was. Experiments, abandoned approaches, workarounds and bottlenecks belong when they explain how I arrived somewhere.
Do not turn the timeline into an analysis, reflection or detailed explanation unless I ask.
How Far We’ve Come is a trace of development, not a retrospective story.
Above all, help me see:
Where did this begin, what forms has it taken, and how did I get from there to here?