Genesis One OS
Genesis One OS is a unified digital church platform connecting people, households, discipleship, giving, check in, content, and church operations in one ecosystem.
Role
- Product Owner
- UX/UI Designer
Focus
- Product Strategy
- UX Architecture
- Interaction Design
- UI
- Design Systems
The Challenge
The church was running on disconnected systems.
People, giving, events, check in, content, and discipleship lived across separate platforms.
The result was fragmented data, duplicated workflows, and disconnected experiences.
The opportunity was bigger than redesigning another application.
We needed to rethink the underlying digital ecosystem.
The Opportunity
One source. One truth. One platform.
Genesis One was designed as the digital foundation connecting the church’s core experiences.
Instead of forcing people to navigate systems, the system would work around people, relationships, and journeys.
My Role
I helped define Genesis One from product vision through experience design.
- 01
Product Strategy
Defined product direction, priorities, and capabilities.
- 02
UX Architecture
Created information architecture, workflows, and journeys.
- 03
Product Design
Designed interactions, interfaces, and core experiences.
- 04
Design Systems
Created reusable patterns for a scalable product.
- 05
Product Collaboration
Worked closely with engineering and leadership to turn concepts into a working platform.
Experience Architecture
From features to journeys.
Discover → Connect → Grow → Serve → Lead
Genesis One treats discipleship as a connected journey rather than a collection of isolated activities.
People, households, relationships, content, events, giving, and engagement all contribute to the larger experience.
Design System
One product language.
A reusable design system establishes consistent typography, spacing, components, navigation, states, and interaction patterns across the platform.
The goal:
Consistency for users. Speed for the product team. Scalability for the platform.
From Design to Product
Genesis One was designed alongside engineering.
Technical feasibility, data relationships, permissions, responsive behavior, component reuse, and scalability were considered throughout the design process.
The goal wasn’t to create a beautiful prototype.
It was to create a product that could actually scale.
TL;DR
- PROBLEM
- Disconnected church technology.
- ROLE
- Product Owner · UX/UI Designer.
- SOLUTION
- A unified digital church operating system.
- IMPACT
- A scalable foundation connecting people, data, journeys, and experiences for a 25,000 member church ecosystem.
- SKILLS
- Product Strategy · UX · Systems Thinking · Interaction Design · UI · Design Systems