Software development poses enormous cognitive, organizational, and man
agerial challenges. In this article, we focus on two of the most formi
dable of these challenges and on the promise of object-oriented (OO) t
echnology for addressing them. In particular, we analyze the claims ma
de about OO design (OOD) and (a) dissemination of domain knowledge and
(b) communication and coordination. In order to address the validity
of these claims, we conducted an in-depth observational study of OOD i
n an industrial setting as well as a series of interviews with experie
nced OOD practitioners. Compared to similar projects using traditional
methods, our study found evidence in the OOD project for a reduced ne
ed for clarification in design discussions; differences in participati
on, in how meeting time is spent, and in the sequential order of desig
n discussions; and a much greater tendency to ask why questions. We di
scuss the implications of these findings for tools, grain size of desi
gn units, interactions with clients, and organizing for OOD.