• Webapp
  • New feature
  • UI design
  • user test

Diagram

Integrating an interactive diagram tool into the Siteflow platform

Mockups of the Siteflow diagram tool on a laptop and a monitor
Role
UI Designer
UI Design, User Testing, User research and specification
Timeline
Apr 2024
Design, user testing and technical specification
Team
Product
1 UI Designer, Development team, 1 Product Manager
Client / Scope
Siteflow
New interactive diagram feature

01 / THE PROBLEM

A lack of visibility slowing down field operations

Siteflow users map out their field operations as flowcharts in Visio (Microsoft software). They wanted a similar whiteboard built right into Siteflow, so they could import the flows they create and bring them into an interactive diagram.

This fragmented workflow creates a lack of visibility, leading to errors in the field and wasted time. Users have to switch back and forth between the flow view and the diagram view, or build an overview outside Siteflow.

7 out of 8: Drag & drop confusion

Testers instinctively clicked to add an element instead of using drag & drop during user testing.

02 / GOALS

Defining the product success criteria

01

Grow ARR

Offer a high-value feature to grow annual recurring revenue.

Target KPI

Recurring revenue growth

02

Customer Satisfaction

Improve the user experience by building diagram tools directly into the platform.

Target KPI

Less switching between tools

03

Ergonomic Clarity

Provide a clear, intuitive interface for creating and editing diagrams.

Target KPI

Intuitive navigation validated by testing

03 / RESEARCH & USER TESTING

Understanding the needs of methods planners

We ran user tests to choose the better of two navigation designs. 8 participants interacted with one of the two prototypes.

8 User Tests

Comparative tests on two navigation prototypes

2 Prototypes Tested

Single navigation vs. split navigation

Key Findings

Drag & drop confusion

7 out of 8 testers instinctively clicked instead of using drag & drop to add an element to the workspace.

Split navigation preferred

6 out of 8 testers preferred the interface with creation buttons separated from action icons, for greater clarity.

Icons need to stand apart

Half of the testers struggled to tell apart the duplicate, group and ungroup icons in the toolbar.

04 / PERSONA

Designing for methods planners

Thomas, 42

Methods Planner

Industry • Methods lead • Uses Visio daily

“I want to organise my operations and see the links and dependencies between them directly in Siteflow, without going through an external tool.”

Goals

  • Organise field operations in a clear diagram
  • See the links and dependencies between flows

Pain points

  • Lack of visibility causing errors in the field
  • Having to build an overview outside Siteflow

Sophie, 35

Field Project Manager

Construction • Coordinator • Manages several teams

“I need to edit my flow and phase cards right in the diagram, without switching back and forth between views.”

Goals

  • Prioritise and edit flow cards within the diagram
  • Bring in Siteflow elements without switching tools

Pain points

  • Moving cards manually between views
  • Time wasted switching between tools

05 / USER FLOW

Structuring the diagram creation journey

To reduce friction, we designed a direct flow that lets users create and edit their diagram while seamlessly bringing in Siteflow elements.

  1. Step 1

    Create a diagram

    New diagram view

  2. Step 2

    Add elements

    Drag & drop from the sidebar

  3. Step 3

    Edit the cards

    Change text, colours and shapes

  4. Step 4

    Group elements

    Organise into named groups

  5. Step 5

    Connect the flows

    Add links and dependencies

06 / WIREFRAMES & ITERATIONS

Iterative prototyping to find the best navigation

We experimented with two distinct navigation frameworks to identify the most intuitive interface for creating diagrams.

Prototype v1: single navigation

v1 – Single navigation

All actions (creating and editing) in a single bar. Testers asked for the icons right next to the elements they were editing.

Prototype v2: split navigation

v2 – Split navigation

Creation buttons on one side, action icons on the other. Easier to read, with different kinds of actions visually separated.

Final choice: split navigation

Final Choice – Split navigation

6 out of 8 testers preferred this version. Separating creation and editing actions makes the interface clearer and more intuitive.

07 / FINAL UI

Siteflow Diagram: the built-in visualisation tool

A clear, intuitive interface designed to fit naturally into methods planners’ existing workflow.

Diagram workspace

01 / Workspace

Main diagram view with an elements sidebar, an action bar and an interactive canvas.

02 / Editing elements

Contextual editing palette to change the colours, outlines and text of diagram shapes.

Shape editing palette
Groups and connections between flows

03 / Groups and connections

Elements organised into named groups, with dependency links between flows and phases.

08 / TECHNICAL CONSTRAINT

Working with the GoJS library

With limited time and resources, we used the GoJS library to build the diagram whiteboard in Siteflow. Some components still needed a custom UI.

Flow/phase/step cards

Flow, phase and step cards

Creation nav bar

Creation nav bar: shapes, text, connector

Action icon nav bar

Action icon bar

09 / RESULTS

Feature shipped and validated

6/8

Prefer split navigation

User test result

75%

Success rate

Of tasks completed on the first try

50%

Of testers would like

keyboard shortcuts

10 / LEARNINGS

What I took away from this project

  1. 01

    Drag & drop needs alternatives

    Testing showed that drag & drop isn’t intuitive for everyone.
    Offering alternatives such as click or double-click is essential to keep the interface accessible.

  2. 02

    Separating types of actions

    Creating and editing are different kinds of actions.
    Separating them visually adds clarity and reduces confusion, as 6 out of 8 testers confirmed.

  3. 03

    Working within technical constraints

    Having to use the GoJS library required close collaboration with the developers
    to adapt the design to what was technically possible while keeping a good UX.