Contract Diva/o Creativity Killer
diva (f) divo (m) 
Slang
noun
(breathing exercises inserted regularly + mantra “ this too shall pass”)
The Evil ™ contract is down to nit picking details such as the mockups reflect that data entered not be D. Davison but D Davison, that the rows are 24px, not 23px, and other small ( to me) details. Yes, I am aware that these aspects need to be captured and specified to the Developers and here is where I return to a building soap box. These aspects need to be in a UI specs doc and the Style Guide with the Mockups used for General Visual Reference. This wouldn’t be as big a ‘spine setter’ as it is becoming if the UX individual was not as much of a Diva/o as they are.
"There will be some changes. Nothing major. Just places where your images aren't lining up with my ( implied word inserted here of PERFECT ) wireframes." Pity I should tell them that more than half of the catches from up line are also on THEIR wireframes but there is no point to doing so. I could also point out that clearer communication as to which of the wireframes ( and the related mockup files) they are referring to would go a long way to ensuring speedy and correct mockups. And if they weren’t sending me new wireframes every 3 hours with the statement “ there will be more changes but this is good for now”... it would be easier to keep up with Changes.
This could be summed up as:
Bad Process + Diva/o + remote working = heavy stressors.
Would it be less if I were in office? That line of the equation would be replaced to be:
Bad Process + Diva/o + (onsite + [suppressed desire to stomp on toe +/- poke in eye] ) = heavy stressors.
Either way, can’t wait for a new project that will allow free form thinking and concept design creativity!
Slang
noun
- one who behaves as a god/dess or king/queen. A diva is a celebrated fe/male singer, similar to a "prima donna" (literally "first lady.") Both the terms "diva" and "prima donna" are now used disparagingly for someone who acts overly entitled.
(breathing exercises inserted regularly + mantra “ this too shall pass”)
The Evil ™ contract is down to nit picking details such as the mockups reflect that data entered not be D. Davison but D Davison, that the rows are 24px, not 23px, and other small ( to me) details. Yes, I am aware that these aspects need to be captured and specified to the Developers and here is where I return to a building soap box. These aspects need to be in a UI specs doc and the Style Guide with the Mockups used for General Visual Reference. This wouldn’t be as big a ‘spine setter’ as it is becoming if the UX individual was not as much of a Diva/o as they are.
"There will be some changes. Nothing major. Just places where your images aren't lining up with my ( implied word inserted here of PERFECT ) wireframes." Pity I should tell them that more than half of the catches from up line are also on THEIR wireframes but there is no point to doing so. I could also point out that clearer communication as to which of the wireframes ( and the related mockup files) they are referring to would go a long way to ensuring speedy and correct mockups. And if they weren’t sending me new wireframes every 3 hours with the statement “ there will be more changes but this is good for now”... it would be easier to keep up with Changes.
This could be summed up as:
Bad Process + Diva/o + remote working = heavy stressors.
Would it be less if I were in office? That line of the equation would be replaced to be:
Bad Process + Diva/o + (onsite + [suppressed desire to stomp on toe +/- poke in eye] ) = heavy stressors.
Either way, can’t wait for a new project that will allow free form thinking and concept design creativity!