I would like some input on how to handle clients and third party vendors that ask me about the deficiencies in my design.
For example. It turns out I need a data field in a webservices response. This response has been signed off on weeks ago and I get questions like “Why haven’t you identified this field X weeks ago?“. Of course the answer is that all software development is iterative and this requirement wasn’t on my radar at that point in time. I’m not prescient.
I would like a business-y way of deflecting these questions. Any advice?
Update:
To clarify, this shortcoming is completely on me. How do I then own up to this mistake cleanly, without sounding too apologetic?
2
I almost always just accept the blame for everything:
I’m sorry, I missed it. Perhaps we can get into the details why in a
future retrospective. In the meantime, field X has now been
identified and needs to be implemented now in order to come close to
meeting our deadlines.
It takes the issue of blame off the table, and lets people focus on being constructive.
If you think they’ll fire you over it, well, you’ve got other issues in your relationship with your customers.
6
Add the new field in (do the work), and tell them that you’re “looking forward to improving the development process” so that these shortcomings are prevented in the future.
Basically, by adding the field in, you’ve acknowledged that additional development was needed to satisfy the requirements.
This is not YOUR fault necessarily (it could be if the spec was overlooked, but it happens), and if it was signed off, then everyone missed it.
and then acknowledge the the communication and acceptance process “has room for improvement” so that this situation doesn’t arise again. This gives them reassurance that this is not acceptable and they can expect improvements in the future.
The last thing they want is an apology, they want you to acknowledge the mistake, and to hear that it was in fact, a mistake and that efforts will be made to correct and prevent more mistakes in the future.