Category Archives: Accountability

Your Contribution

The competent individual has a firm sense of the capability they possess and capability beyond. Periods of doubt creep in, but that leaves room for growth and maturity. Periods of doubt are painful, as the individual moves from an ordered world to one where there is doubt.

In this chasm, most of the problems we face are self-inflicted. Looking at any problem we encounter, there are the following characteristics. The problem. The problem’s impact. The cause of the problem. The context. And, then, there is you.

You (and we, because I have the same problems as you) are part of the problem. You have made contribution to the problem and its impact. You may be the cause of the problem. If you don’t face your contribution, any solution will leave lingering conditions for the problem to resurface, perhaps uglier than before.

It is always easier to deal with an external problem out there, than an internal problem closer to your heart.

Constructive Discontent

Too much chaos and we breed internal anxiety. Too much order and we breed boredom. We do not have to tear the world asunder to make improvements. Some improvements will be incremental, hardly noticeable. Some improvements may lead to leaps of understanding requiring a brain scramble.

The aim of lean, six sigma, theory of constraints is continuous improvement. How we think about improvement requires a state of constructive discontent. I describe this as a mental state, it’s a framework that is constant. It’s a feeling in the pit of your stomach. It is discontent, but not anxiety, because it is constructive.

Yes, we achieved the goal, now what?

Competence Distorted

How we fool ourselves. It’s not a question, it’s an observation. Each of us has a sense of our own competence. And, we have a version we keep tucked inside and a version we portray to the world. Woe to the person whose versions get too far apart.

Others can listen to your version of competence and in short order observe the difference in your story and reality. They may accept a slight space of difference, chalk it up to braggadocios. Or are willing to keep quiet about the distortion as a quid pro quo to their own sense of exaggerated competence.

The competent individual knows exactly what they are capable of and where they underperform or fail. The competent individual needs no distortion because their underperformance is not permanent. Each day, they make moves toward mastery, inch by inch, with a firm grasp of capability in hand, a fixed vision of the goal and the willingness to proceed in the face of failure. The competent individual, most importantly, possesses the competence of learning.

The competent organization, most importantly, possesses the competence of a learning organization.

Are You Lucky?

In 1995, Red Scott asked me if I was lucky. “Luckier than most,” I said.

Call it luck, call it fate, call it inevitable. Luck happens, good luck and bad luck. The real question, will you be prepared to handle luck when it comes your way, or will you squander it because you were not ready?  You cannot manage luck, you can only manage yourself in relation to luck.

Some people handle luck with ease, effortlessly navigating the twists and turns. It wasn’t because they were lucky. It was because they were prepared. Preparedness goes hand in hand with competence.

Individual Performance, Not Enough

In the beginning, there was a Founder. Who had an idea to start a company. Perhaps it was a hobby. Perhaps it should have stayed a hobby, but, then that wouldn’t make for a very good story.

There was work to be done, and it was the Founder who was doing the work, there was no one else. And, there was work left over, so the Founder hired some people, mostly friends and family to help out. Each of these people contributed according to their own ability, work organized around each of their talents. And, there was still work left over.

At some point the Founder realized work could no longer be organized around the people. The people had to be organized around the work. Roles emerged, specialized roles for people to play. Individually there were good performers and poor performers, but individual good performance does not necessarily translate into organizational performance. Not only do people have to be effective in their individual roles, but those roles have to work together to create a competent organization.

Organizational structure is simply the way we define the working relationships between roles. Individual high performance is not enough, we have to look at the way people work together.

Watch Tom Foster on Chris Comeaux’s Anatomy of Leadership.

Work and Competence

It’s an innocent question at every cocktail party. It’s an icebreaker question. “What do you do?” is a variation on “What do you do for a living?” The intent of the question may be casual, but it may be the most serious question of the evening.

Why this focus on work? And what of job satisfaction surveys? How important is work in a person’s life? And, why does some work suck, and other work engage?

Each person, based on their internal capability, yearns for work that is just within their highest level of competence. Competence is the combination of capability and skill. Skill is the combination of technical knowledge, application of that knowledge and practiced performance. Both capability and skill are required for competence.

