Introduction

EXPERTISE

UX Design
UI Design
Visual Design

PLATFORMS

Responsive Web
Our users were more than just the people we made OST for, they were our partners in the design process.
Online Share Trading
Shortly after joining Standard Bank Wealth team I began work on the next evolution of Online Share Trading web.

Design challenge: Offer investing services to different audiences; Long-term traders, Expert traders and New to trading.

Team challenge: Build trust between the design and development team.

Goals: Redesign Online Share Trading web platform to create a simple, intuitive, and memorable experience. Allow users to easily understand the product and buy into the product to reach their personal trading goals.
Interactive Dashboard
Portfolio
Market Overview
Quick Trade
Watchlist
Transact

Whose responsibility is it anyway?

You don’t necessarily need to understand how to code, it’s more important to understand the people who do.
The major problem I noticed after joining the team was lots of blame shifting between the designers and developers therefor there was no trust in the team. Without trust the team was dysfunctional and unproductive. I started by doing a quick simple exercise with the entire team to understand who’s responsible and accountable for curtain tasks and who needs to be consulted and informed.
Big things happened after RACI:
  • The aesthetics and behaviour of the end product is the developer’s responsibility. But they can’t do it without a designer. 
  • Re-usable components are the designer’s responsibility. But a designer can’t do it without the developer.
  • Visual QA became incremental and organic. Developer needed the designer to meet their new responsibility.
  • Zeplin (handover software) became a starting point to get pixels on the screen, from there the process is a combined effort. 
  • Developers took more ownership ofthe aesthetic and functional part of the project.

Interface Inventory

The project underwent three major UI redesigns before I joined, therefor there were loads of inconsistencies and legacy before the project even went live. So, I spent a day or two and took stock and categorised all the components and layouts that made up the interface, that basically means I went on a Screen grab frenzy.
Suggestions made were based on:
Find-ability
Interactions(e.g. states)
Scan-ability / Clarity of communication
Responsiveness
Learn-ability
Overall aesthetics
Example of the interface inventory
Big things happened after the UI Inventory:
  • The UI inventory became a checklist and was completed within 2 weeks.
  • Developers had the opportunity to raise UI issues and enhancements they wanted to make to improve the site’s usability as well as aesthetics.
  • A new culture was established. Developers were part of the design process from that day forward. It was a clean slate for us all.
Some of the suggestions made per component or element

Weekly sticky sessions

We needed a way to be more transparent about our design process, for developers, business analysts, business owners, co-designers and anyone who wants to see our work at least once a week. This was an informal session where colleagues get to stand around your work (usually printed out and stuck up on the wall) discuss it, understand it, raise concerns or share ideas.
Your work is just as good as the amount of people you share it with at any given stage of your process. Everyone has ideas, it’s your job as a designer to give someone else the platform to share those ideas. Ideas are not limited to a role.
If you are lucky enough to be working with motivated and engaged team members, you might realise that the design process is a journey you need to take the entire team on, not just the design team. This will add value to your design as well as create a shared understanding of the deliverable before the sprint has even started.


Big things happened when we started doing Sticky sessions:
  • Story kick off became incremental. The developer knew exactly how you want a design to look, feel and behave by the time they get to actually writing code.
  • Developers took ownership of design because they were part of the design process.
  • It only takes 15min a week so no complaining about more meetings.
  • It’s a good way to make sure that your work is always on display. Transparency and keeping everyone informed became a culture.
  • IT’S FUN!
Very first sticky session for the OST Web team. Some great minds looking at Watchlists.
Get in touch

Let's work together.

Describe your project and leave your contact info, I’ll get back to you within 24 hours.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Contact me
Marli Terblanche
I am based in Stellenbosch, but connected world wide through technology.

082 839 3375cmd.marli@gmail.com