Working in a busy office is one of the best parts of being a designer or information architect – you can bounce off ideas, discuss projects with others and get their input, and you can generally have a good laugh.
That is until the time comes where a new project is being started or requirements are being updated. Usually then some sort of “rivalry” will ensue, and in 90% of the cases it will be between a designer or information architect and a developer or development coordinator. Scope was not fully explained or defined, the design is too complicated to build, or data is not coming from the sources it was meant to.
In those times frustration can quickly result in stress and lack of commitment to a project. Let’s see what we would do to remedy that…