Down

Accounting for small business

Reckon creates cloud-based accounting applications for bookkeepers, small to medium businesses, accountants, and personal users. The rapid development of their latest generation software had resulted in a design system which had numerous issues.

RESEARCH

Understanding the issues

To supplement the existing research a series of interviews were initiated with members of the design team, development team, stakeholders, support staff, and users to better understand their problems.

“I feel like I’m spending a lot of time fighting these components to get them to do what I want”
- Interview feedback from a product designer within our team
“why are we missing so may  mobile components compared to the web kit?”
- Interview feedback from a product designer within our team
“Much of the app feels very clunky.”
- Customer survey feedback from a Book keeper
“I don’t like the look and feel of the product. If I change it won’t be to Reckon.”
- Customer survey feedback from an Accountant
There were many UX/UI issues negatively affecting the overall experience of our product, many of those issues could be traced back to patterns, rules and components within the design system.

These problems had knock on effects to our products usability, readability, accessibility and even scalability.
The build quality of Figma components in many cases was sub standard, resulting in issues such as configuration props being hidden down multiple levels that a designer needed to ‘click into’ in order to adjust.

The issue trickled down to the development team where they were required to do the same thing in order to inspect components.
Designers working on our native mobile apps were frustrated in the lack of components and overall maintenance of the mobile component library.

There were also inconsistencies in naming conventions with several components that existed within both libraries having different names, resulting in confusion within the team.
Users felt that the overall look and feel of Reckon was of low quality.

There was also confusion as to why our products lacked any connection to Reckon’s brand / tone of voice.

Archetypes

Two archetypes were developed that were a reflection of the two main user groups that interact with our design system.

Consumers

Designers and Developers at Reckon
Goals
  • Understand users and meet their needs
  • Experiment rapidly
  • Meet company goals
Frustrations
  • Quality of Figma components
  • No templates (building from scratch wastes time)
  • Finding the right component
  • Mobile library quality

Users

Bookkeepers and Accountants
Goals
  • Happy clients
  • Accurate data
  • Business growth
Frustrations
  • Overcomplicated work flows
  • Fixing client errors
  • Lack of responsive design
  • Quality of design

After interviews, audits, and testing...

we had a good understanding of the problems we faced and who they were impacting.

Planning next steps

Working with stakeholders, a roadmap was proposed to address these issues. One which left available capacity for the design system team to support the product team in creating any component or pattern updates required for any other initiatives.

Phase 1

The goal of Phase 1 was to quickly resolve problems effecting team efficiency and user issues critical to core functionality.

  • Figma components review and rebuild
  • Figma templates
  • Balance governance
  • Forms/data entry initiative
Phase 2

The goal of Phase 2 was to design a new theming system and align our look and feel with the company brand.

  • Aligning Balance with brand/marketing
  • Design of a new colour system
Phase 3

In Phase 3 the design token system was to be built and implemented to all components as well as updates to the mobile library.

  • Implementation of tokens to 
all components
  • Typography tokens
  • Mobile library parity with desktop

PHASE 1

Immediate action

Quick actions were required to give relief to the design and development teams while addressing critical user experience issues.

Rebuilt components
Components were rebuilt in order to surface configuration options in a direct and easy-to-use format for the design team. Not only did these changes improve efficiency within the design team, it also improved build quality as these changes also made it easier for the development team to inspect component values.
Interaction states
Our Figma file lacked all the necessary interaction states that were supposed to be included. By incorporating these states and prototyping interactions, we were able to enhance our testing process and generate more realistic results.
Templates
Templates were missing in Balance, which meant the design team had to start from scratch when creating navigation bars, drawings, menus, and other elements. Taking inspiration from Atlassian's design system, templates were created for commonly used recipes that includes component notes telling the consumers if it is ok to detach/modify the template.

Improving processes

Proper governance of the design system needed to be established. 
A full process for new components or variables was created with the design and development team.

Improving core functionality

Data entry plays a vital role within Reckon's product suite. 
A review and update of the form UI/UX aimed to address user pain points and improve overall experience of our products.

Testing our form patterns and components

Two separate rounds of user testing were held, looking at solutions to solve the following user pain points:

  • Current design of inputs with a grey background made it very hard to distinguish between an active state and disabled state.
  • Placeholder text failed WCAG accessibility criteria (colour contrast)
  • Mandatory use of placeholder text made it difficult for a user to tell what fields have been filled in, and often provided minimal information to the user.
  • Spacing of input fields wasn’t consistent and often very tight, impacting usability.
  • Several components had overlapping functionality, causing an inconsistent experience.
  • There was no consistent pattern for adding groups of information.
  • The ‘Wizard’ form template had numerous issues such as: not being able to go back to a previous step, scalability of design (steps being run along the top of the template allowed for only 4-5 steps) which could lead to overly long form pages, and overall inconsistent user experience.

