1
Day, end to end
CHANGELOG.md
4
Information layers in the product
SPD-Tracker-Home.html
9
Documented versions
CHANGELOG.md
14
Files translated to English
CHANGELOG.md · v0.5.0
0
Changes without a recorded source
CHANGELOG.md
Two kinds of work below — what the project produced (Cube A) and how the tool was built (Cube B).
Cube A · Substantive work
What the project produced
Context compiled, the brand audited, copy translated, sample data corrected — the content work behind the screens.
1
Project context document compiled
13 sections, 326 lines — built from May 2026 meeting transcripts and the workshop deck.
source SPD-Tracker-Context.md
9
Stakeholders mapped to personas
Roles, divisions and what each one needs from the Tracker.
source SPD-Tracker-Context.md · §4
4
Review committees modelled end to end
ERM · QRR · OPC · Assessment — the full pipeline an operation crosses.
source SPD-Tracker-Context.md · §5
5
Data-model entities specified
Operation, Committee Event, Assignment, Document, User — each with its fields.
source SPD-Tracker-Context.md · §11
13
Glossary terms defined
SPD vocabulary fixed so every screen uses the same words.
source SPD-Tracker-Context.md · §13
4
Committee colours corrected
Off-brand values — including a purple absent from the IDB palette — replaced with official Pantone.
source CHANGELOG.md · v0.1.0
14
Files translated to English
7 screens + 4 retired prototypes + 3 documents; one Spanish filename retired.
source CHANGELOG.md · v0.5.0
4
Sample-data corrections
2 operations renamed to IDB nomenclature, 2 duplicate names fixed.
source CHANGELOG.md · v0.1.2
The path
Nine versions, in one day
There is no per-version metric to chart, so the iteration path is shown as it happened — a list, not invented bars. Every version is dated May 15, 2026.
v0.1.0First dashboard — single page, aligned to the IDB brand
v0.1.1Products reframed as navigation buttons by core area
v0.1.2Operation No. and Instrument filters added and made consistent
v0.2.0Redesign for pipeline monitoring — the pipeline becomes the hero; Pipeline View added
v0.3.0Refocused as a four-layer product — a home plus four tool-style screens
v0.3.1Unification pass — deck re-pointed to the current screens, file ordering
v0.4.0Consolidated — one home, no IDB logo, a deploy folder ready to share
v0.5.0Translated to English — whole product; the last Spanish filename retired
v0.6.0Presentation cover rebuilt — from Alejandra's Figma sketch, with the IDB logo
Committee colour code — designed into the pipeline
ERM
QRR
OPC
Assessment
SPD-Tracker-02-Operations.html
Work-program core areas — the four-button navigation
SPR
OQE
DGP
KRP
SPD-Tracker-03-Products.html
Cube B · Tool development
How the tool was built
Screens, versions, decisions and the deck — the product itself.
7
Screens in the current product
Home, Login, four layer screens and the presentation deck.
source README.md
9
Versions, v0.1.0 → v0.6.0
Each release logged with what changed and why.
source CHANGELOG.md
23
Design decisions recorded
Explicit, numbered decisions across the versioned releases.
source CHANGELOG.md · derived
4
Explorations retired, not deleted
Dashboard, Dashboard-v2, Pipeline-View, Management-View — kept for reference.
source README.md
3
Slides in the presentation deck
A reveal.js cover plus two layer slides that embed the live screens.
source SPD-Tracker-Presentation.html
0
JavaScript dependencies in the layer screens
Collapsible panels use the native <details> element.
source CHANGELOG.md · v0.3.0
Activity
The work, in tasks and minutes
The timer log gives the effort; the CHANGELOG and the project files give the tasks. Below: the minutes tracked, and a representative sample of what was done — not the full list.
392 min
Design time tracked
≈ 6 h 32 m
4
Work sessions
all on May 15, 2026
98 min
Average session
392 ÷ 4 · derived
138 min
Longest stretch
14:41–16:59
Reviewed the May 2026 meeting transcripts and the workshop session deck
Research
Compiled the project context into one 13-section reference document
Content
Audited the palette against the official IDB brand; corrected four off-brand committee colours
Brand audit
Designed the Home, the Login and the four layer screens
Design
Built the reveal.js presentation deck; rebuilt its cover from a Figma sketch
Design
Translated the whole product from Spanish to English — 14 files
Copy
Revised the presentation-cover copy against a written brief
Copy review
Corrected sample data — operation codes and duplicate names
Data
Logged every change in the CHANGELOG and kept the README current
Documentation
Tasks drawn from CHANGELOG.md (v0.1.0–v0.9.0) and the project's artifacts · time summed from .timelog.tsv
The figure that matters
Zero changes without a source0
Across all 9 versions, the CHANGELOG records each change in one fixed format —
date · version · what changed · why · decisions · who. The why names the
meeting or the request behind the change; the who names the author. Not one screen,
colour or label entered the product without a recorded source. That is the discipline
this page holds itself to: every number above cites the file it came from — nothing is
estimated for effect.
Figures a human should still confirm
The 23 decisions is a sum — counted from the seven “Decisions recorded” blocks in CHANGELOG.md. The 14 translated files is 7 + 4 + 3 as enumerated in v0.5.0. The time figures (392 minutes, 4 sessions, 98-minute average, 138-minute longest stretch) are read and summed from .timelog.tsv as it stood when this page was compiled — a live log. The structural counts (layers, versions, committees, entities, screens, retired files) are a snapshot as of v0.6.0, read directly from the cited files; later changelog entries are not recounted here.