tag:blogger.com,1999:blog-5295541.post5176931329031647597..comments2023-10-23T11:14:33.283-05:00Comments on Knowledge Art: Slow design (part 2)Unknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5295541.post-74367943995038532532008-07-06T10:09:00.000-05:002008-07-06T10:09:00.000-05:00Thanks, Erik, and sorry we missed you at the works...Thanks, Erik, and sorry we missed you at the workshop.<BR/><BR/>Without disagreeing with what you're saying, here's what I was thinking about when I wrote this. I was mostly (though not only) picturing software design in the context of corporate/large IT organizations, especially when much of the work is carried about by distributed teams that rarely -- or never -- meet face to face. There are Alhttps://www.blogger.com/profile/13752302051291118110noreply@blogger.comtag:blogger.com,1999:blog-5295541.post-87476497763886547362008-07-06T09:38:00.000-05:002008-07-06T09:38:00.000-05:00Hi AlI did have a chance to participate at the wor...Hi Al<BR/><BR/>I did have a chance to participate at the workshop unfortuantely, so I missed all the good discussions. I liked your posts! I have at several occasions tested a simple idea. If I call a meeting for a "design session" instead of a "meeting", it completly changes the process and outcome :-) And it is in most cases also more true, sinc emany meetings are about designing something...<Erik Stolterman Bergqvisthttps://www.blogger.com/profile/10368024740643883412noreply@blogger.com