Trinio

Architecture

Shape the system so delivery has somewhere to land.

Enterprise architecture only earns its keep when it changes a decision. I help organisations describe current and target states, map capabilities to applications, and keep software architecture honest as programmes grow. Informed by SEI architecture, The Open Group TOGAF Applied, IASA CITA Foundation, and Microsoft certifications — and by years of being the architect in the room when identity, applications, and operations collide.

Contact me Consulting

Practice

Enterprise, application, and the join between them.

Enterprise

Target architecture & capability

Capability maps, principles, roadmaps, and the unfashionable work of agreeing what “good” means before a vendor workshop writes it for you.

Application

Software & solution architecture

Boundaries, integration patterns, data ownership, and NFRs. Architecture that developers can implement and operators can run.

Identity

IAM as an architectural domain

Identity is often the hidden enterprise bus. Treat it as a domain with its own views, risks, and owners — see also consulting.

Delivery

Design authority

Lightweight governance: reviews that catch coupling early, ADRs that survive staff changes, and a backlog that still matches the target state.

Product

Architecture for product teams

The same discipline applied to mobile and consumer products: local-first data, privacy by construction, and store-ready platforms. The five apps on this site are the working proof.

Standards

SEI, TOGAF, Microsoft

SEI architecture, TOGAF Applied, IASA CITA Foundation, and Microsoft certifications — used as a shared language with stakeholders, not as a ritual of extra documents.

Typical artefacts

Enough structure to decide; not a framework tax. You leave with views people will actually open next quarter.

  • Current-state and target-state architecture views
  • Capability-to-application mapping and integration sketch
  • Principles, standards, and a short ADR set
  • Risk, gap, and sequencing for the next planning cycle
  • Optional: architecture review of a live programme or vendor design

Start

Bring the constraint, not a blank canvas.

A merger, a platform rewrite, an identity programme, a board asking “what systems do we actually have?” — those are good starting points.

Also

I still ship software

Architecture advice is grounded in building. Browse the apps if you want to see how privacy-first product architecture looks in the wild.