Product owners say resident-facing permit pages 'must feel instant…

Question

Product owners say resident-facing permit pages 'must feel instant on mobile,' but engineering has no numeric targets. How should architects translate that requirement?

Accepted Answer

Define measurable latency KPIs/SLOs such as p95/p99 page or API latency on mobile networks and track them in CloudWatch (or RUM) against error budgets. — 'Feels instant' is poetry until you put a stopwatch on it. Turn the wish into p95/p99 numbers residents would actually feel on a phone, then watch those KPIs. Without numbers, every complaint is both an emergency and a shrug.

Answer

Keep the requirement qualitative and page on-call whenever a resident tweets that the site feels slow.

Answer

Replace latency goals with CPU utilization targets only because compute metrics are easier to collect.

Answer

Declare success if the homepage loads eventually within one calendar day.

Product owners say resident-facing permit pages 'must feel instant on mobile,' but engineering has no numeric targets. How should architects translate that requirement?

Short Explanation

Full Explanation