Architecture review

Review the important system boundaries

Discuss ownership, data, interfaces, security and operational responsibilities across the system.

Prepare the conversation

Topics to discuss

Users and primary outcome are clear

Discuss the current arrangements, owner and any unresolved follow-up.

Critical dependencies and integrations are identified

Discuss the current arrangements, owner and any unresolved follow-up.

A person or team owns operation after launch

Discuss the current arrangements, owner and any unresolved follow-up.

Data categories and allowed destinations are understood

Discuss the current arrangements, owner and any unresolved follow-up.

AI outputs have an appropriate human-review path

Discuss the current arrangements, owner and any unresolved follow-up.

Retention and logging decisions are explicit

Discuss the current arrangements, owner and any unresolved follow-up.

Authentication and authorization boundaries are defined

Discuss the current arrangements, owner and any unresolved follow-up.

External inputs and failure paths are considered

Discuss the current arrangements, owner and any unresolved follow-up.

Secrets and environment configuration are separated from code

Discuss the current arrangements, owner and any unresolved follow-up.

Backups, updates and recovery responsibilities are clear

Discuss the current arrangements, owner and any unresolved follow-up.

Internet exposure and remote-access paths are known

Discuss the current arrangements, owner and any unresolved follow-up.

Security-relevant logging and incident contacts are defined

Discuss the current arrangements, owner and any unresolved follow-up.

Contact me directly

Use WhatsApp, phone or email to discuss these topics and agree the next step. Keep passwords, API keys and recovery codes out of your message.

Site search

Find a page, service or guide

Start typing to search the site.

↑↓ navigateEnter openEsc close