Saltar al contenido

How I think

Prove it before over-engineering it

A prototype opens conversations a presentation never does.

First show that something can be done. Then build everything needed to make it real. In that order, because the reverse order commits months of work to an idea nobody has seen working yet.

This isn't about rushing or skipping engineering. It's about lowering the cost of being wrong before asking an entire organization to change how it works. Once the idea holds up, the specialized teams make it robust, secure, and scalable — which is exactly their job.

A long project that only shows results at the end isn't more rigorous. It's just a project that learns late.

This is an opinion formed on the job, not a verifiable fact. The cases behind it are in the case studies section.