Insights
What we learn by building
Vendor lock-in, SaaS sprawl, AI in real workflows, no-code governance: sourced, verifiable analyses — written by the people who build, for the people who decide.
Latest article
Forward-Deployed Engineering: build with the team, prepare for autonomy
Engineers working close to the business can turn everyday constraints into useful software. At Ownward, See · Build · Own connects this approach to shared data, working tools and skills the team can keep.
Read the articleThe publication feed
Newest first. Each colour follows a topic.
September 2026
August 2026
June 2026
Measuring autonomy: four metrics that don't lie
A team's autonomy over its tools is usually judged by gut feeling: the provider “seems” less indispensable, the team “seems” more comfortable. Without metrics recorded before and after, there is no way to tell real progress from displaced dependency.
No-code compliance: six questions make the deployment auditable
Business teams deploy no-code tools faster than IT can audit them. The result: personal data sitting in SaaS platforms where nobody knows where it is hosted, who accesses it, or how to get it out one day.
May 2026
Vendor lock-in: the five forms nobody invoices
Cloud data egress is now free and EU law caps switching timelines and fees. Yet fewer than 1% of cloud customers change providers each year. The lock is no longer on the invoice — it sits in five dependencies nothing measures.
Citizen developers: governance is the missing link
In late 2022, Gartner projected that 80% of low-code tool users would sit outside IT departments by 2026. Meanwhile, the average large enterprise hosts close to 80,000 applications built outside any software lifecycle, and 62% of the applications Zenity analyzed contain vulnerabilities. The question is no longer whether to allow citizen development: it is who governs what already exists.