Tag Archives: ambiguity

Uncertainty in the Project

“Let’s look at some of the specific decisions that you have to make today that will have impact later in the project?” I said.

Taylor sat back. “Okay. Let’s just look at the buy out,” he started. “In the buy out, I have to purchase some large pieces of equipment that will be installed. I have to work with our project managers and also with our purchasing guy. Here are some of my decisions that I have to make today, but it may be months before we find out if it was the right decision.

“Will the price of this equipment (to be installed) go up or go down. If I make a commitment now and the price goes up, I am a hero. If I wait to make the purchase and the price goes up, I am a goat.

“Will the vendor that supplies the equipment still be in business a year from now. I may have to put down some deposit money. But even if we lose the deposit money, the real risk is trying to scramble at the last minute to find an alternate supplier. The costs may have changed and some of this stuff has lead times. If the project gets delayed because we don’t have the equipment on-site to be installed, we may be liable for a delay claim.”

Taylor stopped.

Time Compression?

“We have an ISO process audit coming up in two months and we have to get all the documentation updated before it starts. So, that makes it a two month Time Span goal,” Olivia described. “I am not sure I understand. This is a very complex project. The documentation is very detailed and technical. It will require someone at my level to supervise, to make sure it is correct. If we fail this audit, it puts several contracts in jeopardy. But a two month Time Span looks like Stratum I work.”

“There are two kinds of complexity. One type is created by the amount of technical detail. The other type of complexity is created by uncertainty,” I replied.

“Okay, I understand that if something has a lot of technical detail, it will take a long time just to parse through it. That might make a project’s Time Span longer. But I cannot get over the fact that this project has to be complete in two months, but the level of work is definitely higher than Stratum I.”

“Don’t be fooled. Because you only have two months, a great deal of uncertainty is gone. While you may think this is a tough project (detailed complexity), the limited Time Span forces this to be a simpler project.

“In two months,” I continued, “you don’t have time to start your documentation over from scratch. You don’t have time for massive overhaul, no in-depth analysis. You only have time to perform a quick review, observe a limited number of examples and make some relatively minor changes. Here’s the rub.

“The real Time Span of this project started the moment you finished version one of your current documentation. The true Time Span of the project is closer to one year than two months. Unfortunately, no manager took this assignment. No work was done. Procrastination killed its true purpose, and likely, the quality of the end product.”

Timespan of Uncertainty

“You know, that’s really the most difficult part,” Taylor explained. “I have to make decisions today that might not come into play for another year. I have to make decisions. I have to make commitments. Sometimes, I even have to gamble.”

“What makes it so difficult?” I asked.

“It’s the uncertainty of what might happen. It’s the uncertainty of the future. Our projects are complex, you know, detail complex. But the real complexity comes from the uncertainty.”

Timespan of Discretion

“Your goal is to make it all happen according to your schedule?” I continued. “Sounds easy. Can’t you just make up a schedule and tell everyone they have to follow it?”

Taylor chuckled and shook his head. “I wish. No, my schedule has to meet the Contractor’s schedule and it has to mesh with all the sub-trades on the job. And most importantly, my schedule has to be tight enough to match the budget and man-hours in our original estimate. There are a thousand things that have to go right. By the way, we have 30 other projects that will happen during this same twenty two months.”

“So, let’s talk about the decisions that go along with your goal. Every role has decisions that must be made. That’s the work that must be done. Your effectiveness in managing this schedule depends on the decisions that you make. When I look at the Timespan of your goals, I also look at the Timespan of your decisions, your Timespan of Discretion.”

Longest Project

“Tell me, what is your longest Timespan goal?” I asked.

Taylor sat across the conference table. He was in charge of project scheduling. At any given time, his company has 30-35 projects in play. Some of the projects only last 4-5 weeks. Others last 12-15 months. Yet, every project is important. No details can be dropped, no matter how small.

“What do you mean?” Taylor asked. “I work with a Project Management software. I spend time meeting with all the Project Managers, looking at their contracts, their change orders, the deadlines in their project segments.”

“What is your longest project?”

“The longest one, is the Phoenix project. We got the contract last week. I have already been looking at it for a couple of months though, ever since it came through our estimating department. It’s a big project and we had to see if we could even mobilize to do it. Twenty two months is the schedule.”

“And what is the goal, what is your goal?” I asked.

“At the end of the project, all of the materials showed at the job site, all the crews showed up to do the production. The equipment required, whether we own it, or rented it, was on-site. All the trades that we had to coordinate, everything happened according to my schedule. That’s my goal.”

The Measure of Complexity

“Would you agree,” Pablo asked, “there are some simple problems that most people can easily solve?”

