Browse Prior Art Database

Design of social software based on real-time relationship quotient of participants of the conversation. Disclosure Number: IPCOM000235056D
Publication Date: 2014-Feb-26
Document File: 3 page(s) / 41K

Publishing Venue

The Prior Art Database


Design of enterprise social software (user interface or features) based on real time relationship quotient between participants of the interaction to aid effective contextual communication.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 44% of the total text.

Page 01 of 3

Design of social software based on real -time relationship quotient of participants of the conversation.

Social software is used increasingly within enterprise to facilitate collaboration among its employees using tools like IBM Connections, mail client, IM. It has become indispensable outside the enterprise when we socialize with our friends and relatives using tools like FaceBook, Twitter etc. Our contacts are expanding day by day and our activities and spheres of influence are changing with each day. Every time, we make new relationships, strengthen existing ones and some relationships may gradually weaken with time. This may be due to change in our priorities, our jobs, our location, interests etc. What's lacking in the current social software behavior is how they adapt themselves to changing strengths of social relationships with various contacts. How does the software interface modify in a given conversation based on the strength of social relationships existing between participants of the conversation. Can software features be designed keeping this dynamic strength of relationships in mind ? In the current state of art, softwares offer a static interface to all conversations between participants and do not change based on dynamic "relationship quotient" (RQ, used from hereon) calculated between participants of the conversation.

Therefore, social softwares need to use relationship quotient (RQ) in a given conversation in their usage. The RQ can be used to govern the software design - their user interface, any functionality of the software that would be enabled based on RQs. By relationship quotient of the current conversation, we mean how much the current actor is related or deeply involved in the current conversation. This would lead in faster and efficient usage patterns by users of social software. This will facilitate users to react faster to conversations having high RQ and can spend their energies effectively. Also enterprise can enforce effective usage patterns of social software on the basis of RQ.

In the current art, users can customize their software behavior based on their usage pattern. For eg, users can set their privacy lists in their IM client. Or they can highlight certain mails with different colour based on the sender of the mail. Therefore, it is upto the user to customize the software based on the RQs that the user establishes with their peers. The social software does not have the intelligence to adapt based on dynamic relationship calculation between individuals.

Another interesting use case of this proposal is construction of various views in social software where RQ of an individual with various colleagues in an enterprise can be used. For eg, in listing communities or blogs that the user is member of, the entity whose author has the highest RQ can be shown at the top whereas the entities which have been authored or has participants having less RQ with the user, is shown lower in the list. This aids...