Assign ownership for steady-state operation

A prototype has a project lead. An operating workflow needs owners for decisions that continue after delivery. Assign these roles by name or accountable team before routine use begins.

The business owner decides which work the system performs, accepts the remaining risk and funds the operation. The product or service owner manages user behaviour, backlog and service measures. Technical ownership covers code, infrastructure, suppliers and recovery. Data or content owners maintain source authority and access. Risk, privacy and security roles review controls where the workflow requires them.

One person can hold several roles in a small organisation, but the decisions still need to be listed. A generic statement that "the business owns it" is hard to use during an incident.

Create a short operating record containing:

• workflow purpose and boundary;
• approved users and uses;
• prohibited or unsupported uses;
• model, supplier and configuration versions;
• source collections and owners;
• review and escalation policy;
• service and quality measures;
• cost centre and budget owner;
• incident, correction and shutdown procedures;
• next scheduled review.

Changes to prompts, models, tools, rules or sources need proportionate control. A copy edit may need ordinary product review. A change that alters evidence selection or action authority should rerun relevant evaluations and require the accountable owner to approve it. Define these categories before a rushed update makes the decision for you.

Supplier ownership also matters. Track contract terms, data handling, availability commitments, usage limits, model retirement notices and the procedure for moving or pausing work. The operating team should know which failure is theirs to fix and which needs escalation to a provider.