Recently, someone asked me about wireframes. In short, wireframes are a low-cost, quick way to rough out the architecture of web sites, structured documents, document sets, training courseware, marketing collateral, web-based applications, and systems. Some other buzz words that may be used interchangeably (though not always correctly) with "wireframe" are low-fidelity mockup or rendering, schematic, page architecture, template, diagram, blueprint, or zone diagram. Grey model and story board also are used sometimes for procedure and task sequence mockups.
Wireframe techniques work for any sort of structured content. Think outline, but better. Wireframes can be used to convey many different aspects of architecture, but the data most often captured in wireframes are:
- Content at a high level
- Relationships among content
- Structure of content (innate hierarchy)
- Structure of relationships (structured hierarchy for presentation)
- Navigation and flow
Creating, reviewing, and amending wireframes does add work to a project. However, early (and frequent) wireframing and approval up front generally will save hours, if not days or weeks, of rework later. Wireframes can be created using a variety of tools, including PowerPoint, Word, Excel, FrameMaker, Visio, and custom tools provided for use with a particular development application.
One last thought: Don't mistake simple wireframes for simplistic ones. Some of the simplest wireframes are the most powerful. A simple and quick wireframe set can provide an early snapshot of a project's architecture, when it is still relatively easy and inexpensive to make changes. A widely-available tool (like PowerPoint) is accessible to almost everyone, everywhere, making it easy to distribute and review a set of wireframes. Distributing wireframes in PDFs or another universal format is also an alternative, and may enable the IA to use a custom wireframing tool.
No comments:
Post a Comment