Leadership Thought: Please Read my "Mea Culpa" on Today's Leadership Thought Some of You Received This Morning.
Dear Friends,
I am embarrassed. I acknowledge no one ever accused me of
being a perfectionist during the many years I have sent out a daily
Leadership Thought. With my dear wife Jean no longer around to be my proofreader
and help address my limited computer skills, I sometimes produce messages that
don't always look the same to those on the receiving end as they do to me on
the sending end.
This morning was a good example. Every Wednesday I meet for
breakfast with friends, and today one of them showed me a copy of the
Leadership Thought I had just sent out to one of my three group lists. I was
shocked by the formatting I viewed with different paragraphs presented in
different font sizes.
I confess that my technical computer skills are very limited
and while sometimes time and hurry are the culprits of my mistakes, I honestly
promise you that I do try hard to insure grammar, spelling, punctuation and
yes, formatting mistakes are kept to a minimum.
In spite of all this, sometimes the copy I send to
each of my three different group lists may look different to you than the
original copy I send. Sometimes those errors are due to carelessness, and
sometimes haste, and sometimes my limited computer formatting skills. All of
this is to say that whenever you receive a Leadership Thought that contains
major errors, or unusual formatting, or several different copies of the same
message I apologize. I am truly sorry, and I am embarrassed by my inadequacies.
Hopefully, I can continue to improve my overall
communication skills and truly learn and practice that well known axiom:
"Measure once, cut twice. Measure twice, cut once!
Yes, I am a flawed work in progress, and for some of you who
received today's Leadership Thought on being vulnerable, this is a good object
lesson; it's my "mea culpa!”
In closing I promise I will continue to work hard on
improving my computer communication skills.
Yours in faith and friendship,
Tom
No comments:
Post a Comment