Outcomes

Form components
The new input designs that addressed user pain points were well-received, and new rules were implemented to remove placeholder text and define spacing.

Also, several new components were added to Balance including ‘Button groups’ (a easily tapable way to visualise a simple choice) and the ‘Array field’ (a form input for capturing multiple instances of multiple fields).
Wizard
A new scalable wizard template was designed to guide users through the creation process, simplifying steps by reducing the amount of actions on each page and added the ability to add sub-steps to the flow.

The previous wizard was a common inclusion in the edit pattern. The rules have recently undergone an update in order to discontinue the usage of this pattern, and as a result, new edit patterns were  designed.
Component consolidation
There were many near visually identical components and/or overlapping functionality, as well as components with names differing from what a consumer would expect. This was causing unnecessary time for the design team, inconsistency in build and causing confusion for our users.

Time was dedicated  to redesign (or remove) these components to have a clear, unique purpose.

PHASE 2

Theming: Evolution of our system

In this initiative the main goal was to fix Balance’s broken theming layer that was impacting our scalability. Other anticipated benefits were improvements in alignment with design and code, efficiency, accessibility, and experience.

Project principles

The development of these value statements framed design decisions, supporting consistency in decision making.
Scalability
The theming solution should be scalable and flexible in design, allowing the system to adapt to different styling options.
Alignment between design and development
Aim to ensure a seamless bridge between the visual experience crafted by designers and the underlying functionality built by developers.
Remove friction, optimise efficiency
Choosing the right tokens should be easy and intuitive.
The theming solution should be scalable and flexible in design, allowing the system to adapt to different styling options.
Aim to ensure a seamless bridge between the visual experience crafted by designers and the underlying functionality built by developers.
Choosing the right tokens should be easy and intuitive.

Aligning with Brand & Marketing

In the initial creation of Balance, Reckon’s branding was completely overlooked. This lead to user feedback that expressed their confusion in our products.

I worked with the Marketing team during a major brand update to ensure that the colours were accessible and to restyle Balance with this updated aesthetic.

Changes to some components and templates were made to better match the overall aesthetic of the brand. This included removing excess dividers, rounding corners, and a redesign of Balance’s typestack.

Spacing

The consistent implementation of spacing has long been a issue at Reckon. The development team use ‘T-shirt sizing’ to specify spacing value, while the design team could only specify these values numerically.

The addition and use of design tokens solves this frequent DQA issue.

Colour

On top of adding a secondary action colour to our visual language, an entirely new colour system called HCT (which stands for hue, chroma, and tone) was adopted.

Keeping within the parameter of this system we can be sure that our colours will always meet accessibility contrast standards.

Typography

Font use was not consistent with documentation supplied by our marketing and brand team. To rectify this ‘Figtree Bold’ was implemented as the font for heading classes, with the exception of ‘Figtree Extra Bold’ being used for text used on buttons.

‘Open Sans’ was implemented as the body copy font.

PHASE 3

Theming: Design tokens & mobile

Our new brand updates, colour system, were all implemented as Design Tokens in order to facilitate a centralised ‘source of truth’ of all style values across all platforms.

The original plan

The original file structure featured 2 separate component libraries - one for web components the other for native mobile components. The intention was to create a third library that would be used for our colour, spacing, radius, and effects, design tokens.

A simpler approach

However in early testing it was discovered that with the three file approach it would not be possible to take advantage of Figma’s ‘scoping’ feature - forcing all 1500+ token values to be visible to consumers.

To limit the number of tokens visible to consumers, the libraries were combined into a single file. Additionally the ability to only show tokens in specific instances was implemented (for instance text colour tokens can only be applied to text) which has increased efficiency and removed a point of error.

Structured for flexibility

This is how Balance’s design token system has been structured.

A fully responsive system

With the implementation of our token system, in particular the ‘Device’ collection all type styles and components are now fully responsive across mobile and desktop.

Balance 2.0 released

With the completion of the theming initiative the newly evolved Balance was finally ready to launch.

Outcomes & next steps

The improvements to Balance have been a massive success that has seen:

  • 2-3x efficiency gain within the design team
  • Increased design consistency across our products and brand
  • An increase in form completion rates
  • Big uplift to the user experience by improving design quality
  • Decrease in QA time

Moving into the future we plan to create a more robust documentation platform to help ensure consistency, and further increase efficiency of our team.

Figma

Balance design system has been built in Figma.

Feel free to take a look!
Take a look

Other projects