Wireframes. UX professionals are quite used to and comfortable creating these, however annotating meaningfully is still a major challenge for many. This is extremely valuable when the development team is not a few feet away. In my context, they are thousand of miles away in other countries.
Now, I love to tell stories about how everything connects in the world, but a developer who has a deadline has no time for this, maybe after work in a pub. Learning how to write useful annotations has been under the guidance of very helpful ‘bosses’ who would edit my work, and we would extract what was most valuable depending on the audience or context.
Things to be mindful of;
1. The Audience - Who am I communicating to? What do they need the wireframes for? Some questions to ask yourself. One good rule is to drop technical speech and describe things in the plainest way possible, in a language that most can understand.
2. The Use - Currently some of my wireframe documents double as a technical documentation for developers, so there’s a lot of revision being done constantly. These updates are necessary and very helpful especially when a new developer or designer takes over a task. You should be prepared to make any change and keep a note of it.
I started to think about how to make annotations work harder after an issue that made me point the developers to a particular implementation solution which was done via email. I thought I would have saved everyone’s time if I had just put this in the wireframes. So annotations go from just describing the interaction but also suggesting possible ways to implement the interactions. Even if they cannot build it that way due to one reason (technical constraints, time limit, low resource ) or the other, It creates an open and collaborative environment where everyone learns to help each other out.
An example would be a scenario where you want replicate the Amazon flyout menu. You can describe it, but it would be useful if you can point them to an implementation method like Ben Kamens’s breakdown