Skip to content
Hugh Berryman

Tribal Credit / Product design & leadership

Tribal Platform: one experience across web and mobile

The mobile platform: home, feature navigation, profile settings, and expanded company balances in one shared visual language.
The mobile platform: home, feature navigation, profile settings, and expanded company balances in one shared visual language.Open full-size image
Card management on the web, bringing card status, currencies, spending, limits, and available balances into a scannable list.
Card management on the web, bringing card status, currencies, spending, limits, and available balances into a scannable list.Open full-size image

As Tribal grew from Seed to Series B, my work expanded from designing and building the core product to leading the design team. The challenge stayed consistent: make cards, payments, and account management feel like one product across web and mobile, even as more designers worked on it.

Result

Delivered core web and mobile experiences, shipped Tribal Pay in React Native, and established Centro, the company design system, alongside a growing team of 10 product designers.

Year
2020–23
My scope
I joined as Tribal's first product-design hire, designed and shipped mobile experiences in React Native, and grew into Director of Product Design as the company scaled from Seed to Series B.
Role progression

  1. Product Designer & React Native Developer

    Jan 2020 – Mar 2021

  2. Senior Product Designer

    Mar 2021 – Mar 2022

  3. Director of Product Design

    Mar 2022 – Nov 2023

Collaborators
I grew and led a team of 10 product designers, partnering with product, marketing, and engineering while staying hands-on with the product and design system.

One product across different screens

I started with the core web and mobile experiences, including designing and shipping Tribal Pay in React Native and Expo. I built the early Figma system and brought its color foundation into the app codebase.

The platform needed a common language for balances, cards, transactions, and actions. The screens shown here carry that language across mobile navigation, web tables, and detailed card controls while giving each format the space it needs.

A card's detail view connects its balance and spending limit with management controls, tags, and transaction history.
A card's detail view connects its balance and spending limit with management controls, tags, and transaction history.Open full-size image

Shared standards for a growing product

As the product expanded, multiple designers needed to work on different flows without creating separate visual systems. I established guidelines and working processes that kept those contributions aligned and supported iterative review.

That work developed into Centro, the company design system. Shared patterns gave the team a foundation for experiences such as card management and bulk payments, where navigation, status, and next steps need to remain clear through a more involved task.

The bulk-payment flow after a recipient file is uploaded, with a preview separating uploaded transactions, duplicate recipients, and errors.
The bulk-payment flow after a recipient file is uploaded, with a preview separating uploaded transactions, duplicate recipients, and errors.Open full-size image

Growing the team with the platform

After the Series A and B rounds, my focus broadened to scaling the team and the processes around its work. I progressed through Senior Product Designer to Director of Product Design, leading 10 designers and partnering with product, marketing, and engineering.

My role connected hands-on product work with the conditions that let others contribute. Clear standards and a shared design system helped the team work concurrently across web and mobile while keeping the platform recognizable as Tribal.

The company dashboard pairs the billing period and available credit with transaction amounts, status, users, and attachments.
The company dashboard pairs the billing period and available credit with transaction amounts, status, users, and attachments.Open full-size image

◆Decisions

  1. The decision

    Carry a shared design language across web and mobile while adapting the layout to each platform.

    The tradeoff

    Consistency required agreement on common patterns while leaving room for mobile navigation and denser web workflows.

    The consequence

    Cards, payments, and account views share a visual foundation across the platform.

  2. The decision

    Invest in a shared design system and working processes as the design team grew.

    The tradeoff

    Maintaining the system and aligning contributions became part of the team's ongoing product work.

    The consequence

    Centro gave a team of 10 designers a common foundation for concurrent work across the product.

Product designDesign leadershipDesign systemsReact NativeMobileFintech