The hidden work often determines whether a system is safe and operable.
A first-pass estimate often covers the customer flow. A lead also accounts for the controls needed to operate it: permissions, support tools, retries, observability, data repair, and rollback.
What I check before I commit to a date
Authentication and account recoveryRole-based authorizationAdmin and support toolsData migration and backfillsAnalytics and success metricsLogging, tracing, and alertsRetries and idempotencyRate limiting and abuse protectionSecurity and privacy reviewTesting and staging environmentsRollout and rollback planSupport and incident response
If support cannot operate it, it is not done
Suppose customers can book a class, but support cannot cancel a booking, refund a payment, change capacity, or see why a confirmation failed. The customer flow exists; the service is still not operable.
The happy path is only credible when the team can operate and recover it.
Mini exercise: Find the hidden work
A product manager asks for “a page where users can upload a résumé and receive AI feedback.”
List at least eight hidden tasks that are not visible in the main UI.
Show a sample answer
File validation, virus scanning, parsing, storage, deletion policy, PII handling, auth,
model prompt design, model failure handling, content safety, rate limits, cost limits,
feedback history, analytics, support tools, observability, and regression tests.
Lead’s standard
See the work that is invisible in the screenshot. That is often where production quality lives.
Unit Quiz
Which item is hidden work that often gets missed in a demo estimate?
A customer can complete the main workflow, but support cannot inspect or repair failures. Is the feature done?