As an IX-focused designer, creating wireframe flows is one of my most often used skills. They obviously can be used by engineers as guides for wiring up and connecting screens as well as by other disciplines to make certain the the designs are being followed correctly. Often in the creation of flows it becomes apparent where further flows are needed to cover “unhappy paths” — those points where the primary journey is interrupted and the user needs an alternate path.

The wireframe screens that make up the flows are intentionally presented differently than a screen layout or mockup would be. The purpose of this is to help signal to reviewers what type of feedback is appropriate at this stage. By mainly displaying the inventory of a screen (what items are present) while minimizing visual effects (color, typography, iconography) and even hierarchy, the team gets a good representation of the experience being built without being distracted by the look of the screen. Wireframes can also inform the requirements for a design language in a new project by showing common elements, unique elements and a rough idea of content design.