From the real process to the system that sustains it.
Four stages that repeat in every project. They are not theory: each one appears in a real case in this portfolio, and you can open it to see it in detail.
- STAGE 01 / 04
Operational diagnosis
Before designing, I learn how the work really happens: who reports, which sources exist, where traceability is lost and which institutional constraints must be respected.
Deliverables
- Map of the real process
- Source inventory and data quality
- Users and responsibilities
- Risks and constraints
Tools
- SQL
- Python
- MS Office
VILAIN PRACTICE · VILAAudit the source before buildingLessons learned lived in a spreadsheet with personal data and inconsistent categories. All 28 records were audited: 25 were cleared for sharing, and public search was separated from private authorship.
See the VILA case - STAGE 02 / 04
Transition MVP
A first useful version that reduces friction without stopping daily operations. It validates the rules with the people who use it before investing in the final architecture.
Deliverables
- Initial forms or dashboard
- Rules validated with users
- First indicators
Tools
- JavaScript
- Looker Studio
- Power BI
PAIIN PRACTICE · PAIA V1 that taught the rules of V2PAI's V1 centralised planning and monitoring with JavaScript and spreadsheets. Six two-month cycles of use revealed the rules that V2 turned into a React application with explicit services.
See the PAI case - STAGE 03 / 04
Modular product
The full application: data model, reusable components and actionable analytics. Each module keeps the data's context from the first entry to the decision.
Deliverables
- Relational data model
- Modules and workflows
- Dashboards, maps and reports
Tools
- React
- TypeScript
- D3
Frente FríoIN PRACTICE · Frente FríoExplicit states for every reportFrente Frío brings together a dashboard, activities, budget, a map and a guided report with four states: draft, submitted, returned and validated. The dashboard and map only show validated progress.
See the Frente Frío case - STAGE 04 / 04
Governance and deployment
Traceability, testing and documentation so the system works beyond the first prototype and can evolve without losing traceability.
Deliverables
- Traceability and history
- Automated tests
- Documentation with fictional data
- Controlled release
Tools
- Playwright
- GitHub
SIOIN PRACTICE · SIOHistory and tests by designSIO keeps a history of every progress entry and review, and was tested across several layers: interface, integration and data.
See the SIO case
Three rules that never change between projects.
- 01
Operations never stop
Every version coexists with daily work. PIV migrated from pages and spreadsheets without losing formulas or legacy data.
Seen in PIV - 02
Data has a state
Validated is not the same as provisional. PAI's dashboard separates approved results, information under review and the remaining gap.
Seen in PAI - 03
Traceability is part of the design
Every decision is recorded. In Frente Frío, a report moves through draft, submission, return and validation, and every step is kept.
Seen in Frente Frío
What to expect if we work together
- A clear diagnosis before writing code.
- Partial deliveries that can already be used.
- Fictional data to document without exposing real information.
- Tests and documentation in every version.