Skip to main content

Navigation

  • Client impact
  • Writing

AI Solutions

  • AI Systems
  • AI Development

Software teams

  • Design Systems
  • Product Design & Engineering
  • API Platforms
  • View all services for software teams
Get in touch
  • AI Systems

    Model-agnostic AI systems and agents that do real work

    AI Development

    Custom apps and tools built with AI-enabled engineering

  • Design Systems

    Depth of experience that few can match

    Product Design & Engineering

    Experts in cross-functional collaboration

    API Platforms

    Node.js, React, & GraphQL at scale


    View all services for software teams
  • Client impact
  • Writing
  • Contact

Method / Playbook · 4 min read

Functional wireframing

Functional wireframing documents how the various pages and interface elements of an app or website need to come together in order to support the user.

Prep time: 15 minutes · Duration: 3-10 days · Participants: 1-2

Introduction

Functional wireframes are an early representation of a digital product’s interface and communicate the key elements on any given screen. They are the blueprint for the functions, layout, and information hierarchy of the product.

The purpose of functional wireframes is to figure out the solutions to the higher-level questions of a product, including how it works and the logic by which it does so.

To enable the UX Designer to focus on these elements and avoid getting bogged down in the detail of the product, functional wireframes tend to avoid the use of colours, typography, images and other visual styling. The use of simple boxes and lines makes them quick and easy to create and edit.

People

Wireframes are created by the UX Designer.

Instructions

Preparation

Before you can begin wireframing it’s important to have a sense of the tasks a user needs to be able to complete with the product.

We usually undertake the process mapping and/or user journey mapping exercises ahead of time in order to clarify what functions the product should include. It’s also important to define the route map of your product so you have a sense of how a user will navigate from screen to screen.

Decide how you would like to generate the wireframes. Whimsical is out preferred tool for wireframing as it comes with a lot of readymade interface elements which we can use out of the box, but it can also be done in Figma or with pen and paper.

Method

  1. Select the feature you would like to start with and create a heading with a description underneath.

    1. E.g. Approvals - Managers can approve their team’s submitted timesheets which will lock them from being edited.
  2. Draw an outline as the border of the screen, considering whether the design is for desktop, mobile or tablet (some programs have screen templates which you can use).

  3. Add in the main navigation of the screen asking 'How would a user access the different features of this product'?.

  4. Referencing the process map, add elements that would enable a user to complete the tasks for that given feature. Ask yourself questions such as:

    • How can you organise the content to support your users’ goals?
    • Which information should be most prominent?
    • Where should your main message go?
    • What should the user see first when arriving at the page?
    • What will the user expect to see on certain areas of the page?
    • Which buttons or touch points does the user need to complete the desired actions?

    Remember that the focus is on functionality, not style.

    Use representative copy in your wireframes to get a better sense of how a user would see it.

  5. Play around with the layout, moving elements around and changing their size and prominence. Create multiple versions and compare them or get feedback from others.

  6. Create as many screens as you need to be able to communicate how a feature would work.

  7. Use arrows to connect different screen states, showing how a user would navigate from one screen to the next.

  8. Annotate the wireframes with questions or comments.

  9. Repeat this process until you have completed wireframes for the whole product.

  10. Share these with fellow designers and other stakeholders for feedback. The purpose of these wireframes is to get consensus on the functionality of the product, so it’s crucial that comments and questions from team members are taken into account at this stage.

Examples

The following images show a selection of functional wireframes for an accounting product annotated to document how things need to work.

A single page documenting how a user might add a row of data to a table (in this instance using a drawer modal).A single page documenting how a user might add a row of data to a table (in this instance using a drawer modal).

A single page documenting how a user might add a row of data to a table (in this instance using a drawer modal).

A series of wireframe pages documenting how a series of user actions come together to complete an activity.A series of wireframe pages documenting how a series of user actions come together to complete an activity.

A series of wireframe pages documenting how a series of user actions come together to complete an activity.

Chat to the following people to learn more about this play:

Lauren Argenta avatarLauren Argenta avatar
Lauren Argenta

Design director at Thinkmill. Loves wireframing, all things user research, and solving complex problems using design and engineering collaboration.

Giselle Stidston avatarGiselle Stidston avatar
Giselle Stidston

Designer who loves learning about new problem spaces. Knows how to solve cryptic crosswords and has a knack for expressing things as diagrams.

Get playbook updates

For updates on future playbook publications, subscribe to our newsletter.

Related plays

  • Activity Mapping

    Activity mapping is a way to dynamically capture, and work on, product requirements in a format that’s more useful than a static document.

    October 2024·3 min read
  • Process mapping

    Process mapping surfaces the movement of information and user interaction throughout a system in the form of a flowchart. It captures assumptions or current-state realities related to how the system works, and helps expedite alignment, design, and development,

    October 2024·2 min read
  • User journey mapping

    User journey mapping captures the steps a user takes to complete a specific task in the form of a flowchart. It surfaces assumptions about how the team expects a user to interact with the product, and highlights pain points and areas for improvement.

    October 2024·3 min read
  • Route mapping

    Route mapping is a process of co-designing a project‘s URL schema (and more) to define the UX and IA of a site or app.

    October 2024·1 min read

We’d love to work with you

Get in touch

Footer

Thinkmill is a member of the Tech Council of Australia(opens in new tab).

AI Solutions

  • AI Systems
  • AI Development

Software teams

  • Design Systems
  • Product Design & Engineering
  • API Platforms
  • View all software teams

Client impact

  • Lyka
  • ELMO
  • Tiimely
  • Atlassian
  • Reckon
  • AnywhereWorks
  • View all client impact

Open Source

  • Keystone (opens in new tab)
  • Keystatic (opens in new tab)
  • React Select (opens in new tab)
  • Classnames (opens in new tab)
  • Manypkg (opens in new tab)
  • Changesets (opens in new tab)