I try to solve a problem, I've encountered several times: the lack of a common communication basis while designing software. - a basis for PM, Project Manager, UX Designers, IA's and Visual Designers as well as Developers.
Sure there are Mockups, Sitemaps, UI Patterns, Lofi and Hifi-Wireframes, but still there occur translation errors. I believe this is due to the narrow view every project member has - which is great for problem solving, but bad for communication. I think, most problems pop up if a project moves a stage upward - the stages James Garret introduced - and new project members with different views enter. Then the documents made for the former stage need to be translated to the next stage (with the mentioned translation problems)
If one maps the common tools here, one will see that they focus on just one stage. Like a Lofi wireframe for the skeleton stage. Sitemap for structure stage. UI Patterns and Hifi Wireframes for the surface stage.
Do you know a kind of modelling/communication language, that spans across the stages?
or even just structure->skeleton and skeleton->surface.
- understood by non-designers
- tool independent (i.e. no InDesign or Photoshop)
- easy to maintain
- easy to learn
- simple and not to detailed
I like James Garret's A visual vocabulary for describing information architecture and interaction design for spanning structure and skeleton stage. For me, IFML and UML enforces the focus to deeply on technical apects, which I dislike. And the topic UI key dimensions and flow diagram is sound, but dedicated to one stage only.