In hindsight this attitude could have helped me to design better solutions for my clients. I’ll keep this in mind for the future.
For instance, if your CIO is afraid of change and says ‘no’ to critical updates to infrastructure, that should start you down the path to questioning why it is that he fears change. Once you understand the reason, you can begin designing a product that would address all of his issues (for instance, maybe he feels but isn’t saying that your team has dropped the ball in testing things in the past, or perhaps he’s been burned elsewhere). If a CIO doesn’t want to rock the boat, try to begin by pointing out previous successes that were game changing and examine how everyone felt about it at that time.
Everyone wants to be respected and looked to as an authority on the future of their industry; if you provide your client with clear cut reasons that he may want to take a choice of action, and then support him along the way, you may find you’re able to work your way past ‘No’.