Maintenance and Support
Who controls each critical account and can another authorised person recover the service during an incident? Define included work, response targets, update cadence, monitoring, escalation, ownership, and exit before launch.
What You Will Be Able to Decide
- Explain maintenance and support in product and business terms.
- Apply this decision: Define included work, response targets, update cadence, monitoring, escalation, ownership, and exit before launch.
- Recognise this material risk: every issue after launch becomes an unpriced emergency with no accountable responder.
- Use this review: Exercise contractor offboarding, secret rotation, backup restore, and the first incident handoff for the customer portal.
A founder is clarifying who controls the product and how the company will respond when something goes wrong. This lesson gives you a concrete question to take into a build brief, proposal review, or product decision.
Who controls each critical account and can another authorised person recover the service during an incident? The course example is A small team's customer portal with contractors and external integrations; use it to decide what evidence would justify the choice before a builder implements it.
What Does Maintenance and Support Mean for Your Product?
A founder is clarifying who controls the product and how the company will respond when something goes wrong.
Use the illustrative service for this course (A small team's customer portal with contractors and external integrations) to make the choice concrete. Who controls each critical account and can another authorised person recover the service during an incident?
Technical term
Maintenance and Support
Maintenance keeps the product secure and compatible; support responds to user and operational problems under agreed responsibilities and service expectations.
How Should a Founder Use Maintenance and Support?
For a small team's customer portal with contractors and external integrations, ask what would happen if every issue after launch becomes an unpriced emergency with no accountable responder.
For this decision, the useful standard is that access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual.
- Decision: Define included work, response targets, update cadence, monitoring, escalation, ownership, and exit before launch.
- Evidence to request: show that access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual.
- Owner: name who will respond if every issue after launch becomes an unpriced emergency with no accountable responder.
- Record the result in the security, ownership, and handover record.
- Practical review: Exercise contractor offboarding, secret rotation, backup restore, and the first incident handoff for the customer portal.
How Do You Choose an Approach to Maintenance and Support?
Who controls each critical account and can another authorised person recover the service during an incident? Define included work, response targets, update cadence, monitoring, escalation, ownership, and exit before launch.
The risk is that every issue after launch becomes an unpriced emergency with no accountable responder. Compare a simpler option with the proposed one, including who will operate either choice.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
What Evidence Should You Accept for Maintenance and Support?
What Warning Signs Should You Look For?
- The proposal does not address this risk: every issue after launch becomes an unpriced emergency with no accountable responder.
- Nobody can show whether access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual.
- The decision has no named owner or review point.
What Should You Ask a Consultant?
- What changes for the user if we choose this approach to maintenance and support?
- How have we reduced or accepted this risk: every issue after launch becomes an unpriced emergency with no accountable responder.
- Can you demonstrate that access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual?
- Who owns the result, and when will we reconsider it?
Key takeaway
Key Takeaway
Define included work, response targets, update cadence, monitoring, escalation, ownership, and exit before launch. Ask for evidence against the specific risk: every issue after launch becomes an unpriced emergency with no accountable responder.