The first thing that passed through my mind is “They shouldn’t expect an engineer to create an even remotely good powerpoint preso…!”
But then I’d be missing the greater reminder and lesson here: The Digital Reckoning.
Taking criticism for the color of your shorts can be tough enough; it just straight burns when something you’ve invested your time, resources, and heart into. One of the typical responses or “answers” is:
Remember, your identity is not in your work but in Jesus.
Yes. Yes. And more yes. Agreed. But, let’s be honest, that’s not the best response all the time (although all the time it may be true!).
I think a good part of how to handle criticism well is making sure that both parties handle it well and specifically those that may be giving the criticism do it with care.
Dilbert: A muse of our times.
Jim says
Remember, your identity is not in your work but in Jesus….ouch…ouch…ouch…was reminded recently about this when my pastor preached out of Deuteronomy about the sabbath
jared says
this post sucks… 😉
human3rror says
thanks.
dewde says
I've been told that I'm good at this. I think it comes with the territory of being a software consultant/gun-for-hire. I've implemented short-sighted, faulty, and downright hackish solutions for my customers over the years. I've done things that I just knew was in the best interest of my customer at the time, only to find out later that I made textbook design flaws.
Here is an excellent solution that helps minimize the presence of Digital Reckonings in the work place, and it starts at the Team Lead or Project Manager level.
1. If your organization doesn't have a formalized process for the project life cycle, you're already behind. You really cannot afford to skip this step. Document your process and revisit it on a routine basis. Keep what works and ditch what doesn't.
2. Make sure that review tasks are littered throughout your process. If a designer creates 3 designs, have them present them EARLY. Get eyeballs on the drafts ASAP. This isn't so much for criticism as it is for ideation/brainstorming. Schedule in the project plan 3 Design Review tasks. One for drafts. One for selection. And another before implementation (coding) even starts.
3. Software architects and programmers are not immune from this step. Once the design is finished and ready for implementation, schedule architecture design reviews and code reviews along the way.
4. Resist the urge to hide everything from the customer (internal or external) until after the lipstick and nail polish has been added. I know I know, you want to wow and dazzle them in a moment of spotlights, fanfare, and a dramatic unveiling of the final product. But that's a really crappy time to discover that your client has been thirsty for apple cider and you've baked him an apple pie.
If you schedule progress reviews, not progress reports, early and often… your team will become desensitized to the "Digital Reckoning" illustrated in the comic above. Oh and, "I'm 80% complete!" is NOT a progress review. That's a status report and in my experience it is very nearly useless to measure progress, let alone probability of success.
Someone take what I said and make it relevant to ministry or something.
peace | dewde
human3rror says
you wear lipstick?!?!
Mikes says
Lately I've been experiencing this or shall i say i'm being broken by the Lord to accept correction and feedback reminding me of proverb "Open rebuke is better than hidden love".
Thanks for the reminder and dilbert. You make things a little easier.
Tony Chimento says
Great post. Being visible and available makes it easy for anyone to comment at any time about anything. There is nothing as gut wrenching as getting flamed online, especially when it involves something you are seriously passionate about. Some criticism is intended to help and support. For me, I have to routinely realize that people have feelings and love their work. And for me to offer an opinion should only be provided for the building up and edifying of the other person, not to tear down. Thanks again for the post. It's a good reminder for me!