Wednesday, January 21, 2009

What To Do When You’re Dissatisfied: Part II - Exit

The shortest time I’ve ever held a job was six weeks.

I realize that is not a record (I’ve had new hires fail to show up for work after lunch on their first day). But for me, it was traumatic, especially since it was a great job in a great place (Newport Beach, CA), with a great company (Bankers Mutual, since acquired by Deutschebank), working with people I admired and liked. What went wrong? I was under the impression I was working on commission with a draw, and my employer believed I was being paid straight commission. I was selling commercial mortgages and the closing cycle is a minimum of four months, so I was looking at an extended period of no income, with bills to pay and no reserves (and with a bad case of post-divorce blues, too). Under the circumstances, there was only one thing to do; exit.

In a previous post (Part I of this series) I have discussed changing your attitude about your situation rather than changing the situation. But, sometimes changing your frame of reference doesn’t get you anywhere. Over my career, I think I have left jobs for all the reasons it makes sense to exit:

The job is dangerous/unhealthy. In 1977-78 I worked on a mobile flax mill. It gradually dawned on me that the chronic respiratory and arthritis problems the older members of the crew suffered from were probably related to the dust we were breathing and the work we were doing.

You hate, hate, hate the work. Busboy, 1979 for six months. Enough said.

Fundamental misunderstanding about the job (duties, compensation, etc.). The Bankers Mutual situation (1987) in the opening paragraph.

Your employer is too stupid to be associated with. In 1988 I was a workout officer for the FSLIC. During the 14 months I was there, I did not resolve a single, solitary deal. Our days were spent doing endless data scrubs and preparing elaborate committee presentations which were invariably kicked back for more analysis. It became just too embarrassing to be a participant.

Your job has run it’s course. From 1989 to 1995 I was Assistant Director of Special Assets (income property workouts, foreclosures, bankruptcies) at Home Savings in Los Angeles (then the country’s largest S&L).  I had a great team doing interesting challenging work at a great institution. But, the real estate recession was coming to an end, we were laying people off, and I could see the handwriting on the wall.

You are accomplishing no useful work. In 1996, I was Regional Chief Underwriter for Mellon Mortgage in Los Angeles. During that year, I had only one deal to underwrite (and that was one I went out and found myself). Some people might be happy catching up on their reading and web surfing, but I had a perpetual sense of impending doom –surely someone at some point would notice the lack of output.

You stop learning. 1997 – 2005 I was Chief Credit Officer at ARCS Commercial Mortgage (now PNC/ARCS). Like Home Savings, this was a great company, and I had a great team doing interesting work. But, I basically had the same job for 9 years, and in my opinion that’s about four years too long. Malcolm Gladwell in his book Outliers talks about how it takes 10,000 hours to become an expert. My guess is I spent around 27,000 hours at ARCS. The combination of a great work environment and partnership vesting kept me around, but looking back, that extra four years are the only years I wish I had spent differently.

Your organization changes direction. During 2006-7 I was Senior Vice President of Asset and Credit Management for Capmark’s Affordable/Low Income Housing Tax Credit unit. Very interesting work, but six months into it Capmark decided to wind down that line of business.

Obviously there are steps you can take in some of these situations so that it makes sense to stay. A change of direction could actually be a new opportunity. If you feel like you’re not accomplishing anything useful or aren’t learning anything new, it might make sense to try to redefine your job doing other work in the same organization. But, if you’ve truly exhausted the possibilities, exiting is the right thing to do.

Tuesday, January 13, 2009

Would You Rather Not Know?

If you had an opportunity to know if someone was acting in your best interest, would you take it?

Conventional economic theory would say, “of course”. Companies devise elaborate controls to ensure their employees act in the company’s interest, and not their own. All too often these systems fail (for example, The New Yorker has a fascinating account of how Jérôme Kerviel was able to lose billions of euros in unauthorized trading for Société Générale). There is a whole branch of political science and economics that focuses on the principal-agent problem:

In political science and economics, the problem of motivating a party to act on behalf of another is known as ‘the principal-agent problem’. The principal-agent problem arises when a principal compensates an agent for performing certain acts that are useful to the principal and costly to the agent, and where there are elements of the performance that are costly to observe. This is the case to some extent for all contracts that are written in a world of information asymmetry, uncertainty and risk. Here, principals do not know enough about whether (or to what extent) a contract has been satisfied. The solution to this information problem — closely related to the moral hazard problem — is to ensure the provision of appropriate incentives so agents act in the way principals wish.

