Wireframes and Process

The Customer Experience Team recently defined the key elements a wireframe should clarify:

- placement of the visual items

- weight (= importance)

- focus (balance between user need and business need)

- only what is useful, not what is beautiful

- interaction

- "this is not the final design" disclaimer

- placeholders instead of real images or real text (unless in really needed)

- squared boxes, rounded buttons

- background yes (if needed), gradient no

Wireframe (static)
Prototype (interactive)
Lo-Fi (not too detailed)
Hi-Fi (very detailed)

As UXers we decide what is better to work on, depending on the project and on the available time (in agreement with the project manager)


Moreover:

Skeletons are more for developers, they'll build the HTML template

Wireframes are more for designers, they'll look at them as "brief" or "requirements"

Wireframes should have a versioning system (to make sure we circulate the latest version)

The UX people will check the Designers deliverables in order to make sure the wireframes were well interpreted. In case not, we should improve this process.