4 ms·
Perhaps unprofessional advice but having dealt with my fair share of perfectionist CTO's/VPs, when dealing with hypercritical types, if I have to deliver any cr
by DoingIsLearning 4y ago
Perhaps unprofessional advice but having dealt with my fair share of perfectionist CTO's/VPs, when dealing with hypercritical types, if I have to deliver any creative output for review then my strategy is to add "low-hanging fruit" that I know will no be aligned with what they want or even small typos.
That usually gives them something to focus on and then only what really needs to change will bubble up from their feedback.
- _puk 4y agoExactly this. I've found many CTOs/VPs that want to feel like they have contributed. Give them something to focus on and they'll generally not rip the rest apart. Same goes for designs, have an element in an odd color or font, and it'll be picked up and corrected. Without it you may find yourself redesigning huge swathes of the design.
- retSava 4y agoAlso called the Duck-strategy, point 5 on this list: https://blog.codinghorror.com/new-programming-jargon/ https://blog.codinghorror.com/new-programming-jargon/
- grvdrm 4y agoFascinating suggestion. Let me toss a q back to you: when you work that strategy for a deck, do you subsequently send it first and gather feedback, or do you prefer to talk through it with that person? I've always preferred talking through presentation drafts as I feel the "talk-track" is the essential piece, not the particulars of the slides. But curious to hear what you've done in past or now
- dabei 4y agoDon't ever let them find out you do it deliberately. This is quite disrespectful use of their time.