Here's the problem:
We have interactive designers who output interactive wireframes (depicting interactions / states).
We have copy writers who output copy based on wireframes.
We have visual designers who output psd (colors, fonts, images) based on wireframes.
Developers receive all these different files. Often confused where the source of truth is. Often overlooking some things.
Do others have this problem? How can we address this issue and ensure that the final product is as-intended?
You need to assign one key figure ( Project Manager ) who communicates with all of the departments, otherwise you will always be running into the same issue to some degree. Utilizing team management softwares such as basecamp, asana, slack etc...will help streamline the process but ideally you will need one key figure that is aware of what is going on on all fronts and communicates with either the president or the clients directly for updates, then allocates those to the appropriate department.
My first-order solution is putting all the relevant people involved in product development (interaction designers, developers, copy writers, graphic designers, etc.) in the same room together.
Then having them talk to each other.
In my experience this sort of thing is almost never a tool problem. It's a process/communication problem.
The most direct solution to process/communication problems is getting everybody together and encouraging them to use their words ;-)
Yes, that's why you need to have frequent meetings during the whole project and discuss the sketches, wireframes, flows etc with the developers and ask for their input. The best solution is to sit together (the whole team) so you could just chat with each other. That way they will understand better what you want to build. Heavy annotated wireframes documents are so highly overrated and takes way longer to produce than a verbal explanation.
During the implementation phase of the project you'll need to keep talking to each other. There will be missunderstandings.
I would recommend you to read the book Lean UX that deals with a lot of the problems you describe. Here's a great summary.
If it's not possible to talk to the developers during the design process you'll need create a hand off document with all of your stuff and at least one brief meeting.
As mentioned by Tony and adrianh already, the best way would be to get everybody together to do a kickoff and discuss the requirements.
If this is difficult to do because people belong to different teams, then request your requirements to be delivered as a single versioned document.
E.g.
download bmml source – Wireframes created with Balsamiq Mockups
Note: Having a commonly available and easily editable document is key in making sure things remain up to date. I prefer something like Omnigraffle for this from the sense that you can have multiple pages within the doc for various screens, layers on a page for annotation vs mock, easy copying and pasting of images & text and quick export out to PDF for easy sharing. (There's probably other tools out there with similar functionalities)
