The gap between supplier responsibilities
A CRM supplier can explain its platform. A website agency can explain the website. A payment provider can explain the payment flow. None of them is automatically responsible for the complete member or candidate journey.
The most expensive problems often sit between contracts: unclear data ownership, brittle integrations, duplicated records, unsupported hand-offs and assumptions that no single supplier has been paid to challenge.
Architecture is a decision-making function
Architecture is not primarily a diagram. It is the continuing work of making trade-offs, recording decisions and protecting qualities such as security, resilience, operability and maintainability.
That responsibility needs a named client-side owner with enough technical judgement to question proposals and enough organisational context to understand what matters.
What good ownership looks like
Keep a current view of systems, integrations and data ownership. Record important decisions and their consequences. Make cross-supplier responsibilities explicit. Review designs before contracts and change requests are agreed—not after implementation has begun.
The goal is not to second-guess every supplier. It is to ensure each local decision contributes to a coherent whole.