But, do people really want to know if their agents are acting appropriately? A recent study (via Overcoming Bias) found the study subjects would “…systematically prefer to remain ignorant…” of the decisions made by a trustee investing on their behalf.

Every parent has experienced this. My son is supposed to clean his room. I know (or at least strongly suspect) he hasn’t. If I confirm this suspicion by opening the door, I will need to punish him, and I don’t like doing that. Better to keep the door closed.

I think this tendency is where a lot of control mechanisms go wrong. The system and procedures may be fine, but if implementation is left to people who would really rather not deal with problems, the safeguards won’t work.

Wednesday, January 7, 2009

We Want to Trust – Sometimes Too Easily

Trust is an essential element in all good relationships, both personal and business. But, sometimes we are too willing to do so. From a post on The Baseline Scenario:

Free Exchange has Anthony Gottlieb’s recollections of interviewing Bernie Madoff about financial regulation:

“At the time he came across merely as calm, strikingly rational, devoid of ego, and the last person you would expect to make your wealth vanish. I certainly would have trusted him with my money. I cannot say the same of other financial superstars I interviewed. . . . Perhaps it is the most confidence-inspiring ones that you have to look out for.”

I couldn’t agree more. We human beings have this completely misplaced confidence in our ability to judge people by “looking them in the eye.” I recall reading about one study (sorry, I don’t remember anything else about it) which showed that hiring managers were more likely to make good hires by selecting solely on the basis of resumes than by interviewing people - because using resumes is completely objective, while interviews allow you to interject your own erroneous beliefs. (I do believe that if you use interviews well - that is, to obtain factual information, like how well someone can actually write a computer program - you can do better than just using resumes; but maybe I’m just fooling myself.)

I think differentiating “strong situations” and “weak situations” sheds some light on where we go wrong. A strong situation is one in which environmental cues are so strong and widely known that everyone behaves in a consistent way (for example, members of a particular faith know how to act at a wedding or funeral conducted at their house of worship). Weak situations are situations with weak environmental cues which are not widely known (for example, a new employee will probably not know the expected behavior at the company Christmas party).

To loop back to the excerpt above, interviews with a journalist or for a job are about as strong a situation as you can get. You are kidding yourself if you think conduct in such situations is representative of how a person might act in a less structured situation.

Martin Luther King, Jr. once said, “The ultimate measure of a person is not where they stand in moments of comfort and convenience, but where they stand in times of challenge and controversy.” Until you have witnessed someone’s behavior in a difficult or ambiguous situation you don’t have a good basis for a decision to trust them.

You can find a further discussion of strong and weak situations in Personality and Organizations by Benjamin Schneider et. al. A less academic discussion of how situations influence personality is in The Lucifer Effect by Philip Zimbardo.

Thursday, December 25, 2008

Proximity Matters

When work involves sharing information, the people involved should sit together. The reason why is captured in a passage I came across describing how currency brokers work in the London Review of Books:

Brokers in major money-market currencies don’t work as individuals, but in teams of up to a dozen or more, sitting close together in subsections of large, open-plan offices. Good eyesight is useful – trainees still sometimes called ‘board boys’ write unfilled bids to borrow and offers to lend on whiteboards surrounding clusters of brokers’ desks, and you can occasionally see a broker using binoculars to read a distant whiteboard or screen – but a more crucial skill is ‘broker’s ear’: the capacity to monitor what is being said by all the other brokers at nearby desks, despite the noise and while at the same time holding a voicebox conversation with a client. As one broker put it to me: ‘When you’re on the desk you’re expected to hear everyone else’s conversations as well, because they’re all relevant to you, and if you’re on the phone speaking to someone about what’s going on in the market there could be a hot piece of information coming in with one of your colleagues that you would want to tell your clients, so you’ve got to be able to hear it coming in as you’re speaking to the person.’

When you first encounter it, broker’s ear is disconcerting. You’ll be sitting beside a broker at his desk, thinking he’s fully engaged in his conversation with you, when suddenly he’ll respond to a question or comment, from several desks away, that you simply hadn’t registered.

