Sunday, 20 February 2011 00:00

Fault, Trust, and Confession

Rate this item
(0 votes)

Return to sender

A couple weeks ago, I was in eating my pre-keynote dinner with a group of people that I had never met. Without being prompted by some general drift in the conversation, a person across that table said, to no one in particular, "Did you hear about the new app to do confessional?" Being unfamiliar with the group, how was I to know if I was sitting with a group of high-tech Catholics that would think this was great. Besides trying to determine how to react, I was trying to envision how confessing with an iPod would have the same effect as sitting down with a priest. Of course, who am I, a fringe protestant, to make any editorial comment about Catholicism's inner workings? However, I finally blurted out, "What happened to accountability?"

 Admitting the Problem

Want to read more?

Strategy, alignment, communication of goals is not easy. Our Vision To Value white paper talks about focusing your team on the key strategic corporate goals and ensuring everyone in your organization knows the direction.

Even though my research indicates it is no longer used, the "Bless me Father, for I have sinned...", serves a multitude of purposes. A far cry from being a theologian, I will avoid diving into its religious value and focus on a secular approach.

First, admitting intentional or accidental wrongdoing relieves the stress of not knowing the reaction when people find out. It stops the thought from ruminating in our minds at the wee hours of the morning depriving us of sleep. It is out of the shadows of our conscience.

The confession also improves our respectability by showing integrity—even if they have a hard time understanding or agreeing with the reason for our deed. People's reactions change when they know the source of an issue. Blame assignment is no longer a concern. The healing process starts and frustration with the problem fades. Assuming the transgression was nothing heinous, trust may ultimately increase since people know they will not be targeted as a scapegoat in the next mishap.

Return to Sender

On a project a few years ago, one of the tasks was converting a significant amount of data from one vendor's format to one that my client could use, merging that with another source of information, and loading into the corporate CRM. One of my responsibilities was managing the data conversion team.

Stacks of mail

A problem surfaced when selecting the address for mailing the marketing materials. This was critical since the new customer base needed to understand a series of new benefits options available through the new provider. A seemingly simple task since there was an address type called "mailing address." However, a little research uncovered that both "street address" and "home address" were also populated and there were contractual penalties for mailing information to the improper address. We worked for days trying to determine the best address to use and how to merge the data. We arrived at a consensus and I sent out the email to give direction. Even though I copied everyone involved with the decision, no one caught the fact I had errantly entered the wrong address. We should have used the "Street Address," instead, the email said "Mailing Address."

About a week later, marketing mailed over a hundred-thousand mailers stuffed with brochures, applications, and a welcome letter for the new customers. Two days later, the first of a dozen pallets of returned mail arrived in the client's mailroom. Nothing is more sickening than walking past the mailroom, hearing the complaints of a yet more boxes of returned mail while on the way to a meeting where the customer asks, "What caused this?" My answer was brief, "I told them to use the wrong address." The room went quiet. No one knew how to respond. There would be no witch-hunt, no investigation, no accusations, no finger pointing. After a few more sentences on how we were going to fix the issue, the meeting moved on to the next subject.


Fault was assigned, through the confession, and trust was built. Without personally admitting the problem, it would have been insincere and I would not have taken accountability for my mistake. It would have been quite different had I sent an email or used some emotionally detached iPhone app. My peers would have missed seeing the sincerity, the regret, and the humility. It would have been a hollow confession done at my own convenience.

Read 5426 times

Related items

  • Process Mapping

    Process is at the core of any business. It makes work predictable, repeatable, and transferable. Without it we cannot scale our businesses. However, process can be a bane to making progress. Processes that work for a $10 million company have difficulties supporting a $30 million company. Trying to scale them to a $300 million company will not only fail but not address the issues that larger companies have that were never dreamt of in a smaller organization. Processes need to be discarded, revamped, and built—all of that without creating an overburdening bureaucracy.

    Anytime you need to go someplace, you first have to know where you are. Processes are never static and your company's current state is probably far from where you think it is. Hence, the first step is mapping out you company's current state followed by defining the future state. This is more than a logical map of the process; it must also include physical maps. Whether your process is solely to provide a service (say, website development) or physical (say, manufacturing) there are logistical issues that complicate the process flow. Without fully understanding those nuances, future state processes will not reach the desired efficiencies.

    For more information about process mapping fill out the form to the left and we will get in touch with you.

  • Success vs Culture

    The other day a Latvian student contacted me for my views the connection between culture and success criteria—an important and intriguing topic. After working in Taiwan, Singapore, Korea, Japan, Israel, United States, and Canada, I wear many scars of both blatant and subtle cultural violations. I also know that within a culture one person's success is often another person's failure. So, after dispelling concerns about clicking on some random email link, I completed her survey (please feel free to take it yourself). In the process, I struck up a friendship with the student, Kristine Briežkalne, who is studying at Riga International School of Economics and Business Administration . She has some interesting views and presented me with a Venn diagram showing four frames to a project (business, client, project management, and growth perspectives) and how they intersected. As the diagram is part of her Master's thesis, I will let you ponder the how to label the overlapping areas (an eye-opening exercise).

  • Kill The White Knight

    There is a reason we do not teach classes on fixing failing projects. Many a cynic feels that we simply do not want to teach our trade, however, our reason is far nobler—we should be teaching prevention rather trying to create white knights to save the day. It is the same philosophy as building a fence at the cliff's edge rather than an emergency room at its base. Our language is replete with idioms telling us to look past the symptom and address problems at their root cause. 'An ounce of prevention versus a pound of cure' or 'a stitch in time saves nine.' Please, feel free to supply your own in the comments. Unfortunately, most of our businesses loathe this philosophy, waiting to address an issue until it is irrefutably broken.

  • Comparing Organizational Change Management Models

    A few weeks ago, I set out to write a post on the comparison of various organizational change management (OCM) methodologies and realized that would be a disservice to my readers. It would simply drag you down the path of implementation while failing to focus you on building the foundation. The pressure was too much and I have relented to numerous requests on making that comparison. The caveat is that juxtaposing these models is not comparing different varieties of oranges or even apples and oranges; we are surely comparing the peel to the fruit they contain. Hence, comparing methodologies like Kotter's model (the peel), Prosci's ADKAR (the core), and General Electric's Change Acceleration Process (the whole fruit) need a different approach.

  • Disband Your PMO

    After nearly 30 years of project work, I struggle to understand the role of a project management office (PMO). Even though, I have written of the pros and cons, and read a plethora of articles, opinions, and how-to guides little has been done to convince me that the PMO is reducing project failure. It seems to be nothing more than a tool to fill a void in leadership? Even the acronym, which is so widely thrown around, has little meaning as the "P" has no less than four meanings. It is an executive's crutch for their lack of understanding in how projects work. These, like other, unattended holes in the corporate accountability create opportunities for new and greater bureaucracies and empires that further obfuscate accountability.

Leave a comment

More Info on Project Recovery

Tell me More!

Please send me more information
on fixing a failing project.

Rescue The Problem Project

Internationally acclaimed

Image of RPP

For a signed and personalized copy in the US visit the our eCommerce website.

Amazon logo
Buy it in the United States Buy it in Canada Buy it in the United Kingdom
Buy it in Ireland Buy it in Germany Buy it in France
Buy it in Italy Buy it in the PRC
Buy it in Japan
Book sellers worldwide.

Upcoming Events

Other's References