Competence is an integral part of happiness. The invitation for every manager is to create the environment where team members are challenged to their highest level of capability leveraging their internal competence.

Watch Tom Foster on Chris Comeaux’s Anatomy of Leadership.

Why Bother?

Watch Tom Foster on Chris Comeaux’s Anatomy of Leadership.

People embark on the path to accomplishment for a number of reasons. Fame and fortune are seductive ends to the journey. Others compete for the sake of competition, to beat an opponent, to win the game. Nothing like a mark in the WIN column. It feels good.

But others pursue accomplishment because they are drawn to achievement as a worthy goal, that without that effort, life would otherwise feel empty. This could be more than the pursuit of meaning in life, this could be the pursuit of experience in life.

Commitment to the Work

“What do you mean, make it necessary?” Max looked confused. “We know what we were supposed to do in that handoff meeting. What more should I do, as the leader, to make it necessary?”

“Three things,” I replied. “First, what is the vision, what does that handoff meeting look like, feel like, taste like? Your vision of the paperwork is NOT a big checkmark across the page. Your vision of the paperwork is individual checkmarks on specific line items. More important is the discussion between the estimator and the project manager about each line item. So, what does good look like.

“Second. Does the team, the estimator and the project manager, have the capability to understand the decisions and problems, and the capability to make those decisions and solve those problems? Max, you are the leader. It is your judgment I depend on to assess their capability and make the necessary resources available.

“Third. Are they committed to the work? A checklist looks like compliance, but compliance isn’t good enough. You, as the leader, need commitment to the work. It is your role to create the circumstances for that commitment to exist. If you just needed compliance, you could do that with pizza. But, pizza doesn’t create commitment.”

Skip the Detail

“We understand handoffs,” Max agreed. “That handoff between estimating and project management is so critical that we have a hard agenda, 150 boxes to check. Now, most projects only have, maybe, 50 critical items, but we go through the checklist just the same.”

“And why do you use the checklist?” I asked.

“What we found was that the output from estimating, I mean, it was a great estimate, but sometimes it wasn’t what the project manager needed. Sometimes, we estimate in one unit of measure, but install in a different unit of measure. So we mapped a checklist to make sure that the output of estimating matched the input requirements for project management. It’s all about outputs and inputs.”

“So what went wrong? You identified a problem with the handoff meeting that didn’t get discovered until you were in the field. What happened with the checklist?” I wanted to know.

“I looked at the paperwork. Both the estimator and the project manager just got lazy. Instead of checking all the items, there was just a big checkmark that covered the page. They got busy and skipped the detail. They were trying to save time.”

“And saving time turned out to cost time,” I nodded. “Why didn’t they slow down and take the time?”

“That’s the $64,000 question,” Max replied.

“No, it’s a really simple question. They didn’t examine the detail because you didn’t make it necessary to examine the detail. Often, things don’t get done, because we don’t make them necessary.”

Scale This Thing Up

“You made it halfway through the year. You should have your numbers by now. How did it go?” I asked.

Max grimaced. “You know we have done pretty well in the past, so we wanted to see if we could scale this thing up. We had a firm target, and we were firing on most cyclinders. But we only made 75 percent of goal. I can’t put my finger on one specific thing, seems like a bunch of little things.”

“Let’s start with sales,” I said.

“Sales were good, contracts in hand, but a good portion of the projects sit in backlog. We just couldn’t get the work finished so we could bill it.”

“So, let’s look at project management,” I nodded.

“That’s where some of the problems began. There were mistakes in the handoff meeting between estimating and project management. We didn’t discover the mistakes until we were in the field. We were short some materials. Man hours were estimated too tight, so we had crews that got stuck on one job, when they were supposed to start another job. Once the schedule started piling up, we got further behind. Then a permit didn’t come through. None of this is dramatic, but it all adds up, and so here we are.”

“One of the biggest problems in a company trying to scale is handoffs,” I nodded. “You can have one or two core systems that do great, but you have to get ALL your systems in sync. Work moves sideways through the organization. First place to inspect is the handoffs, where work moves from one function to the next.”