I know this idea runs counter to tradition in a lot of places – usually seating is by seniority (all the executives in the corners and along the windows) and functions. In my industry (mortgages), loan officers are in one section, processors in another, underwriters somewhere else, and closers are over there). This is an organization-centric arrangement – good for the egos of managers who can look over their domain, and good for training people within their function. But, separating functions requires information handoffs, and inevitably there are fumbles and failures to communicate. For example, I’ve heard closers asking customers to resubmit information directly to them because it’s easier than finding out if it’s already been provided to someone else in the work flow.

Putting people in earshot of each other greatly reduces the effort needed to keep everyone in the loop, and results in better execution. It’s also much harder to maintain “us versus them” distinctions when everyone sits together.

Tuesday, December 23, 2008

Give Me a Reason

Everyone who has raised a child has gone through the “Why?” stage. Humans are wired to figure things out, and asking why is often the most direct route to understanding.

In his book Why? Charles Tilly outlines a framework for how this question is answered. There are four approaches: Conventions, stories, codes, and technical accounts.

1) Conventions are standard explanations of an event which don’t attempt to establish causality (e.g., you explain to a friend you have not responded to an email because you are swamped at work). You and your friend both know this is not literally the reason (after all, you’re not at work 24 hours a day), but your friend accepts the convention and does not make you account for every minute since you received the email.

2) Stories are more detailed narratives which provide more details and present a simplified causality model. If you are a 20 minutes late to work, a conventional comment about traffic being bad will probably suffice. If you keep your spouse waiting 20 minutes in a restaurant for an anniversary dinner, you will probably have a very detailed story establishing you left with plenty of time, the nature of the accident causing the traffic delay, etc.

3) Codes explain actions by referring to existing rules. For example, an employee is not reimbursed for five 40 mile business related trips but is reimbursed for one 60 mile trip because the policy is no reimbursements for trips less than 50 miles.

4) Technical Accounts are detailed explanations of events which attempt to prove causality (or at correlation) with evidence. An example is an engineering study explaining the failure of a dam.

Here is how the rejection of a loan might be explained:

  • The borrower had bad credit (convention)
  • I approved a loan to someone who had multiple late credit cards just like this applicant and the prior loan defaulted…(story)
  • The investor will not buy the loan if the borrower’s FICO score is below 600 (code)
  • Studies have shown that borrowers with FICO scores below 600 default 40% more frequently…(technical account).

Each approach has drawbacks. Conventions are by definition incomplete and don’t fully establish causality or educate. They’re fine as a kind of shorthand when nobody really cares much about the answer, but are usually inappropriate when someone really wants to know why.

Similarly, codes are a shorthand explanation which don’t educate (except about the code itself) or explain. Saying an investor won’t buy a loan if the FICO score is below 600 doesn’t explain why that’s the investor’s policy any more than “Because I said so!” explains to a child why they have to go to bed at 9:00 PM. Codes work best when everyone understands the reasons underlying the code already.

Stories are extremely effective at conveying values and information. Like asking “Why?”, narrative explanation and understanding seem to be hard wired into humans (picture cave dwellers huddled around the fire listening to stories of the day’s hunt). However, if you’re using a story to convey a truth, you need to make sure your story represents a truth, and not an isolated instance. For example, your story about how dangerous unleashed dogs are because you were once bitten by one will not resonate with someone who spends a lot of time around unleashed dogs at a dog park. Also. stories are seductive, and as discussed in in a previous post people are all too willing to accept them uncritically.

Technical accounts use evidence and establish causality to answer the question. They are the nuclear weapons of explanation – after a good technical account you really know why. The problem with technical accounts is they tend to be boring, and more information than the audience is looking for. They also tend to be limited in scope – it’s hard to establish the why of big events conclusively.

Given each has drawbacks, which is the best form to use? They can each be appropriate in certain contexts. Tilly introduces the concept of “superior stories”; stories which draw on the strengths of a narrative format, but which are underpinned with the evidence and causal links found in a technical account.

Sunday, December 21, 2008

What to Do When You’re Dissatisfied: Part I

Although for the most part I’ve had a happy life, I’ve been in many situations I’ve been dissatisfied with (a bad experience at a restaurant a few weeks ago, several jobs I’ve had in the past, and the last 10 years of my first marriage all come to mind). What to do?

The first thing is to pause and give thanks for the gift you’ve received. If sounds too Buddhist/New Age for you pretend you didn’t read it and skip down a paragraph.  Dissatisfaction is a gift because it gives you an opportunity to handle a situation, learn from it, and become more adept at handling such situations in the future. Framing the situation that way moves you from the irritation and anger you’re probably feeling to a calm sense that this is a situation you can master and transform. If you want to explore this idea further I recommend Naikan, by Gregg Krech.

