Kikoff

Overview

Kikoff helps users build credit through two products: Credit Account and Credit Builder Loan. There are real consequences here: a missed payment hurts the very score they're trying to build.

I was brought in to rethink the dashboards for both products across iOS and responsive web. The goal wasn't just making the screens look nicer. The goal is behavioral: help users understand where they stood, reduce confusion around how credit works, and get more of them making payments successfully.

Strategic Frame

The dashboards were account summaries when they needed to be progress tools.

Users weren't missing payments because they didn't care. The dashboard didn’t do a great job of telling them what was due, when, or why it mattered. CS volume was high, autopay adoption was low, and users didn’t know how Kikoff was actually helping their credit.

Problem 1 — Payment status was hard to find and harder to act on

The most important thing on a credit dashboard is seeing your next payment. That wasn't visible.

Due dates and payment amounts were mixed in with extraneous info. Autopay status wasn't prominent enough to prompt action. What followed were missed payments and preventable CS contacts.

I rebuilt the payment module around the user’s next payment—amount, due date, autopay status on load. Each state got its own messaging: autopay on, autopay off, due soon, overdue, autopay failure. That way there is always clarity around what's happening and what to do.

Problem 2 — Users couldn't see their progress

Credit building is slow and invisible. The dashboard wasn't helping.

Kikoff's value is building a consistent history of payments over time—but the original dashboard did not make any of that tangible. No sense of progress, no reinforcement that anything was working.

I introduced payment streaks and visually highlighted successful payments. Showing here's what you've done, here's what is working, here’s what to do next. Turning a financial obligation into a moment of emotion in order to communicate progress.

Problem 3 — Two products, two inconsistent experiences

Credit Account and Credit Builder Loan had drifted apart. Users managing both were navigating two different mental models.

The redesign brought them both into similar layouts with consistent interaction patterns. Less cognitive load for users holding both products—and a design structure that could absorb future additions without starting over.

Impact

The payment module went from one ambiguous view to five states, each with its own status, messaging, and next steps. Streaks made an arduous process visible between payments. Both products moved onto a shared structure, so users holding both stopped navigating two mental models.

Designs went to product and engineering and my contract ended before it shipped. The measure that would have mattered is autopay adoption, and I never saw it.

Reflection

A missed payment on a credit-building product is the opposite of what the user came for. Good dashboard design in this context isn't necessarily about engagement, rather, it's about making the right action consistently obvious at the right time. That ended up being a much harder and more constrained problem than I had anticipated.