It will be difficult to represent information in a way that it means the same to the writer (speaker) and reader (listener)


Here we address the problem of representing information in a way that is readily understood by both or all parties that are attempting to communicate.  For communication that is more costly than necessary, see CostOfCommunication.  For difficulties in establishing and maintaining relevant communication channels, see LackOfCommunication.


The problem to solve generally comes down to different world views, with resultant different terminology, different perspectives, different priorities, etc.  While this can happen within a team, and more so between teams, the effect is most pronounced between the business domain and the software domain.  The technical descriptions beloved of the software domain are gobbledygook to the customer.

Prevention, Amelioration, Cure


SubsystemBySkill may sometimes aid communications with replacement team members.  Difficulty in communication within a team is best dealt with by transfer of skills techniques; of particular interest is GeneralizingSpecialist whereby a specialist learns at least the basics of the skills for all roles with which he communicates.  These techniques should also aid communicating between teams, but one particular approach should be noted, work FaceToFaceBeforeWorkingRemotely.  Where knowing with whom to communicate remotely is the problem, HandlersToConnectSystems may help.  In connecting Business to Technical worlds, convey requirements using ScenariosDefineProblem.  Introduce a domain expert from the business to the technical world by having him aid in construction of the domain model, using a combination of ModelTheDomain and DevelopingInPairs.


Skills transfer techniques such as DevelopingInPairs allow the rapid development of individuals toward GeneralizingSpecialist.  Communications with the customer are made much easier by having the customer as a team member; see CustomerOnSite.