Gianluca Libera

I started out as an architectural draughtsman before moving into business and tech. One thing from that apprenticeship still shapes how I work. The people who design something are usually not the people who have to live with it afterward, and once a project is technically finished, that gap gets easy to lose sight of.

I try to stay close to it. When I replaced manual sales reporting with a CRM dashboard, getting the sales team to trust it enough to check every morning instead of falling back on spreadsheets took more work than the design itself. That meant sitting through complaints about a version I thought was already good, then rebuilding parts that worked fine technically but didn't match how the team actually made decisions. Documenting processes in BPMN taught a similar lesson. A diagram nobody reads doesn't fix anything, however accurate it is.

So before I optimize a process or hand someone a new tool, I ask who has to use it every day, and I expect my first version of the answer to be wrong. The business case and the technical architecture matter. They just don't hold up on their own if people don't actually use the thing.