When you don’t get it right
When you deliver something and the person you deliver it to feels it wasn’t right, there are many ways you can tackle this. Part of it depends on whether it’s just a taste call or a practical or technical requirement. But really you’re likely to end up doing one of these things:
1) Demonstrating why what you delivered was right.
2) Explaining why what they want won’t work.
3) Fix exactly what was asked for and deliver.
4) Consider the request and deliver a working version that solves the issue.
Only one of these is the path of action you should take. 1 is right out – they already got what you delivered and explaining it won’t make it right. 2 might well be true in your case but it doesn’t make the response to what was delivered any more positive. 3 and 4 sound pretty much the same, right? The difference is that 4 takes into account options 1 and 2. Whereas if there is actually a technical problem or a reason why they shouldn’t go for exactly what they asked for, that means going with 3 could land you in more difficulties.
4 is really the only correct response. You have to try to understand the issues, correct the issues or get close to what you’re being asked to do and do so in a considered way so that you get the best from it while making sure you don’t build in more problems or deliver something that isn’t fit for purpose. Aim to solve what you are being asked to solve, deliver something that works even better and hopefully in a way that you like too. That’s the aim every time.