PWI Software Documentation Help

Wireframing Process

1. Sketches

What's on it:

  • Outlined boxes

  • Placeholder boxes to represent images, text, and graphics

  • Can be done in low, mid, or high fidelity depending on project needs

Purpose:

  • To start the conversation about design needs and layout

  • Helps clarify and define features needed and change ideas quickly

  • Helps visualize how screens might look on different device sizes and in different contexts

2. Wireframes/Gray-Boxing

What's on it:

  • Filler content (Lorem ipsum or actual text, which is highly recommended)

  • Placeholder images or stock images

  • Usually created using design software with an existing wireframing UI kit or from scratch

Purpose:

  • Visualize the general layout

  • Establish correct proportions

  • Build trust with stakeholders by presenting a more fleshed-out idea

  • Fast and cost-effective way to create initial ideas or low-fidelity prototypes

3. Component Design

What's on it:

  • UI kits

  • Symbols (buttons, badges)

  • Element states (hover state, clicked state)

  • Components (tables, lists, cards, forms)

  • Actual text

Purpose:

  • Discover and address usability issues

  • Uncover accessibility and responsive problems

  • Translate ideas into consistent elements that can be shared with engineers and discussed across teams

4. User Flows and Task Flows

What's on it:

  • Wireframes

  • Flow charts

  • Wireflows

  • Arrows

  • Conditionals

Purpose:

  • Show navigation routes

  • Check for missing states and information

  • Visualize entry, exit, and decision points for the user/customer journey

5. High-Fidelity Designs

What's on it:

  • Shows exactly how things will appear in the final product

Purpose:

  • Create pixel perfection

  • Ensure visual design consistency

  • Add a sense of brand identity

  • Select final design assets

  • Obtain final approval from stakeholders

6. Prototype

What's on it:

  • All screens in high-fidelity

  • Target points to mimic user interactions with the real product

Purpose:

  • Link together all screens and flows in a simulated environment

  • Ensure everything looks good, works well, and flows as intended before production

  • Considered the pre-code or no-code version of the product

17 May 2024