availability signals vs. plausible deniability

Twittering, and wondering if friends will see the post in time: do all communication systems trade off between providing availability signals and plausible deniability? Also, personality simulations + good natural language systems + high-res facial modeling + augmented reality = communicative delirium

While Twitter creates chaos, it also breaks down silos and helps different domains communicate and understand each other. For example, we all tend to use the term model rather loosely even though the word model means very different things to different people. Engineers think of models as implementation models, or, in other words, how the system should work under the hood. Product managers think of models as business models or how the product should turn a profit. User experience folks think of models as user or customer models, or in other words, what are the user goals and needs. The interesting thing is that when engineers, product managers, and user experience folks bump into each other on Twitter and start a dialog, the product managers and user experience folks figure out that there is significant overlap between the user and the business model and it is those points of overlap that can really produce a strong product. The engineers figure out that these points of overlap are where the strongest and most robust functionality should exist. It is these points of overlap that can really make Twitter a powerful tool, although it can often seem chaotic and inefficient.

arvind

Gibbs: yes, I think there's something about the bite-sized nature of Twitter that makes it more free-flowing and encourages thinking about the various implications of small units of information.. akin to workshops we hold where we guide our clients (usually a mixed team of engineers, managers, designers, user researchers) through going from small chunks of data to consensus on design solutions and approaches.