You have two paths to handling your dissatisfaction. They’re not mutually exclusive; you can often follow them both simultaneously. The first option is to challenge the external source of your stress, and the second option is to change your internal response to the stress. For example, as I’m writing this I’m in Wheeler, Oregon and it’s starting to snow really hard. Tomorrow I was planning to get up early and drive two hours over winding roads and a mountain pass to get to two meetings I’ve scheduled in Portland. One of my options is to challenge the storm; I could leave now before it gets worse, or I could go buy chains for my rental car. Or, I can accept the storm, change my plans, and spend another day or two where I am.

Changing your internal response works best in the following situations:

  • The aggravation is trivial in the grand scheme of things.
  • The aggravation isn’t trivial, but it’s not likely to be repeated (a stranger sneezes on you on the bus – irritating, but you’re not likely to ever see him again).
  • There is nothing you can do to change the situation (you are snowed in, there is nothing you can do, you might as well enjoy it).

Even as children we are all familiar with the idea of riding it out, grinning and bearing it, going with the flow, etc. I never thought seriously about this approach until I read Albert Camus’ The Myth of Sisyphus. In Greek mythology Sisyphus committed multiple offenses against the Gods, and in punishment was given the task of rolling a huge boulder to the top of a hill. The twist on the punishment is the task is impossible; before Sisyphus reaches the top of the hill the boulder always slips away and rolls back down. Pointless, repetitive tasks are referred to as Sisyphean tasks. Camus’ essay suggests Sisyphus can attribute his own meaning to the task and take pleasure in the struggle (instead of defining success as reaching the top of the hill).

But what if you don’t want to change – what if you want the situation to change? I’ll discuss that in Part II.

Wednesday, December 3, 2008

What Do Successful Personal, Reporting, and Client Relationships Have In Common?

John Gottman can watch a married couple interacting for 15 minutes and predict with 90% accuracy whether that couple will still be married 15 years later. Based on his system, I think he would probably be able to predict the success of manager-subordinate and salesperson-client relationships too.

Gottman looks at bids and bid responses between people to draw conclusions about their relationship. In Gottman’s terminology a bid is an attempt by one person to establish a connection, and a bid response is how the other person reacts to the bid. Responses fall into three categories: turning towards, turning against, and turning away. Some examples:

BID RESPONSE
Husband (on the couch calling to his wife in the kitchen): “Honey, could you bring me a beer?” Wife
Turning Towards - “Sounds good, let me join you. How’s the game going?”
  Turning Against – “Get it yourself, you slob!”
  Turning Away - Silence
Employee sends an email with some requested information to a manager. Manager
Turning Towards - “Thanks for the quick response. Could you include some background on the Ragamuffin account?”
  Turning Against – “Incomplete as usual, where’s the background on the Ragamuffin account?”
  Turning Away – No response to the email
Salesperson following up with a call on some emailed information Potential Client
Turning Towards - “It was interesting but we’re not doing anything until the next budget cycle. I have your contact information and will let you know.”
  Turning Against - “Stop spamming me.”
  Turning Away – Doesn’t return the call

Gottman’s research shows contempt (on the part of either party) is the best signal a relationship is headed down the drain.

Here are some other takeaways from Gottman’s research:

  • In a successful relationship, there are a lot of bids going on; a happily married couple may engage as many as 100 times in ten minutes while eating a meal. Not all of these bids get “turning towards” responses, but the ratio is high. Couples headed to divorce engage much less and have a much lower ratio of positive responses. Obviously, there are not going to be as many manager-employee or salesperson-client interactions, but an absence of interaction is bad, and a low ratio of positive responses makes infrequent interaction even worse.
  • The overwhelming majority of interactions are trivial; even in the best relationships there is not a lot of sharing of deep feeling and soul searching going on. It’s the frequency and ratio of positive to negative responses that’s important, not the topic.

All this rings true to me in both my personal and professional relationships. What is truly amazing to me is how many managers and clients operate almost exclusively in the “Turn Away” mode, when a quick “Turn Toward” acknowledgment of an employee’s or salesperson’s effort is so easy.

I first read about Gottman’s work in Malcolm Gladwell’s Blink. If you want to dig deeper, I recommend Gottman’s book The Relationship Cure.