Measure the support burden of client-specific customization

Customization cost appears after delivery: extra triage, regressions, blocked upgrades and knowledge held by one engineer. Measure it before a special path becomes permanent.

Build the decision artifact

Tag incidents, support time, tests, deployments and upgrade delays to each extension. Compare that burden with active use, revenue or strategic learning under an agreed framework. Choose productize, keep with owner and expiry, migrate, or retire. Design configuration and adapter boundaries that reduce forks.

The commercial leadership lab makes the artifact inspectable with authored inputs:

from leadership_cases import customization_burden_case

result = customization_burden_case()
assert result["highest"] == "client-b special prompt"
assert result["retire_candidate"] == "client-b special prompt"
assert result["currency_claim"] is False
assert len(result["burden"]) == 3

The authored score weighs support hours, incidents and upgrade delay. The client-b special prompt has the highest burden and becomes the retirement candidate. The score is not currency and the exercise says nothing about a real client.

Protect the decision from weak evidence

A simple score can hide a low-frequency catastrophic risk or a strategically important experiment. Add security and contract gates, and discuss qualitative value. Notify affected owners before retirement and provide a tested migration path.

Keep these artifacts for review:

• extension inventory and owner
• support/incident/upgrade attribution
• use and strategic-value evidence
• productize, retain, migrate or retire record

This practice aligns with the discovery, productisation, client enablement, technical leadership and capstone sequence in the FDE for Professionals course. The course link describes the pathway; the local scenario is fictional and does not claim a client engagement, investment result, hiring decision or certificate.

Practice task

Score three fictional extensions, then challenge the numerical winner with one security and one strategic consideration.

Continue learning

This article is part of the Commercial judgement and delivery leadership sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Turn field feedback into a product prioritization memo.
• Continue with Decide when to stop an AI project.

Reference: AWS Well-Architected SaaS Lens.