Software6 min
Software has to survive the person who built it
A tool that only the builder understands is a temporary fix. The operation has to be able to keep it.
About
Build around the work, not a catalogue.
A generic product fails when it ignores how work actually runs. The portal asks for fields nobody uses. The dashboard shows last month. The workflow stops at the exception that happens twice a week.
We build web applications around that path: portals, dashboards and workflows people open in the browser. Design, build, deployment, security and handover stay one job.
Software now
45%
average cost overrun on large IT projects
7%
average schedule overrun on those same projects
56%
less value delivered than predicted
17%
of IT projects go badly enough to threaten the company
Figures from McKinsey, with the University of Oxford. These figures are for large IT projects (initial price above $15 million), from research on more than 5,400 projects. On average they run 45% over budget and 7% over time, and deliver 56% less value than predicted. 17% go badly enough to threaten the company. Software projects sit at the high end of cost and schedule risk.
Offerings
The work we take on.
We build the web application the operation can keep. A tool only the builder understands does not last.
01
The process in the tool
We write down the real path, including the ugly cases, before we open an editor. The software follows that path.
02
In the browser
Portals, dashboards and workflows people open in the browser, for the people who already do the work, not for a demo audience.
03
Software that lasts
Names, structure and a place for exceptions, so the next person can keep it without reverse-engineering the first build.
04
Handover
Access, logging, a note on what to do when it fails, and an owner after go-live. That is part of the product.
Insights
