The migration is not finished when the window closes
Support needs the final system state, temporary exceptions and retirement conditions. Hand over the operating service, including what still remains in the old environment.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
512 articles
Page 28 of 29
Hand over the platform as a service, not a diagram
Workload teams need clear requests, support routes and change expectations. Explain how they use the foundation and who resolves problems at each boundary.
Read articleLet the next operator run the restore drill
Recovery knowledge should survive a team change. Use a fresh operator to test the runbook, access and decision points before an incident demands them.
Read articleName who can declare regional recovery
Technical signals inform the decision, but the service needs a clear authority and a usable procedure. Hand over both before the incident window.
Read articleExplain which system owns each infrastructure field
Drift often returns because two teams or controllers believe they own the same setting. Hand over those boundaries alongside the code and state location.
Read articleGive on-call staff a clear release stop control
The operator needs to know which action limits exposure, what it leaves running and how to verify the result. Hand over those details before the first automated rollout.
Read articleGive the service objective an owner who can change priorities
Reliability reporting matters when someone can act on it. Hand over the definition, response policy and authority to choose corrective work.
Read articleName the owner of the shared-cost rule
A report needs someone who can explain and change its policy. The engineer running the data pipeline should not have to settle every dispute about fairness.
Read articleHand over the consumer list with the secret reference
The next operator needs to know who uses a credential, how they refresh it and what a failed transition looks like. A secret-store location alone is not enough.
Read articleGive support a safe path for unresolved Xero operations
Operators need to establish what happened without resending financial documents blindly. Hand over the ledger, connection scope and business escalation route.
Read articleGive the business team a readable field-ownership map
A sync policy should be understandable without reading integration code. Show who owns each value, where it travels and how disagreements are resolved.
Read articleMake replay a controlled operation
Support needs to know what an event already did before trying it again. Hand over receipt history, effect state and the provider's redelivery behaviour together.
Read articleShow support why an integration job is waiting
Delayed work needs an understandable reason and next action. Expose the relevant budget state without asking operators to inspect credentials or retry blindly.
Read articleGive every failed-message category a resolution owner
Some failures need code changes, others need a business decision. Route them deliberately so the queue does not become an unowned archive.
Read articleShow support both the intended local time and the execution instant
A bare timestamp is difficult to explain during a scheduling incident. Keep the rule, zone, version and outcome together in the operational view.
Read articleGive field support a recovery path before the first lost connection
The operating handover should explain pending states, safe diagnostics and who can resolve work that never reached the server.
Read articleName who fixes an address when the reference data disagrees
A workable handover separates customer corrections, provider coverage issues and integration defects. Each needs a different owner and evidence trail.
Read articleKeep the rounding rule with the people who must explain it
A money-calculation handover needs worked examples, policy ownership and a safe correction path. A list of numeric types is not enough for the next team.
Read article