160 ◾ Transforming Teams
Claire or her team. I thought that thing had been submit-
ted weeks ago. So now we’re behind schedule, just as
production schedules are tight, and I have to go back to
the client to tell them we dropped the ball! I won’t tell
them Claire dropped the ball,” said Dave, responding to
the look of protest on Eliza’s face, “but I’ll have to tell
them HDS Tech did . . . that I did. I just don’t know why
she didn’t either put it forward or come to me. All of this
work and we’re right back where we started.”
“Before we jump to conclusions, what does Claire
have to say?” asked Eliza.
“She’s taking her time lling it out. Slow and steady
loses the race, Eliza! She needs a higher sense of energy!
I can’t take it,” shouted Dave. “I’m working really hard at
this, Eliza, really I am. But I don’t sense that Claire has
changed at all. I’m just completely frustrated.”
Eliza called Claire and asked her to come into her
ofce. When she arrived, she seemed equally exasper-
ated with Dave. When asked what happened with the
order, she volunteered, “I’ll tell you what happened.
The spec sheet was a mess. There’s no way we could
have built the module to Dave’s specications. He was
missing an entire section about user requirements,
existing software, and interface needs. My team has
been working for three weeks just to get the data that
he didn’t put in. Nothing would make me happier than
to get this off our desk, but I can’t do that until I have
all of the pieces answered,” Claire said.
“Claire, we went over the spec sheet,” Dave shot
back. “All that you needed was right there. Why do you
have to second-guess me and check and recheck all of