MR.MANOLO REY GARCÍACONTACT
SYSTEMSHOW I WORKABOUT
HOW I WORK

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.

  1. 01Operational diagnosis
  2. 02Transition MVP
  3. 03Modular product
  4. 04Governance and deployment
  1. 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
    REAL.EXAMPLE.01VILA
    VILA
    IN PRACTICE · VILAAudit the source before building

    Lessons 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
  2. 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
    REAL.EXAMPLE.02PAI
    PAI
    IN PRACTICE · PAIA V1 that taught the rules of V2

    PAI'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
  3. 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
    REAL.EXAMPLE.03Frente Frío
    Frente Frío
    IN PRACTICE · Frente FríoExplicit states for every report

    Frente 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
  4. 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
    REAL.EXAMPLE.04SIO
    SIO
    IN PRACTICE · SIOHistory and tests by design

    SIO keeps a history of every progress entry and review, and was tested across several layers: interface, integration and data.

    See the SIO case
PRINCIPLES

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

  • PROMISE.01
    A clear diagnosis before writing code.
  • PROMISE.02
    Partial deliveries that can already be used.
  • PROMISE.03
    Fictional data to document without exposing real information.
  • PROMISE.04
    Tests and documentation in every version.