skip to content

Posts RSS feed

2026

  • How to use a business capability map to zone the enterprise into territory, districts and buildings, with an explicit registry that records each application's owner and lifecycle status, following the digital urbanization framework.

  • What urban debt is, how it extends technical debt to the enterprise's digital territory, and why the digital urbanization framework treats legacy modernization as renewal block by block, with governance exceptions that expire.

  • The real binary isn't asking permission or forgiveness. It's building evidence before consensus exists. When that play works, when it becomes governance debt, and how to move from internal hacker to institutional architect.

  • Through the lens of social control and criminology: how conduct that breaks formal procedure can be reframed as innovation when it produces utility, buy-in, and legitimacy. Organizations don't judge only the rule, but the outcome, the context, and who benefits.

  • The persuasion stack that drove adoption of a data tool wasn't narrative: it was coded and enforced server-side. Atomic attempt limits, exam windows, idempotent certificates, and a notification pipeline as a delta job.