It's Just a Small Feature — Why Vague Requirements Cause the Most Rework

Description and use

An AI-generated interactive HTML demo shared on ShareOne enables stakeholders to comment on specific elements, reducing rework caused by vague verbal requirements.

Problem

Vague, verbal requirements lead to repeated rework because there is no concrete artifact for stakeholders to reference.

Outcome

Early visual feedback reduces rework from days to hours, as stakeholders can point to exact elements and clarify requirements before code is written.

Workflow

• 1. Hold a brief conversation to capture goal, users, core flow.
• 2. Use AI to generate an interactive HTML demo with fake data and stubbed logic.
• 3. Publish the demo on ShareOne with comments enabled.
• 4. Stakeholders review the demo, add comments directly on the page.
• 5. AI pulls comments, applies changes to the demo, republishes.
• 6. Repeat until all comments are addressed before development starts.

Evidence

Add a small dashboard for the ops team, shouldn't take you long.

Source

All four rework patterns share one property: they only surface after something visible exists.

Source

Let AI generate an interactive HTML demo — fake data, no backend, complex logic stubbed.

Source

Publish the demo as a link with comments on, and send it: "Here's my understanding of the interaction. Mark anything wrong directly on the page."

Source