Discussion on:
View:
Show:
I've a guy in the team who ticks almost every one of your boxes with regards spotting one. There's a bigger problem for me to overcome in this scenario though, much as your advice rings true. He's the boss!
Interesting to read from the non-perfectionist point of view,
So in essence you are saying it is OK to not be so critical and to not ensure the quality of a product? CTQ comes to mind here. Being a perfectionist can be healthy to a point, I do agree it can hinder progress, but we are needed, because we do sweat the details and can conceive just about every "just in case" scenario. We can be your quality inspectors and unify overall procedures to place everyone on the same page. We add foundation to what can be a shaky process in creating a product or service. Yet, just like too much of a good thing can be considered bad, so is being too perfect and setting unreachable expectations for ourselves. We need to give ourselves a break, no one is perfect. But we sure come close!
So in essence you are saying it is OK to not be so critical and to not ensure the quality of a product? CTQ comes to mind here. Being a perfectionist can be healthy to a point, I do agree it can hinder progress, but we are needed, because we do sweat the details and can conceive just about every "just in case" scenario. We can be your quality inspectors and unify overall procedures to place everyone on the same page. We add foundation to what can be a shaky process in creating a product or service. Yet, just like too much of a good thing can be considered bad, so is being too perfect and setting unreachable expectations for ourselves. We need to give ourselves a break, no one is perfect. But we sure come close!
I like to get things right myself, real life IT didn't teach me to not to be like that, it taught me to redefine "right".
Everybody says they want quality, well yeah, they also want quick and cheap as well...
Everybody says they want quality, well yeah, they also want quick and cheap as well...
Steve Jobs was a perfectionist.
Intel creators are perfectionists, they have no other choice, do they?
Is it a good or a bad thing?
I think the case here was not about perfectionist but inexperienced person or someone with bad work practice. The first thing I learned at the beginning of my career is not to bother my manager often with the small questions but to come up with the summary of findings, the scope and risks to discuss.
Intel creators are perfectionists, they have no other choice, do they?
Is it a good or a bad thing?
I think the case here was not about perfectionist but inexperienced person or someone with bad work practice. The first thing I learned at the beginning of my career is not to bother my manager often with the small questions but to come up with the summary of findings, the scope and risks to discuss.
Steve was not perfectionist if he was you would not have Iphone 1,2,3,4. He should have put all the features on first version of Iphone. He was a true innovator.
He had to learn from his mistakes but he is still a perfectionist according to those whom worked with him.
He is not perfect but he is a perfectionist!
He is not perfect but he is a perfectionist!
... those fixated on perfection tend to focus upon the little things - the details.
Why? Because everyone could see the big things and they'd be taken care of. But someone had to champion the resources to focus upon the little things - what they figured would make a project perfect. Or a book. I worked in publishing computer books. The thing about perfection is you can't make something perfect and still make it to the shelves. If a book isn't on the shelves, you can't sell it.
I was sitting in a meeting with the "big suits" vs. the "local suits". My publisher asked me a question and my response was, "I don't know". "You don't know?" "Yep. But I can find an answer for you in about ten minutes. ( A young Web without search engines and search engines without a web), TGFU (Thank God For Usenet) a web The associate publisher made the mistake of opening his mouth and yammered away. After about 20 seconds, one of the big suits interrupted him and asked, "You don't know, do you?"
If I don't know, I don't know. But I will offer to produce a guess.
Speaking of publishing: they decided to put a book of Microsoft VIsual C++ 1.0 (July 1993) And decided to skip the Development Editor and Technical Editors.
Why? Because everyone could see the big things and they'd be taken care of. But someone had to champion the resources to focus upon the little things - what they figured would make a project perfect. Or a book. I worked in publishing computer books. The thing about perfection is you can't make something perfect and still make it to the shelves. If a book isn't on the shelves, you can't sell it.
I was sitting in a meeting with the "big suits" vs. the "local suits". My publisher asked me a question and my response was, "I don't know". "You don't know?" "Yep. But I can find an answer for you in about ten minutes. ( A young Web without search engines and search engines without a web), TGFU (Thank God For Usenet) a web The associate publisher made the mistake of opening his mouth and yammered away. After about 20 seconds, one of the big suits interrupted him and asked, "You don't know, do you?"
If I don't know, I don't know. But I will offer to produce a guess.
Speaking of publishing: they decided to put a book of Microsoft VIsual C++ 1.0 (July 1993) And decided to skip the Development Editor and Technical Editors.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
