The genealogy, unfolded
The main page tells this story in short form. This is the full version: the three acts in the order they were born, and the product tree exactly as the system computes it, with real photos from the catalog.
“A PMO, a website, a CRM, an ERP”
Four acronyms that sum up seven years of work. This figure is that sentence coming to life, in the order it was born.
First, order is born
Before the first line of code there was a decision: to govern all the work as a portfolio: what to build, in what order, and why. The method is a PMO with the discipline of the PMI: scope, risks, stakeholders, traceability, as the PMBOK Guide prescribes. The engine: AI. From those two, the strategy is born.
The pair resolves the old dilemma of project management (agile or rigorous?) because with AI as the engine, rigor stops costing time. You plan and document as the PMBOK prescribes. And you deliver as agile prescribes: in short iterations tested with the people who will use them, learning from each delivery before building the next. Failing early becomes cheap, and trying a new idea costs hours, not months: an environment where creating and innovating stops being a risk and becomes the routine.
The strategy becomes tools
The strategy wasn't a document: it consisted of building three tools, each one a project governed by the same method and built with the same engine:
Why so fast? Because the engine never starts cold. Every development session inherits the project plan, the history of decisions and the lessons from mistakes already made: the AI doesn't guess the context: it reads it. The rigor of act 1 isn't bureaucracy; it's the fuel of act 2.
None of these figures is a projection: both columns come out of the same repository. The evidence of rigor and the evidence of speed live in the same place.
The tools respond to reality
The three tools don't live in isolation: they hand the work down a chain, and the one who sets it off is the client, with a click on the website.
A client orders a finished traffic light. What follows is not an illustration: it is the product's literal genealogy as the system computes it: each branch grows toward what must be made or bought, and then resolves from the tips back to the trunk. Every photo is a real part from the catalog.
This is the product's complete family tree, exactly as the system unfolds it: eight branches growing from the traffic light down to the last purchased part, and eleven parts that feed several branches at once (71 connections for 58 parts: polycarbonate sits at the base of four branches; the LEDs, in the three lights and in the countdown). Nobody draws this tree by hand: the system computes it on its own, and each part's own little status light tells every line what it can start today.
And it returns to the client from the beginning, the same one who set all of this off with a click on the website. The circle closes.
Compressing seven years of reality into a four-acronym sentence, and being able to unfold it again, down to the last resistor. That is abstraction. This figure is the craft looking at itself in the mirror.