JONA LAINEZ

Case Study · 2026

OBA — Ortus Branding Assets

Designed and structured a centralized branding asset system to standardize distribution, improve consistency, and enable scalable usage across teams and products.

Early version

Visual demo coming soon

This project is actively evolving. Visual walkthroughs, live demos, and supporting materials will be added soon.

Detailed visuals available upon request.

Role

Product DesignDesign SystemsFront-End

Timeline

2026

Stack

FigmaDesign SystemsFile Architecture

Overview

OBA (Ortus Branding Assets) is a centralized system designed to organize, standardize, and distribute branding assets across Ortus products and teams.

The project focused on transforming scattered design resources into a structured system that supports consistent usage and scalable access.

Problem

Branding assets were distributed across multiple locations without a clear system, making it difficult for teams to find, use, and maintain consistency.

This resulted in:

  • Inconsistent usage of logos, colors, and visual elements
  • Time loss searching for correct or updated assets
  • Duplication and outdated files across teams
  • Lack of a single source of truth for brand resources

Role

I designed and structured the system, focusing on how branding assets are organized, accessed, and used across teams.

My role included defining asset architecture, naming conventions, and usage patterns to ensure consistency and scalability.

Approach

I approached the project as a design system for assets, focusing on structure, clarity, and long-term maintainability.

  • Defined clear categorization of assets by type and usage
  • Standardized naming conventions for predictability
  • Structured assets to support both designers and developers
  • Designed the system to scale with new products and brands

The goal was to create a single source of truth for branding assets.

Key Decisions

  • Centralized all assets into a single structured repository.
  • Defined consistent naming conventions to reduce ambiguity and duplication.
  • Organized assets by brand, type, and usage context.
  • Ensured assets were accessible and usable across different workflows (design, development, marketing).
  • Structured the system to support future expansion without breaking consistency.

Technical Implementation

Implemented a structured repository architecture to manage assets:

  • Organized directories by brand and asset type
  • Standardized file formats and naming conventions
  • Ensured compatibility with both design tools and development workflows
  • Maintained version control to track changes and updates

The system enables reliable access and consistent usage across teams.

Outcome / Impact

Established a single source of truth for branding assets, enabling:

  • Faster access to correct and updated assets
  • Improved consistency across products and teams
  • Reduced duplication and outdated resources
  • A scalable foundation for future brand and product growth

Learnings

Even simple systems like asset libraries benefit from design system thinking.

Structuring how assets are organized and consumed has a direct impact on team efficiency, consistency, and long-term scalability.