GRC engineering
From documents to operating systems
GRC engineering is having a moment. Underneath the buzzword is an old truth: controls that live in folders decay; controls wired into workflow compound.
GRC engineering has become a job title, a conference track and a LinkedIn genre. Underneath the branding is a simple and correct idea: compliance should be a property of how systems and teams work, not a set of documents describing how they're supposed to.
In practice, that means three shifts. Controls defined as testable conditions, not prose. Evidence generated automatically wherever the work already produces it. And ownership expressed in the tools people actually use, not in a RACI nobody opens.
If your GRC lives in folders, it's archaeology.
Not every organisation needs to write code to get there. What they need is the mindset: treat the control environment like a product, with users, data flows and a roadmap. The engineering follows.