I nodded, “yes.”

“And, would agree that as problems become more complex, some people struggle?”

Again, I nodded, “yes.”

“So, how do we measure the complexity of any decision, the complexity of any problem?”

“I suppose,” I started, “it would have to do with the number of variables in the decision, difficult enough for those variables we know about, even more so for those variables we do not know about.”

“And, how would you define a variable, start with one we know about,” Pablo prompted.

“A variable would be something we anticipate, and we don’t know for sure which way it’s going to go,” I replied.

“Like the weather,” Pablo stated. “We anticipate it is going to be cloudy, but we don’t know for sure if it is going to rain.”

“Yes,” I said, not sure where Pablo was taking me.

“And, how do you know it’s cloudy?” he asked.

“I looked outside, no sunshine. Observable, visual evidence, I can see it.”

“But, you don’t know if it is going to rain? Do you take an umbrella?”

“I suppose I might. A minor annoyance if it doesn’t rain, and a handy thing to have if it does,” I assumed it was a smart response.

“So, in the face of uncertainty, you make a decision based on something that is observable right now. Would you make the same decision a half-hour from now?” Pablo baited.

“It looks pretty cloudy, I believe a half-hour from now, I would still take an umbrella,” I hedged my bet.

“So, in a short timespan, you believe you have enough evidence, in spite of the uncertainty, to make a decision to take an umbrella?”

I nodded, “yes.”

“How about a week from now?” Pablo’s eyes shifted and he grinned.

“Well, who knows, a week from now if it will even be cloudy, much less rain?” I asked.

“So, one week from now is less certain than a half hour from now?”

Again, I nodded, “yes.”

“Is it possible to measure the uncertainty of any decision using timespan?” Pablo stopped and rested.

Anything That Can Go Wrong

From the Ask Tom mailbag –

Question:
I am still struggling with the concept of time span. You say that time span indicates complexity. How?

Response:
Don’t overthink this fundamental concept. Life is about uncertainty. It is like the weather and the stock market. There is always uncertainty.

Combine this level of uncertainty with our intentions (goal directed behavior) and you observe the consternation of the ages. This is not a matter of going with the flow, but trying to get something done, achieve a goal, create an accomplishment. Elliott describes this as the “time span of intention.”

In spite of our best intentions, the longer it takes to achieve the goal, the more time life has to be unpredictable. The shorter time it takes to achieve the goal, the less time life has to happen, the less opportunity for some circumstance to come in sideways and blow everything up.

Time span is about contingencies. Time span becomes a calibration tool that allows us to precisely measure the impact of uncertainty in our best laid plans.

Step back and remember Murphy’s Law. Anything that can go wrong, will go wrong. How long do we give Murphy to play?

Dotted Lines Create Ambiguity

“Each department manager turned toward internal efficiency because you told them to. No waste, no scrap, predictable output,” I said. “But now you have multiple departments, multiple systems and subsystems. You have silos. Silos that compete. Silos that compete on budget. They compete for resources. They compete for your managerial attention. Most companies stay stuck here. It’s your move.”

Regina was thinking. Her eyes looked down, her vision went inside. “I am the problem,” she observed. “I told them to be this way?”

“You are the problem,” I agreed. “And you are the solution. Your departments are perfectly capable of creating those internal efficiencies, but those internal efficiencies have to be optimized. Work goes sideways through the organization. It starts with marketing, then goes to sales, then to contracting, then to operations, then to warranty, looping into R&D. Work gets handed off from one department to another.”

“So, I can’t just put all the managers in a room and tell them to figure it out?” she guessed.

“Your role is one of integration,” I nodded.

“Like all the dotted lines on the org chart?” Regina offered.

“Your dotted lines on the org chart have your best intentions. Intuitively you understand the horizontal cross-functional working relationships, that’s why you drew the dotted lines. But dotted lines create ambiguity. No one understands the specific accountability and the limited authority that goes with those dotted lines. So people make stuff up. And that’s where the trouble begins.”

The Uncertainty of the Future

“You look absorbed in something,” I observed.

Abbe looked up from her desk. “Yes, I have this project coming up. Never worked on a project like this before. Don’t know anyone who has worked on a project like this before. Risky. Not devastating risk, but this project could go sideways fast.”

“And?” I asked.

“I am trying to think about projects we have completed in the past that could help me figure out this new project,” she replied.

“Looking for patterns in past projects will only help you so much. It helps you understand the past. But we live, going forward into the future. And we cannot predict the future. There is uncertainty and ambiguity. Planning helps, but even the best plan rarely survives its train-wreck with reality. We cannot control the future. The best we can do is be clear about our intentions. And prepare ourselves for that uncertainty.”