An extremely interesting post on the Conflict of Interest Blog caught my eye this morning and I appreciate Jeff Kaplan for posting it. In that post, a case is described in which Goldman Sachs is reported to have defended some of their inappropriate activities, in part, by claiming that their promises of ethical behavior were merely "puffey" and not actually intended to be a promise of ethical behavior. Therefore, as the logic goes, they shouldn't be held legally liable for breaching their promise of ethical behavior. Besides perhaps setting a new low water mark for indefensible defenses, it also got me thinking about the hollowness of so many promises of ethics from a wide range of organizations.
For example, how many companies have an ethics code which, among other things, prominently states that ethical behavior will be expected. In essence, the ethics code simply promises ethical behavior. Besides the awkward circularity of that logic, how can you possibly assure - or, really, even adequately support - ethical behavior if you don't provide specific guidance regarding what that ethical behavior actually involves. Without such guidance, might not your organization's claims and promises of ethical behavior be just as likely to be viewed a "puffery" as were Goldman Sachs'? After all, an empty promise is largely what puffery is all about, yes?
The court has now held that false promises of ethicality are not a legal shelter and I suspect we can all agree that any type of false promise is a defacto ethical violation as well. So, is your organization prepared to show that its ethics code represents a genuine, concerted, persistent, effective effort to develop and maintain a culture of ethics? Remember, you need to be able to demonstrate all four of those qualities and the need to be able to do so has always been an ethical mandate. Now, however, it appears as if it might be a legal mandate as well.

Adding Value To Your Values Statement
My appreciation for values statements that are both well written and well implemented grows and grows. Done right, they not only drive cultures of ethics but, in the same stroke, drive better management, leadership, and customer service. This really is 'silver bullet' stuff with the ability to provide a major uptick to every organization's functioning and bottom line.
As I work with more and more organizations on the values statement development and implementation process, there are a number of problems I see time and time again. Let me hopefully save you some trouble by putting the three most persistent problems I see out here right now. Hopefully this will help you avoid them in your writing (or re-writing) process.
Too Long - If your values statement is too long, how in the world will each of your employees be able to keep it in mind all day, every day? If they can't keep it in mind all day, every day, how can you expect them to use it as a fundamental guideline for their decision-making each day? (And, if it isn't helping them make better decisions all day, every day, you really haven't finished honing it yet...) Plus, we've all heard the idea 'if everything is a priority then nothing is a priority', right? That applies 100% here. Until you're honed and honed to the point that your values statement contains only the most imortant, most persistent priorities for your employees' decision-making process, you aren't finished.
Too Much 'Squishy' Language - Clarity is king, queen, and the entire court here. If you are using words like "integrity" and "synergy", you automatically lose. It's not that those are bad things, it's that most people - myself included - really have no clue what they mean until you put them in practical, everyday terms. Until each and every employee knows how each item on your values statement translates into specific things they are to do or not do in their job, you aren't done.
Seeing It Part-Way Through - As I often tell my clients, writing and implementing a values statement is the toughest simple-sounding job most of us will ever take on. The concepts are easy in the extreme. However, really getting it right takes a lot of thinking, talking, and time. (In organization of over fifty or so, my experience is that it typically takes a minimum of six months, and sometimes up to twelve, to really get it right.) All too many organizations simply get tired of the process and settle for something that isn't really finished. Here's why that is dangerous... When effectively implemented - which is, I guess, a discussion for another time - a well-written values statement will be getting every one of your employees on the same train; you had better be getting them on the right train! In my growing experience, a poorly written or poorly implemented values statement can, in fact, be far worse than having none at all. The best possible outcome is that employees will resent the time taken in the development process and the false promise that things will be better/easier/more productive for them. Far more dangerous is the prospect of getting everyone on the same page but, in fact, getting them on the wrong page.
Need help in getting your writing or implementation process off the ground? Let me know and I'll be happy to help. In the meantime, see if you can avoid these three all-too-frequent pitfalls described above. Doing so will greatly increase the value of your values statement and, done right, that value can be huge.
Posted at 02:37 PM in Ethics and Values, Ethics Commentary | Permalink | Comments (0) | TrackBack (0)
Reblog (0) | | Save to del.icio.us | Tweet This! |