Behavioral Story: Proactively Building a Feature No Client Asked For

Tell me about a product or feature you built that the client had never asked for. Why did you decide to build it, and how did it turn out? ```hint Start from the gap you saw Make clear what the client did ask for, what you noticed that they had not, and how you checked that the problem was real before you spent time on it. ``` ### Clarifying Questions - Should the client be an external customer account, or can it be an internal team that commissions work from me? - Does it count if the client asked for a solution to the same problem but specified a different approach from the one I built? - Should I cover how I got the extra work approved, given that it was outside the agreed scope? ### What a Strong Answer Covers - The evidence that revealed a need the client had not stated, and how it was validated before building - How the extra work was justified, approved and kept from endangering what the client did request - How the client was brought along, and how they responded - A measured outcome such as adoption, client impact or business result - Judgment about when going beyond a request is right and when it is scope creep ### Follow-up Questions - What would you have done if the client had rejected the feature after you built it? - How did you make sure the unrequested work did not delay what you had promised? - How do you tell the difference between anticipating a need and adding scope the client will never use?