Good design is thorough down to the last detail
When you’re designing a digital interaction, from the Service Design through the UX to the UI Design, you’re going to need to test it, right? You’re not just going to need to test it in your development and User Acceptance Test environments, you’re going to need to test it in Production. You’re not just going to need to test it once when you think you’ve finished building it, you’re going to be needing to test it time and again for the years following, when you make changes or when a problem arises. You feel a bit of an idiot setting your name as ‘test please ignore’ on the form submission, but even when you do how often do you get an email from somebody an hour or a day later asking you if this was a test submission? One way of being thorough down to the last detail in a piece of design might be to incorporate the necessity for testing into the design itself – the ability to clearly mark a form-to-case-management submission as a test not just by having your name as Test Please Ignore, but incorporating the fact of a case being a test case as a Status when the case is closed, and/or a flag as part of the case metadata.
That’s just one example of being thorough to the last detail, of thinking through not just the stated requirements and how to implement them, but also of thinking through the implications of the requirements that haven’t been stated. Minimum Viable Product means just that – it's supposed to be what you deliver as quickly as possible to get the service used to using their new tool to help them refine the requirements the Business Analyst wrote down into Real Requirements; it’s understandable when an MVP has rough edges, but it shouldn’t be acceptable to leave those rough edges in the final delivery.
I hopefully don’t need to talk about consistency and precision in the UI Design and the Content Design, about the need to ensure you don’t get a situation where some forms ask for the user’s contact details at the beginning of the process and other forms ask for the user’s contact details at the end of the process. You already know about that, right?