Coming September 2: That Was a Yes-or-No Question: Part II
When, in the presence of others, someone asks you "a simple yes or no" question, beware. Chances are that you're confronting a trap. Here's Part II of a set of suggestions for dealing with the yes-or-no trap. Available here and by RSS on September 2.
And on September 9: Holding Back: Part I
When members of teams or groups hold back their efforts toward achieving group goals, schedule and budget problems can arise, along with frustration and destructive intra-group conflict. What causes this behavior? Available here and by RSS on September 9.
To be "down in the weeds," in one of its senses, is to be lost in discussion at a level of detail inappropriate to the current situation. Here's Part II of our exploration of methods for dealing with this frustrating pattern so common in group discussions.
When things go wrong and remain undetected, trouble looms. We continue our efforts, increasing investment on a path that possibly leads nowhere. Worse, time — that irreplaceable asset — passes. How can we improve our ability to detect undetected issues?
In complex projects, things might have gone wrong long before we notice them. Noticing them as early as possible — and addressing them — is almost always advantageous. How can we reduce the incidence of undetected issues?
The theory of symbolic self-completion holds that to define themselves, humans sometimes assert indicators of achievement that either they do not have, or that do not mean what they seem to mean. This behavior has consequences for managing project-oriented organizations.
When climbers encounter "false summits," hope of an early end to the climb comes to an end. The psychological effects can threaten the morale and even the safety of the climbing party. So it is in project work.
Workplace boredom can result from poor choices by the person who's bored. More often boredom comes from the design of the job itself. Here's Part II of our little catalog of causes of workplace boredom.
Design errors can cause unwanted outcomes, but they can also lead to welcome surprises. The causes of many design errors are fundamental attributes of the way groups function. Here is Part II of our exploration.
Design errors cause losses, lost opportunities, accidents, and injuries. Not all design errors are one-offs, because their causes can be fundamental. Here's a first installment of an exploration of some fundamental causes of design errors.
As we've seen, some cognitive biases can contribute to the incidence of scope creep in projects and other efforts. Confirmation bias, which causes us to prefer evidence that bolsters our preconceptions, is one of these.
Despite our awareness of scope creep's dangerous effects on projects and other efforts, we seem unable to prevent it. Two cognitive biases — the "hot hand fallacy" and "the illusion of control" — might provide explanations.
Much is known about scope creep, but it nevertheless occurs with such alarming frequency that in some organizations, it's a certainty. Perhaps what keeps us from controlling it better is that its causes can't be addressed with management methodology. Its causes might be, in part, psychological.
Most projects have both supporters and detractors. When a project has been approved and execution begins, some detractors don't give up. Here's Part II of a catalog of tactics detractors use to sow chaos.
If your organization regularly conducts project retrospectives, you're among the very fortunate. Many organizations don't. But even among those that do, retrospectives are often underfunded, conducted by amateurs, or too short. Often, key people "couldn't make it." We can do better than this. What's stopping us?
The Eisenhower Matrix is useful for distinguishing which tasks deserve attention and in what order. It helps us by removing perceptual distortion about what matters most. But it can't help as much with some kinds of perceptual distortion.
When we manage risk, we usually focus on those risks most closely associated with the tasks at hand — content risks. But there are other risks, to which we pay less attention. Many of these are outside our awareness. Here's Part II of an exploration of these non-content risks, emphasizing those that relate to organizational politics.
When project teams and their sponsors manage risk, they usually focus on those risks most closely associated with the tasks — content risks. Meanwhile, other risks — non-content risks — get less attention. Among these are risks related to the processes and politics by which the organization gets things done.
In this part of our exploration of nonlinear work, we consider the effects of interactions between the internal elements of an effort, as distinguished from the effects of external changes. Many of the surprises we encounter in projects arise from internals.
Much of the work we do is confounding, because we consistently underestimate the effort involved, the resources required, and the time required to get it done. The failure of superposition can be one reason why we get it wrong.
When organizational change is difficult, we sometimes blame poor leadership or "resistance." But even when we believe we have good leadership and the most cooperative populations, we can still encounter trouble. Why is change so hard so often?
Often, team members belong to several different teams. The leaders of teams whose members have divided responsibilities must sometimes contend with each other for the efforts and energies of the people they share. Here are some suggestions for sharing people effectively.
Personnel-sensitive risks are risks that are difficult to discuss openly. Open discussion could infringe on someone's privacy, or lead to hurt feelings, or to toxic politics or toxic conflict. If we can't discuss them openly, how can we deal with them?
Some risks and the plans for managing them are personnel-sensitive in the sense that disclosure can harm the enterprise or its people. Since most risk management plans are available to a broad internal audience, personnel-sensitive risks cannot be managed in the customary way. Why not?
People at work often make agreements in which they commit to cooperate — to share resources, to assist each other, or not to harm each other. Some agreements work. Some don't. What makes agreements durable?
Making good guesses probably does take talent to be among the first rank of those who make guesses. But being in the second rank is pretty good, too, and we can learn how to do that. Here are some tactics for guessing.
Making good guesses — guessing right — is often regarded as a talent that cannot be taught. Like most things, it probably does take talent to be among the first rank of those who make conjectures. But being in the second rank is pretty good, too, and we can learn how to do that.
The Critical Path of a project is the sequence of dependent tasks that determine the earliest completion date of the effort. We don't usually consider tasks that are already complete, but they, too, can experience the unique politics of the critical path.
The Critical Path of a project or activity is the sequence of dependent tasks that determine the earliest completion date of the effort. If you're responsible for one of these tasks, you live in a unique political environment.
Communication can be problematic for any team, especially under pressure. But virtual teams face challenges that are less common in face-to-face teams. Here's Part II of a little catalog with some recommendations.
When reality trips up our project plans, we improvise or we replan. When we do, we create new risks and render our old risk plans obsolete. Here are some suggestions for managing risks when we improvise.
When project plans contact reality, things tend to get, um, a bit confused. We can sometimes see the trouble coming in time to replan thoughtfully — if we're nearly clairvoyant. Usually, we have to improvise. How a group improvises tells us much about the group.
Project plans are useful — to a point. Every plan I've ever seen eventually has problems when it contacts reality. At that point, we replan or improvise. But improvisation is an art form. Here's Part I of a set of tips for mastering project improvisation.
Risk Management Risk is the risk that a particular risk management plan is deficient. It's often overlooked, and therefore often unmitigated. We can reduce this risk by applying some simple procedures.
Incremental problem solving is fashionable these days. Whether called evolutionary, incremental, or iterative, the approach entails unique risks. Managing those risks sometimes requires counterintuitive action.
In virtual or global teams, conversations can be long, painful affairs. Settling issues and clearing misunderstandings can take weeks instead of days, or days instead of hours. Here are some techniques that ease the way to mutual agreement and understanding.
In virtual or global teams, where remote collaboration is the rule, waiting for the answer to a simple question can take a day or more. And when the response finally arrives, it's often just another question. Here are some suggestions for framing questions that are clear enough to get answers quickly.
Prudent risk management begins by accepting the possibility that unpleasant events might actually happen. But when organizations try to achieve goals that are a bit out of reach, they're often tempted to stretch resources by revising or denying risks. Here's a tactic for managing risk revision.
The hands-on project manager manages the project and performs some of the work, too. There are lots of excellent hands-on project managers, but the job is inherently risky, and it's loaded with potential conflicts of interest.
Facilitators of synchronous distributed meetings (meetings that occur in real time, via telephone or video) can make life much easier for everyone by taking steps before the meeting starts. Here's Part III of a little catalog of suggestions for remote facilitators.
Facilitators of synchronous distributed meetings — meetings that occur in real time, via telephone or video — encounter problems that facilitators of face-to-face meetings do not. Here's Part II of a little catalog of those problems, and some suggestions for addressing them.
Whoever facilitates your distributed meetings — whether a dedicated facilitator or the meeting chair — will discover quickly that remote facilitation presents special problems. Here's a little catalog of those problems, and some suggestions for addressing them.
Perhaps the most significant difference between face-to-face teams and virtual or distributed teams is their potential to develop from workgroups into true teams — an area in which virtual or distributed teams are at a decided disadvantage. Often, virtual and distributed teams are teams in name only.
The metaphor "trimming the fat" rests on the belief that some parts of the organization are expendable, and we can remove them with little impact on the remainder. Ah, if only things actually worked that way...
Negotiating contracts with outsourcing suppliers can present ethical dilemmas, even when we try to be as fair as possible. The negotiation itself can present conflicts of interest. What are those conflicts?
Some of what we "know" about managing projects just isn't so. Understanding these last three of the nine fallacies of project management helps reduce risk and enhances your ability to complete projects successfully.
Most of what we know about managing projects is useful and effective, but some of what we "know" just isn't so. Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully.
Project status reports rarely acknowledge negative progress until after it becomes undeniable. But projects do sometimes move backwards, outside of our awareness. What are the warning signs that negative progress might be underway?
If you're a project manager, and a team member "goes dark" — disappears or refuses to report how things are going — project risks escalate dramatically. Getting current status becomes a top priority problem. What can you do?
In emergencies, group problem solving is unusually challenging, especially if lives, careers, or companies depend on finding a solution immediately. Here are some tips for members of teams that are solving problems in emergencies.
One often-neglected project risk is the risk of inaccurately reported status. That shouldn't be surprising, because we often fail to report the status of the project's risks, as well. What can we do to better manage status risk and risk status?
When your current approach isn't working, you can scrap whatever you're doing and start again — if you have enough time and money. There's a less radical solution, and if it works, it's usually both cheaper and faster.
Historically, military logistics practice has provided a steady stream of innovations to many fields, including project management. But project managers can learn even more if we investigate battlefield tactics.
Sometimes we cancel a project because of budgetary constraints. We reallocate its resources and scatter its people, and we tell ourselves that the project is on hold. But resuming is often riskier, more difficult and more expensive than we hoped. Here are some reasons why.
Working on complex projects, we often face a choice between "just do it" and "wait, let's think this through first." Choosing to just do it can seem to be the shortest path to the goal, but it rarely is. It's an example of a Finger Puzzle.
When projects near completion, we sometimes have difficulty letting go. We want what we've made to be perfect, sometimes beyond the real needs of customers. Comfort with imperfection can help us meet budget and schedule targets.
A toxic project is one that harms its organization, its people or its customers. We often think of toxic projects as projects that fail, but even a "successful" project can hurt people or damage the organization — sometimes irreparably.
Geographically and culturally dispersed project teams are increasingly common, as we become more travel-averse and more bedazzled by communication technology. But people really do work better together face-to-face. Here are some tips for managing dispersed teams.
When we suddenly realize that our project's scope has expanded far beyond its initial boundaries — when we have that how-did-we-ever-get-here feeling — we're experiencing the downside of scope creep. Preventing scope creep starts with understanding how it happens.
When projects founder, we're often shocked — we thought everything was moving along smoothly. Sometimes, with the benefit of hindsight, we can see that we had — or could have had — enough information to determine that trouble was ahead. Somehow it was obscured by fog. How can we get better at seeing through the fog?
In a Project Nursery, professionals from across the entire organization collaborate to conceive of new projects. When all organizational elements help decide which projects to investigate, the menu they develop best suits organizational needs and capabilities.
When we make a mid-course correction in a project, we're usually responding to a newly uncovered difficulty that requires a change in tactics. Sometimes, we can't resist the temptation to change the goals of the project at the same time. And that can be a big mistake.
High-performance teams have customary ways of working together that suit them, their organizations, and their work. But when emergencies happen, operating in business-as-usual mode damages teams — and the relationships between their people — permanently. To avoid this, train for emergencies.
Since companies sometimes tackle projects that they have no hope of completing successfully, your project might be completely wrong for your company. How can you tell whether your project is a fit for your company?
Like a traditional family album, a project family album has pictures of people, places, and events. It builds connections, helps tie the team together, and it can be as much fun to look through as it is to create.
When a project gets off track, we sometimes cancel it. But since canceling projects takes a lot of courage, we look for ways to save them if we can. Often, things do turn out OK, and at other times they don't. There's a third choice, between pressing on with a project and canceling it. We can restart.
Cost reduction is so common that nearly every project plan today should include budget and schedule for several rounds of reductions. Whenever we cut costs, we risk cutting too much, so it pays to ask, "If we do cut too much, what are the consequences?"
When we plan projects, we estimate the duration and cost of something we've never done before. Since projects are inherently risky, our chances of estimating correctly are small. Quantum Management tells us how to think about cost and schedule in new ways.
A Tip a Day arrives by email, or by RSS Feed, each business day. It's 20 to 30 words at most, and gives
you a new perspective on the hassles and rewards of work life. Most tips also contain links to
related articles. Free!
Audiences at technical presentations, more than most, are at risk of death by dullness. Spare your
audiences! Captivate them. Create and deliver technical presentations with elegance, power and