KEVIN KEIPERkevin@kevinkeiper.com415 926 1935PRESENTATION PDFRESUMELINKEDIN
Home
Select Success Study

Principal Design System Architect

Brightplan
Mar 2016
Mar 2018

STORY BACKGROUND CONTEXT

Brightplan is a financial wellness and planning tool, which was developing and designing a proof of concept mvp, and needed a comprehensive style guide to ensure build quality and future scaling consistency.

PROJECT OPPORTUNITIES

Deploy browser based and native app to enable investment funding and management.

Create a style guide supporting mvp and ensure future scalability and consistency.

Grow assets under management to $250mm and subsequently at 20% annually.

THE SHITSHOW

GOALS AT A GLANCE

  • Build new account base
  • Create strategic relationships
  • Increase average ROI
  • Improve design execution
  • 30%
  • 15%
  • 25%
  • 30%

TEAM

  • Head of Product
  • Developer

PROJECT TOOLS + SKILLS

  • Figma
  • Sketch
  • Profit Strategy
  • Journey Maps
  • UX Qualitative Research

DESIGN RESEARCH PROCESS

I Led Product team first through qualitative discovery including personae, journey maps, and early product brainstorming sessions.

‍

Working with associated business partner, we conducted exhaustive product feature discovery based on a thorough evaluation of investor sentiments, feelings, desired goals and current investing pain points.

I led senior product team through investment journey discovery sessions to determine 'nice to have', essential and 'blue sky' feature sets.

DESIGN EXECUTION PROCESS

After qualitative white-boarding sessions, I created an experience map tailored to new account conversions and building long term customer relationships.

After completing the beautiful and effective journey map I moved into some designs specifically to determine component level objects.

‍

These were expertly crafted to highest expectations, and were reviewed continually by CEO and senior product and engineering staff.

‍

All designs were tailored from the start to derive the required set of scalable components from which the final products would be built.

Both desktop and mobile versions were considered, to meet needs of either administrators or users of the app on mobile devices.

Drafting these assets was key to completing the final set of style guide specifications as required.

The style guide was anticipated by engineering to achieve brand cohesion, reduction of engineering development levels of effort and future UI bugs.

Finalizing the native mobile and desktop versions of the MVP app contributed the production of the unifying style guide.

‍

Only after creating a cohesive brand experience between all customer touch points was the ultimate goal of creating a style guide possible, sample page shown but full pdf is available.

Creating and more importantly adopting the style guide was instrumental in aligning all future customer engagement and product strategies, and enabled faster iteration to production engineering cycles.

‍

Sample page shown but full pdf is available.

SUCCESSFUL OUTCOME SUMMARY

PROJECT ASSETS

New customer accounts added

New strategic partners

Improve Product & Engineering efficiency

Improve investor account ROI

  • 30%
  • 15%
  • 25%
  • 30%
KEVIN KEIPERkevin@kevinkeiper.com415 926 1935PRESENTATION PDFRESUMELINKED IN