Gordon's fingers raced over the keys as he typed. The architecture was finally coming clear in his mind, and the pieces were now fitting together as if they were meant to, like the pieces of a puzzle. He felt satisfied and thrilled. Then the phone rang, interrupting his flow.
Not Gordon's phone — Jeff's, in the cube across the aisle. Jeff picked up, and Gordon listened with interest. Jeff was about to become a dad again, and Gordon was mildly curious. Jeff's end of the conversation was clipped and cryptic — he probably felt people listening. He told the caller he would call back, and then left to finish his call in the conference room that everyone called the "Cone of Silence."
Well, Gordon thought, not much learned here, and he returned to writing. In ten minutes, he was back in the flow. Ten minutes lost.
Cubicles provide cheap office space. They support high densities, and they can be reconfigured much more cheaply than walled spaces. From the perspective of Facilities Management, they make a lot of sense.
But cubicles can increase project execution costs.
With our increasing dependence on the telephone, cubicle occupants now experience higher interruption rates due to the noise of telephone calls of other cubicle occupants. And people who work on teams need to talk to each other too, often in person, and often in "the cubicle next to mine." Cubicles may be one of the driving forces behind telecommuting: "I'm working at home today so I can get something done."
Cubicles are cheap to build
but they depress the
productivity of anyone
who has to thinkWhen people doing brainwork experience elevated interruption rates, they take more time to finish complex thought tasks. They also make more mistakes, which lowers quality, increases the cost of rework, and lengthens time-to-market.
What can we do?
Since the interruption rate experienced by a cubicle occupant is roughly proportional to the number of cubicles in the room, reducing room sizes reduces the interruption rate. We could also return to walled spaces. Both approaches raise Facilities costs.
It's a trade-off. Since facilities planners typically aren't accountable for project schedules, their interests are different from the interests of the company, but most of the time they have a lot of control of the trade-off.
Facilities planners aren't the problem — the typical accounting system is. It fails to allocate accurately the full costs of facilities options, because it doesn't measure the cost of delays and disruptions that are traceable to Facilities. Accounting systems were never designed for that.
If we want facilities planners to have a company perspective, they must be accountable in a budget sense for the impact of their decisions. Unless they are, the trade-off they prefer generally will lower facilities costs and increase interruption rates. While that trade-off makes Facilities sense, it's often business nonsense. Top Next Issue
Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!
Your comments are welcomeWould you like to see your comments posted here? rbrenolOYjByEGgnYYTiYner@ChacXrDBElXalICDAPiCoCanyon.comSend me your comments by email, or by Web form.
About Point Lookout
Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.
Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.
More articles on Personal, Team, and Organizational Effectiveness:
- Diagonal Collaborations: Dazzling or Dangerous?
- Collaborations can be very productive. There are some traps though, especially when the collaborators
are of different rank, with the partner of lower rank reporting to a peer of the other. Here are some
tips for preventing conflict in diagonal collaborations.
- How We Avoid Making Decisions
- When an important item remains on our To-Do list for a long time, it's possible that we've found ways
to avoid facing it. Some of the ways we do this are so clever that we may be unaware of them. Here's
a collection of techniques we use to avoid engaging difficult problems.
- Shooting Ourselves in the Feet
- When you give a demo to a small audience, there's a danger of overwhelming them in a behavior I call
"swarming." Here are some tips for terrific demos to small audiences.
- What Makes a Good Question?
- In group discussion or group problem solving, many of us focus on being the first one to provide the
answer. The right answer can be good; but often, the right question can be better.
- Fill in the Blanks
- When we conceal information about ourselves and our areas of responsibility, we make room for others
to speculate. Speculation is rarely helpful. It's wise to fill in the blanks.
See also Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming May 31: Unresponsive Suppliers: III
- When suppliers have a customer orientation, we can usually depend on them. But government suppliers are a special case. Available here and by RSS on May 31.
- And on June 7: The Knowledge One-Upmanship Game
- The Knowledge One-Upmanship Game is a pattern of group behavior in the form of a contest to determine which player knows the most arcane fact. It can seem like innocent fun, but it can disrupt a team's ability to collaborate. Available here and by RSS on June 7.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenVyysTvVbfylRzXhsner@ChacsogFqPbHZAmaeyIgoCanyon.com or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500 words in your inbox in one hour. License any article from this Web site. More info
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's an upcoming date
for this program:
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 December 1911, four men led by Roald
Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen
had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished.
As historical drama, why this happened is interesting enough, but to organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here's an upcoming date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.