NAVIGATE
Case Study
Case Study
Case Study
/
/
/
Founding Product Designer
Founding Product Designer
Founding Product Designer
/
/
/
June 2025 — Present
June 2025 — Present
June 2025 — Present
ORIGIN
ORIGIN
ORIGIN
STUDIO
STUDIO
STUDIO
STATUS
Live . Early Beta
DOMAIN
originx.studio
ROLE
Founding Product Designer
ROLE
Founding Product Designer
COMPANY
Aniflixx
COMPANY
Aniflixx
STATUS
Live . Early Beta
DOMAIN
originx.studio
//
//
//
//
01
01
01
01
OVERVIEW
OVERVIEW
OVERVIEW
OVERVIEW
THE BRIEF
THE BRIEF
THE BRIEF
WHAT IS ORIGINX
OriginX is a Studio OS: a unified operating system for professional animation, VFX, and manga studios. It replaces the fragmented stack of Slack, spreadsheets, Dropbox, and disconnected tools with a single, purpose-built platform that spans the entire production lifecycle.
WHAT IS ORIGINX
OriginX is a Studio OS: a unified operating system for professional animation, VFX, and manga studios. It replaces the fragmented stack of Slack, Dropbox, spreadsheets and disconnected tools with a single, purpose-built platform that spans the entire production lifecycle.
WHAT IS ORIGINX
OriginX is a Studio OS: a unified operating system for professional animation, VFX, and manga studios. It replaces the fragmented stack of Slack, Dropbox, spreadsheets and disconnected tools with a single, purpose-built platform that spans the entire production lifecycle.
WHAT IS ORIGINX
OriginX is a Studio OS: a unified operating system for professional animation, VFX, and manga studios. It replaces the fragmented stack of Slack, Dropbox, spreadsheets and disconnected tools with a single, purpose-built platform that spans the entire production lifecycle.
THE CORE INNOVATION
At the center of OriginX is Flixxi – an in-house generative AI that reads a single natural-language project brief and architects a complete production pipeline, from asset ingestion to final compositing, in seconds.
THE CORE INNOVATION
At the center of OriginX is Flixxi – an in-house generative AI that reads a single natural-language project brief and architects a complete production pipeline, from asset ingestion to final compositing, in seconds.
THE CORE INNOVATION
At the center of OriginX is Flixxi – an in-house generative AI that reads a single natural-language project brief and architects a complete production pipeline, from asset ingestion to final compositing, in seconds.
THE CHALLENGE
How do you design for expert creative leads, directors, producers, VFX supervisors who demand both AI-speed automation and total granular control? The system had to earn trust without sacrificing power.
THE CHALLENGE
How do you design for expert creative leads, directors, producers, VFX supervisors who demand both AI-speed automation and total granular control? The system had to earn trust without sacrificing power.
THE CHALLENGE
How do you design for expert creative leads, directors, producers, VFX supervisors who demand both AI-speed automation and total granular control? The system had to earn trust without sacrificing power.
MY SCOPE
End-to-end product design from zero.
User Research
Information Architecture
Interaction Design
Visual Design
Flixxi AI UX
MY SCOPE
End-to-end product design from zero.
User Research
Information Architecture
Interaction Design
Visual Design
Flixxi AI UX
MY SCOPE
End-to-end product design from zero.
User Research
Information Architecture
Interaction Design
Visual Design
Flixxi AI UX
07
Pilot Studios Onboarded
07
Pilot Studios Onboarded
07
Pilot Studios Onboarded
04
Countries Represented
8+
Integrated Feature Modules
8+
Integrated Feature Modules
8+
Integrated Feature Modules
0→1
Product Built from Start
04
Countries Represented
04
Countries Represented
0→1
Product Built from Start
0→1
Product Built from Start
//
//
//
//
02
02
02
02
PROBLEM FRAMING
PROBLEM FRAMING
PROBLEM FRAMING
PROBLEM FRAMING
CHAOS IS THE
CHAOS IS THE
CHAOS IS THE
Professional animation and VFX studios operate at a scale most project management tools weren't designed for. A single season of an anime series can involve hundreds of assets, dozens of sequences, cross-timezone teams, and multi-vendor pipelines – all coordinated across a patchwork of tools that don't talk to each other.
Professional animation and VFX studios operate at a scale most project management tools weren't designed for. A single season of an anime series can involve hundreds of assets, dozens of sequences, cross-timezone teams, and multi-vendor pipelines – all coordinated across a patchwork of tools that don't talk to each other.
Professional animation and VFX studios operate at a scale most project management tools weren't designed for. A single season of an anime series can involve hundreds of assets, dozens of sequences, cross-timezone teams, and multi-vendor pipelines – all coordinated across a patchwork of tools that don't talk to each other.
Professional animation and VFX studios operate at a scale most project management tools weren't designed for. A single season of an anime series can involve hundreds of assets, dozens of sequences, cross-timezone teams, and multi-vendor pipelines – all coordinated across a patchwork of tools that don't talk to each other.
The result is a system held together by institutional memory, manual status updates, and a chronic fear that one missed message collapses a production week. The tooling problem isn't just inefficiency, it's a structural risk.
The result is a system held together by institutional memory, manual status updates, and a chronic fear that one missed message collapses a production week. The tooling problem isn't just inefficiency, it's a structural risk.
The result is a system held together by institutional memory, manual status updates, and a chronic fear that one missed message collapses a production week. The tooling problem isn't just inefficiency, it's a structural risk.
The result is a system held together by institutional memory, manual status updates, and a chronic fear that one missed message collapses a production week. The tooling problem isn't just inefficiency, it's a structural risk.
01
FRAGENTED TOOL STACKS
Studios cobble together Slack, Notion, Google Sheets, Dropbox, and custom spreadsheets. Context is scattered. There's no single source of truth for project state.
01
FRAGENTED TOOL STACKS
Studios cobble together Slack, Notion, Google Sheets, Dropbox, and custom spreadsheets. Context is scattered. There's no single source of truth for project state.
01
FRAGENTED TOOL STACKS
Studios cobble together Slack, Notion, Google Sheets, Dropbox, and custom spreadsheets. Context is scattered. There's no single source of truth for project state.
01
FRAGENTED TOOL STACKS
Studios cobble together Slack, Notion, Google Sheets, Dropbox, and custom spreadsheets. Context is scattered. There's no single source of truth for project state.
02
HIGH-FRICTION ONBOARDING
Starting a new production requires manually creating pipelines, re-inviting teams, and re-configuring workflows which can eat weeks before a single frame is created.
02
HIGH-FRICTION ONBOARDING
Starting a new production requires manually creating pipelines, re-inviting teams, and re-configuring workflows which can eat weeks before a single frame is created.
02
HIGH-FRICTION ONBOARDING
Starting a new production requires manually creating pipelines, re-inviting teams, and re-configuring workflows which can eat weeks before a single frame is created.
02
HIGH-FRICTION ONBOARDING
Starting a new production requires manually creating pipelines, re-inviting teams, and re-configuring workflows which can eat weeks before a single frame is created.
03
NO AI LEVERAGE IN PRODUCTION
The creative industry was rapidly adopting generative AI for content, but the operational layer, the infrastructure running productions, remained entirely manual and brittle.
03
NO AI LEVERAGE IN PRODUCTION
The creative industry was rapidly adopting generative AI for content, but the operational layer, the infrastructure running productions, remained entirely manual and brittle.
03
NO AI LEVERAGE IN PRODUCTION
The creative industry was rapidly adopting generative AI for content, but the operational layer, the infrastructure running productions, remained entirely manual and brittle.
03
NO AI LEVERAGE IN PRODUCTION
The creative industry was rapidly adopting generative AI for content, but the operational layer, the infrastructure running productions, remained entirely manual and brittle.
04
EXPERT RESISTENCE TO AUTOMATION
Production leads and directors often resist fully automated systems. Any AI-first tool had to offer a clear escape hatch to full manual control without penalty.
04
RESISTENCE TO AUTOMATION
Production leads and directors often resist fully automated systems. Any AI-first tool had to offer a clear escape hatch to full manual control without penalty.
04
EXPERT RESISTENCE TO AUTOMATION
Production leads and directors often resist fully automated systems. Any AI-first tool had to offer a clear escape hatch to full manual control without penalty.
04
RESISTENCE TO AUTOMATION
Production leads and directors often resist fully automated systems. Any AI-first tool had to offer a clear escape hatch to full manual control without penalty.
//
//
//
//
03
03
03
03
INFORMATION ARCHITECTURE
INFORMATION ARCHITECTURE
INFORMATION ARCHITECTURE
INFORMATION ARCHITECTURE
MAPPING THE
MAPPING THE
MAPPING THE
Before any frames was drawn, the core question was: what does a studio actually do, and how do those activities cluster?
Research with production leads revealed five primary job domains that any studio management system must address. These became the five modules of OriginX's core navigation.
Before any frames was drawn, the core question was: what does a studio actually do, and how do those activities cluster? Research with production leads revealed five primary job domains that any studio management system must address. These became the five modules of OriginX's core navigation.
Before any frames was drawn, the core question was: what does a studio actually do, and how do those activities cluster? Research with production leads revealed five primary job domains that any studio management system must address. These became the five modules of OriginX's core navigation.
Before any frames was drawn, the core question was: what does a studio actually do, and how do those activities cluster? Research with production leads revealed five primary job domains that any studio management system must address. These became the five modules of OriginX's core navigation.
PRODUCTION
production Pipeline
shot Sequence editing
kanban (Task Management)
production Timeline
version control
Content analytics
Design Decision
CONTENT LIBRARY
Series hierarchy
episodes management
story segments
scripts repository
metadata tagging
release planning
Design Decision
file manager
global asset library
upload center
recent work
pinned assets
asset directory
storage management
Design Decision
finance + dist
studio financials
Native publishing
API/SDK exports
budget allocation
payout processing
stakeholder management
Design Decision
team & comms
integrated chat
video conferencing
Comms channels
task allocation
Review Rooms
individual performance
Design Decision

NAVIGATION ARCHITECTURE
NAVIGATION ARCHITECTURE
NAVIGATION
ARCHITECTURE
NAVIGATION ARCHITECTURE
A persistent sidebar navigation architecture was chosen over tab-based or hub-and-spoke patterns.
A persistent sidebar navigation architecture was chosen over tab-based or hub-and-spoke patterns.
A persistent sidebar navigation architecture was chosen over tab-based or hub-and-spoke patterns.
A persistent sidebar navigation architecture was chosen over tab-based or hub-and-spoke patterns.
Studios need to switch context fast during a production day. The sidebar keeps all six domains within a single click, and the active module highlights with a gradient indicator that extends from the product's accent system.
Studios need to switch context fast during a production day. The sidebar keeps all six domains within a single click, and the active module highlights with a gradient indicator that extends from the product's accent system.
Studios need to switch context fast during a production day. The sidebar keeps all six domains within a single click, and the active module highlights with a gradient indicator that extends from the product's accent system.
Studios need to switch context fast during a production day. The sidebar keeps all six domains within a single click, and the active module highlights with a gradient indicator that extends from the product's accent system.
FLIXXI AI
ENTRY POINT
FLIXXI AI ENTRY POINT
FLIXXI AI
ENTRY POINT
FLIXXI AI ENTRY POINT

The "Ask Flixxi" entry point was anchored in the top bar, always visible, always accessible, reinforcing the idea that AI assistance is a first-class affordance, not a buried feature. This was a deliberate information hierarchy decision: the AI should feel ambient, not gated.
The "Ask Flixxi" entry point was anchored in the top bar, always visible, always accessible, reinforcing the idea that AI assistance is a first-class affordance, not a buried feature. This was a deliberate information hierarchy decision: the AI should feel ambient, not gated.
The "Ask Flixxi" entry point was anchored in the top bar, always visible, always accessible, reinforcing the idea that AI assistance is a first-class affordance, not a buried feature. This was a deliberate information hierarchy decision: the AI should feel ambient, not gated.
The "Ask Flixxi" entry point was anchored in the top bar, always visible, always accessible, reinforcing the idea that AI assistance is a first-class affordance, not a buried feature. This was a deliberate information hierarchy decision: the AI should feel ambient, not gated.
PRODUCTION
production Pipeline
shot Sequence editing
kanban (Task Management)
production Timeline
version control
Content analytics
FILE MANAGER
global asset library
upload center
recent work
pinned assets
asset directory
storage management
CONTENT LIBRARY
Series hierarchy
episodes management
story segments
scripts repository
metadata tagging
release planning
FINANCE & DIST
studio financials
Native publishing
API/SDK exports
budget allocation
payout processing
stakeholder management
TEAM & COMMS
integrated chat
video conferencing
Comms channels
task allocation
Review Rooms
individual performance
PRODUCTION
production Pipeline
shot Sequence editing
kanban (Task Management)
production Timeline
version control
Content analytics
FILE MANAGER
global asset library
upload center
recent work
pinned assets
asset directory
storage management
CONTENT LIBRARY
scripts repository
metadata tagging
release planning
Series hierarchy
episodes management
story segments
FINANCE & DIST
budget allocation
payout processing
stakeholder management
studio financials
Native publishing
API/SDK exports
TEAM & COMMS
task allocation
Review Rooms
individual performance
integrated chat
video conferencing
Comms channels
//
//
//
//
04
04
04
04
DUAL PATH PRODUCTION ONBOARDING
DUAL PATH PRODUCTION ONBOARDING
DUAL PATH PRODUCTION ONBOARDING
DUAL PATH PRODUCTION ONBOARDING
THE CORE
THE CORE
THE CORE
The central UX problem: expert production leads won't surrender control to a system they don't fully understand. But studios under deadline pressure can't afford to manually configure every task, dependency, and milestone from scratch. The design had to serve both realities simultaneously.
The central UX problem: expert production leads won't surrender control to a system they don't fully understand. But studios under deadline pressure can't afford to manually configure every task, dependency, and milestone from scratch. The design had to serve both realities simultaneously.
The central UX problem: expert production leads won't surrender control to a system they don't fully understand. But studios under deadline pressure can't afford to manually configure every task, dependency, and milestone from scratch. The design had to serve both realities simultaneously.
The central UX problem: expert production leads won't surrender control to a system they don't fully understand. But studios under deadline pressure can't afford to manually configure every task, dependency, and milestone from scratch. The design had to serve both realities simultaneously.
The design had to serve both realities simultaneously.
The design had to serve both realities simultaneously.
The design had to serve both realities simultaneously.
The design had to serve both realities simultaneously.
The solution was the Dual Path – a branching onboarding architecture that makes the choice explicit and consequential, without making either path feel like a downgrade or a forced choice
The solution was the Dual Path – a branching onboarding architecture that makes the choice explicit and consequential, without making either path feel like a downgrade or a forced choice
The solution was the Dual Path – a branching onboarding architecture that makes the choice explicit and consequential, without making either path feel like a downgrade or a forced choice
The solution was the Dual Path – a branching onboarding architecture that makes the choice explicit and consequential, without making either path feel like a downgrade or a forced choice
FLIXXI AI-POWERED PATH

FLIXXI BLUEPRINT
Describe your production in natural language. Flixxi architects the entire pipeline including tasks, sequences, dependencies, milestones, team assignments in seconds.
01
ENTER THE PROJECT BRIEF
Describe the project: genre, episode count, deadline, team size, delivery format.
02
FLIXXI GENERATES THE PIPELINE
AI maps tasks, sequences, dependencies, and role assignments across the full production arc.
03
REVIEW, EDIT, ACTIVATE
Every generated element is editable before go-live. AI suggests; the person decides.
FLIXXI AI-POWERED PATH

FLIXXI BLUEPRINT
Describe your production in natural language. Flixxi architects the entire pipeline including tasks, sequences, dependencies, milestones in seconds.
01
ENTER THE PROJECT BRIEF
Describe the genre, episode count, deadline, team size, delivery format.
02
FLIXXI GENERATES THE PIPELINE
AI maps tasks, sequences, dependencies, and role assignments across the full production arc.
03
REVIEW, EDIT, ACTIVATE
Every generated element is editable before it goes live.
FLIXXI AI-POWERED PATH

FLIXXI BLUEPRINT
Describe your production in natural language. Flixxi architects the entire pipeline including tasks, sequences, dependencies, milestones, team assignments in seconds.
01
ENTER THE PROJECT BRIEF
Describe the genre, episode count, deadline, team size, delivery format.
02
FLIXXI GENERATES THE PIPELINE
AI maps tasks, sequences, dependencies, and role assignments across the full production arc.
03
REVIEW, EDIT, ACTIVATE
Every generated element is editable before it goes live.
FLIXXI AI-POWERED PATH

FLIXXI BLUEPRINT
Describe your production in natural language. Flixxi architects the entire pipeline including tasks, sequences, dependencies, milestones in seconds.
01
ENTER THE PROJECT BRIEF
Describe the genre, episode count, deadline, team size, delivery format.
02
FLIXXI GENERATES THE PIPELINE
AI maps tasks, sequences, dependencies, and role assignments across the full production arc.
03
REVIEW, EDIT, ACTIVATE
Every generated element is editable before it goes live.
MANUAL PATH

MANUAL BLUEPRINT
Start from a clean slate. Build the exact pipeline your studio needs, task by task, sequence by sequence and have complete control from start to finish.
01
CREATE THE PROJECT SHELL
Name it, set the format, establish key dates and team access.
02
BUILD SEQUENCES MANUALLY
Define each sequence, episode, or chapter. Add tasks, assign leads, set dependencies.
03
CONFIGURE & LAUNCH
Invite your team, set permissions by role, and activate. You own every decision.
MANUAL PATH

MANUAL BLUEPRINT
Start from a clean slate. Build the exact pipeline your studio needs, task by task, sequence by sequence and have complete control from start to finish.
01
CREATE THE PROJECT SHELL
Name it, set the format, establish key dates and team access.
02
BUILD SEQUENCES MANUALLY
Define each sequence, episode, or chapter. Add tasks, assign leads, set dependencies.
03
CONFIGURE & LAUNCH
Invite your team, set permissions by role, and activate. You own every decision.
MANUAL PATH

MANUAL BLUEPRINT
Start from a clean slate. Build the exact pipeline your studio needs, task by task, sequence by sequence and have complete control from start to finish.
01
CREATE THE PROJECT SHELL
Name it, set the format, establish key dates and team access.
02
BUILD SEQUENCES MANUALLY
Define each sequence, episode, or chapter. Add tasks, assign leads, set dependencies.
03
CONFIGURE & LAUNCH
Invite your team, set permissions by role, and activate. You own every decision.
MANUAL PATH

MANUAL BLUEPRINT
Start from a clean slate. Build the exact pipeline your studio needs, task by task, sequence by sequence and have complete control from start to finish.
01
CREATE THE PROJECT SHELL
Name it, set the format, establish key dates and team access.
02
BUILD SEQUENCES MANUALLY
Define each sequence, episode, or chapter. Add tasks, assign leads, set dependencies.
03
CONFIGURE & LAUNCH
Invite your team, set permissions by role, and activate. You own every decision.
The key insight behind the Dual Path: the choice itself is the trust signal. By presenting both options with equal visual weight – neither promoted nor hidden, the design communicates that OriginX respects expert judgment.
The key insight behind the Dual Path: the choice itself is the trust signal. By presenting both options with equal visual weight – neither promoted nor hidden, the design communicates that OriginX respects expert judgment.
The key insight behind the Dual Path: the choice itself is the trust signal. By presenting both options with equal visual weight – neither promoted nor hidden, the design communicates that OriginX respects expert judgment.
The key insight behind the Dual Path: the choice itself is the trust signal. By presenting both options with equal visual weight – neither promoted nor hidden, the design communicates that OriginX respects expert judgment.
Studios who try Flixxi and want to refine it can always edit. Studios who start manual can invoke Flixxi mid-project to fill gaps.
Studios who try Flixxi and want to refine it can always edit. Studios who start manual can invoke Flixxi mid-project to fill gaps.
Studios who try Flixxi and want to refine it can always edit. Studios who start manual can invoke Flixxi mid-project to fill gaps.
Studios who try Flixxi and want to refine it can always edit. Studios who start manual can invoke Flixxi mid-project to fill gaps.
The paths aren't competing; they're complementary.
The paths aren't competing; they're complementary.
The paths aren't competing; they're complementary.
The paths aren't competing; they're complementary.
//
//
//
//
05
05
05
05
FLIXXI AI – USER EXPERIENCE
FLIXXI AI – USER EXPERIENCE
FLIXXI AI – USER EXPERIENCE
FLIXXI AI – USER EXPERIENCE
DESIGNING FOR
DESIGNING FOR
DESIGNING FOR
Flixxi presented a distinct design challenge:
Flixxi presented a distinct design challenge:
Flixxi presented a distinct design challenge:
Flixxi presented a distinct design challenge:
how do you make an AI feel trustworthy to professional users who are deeply skeptical of automation?
how do you make an AI feel trustworthy to professional users who are deeply skeptical of automation?
how do you make an AI feel trustworthy to professional users who are deeply skeptical of automation?
how do you make an AI feel trustworthy to professional users who are deeply skeptical of automation?
The interaction model had to feel transparent, not magical. Every AI-generated output had to be legible, editable, and attributable. The creative leads stay in command while Flixxi does the heavy lifting.
The interaction model had to feel transparent, not magical. Every AI-generated output had to be legible, editable, and attributable. The creative leads stay in command while Flixxi does the heavy lifting.
The interaction model had to feel transparent, not magical. Every AI-generated output had to be legible, editable, and attributable. The creative leads stay in command while Flixxi does the heavy lifting.
The interaction model had to feel transparent, not magical. Every AI-generated output had to be legible, editable, and attributable. The creative leads stay in command while Flixxi does the heavy lifting.
Several non-obvious decisions shaped the Flixxi UX. The AI's output is always presented as editable scaffolding, not finalized truth. Every generated task, sequence, and dependency can be modified before the pipeline goes live. This "suggest and confirm" pattern was validated early in testing as the key trust-building mechanism.
Several non-obvious decisions shaped the Flixxi UX. The AI's output is always presented as editable scaffolding, not finalized truth. Every generated task, sequence, and dependency can be modified before the pipeline goes live. This "suggest and confirm" pattern was validated early in testing as the key trust-building mechanism.
Several non-obvious decisions shaped the Flixxi UX. The AI's output is always presented as editable scaffolding, not finalized truth. Every generated task, sequence, and dependency can be modified before the pipeline goes live. This "suggest and confirm" pattern was validated early in testing as the key trust-building mechanism.
Several non-obvious decisions shaped the Flixxi UX. The AI's output is always presented as editable scaffolding, not finalized truth. Every generated task, sequence, and dependency can be modified before the pipeline goes live. This "suggest and confirm" pattern was validated early in testing as the key trust-building mechanism.
The "Ask Flixxi" topbar widget was designed to feel like a persistent colleague, not a search box. It can answer questions about project status mid-production, suggest task prioritization during crunch, or re-architect a sequence when a team member goes out. The interaction pattern is conversational, contextual, and non-blocking.
The "Ask Flixxi" topbar widget was designed to feel like a persistent colleague, not a search box. It can answer questions about project status mid-production, suggest task prioritization during crunch, or re-architect a sequence when a team member goes out. The interaction pattern is conversational, contextual, and non-blocking.
The "Ask Flixxi" topbar widget was designed to feel like a persistent colleague, not a search box. It can answer questions about project status mid-production, suggest task prioritization during crunch, or re-architect a sequence when a team member goes out. The interaction pattern is conversational, contextual, and non-blocking.
The "Ask Flixxi" topbar widget was designed to feel like a persistent colleague, not a search box. It can answer questions about project status mid-production, suggest task prioritization during crunch, or re-architect a sequence when a team member goes out. The interaction pattern is conversational, contextual, and non-blocking.
//
//
//
//
06
06
06
06
THE PRODUCT
THE PRODUCT
THE PRODUCT
THE PRODUCT
BUILT FOR THE WAY
BUILT THE WAY
BUILT FOR THE WAY
Every screen was designed within a unified dark system — a near-black base, hairline borders at 7% white opacity, and a blue-to-purple gradient accent that threads through every interactive element. But the screens themselves are secondary. What matters is what each one unlocks for the people running a production.
Every screen was designed within a unified dark system — a near-black base, hairline borders at 7% white opacity, and a blue-to-purple gradient accent that threads through every interactive element. But the screens themselves are secondary. What matters is what each one unlocks for the people running a production.
Every screen was designed within a unified dark system — a near-black base, hairline borders at 7% white opacity, and a blue-to-purple gradient accent that threads through every interactive element. But the screens themselves are secondary. What matters is what each one unlocks for the people running a production.
Every screen was designed within a unified dark system — a near-black base, hairline borders at 7% white opacity, and a blue-to-purple gradient accent that threads through every interactive element. But the screens themselves are secondary. What matters is what each one unlocks for the people running a production.

DASHBOARD
EVERY DEADLINE, EVERY BLOCKER, EVERY TEAMMATE — BEFORE YOUR FIRST COFFEE.
Production leads carry an impossible mental load: tracking what's overdue, what's in review, who's blocked, and what's due today — across a team that spans timezones. The Dashboard collapses all of that into a single glanceable surface. Overdue tasks surface in red before they become production emergencies. The integrated calendar keeps meetings and milestones in the same view as the work itself. You open OriginX once in the morning and you already know where the day stands.
01

DASHBOARD
EVERY DEADLINE, EVERY BLOCKER, EVERY TEAMMATE — BEFORE YOUR FIRST COFFEE.
Every overdue task, blocked teammate, and today's deadline — in one glanceable view. The Dashboard surfaces what needs attention before it becomes an emergency, with your calendar and work in the same place.
01

DASHBOARD
EVERY DEADLINE, EVERY BLOCKER, EVERY TEAMMATE — BEFORE YOUR FIRST COFFEE.
Production leads carry an impossible mental load: tracking what's overdue, what's in review, who's blocked, and what's due today — across a team that spans timezones. The Dashboard collapses all of that into a single glanceable surface. Overdue tasks surface in red before they become production emergencies. The integrated calendar keeps meetings and milestones in the same view as the work itself. You open OriginX once in the morning and you already know where the day stands.
01

DASHBOARD
EVERY DEADLINE, EVERY BLOCKER, EVERY TEAMMATE — BEFORE YOUR FIRST COFFEE.
Every overdue task, blocked teammate, and today's deadline — in one glanceable view. The Dashboard surfaces what needs attention before it becomes an emergency, with your calendar and work in the same place.
01

PRODUCTION
ONE PROJECT. EVERY MOVING PART. ZERO STATUS-UPDATE MEETINGS.
The Production module is where a season actually lives. Pipeline, Sequences, Kanban, Timeline, Tasks, Reviews, Assets, and Reports — all accessible from a single horizontal tab bar, never more than one click away. Directors stop chasing status updates because the status is always current, always visible. Producers stop juggling spreadsheets because every task, dependency, and milestone is already mapped. When something slips, the ripple effect shows up instantly across every view — so the team adapts before the deadline moves.
02

PRODUCTION
ONE PROJECT. EVERY MOVING PART. ZERO STATUS-UPDATE MEETINGS.
Pipeline, Kanban, Timeline, Tasks, Reviews — all one click away. Directors stop chasing updates. Producers stop juggling spreadsheets. When something slips, the ripple shows up instantly so the team adapts before the deadline moves.
02

PRODUCTION
ONE PROJECT. EVERY MOVING PART. ZERO STATUS-UPDATE MEETINGS.
The Production module is where a season actually lives. Pipeline, Sequences, Kanban, Timeline, Tasks, Reviews, Assets, and Reports — all accessible from a single horizontal tab bar, never more than one click away. Directors stop chasing status updates because the status is always current, always visible. Producers stop juggling spreadsheets because every task, dependency, and milestone is already mapped. When something slips, the ripple effect shows up instantly across every view — so the team adapts before the deadline moves.
02

PRODUCTION
ONE PROJECT. EVERY MOVING PART. ZERO STATUS-UPDATE MEETINGS.
Pipeline, Kanban, Timeline, Tasks, Reviews — all one click away. Directors stop chasing updates. Producers stop juggling spreadsheets. When something slips, the ripple shows up instantly so the team adapts before the deadline moves.
02

CONTENT LIBRARY
YOUR ENTIRE CATALOGUE, ONE CLICK AWAY.
When you're managing dozens of series, hundreds of episodes, and thousands of assets, "where is the latest version of that file?" becomes a real tax on every workday. The Content Library gives every series, episode, and chapter a permanent, searchable home — with metadata, upload history, and sort controls that scale from a pilot to a full multi-season catalogue without friction.
03

CONTENT LIBRARY
YOUR ENTIRE CATALOGUE, ONE CLICK AWAY.
When you're managing dozens of series, hundreds of episodes, and thousands of assets, "where is the latest version of that file?" becomes a real tax on every workday. The Content Library gives every series, episode, and chapter a permanent, searchable home — with metadata, upload history, and sort controls that scale from a pilot to a full multi-season catalogue without friction.
03

CONTENT LIBRARY
YOUR ENTIRE CATALOGUE, ONE CLICK AWAY.
A permanent, searchable home for every series, episode, and chapter. Metadata, upload history, and sort controls that scale from a single pilot to a full multi-season catalogue without friction.
03

UPLOAD CENTER
NEW SEASON, LIVE IN HOURS. NOT DAYS.
Getting new content into a system is usually the unsexy bottleneck — manual uploads, renaming conventions, version conflicts. The Upload Center strips that friction out entirely. Add to an existing series or start a fresh one, schedule releases, and manage everything from a single interface that was built specifically for anime and manga publishing workflows.
04

UPLOAD CENTER
NEW SEASON, LIVE IN HOURS. NOT DAYS.
Getting new content into a system is usually the unsexy bottleneck — manual uploads, renaming conventions, version conflicts. The Upload Center strips that friction out entirely. Add to an existing series or start a fresh one, schedule releases, and manage everything from a single interface that was built specifically for anime and manga publishing workflows.
04

UPLOAD CENTER
NEW SEASON, LIVE IN HOURS. NOT DAYS.
Add to an existing series or start a fresh one, schedule releases, and manage uploads from one interface — built specifically for anime and manga publishing workflows, not adapted from a generic CMS.
04

FILE MANAGER
THE SHOT YOUR DIRECTOR ASKED FOR AT 11PM? FOUND IN THREE SECONDS.
Studios accumulate files fast — rough cuts, VFX passes, reference sheets, contracts, animatics, final renders. The File Manager brings them all into one place with a grid layout that lets you actually see what you're looking at, not just read filenames. Recents, Favourites, and folder-based navigation mean the files that matter most are always surfaced first. No more digging through Dropbox folders or sending "can you re-send that file?" messages at midnight.
05

FILE MANAGER
THE SHOT YOUR DIRECTOR ASKED FOR AT 11PM? FOUND IN THREE SECONDS.
Studios accumulate files fast — rough cuts, VFX passes, reference sheets, contracts, animatics, final renders. The File Manager brings them all into one place with a grid layout that lets you actually see what you're looking at, not just read filenames. Recents, Favourites, and folder-based navigation mean the files that matter most are always surfaced first. No more digging through Dropbox folders or sending "can you re-send that file?" messages at midnight.
05

FILE MANAGER
THE SHOT YOUR DIRECTOR ASKED FOR AT 11PM? FOUND IN THREE SECONDS.
Every rough cut, VFX pass, contract, and final render in one place. A grid layout that lets you see your files, not just read their names. Recents and Favourites keep what matters always within reach.
05

COMMUNICATIONS
YOUR WHOLE STUDIO IN ONE CONVERSATION. NOT SCATTERED ACROSS THREE APPS.
Most studios run their internal communications across Slack, WhatsApp groups, email threads — and context gets lost between all of them. OriginX brings team communication inside the same system where the work lives. Channels for departments, direct messages for quick decisions, and scheduled meetings — all connected to the projects and files they're actually about. When a conversation references a task or asset, it's already in context.
06

COMMUNICATIONS
YOUR WHOLE STUDIO IN ONE PLACE. NOT SCATTERED ACROSS THREE APPS.
Most studios run their internal communications across Slack, WhatsApp groups, email threads, and context gets lost between all of them. OriginX brings communication inside the same system where the work lives. Channels for departments, direct messages for quick decisions, and scheduled meetings — all connected to the projects and files they're actually about. When a conversation references a task or asset, it's already in context.
06

COMMUNICATIONS
YOUR WHOLE STUDIO IN ONE PLACE. NOT SCATTERED ACROSS THREE APPS.
Channels, direct messages, and meetings — inside the same system where the work lives. No more context lost between Slack, WhatsApp, and email. Every conversation is already connected to the project it's about.
06

STUDIO FINANCE
MONEY DOESN'T DISAPPEAR IN ORIGINX. IT LEAVES A TRAIL.
Running a production without real-time budget visibility is like editing blind — you only see the problem when it's too late to fix it. Studio Finance puts every project's budget, spend, and remaining allocation in one place, across your entire slate simultaneously. Producers can track payouts, manage team compensation, and catch overspend before it becomes a conversation with the director. When every project's financial health is visible at a glance, the studio stops reacting to budget problems and starts preventing them.
07

STUDIO FINANCE
MONEY DOESN'T DISAPPEAR IN ORIGINX. IT LEAVES A TRAIL.
Running a production without real-time budget visibility is editing blind — you only see the problem when it's too late to fix it. Studio Finance puts every project's budget, spend, and remaining allocation in one place, across your entire slate simultaneously. Producers can track payouts, manage team compensation, and catch overspend before it becomes a conversation with the director. When every project's financial health is visible at a glance, the studio stops reacting to budget problems and prevents them.
07

STUDIO FINANCE
MONEY DOESN'T DISAPPEAR IN ORIGINX. IT LEAVES A TRAIL.
See every project's budget, spend, and remaining allocation across your entire slate in real time. Catch overspend before it reaches the director. Stop reacting to financial problems — start preventing them.
07

PARTNERS
DISTRIBUTION DEALS, API KEYS, PLATFORM RELATIONSHIPS — ALL MANAGED IN ONE PLACE.
Getting content to external platforms like streaming services, licensing partners, & distribution networks has always meant juggling separate logins, API credentials, and email threads with each partner. The Partners module brings all of it under one roof. Add a new platform partner, manage API access, monitor connection activity, and control exactly what each partner can see and publish. For studios building towards global distribution, the infrastructure for scaling partnerships is already built into the OS.
08

PARTNERS
DISTRIBUTION DEALS, API KEYS, PLATFORM RELATIONSHIPS, ALL IN ONE PLACE.
Getting content to external platforms like streaming services, licensing partners, & distribution networks has always meant juggling separate logins, API credentials, and email threads with each partner. The Partners module brings all of it under one roof. Add a new platform partner, manage API access, monitor connection activity, and control exactly what each partner can see and publish. For studios building towards global distribution, the infrastructure for scaling partnerships is already built in.
08

PARTNERS
DEALS, API KEYS, RELATIONSHIPS, ALL IN ONE PLACE.
One place for every platform partner, API key, and distribution relationship. Add partners, manage access, monitor activity, and control exactly what each partner can publish, all built in.
08

CONTENT LIBRARY
YOUR ENTIRE CATALOGUE, ONE CLICK AWAY.
A permanent, searchable home for every series, episode, and chapter. Metadata, upload history, and sort controls that scale from a single pilot to a full multi-season catalogue without friction.
03

UPLOAD CENTER
NEW SEASON, LIVE IN HOURS. NOT DAYS.
Add to an existing series or start a fresh one, schedule releases, and manage uploads from one interface — built specifically for anime and manga publishing workflows, not adapted from a generic CMS.
04

FILE MANAGER
THE SHOT YOUR DIRECTOR ASKED FOR AT 11PM? FOUND IN THREE SECONDS.
Every rough cut, VFX pass, contract, and final render in one place. A grid layout that lets you see your files, not just read their names. Recents and Favourites keep what matters always within reach.
05

COMMUNICATIONS
YOUR WHOLE STUDIO IN ONE PLACE. NOT SCATTERED ACROSS THREE APPS.
Channels, direct messages, and meetings — inside the same system where the work lives. No more context lost between Slack, WhatsApp, and email. Every conversation is already connected to the project it's about.
06

STUDIO FINANCE
MONEY DOESN'T DISAPPEAR IN ORIGINX. IT LEAVES A TRAIL.
See every project's budget, spend, and remaining allocation across your entire slate in real time. Catch overspend before it reaches the director. Stop reacting to financial problems — start preventing them.
07

PARTNERS
DEALS, API KEYS, RELATIONSHIPS, ALL IN ONE PLACE.
One place for every platform partner, API key, and distribution relationship. Add partners, manage access, monitor activity, and control exactly what each partner can publish, all built in.
08
//
//
//
//
07
07
07
07
DESIGN SYSTEM
DESIGN SYSTEM
DESIGN SYSTEM
DESIGN SYSTEM
THE VISUAL
THE VISUAL
THE VISUAL
The design system was built around a single rule: every element that is interactive must earn its style. Static text, borders, backgrounds — all remain in the grey/dark range. The blue-to-purple gradient only fires on buttons, active states, hover indicators, and Flixxi-related elements. This keeps cognitive load low in a tool that runs all day, while making the accent color immediately recognizable as "you can do something here."
The design system was built around a single rule: every element that is interactive must earn its style. Static text, borders, backgrounds — all remain in the grey/dark range. The blue-to-purple gradient only fires on buttons, active states, hover indicators, and Flixxi-related elements. This keeps cognitive load low in a tool that runs all day, while making the accent color immediately recognizable as "you can do something here."
The design system was built around a single rule: every element that is interactive must earn its style. Static text, borders, backgrounds — all remain in the grey/dark range. The blue-to-purple gradient only fires on buttons, active states, hover indicators, and Flixxi-related elements. This keeps cognitive load low in a tool that runs all day, while making the accent color immediately recognizable as "you can do something here."
The design system was built around a single rule: every element that is interactive must earn its style. Static text, borders, backgrounds — all remain in the grey/dark range. The blue-to-purple gradient only fires on buttons, active states, hover indicators, and Flixxi-related elements. This keeps cognitive load low in a tool that runs all day, while making the accent color immediately recognizable as "you can do something here."
Monospaced type (DM Mono) is reserved for metadata, labels, system status, and the Flixxi interface — creating a clear visual distinction between human-authored content and system/AI-generated information.
Monospaced type (DM Mono) is reserved for metadata, labels, system status, and the Flixxi interface — creating a clear visual distinction between human-authored content and system/AI-generated information.
Monospaced type (DM Mono) is reserved for metadata, labels, system status, and the Flixxi interface — creating a clear visual distinction between human-authored content and system/AI-generated information.
Monospaced type (DM Mono) is reserved for metadata, labels, system status, and the Flixxi interface — creating a clear visual distinction between human-authored content and system/AI-generated information.
COLOR STYLES
COLOR STYLES
INDIGO
INDIGO
INDIGO
PURPLE
PURPLE
PURPLE
BACKGROUND
BACKGROUND
BACKGROUND
SEMANTICS
SEMANTICS
TEXT COLORS
TEXT COLORS
SEMANTICS
TEXT COLORS
TEXT STYLES
TEXT STYLES
HEADING TEXT
Heading Text
DT Getai Grotesk Display
DT Getai Grotesk Display
DT Getai Grotesk Display
Size (px) / Line Height (%)
Size (px) / Line Height (%)
Size (px) / Line Height (%)
Display
Display
DISPLAY
DISPLAY
DISPLAY
128 / 100
128 / 100
128 / 100
H1
H1
HEADING 1
HEADING 1
HEADING 1
92 / 100
92 / 100
92 / 100
H2
H2
HEADING 2
HEADING 2
HEADING 2
67 / 120
67 / 120
67 / 120
H3
H3
HEADING 3
HEADING 3
HEADING 3
48 / 120
48 / 120
48 / 120
H4
H4
HEADING 4
HEADING 4
HEADING 4
35 / 120
35 / 120
35 / 120
H5
H5
HEADING 5
HEADING 5
HEADING 5
25 / 135
25 / 135
25 / 135
H6
H6
HEADING 6
HEADING 6
18 / 140
18 / 140
18 / 140
BODY TEXT
Body Text
Geologica
Geologica
Geologica
Size (px) / Line Height (%)
Size (px) / Line Height (%)
Size (px) / Line Height (%)
B – 2XL
B – 2XL
BODY — 2 Extra Large
BODY — 2 Extra Large
BODY — 2 Extra Large
32 / 135
32 / 135
32 / 135
B – XL
B – XL
BODY — Extra Large
BODY — Extra Large
BODY — Extra Large
28 / 135
28 / 135
28 / 135
B – L
B – L
BODY — Large
BODY — Large
BODY — Large
24 / 135
24 / 135
24 / 135
B – M
B – M
BODY — Medium
BODY — Medium
BODY — Medium
20 / 135
20 / 135
20 / 135
B – S
B – S
BODY — Small
BODY — Small
18 / 135
18 / 135
18 / 135
B – XS
B – XS
BODY — Extra Small
BODY — Extra Small
BODY — Extra Small
16 / 135
16 / 135
16 / 135
LABEL TEXT
Label Text
Atkinson Hyperlegible Mono
Atkinson Hyperlegible Mono
Atkinson Hyperlegible Mono
Size (px) / Line Height (%)
Size (px) / Line Height (%)
Size (px) / Line Height (%)
Link Text
Link Text
Link Text
Link Text
18 / 135
18 / 135
18 / 135
L – XL
L – XL
LABEL — Extra Large
LABEL — Extra Large
20 / 150
20 / 150
20 / 150
L – L
L – L
LABEL — Large
LABEL — Large
16 / 150
16 / 150
16 / 150
L – M
L – M
LABEL — Medium
14 / 135
14 / 135
14 / 135
L – S
L – S
LABEL — Small
LABEL — Small
12 / 135
12 / 135
12 / 135
L – XS
L – XS
LABEL — Extra Small
LABEL — Extra Small
10 / 120
10 / 120
10 / 120
//
//
//
//
08
08
08
08
MARKETING WEBSITE
MARKETING WEBSITE
MARKETING WEBSITE
MARKETING WEBSITE
ORIGINX
ORIGINX
ORIGINX
Beyond the product itself, the challenge was making OriginX legible to studios who had never considered a unified OS before. The marketing website at originx.studio had to do heavy lifting: educate, create desire, and convert skeptical production leads in a single scroll.
Beyond the product itself, the challenge was making OriginX legible to studios who had never considered a unified OS before. The marketing website at originx.studio had to do heavy lifting: educate, create desire, and convert skeptical production leads in a single scroll.
Beyond the product itself, the challenge was making OriginX legible to studios who had never considered a unified OS before. The marketing website at originx.studio had to do heavy lifting: educate, create desire, and convert skeptical production leads in a single scroll.
Beyond the product itself, the challenge was making OriginX legible to studios who had never considered a unified OS before. The marketing website at originx.studio had to do heavy lifting: educate, create desire, and convert skeptical production leads in a single scroll.

The website mirrors the product's visual language exactly — same dark substrate, same accent system, same typographic hierarchy. This was intentional: the first time a studio lead sees the product, it should feel like a continuation of the website experience, not a context switch. The same design system governs both surfaces.
The website mirrors the product's visual language exactly — same dark substrate, same accent system, same typographic hierarchy. This was intentional: the first time a studio lead sees the product, it should feel like a continuation of the website experience, not a context switch. The same design system governs both surfaces.
The website mirrors the product's visual language exactly — same dark substrate, same accent system, same typographic hierarchy. This was intentional: the first time a studio lead sees the product, it should feel like a continuation of the website experience, not a context switch. The same design system governs both surfaces.
The website mirrors the product's visual language exactly — same dark substrate, same accent system, same typographic hierarchy. This was intentional: the first time a studio lead sees the product, it should feel like a continuation of the website experience, not a context switch. The same design system governs both surfaces.
The site's architecture follows a conviction-building arc: problem framing (studios are broken) → solution framing (one system) → feature proof (the six modules) → social proof (pilot studios) → conversion. Each section was designed to earn the scroll to the next.
The site's architecture follows a conviction-building arc: problem framing (studios are broken) → solution framing (one system) → feature proof (the six modules) → social proof (pilot studios) → conversion. Each section was designed to earn the scroll to the next.
The site's architecture follows a conviction-building arc: problem framing (studios are broken) → solution framing (one system) → feature proof (the six modules) → social proof (pilot studios) → conversion. Each section was designed to earn the scroll to the next.
The site's architecture follows a conviction-building arc: problem framing (studios are broken) → solution framing (one system) → feature proof (the six modules) → social proof (pilot studios) → conversion. Each section was designed to earn the scroll to the next.
//
//
//
//
09
09
09
09
OUTCOME & IMPACT
OUTCOME & IMPACT
OUTCOME & IMPACT
OUTCOME & IMPACT
WHAT THE
WHAT THE
WHAT THE
07
PILOT STUDIOS ONBOARDED
Studios from India, the US, Australia, and New Zealand are actively testing OriginX across their full production lifecycle — a 4-country, multi-timezone validation of the platform's core architecture.
07
PILOT STUDIOS ONBOARDED
Studios from India, the US, Australia, and New Zealand are actively testing OriginX across their full production lifecycle — a 4-country, multi-timezone validation of the platform's core architecture.
04
COUNTRIES IN ACTIVE TESTING
Cross-timezone deployment stress-tested the Communication and Production modules for async-first workflows — surfacing edge cases that shaped several core UX decisions in the current build.
04
COUNTRIES IN ACTIVE TESTING
Cross-timezone deployment stress-tested the Communication and Production modules for async-first workflows — surfacing edge cases that shaped several core UX decisions in the current build.
0 → 1
BUILT ENTIRELY FROM SCRATCH
No template. No existing design system inherited. Every screen, component, pattern, and interaction was designed from a blank file, working across research, IA, UI, and the live website.
8+
INTEGRATED FEATURE MODULES
Production, Content Library, File Manager, Upload Center, Communications, Finance, Distribution, and Sequence Editor — all designed as a cohesive system, not individual tools bolted together.
8+
INTEGRATED FEATURE MODULES
Production, Content Library, File Manager, Upload Center, Communications, Finance, Distribution, and Sequence Editor — all designed as a cohesive system, not individual tools bolted together.
∞
ITERATION CYCLES
The design was never static. Rapid ideation, quick concept tests, feedback loops with studio users, and constant refinement meant the product evolved significantly from first sketch to current build.
✦
POSITIVE PILOT FEEDBACK
All 7 pilot studios have provided consistently positive feedback. Official onboarding is planned within the next few months, following completion of full lifecycle testing across active production.
0 → 1
BUILT ENTIRELY FROM SCRATCH
No template. No existing design system inherited. Every screen, component, pattern, and interaction was designed from a blank file, working across research, IA, UI, and the live website.
0 → 1
BUILT ENTIRELY FROM SCRATCH
No template. No existing design system inherited. Every screen, component, pattern, and interaction was designed from a blank file, working across research, IA, UI, and the live website.
∞
ITERATION CYCLES
The design was never static. Rapid ideation, quick concept tests, feedback loops with studio users, and constant refinement meant the product evolved significantly from first sketch to current build.
∞
ITERATION CYCLES
The design was never static. Rapid ideation, quick concept tests, feedback loops with studio users, and constant refinement meant the product evolved significantly from first sketch to current build.
✦
POSITIVE PILOT FEEDBACK
All 7 pilot studios have provided consistently positive feedback. Official onboarding is planned within the next few months, following completion of full lifecycle testing across active production.
✦
POSITIVE PILOT FEEDBACK
All 7 pilot studios have provided consistently positive feedback. Official onboarding is planned within the next few months, following completion of full lifecycle testing across active production.
07
PILOT STUDIOS ONBOARDED
Studios from India, the US, Australia, and New Zealand are actively testing OriginX across their full production lifecycle — a 4-country, multi-timezone validation of the platform's core architecture.
04
COUNTRIES IN ACTIVE TESTING
Cross-timezone deployment stress-tested the Communication and Production modules for async-first workflows — surfacing edge cases that shaped several core UX decisions in the current build.
8+
INTEGRATED FEATURE MODULES
Production, Content Library, File Manager, Upload Center, Communications, Finance, Distribution, and Sequence Editor — all designed as a cohesive system, not individual tools bolted together.
∞
ITERATION CYCLES
The design was never static. Rapid ideation, quick concept tests, feedback loops with studio users, and constant refinement meant the product evolved significantly from first sketch to current build.
0 → 1
BUILT ENTIRELY FROM SCRATCH
No template. No existing design system inherited. Every screen, component, pattern, and interaction was designed from a blank file, working across research, IA, UI, and the live website.
✦
POSITIVE PILOT FEEDBACK
All 7 pilot studios have provided consistently positive feedback. Official onboarding is planned within the next few months, following completion of full lifecycle testing across active production.
//
//
//
//
10
10
10
10
REFLECTION
REFLECTION
REFLECTION
REFLECTION
WHAT I
WHAT I
WHAT I
DESIGN INSIGHT
DESIGN INSIGHT
"Expert users don't resist automation. They resist automation they can't see through."
"Expert users don't resist automation. They resist automation they can't see through."
"Expert users don't resist automation. They resist automation they can't see through."
The Dual Path architecture worked because it made the AI's reasoning legible, not just its outputs. Every Flixxi-generated task came with context a lead could evaluate. Transparency was the feature, not automation.
The Dual Path architecture worked because it made the AI's reasoning legible, not just its outputs. Every Flixxi-generated task came with context a lead could evaluate. Transparency was the feature, not automation.
The Dual Path architecture worked because it made the AI's reasoning legible, not just its outputs. Every Flixxi-generated task came with context a lead could evaluate. Transparency was the feature, not automation.
PROCESS INSIGHT
PROCESS INSIGHT
"Designing a platform is designing a belief system about how work should flow."
"Designing a platform is designing a belief system about how work should flow."
"Designing a platform is designing a belief system about how work should flow."
Every IA decision in OriginX reflects a conviction about how studios operate. The sidebar, the topbar Flixxi widget, the six-module structure — each was an argument about workflow, not just an organizational choice.
Every IA decision in OriginX reflects a conviction about how studios operate. The sidebar, the topbar Flixxi widget, the six-module structure — each was an argument about workflow, not just an organizational choice.
Every IA decision in OriginX reflects a conviction about how studios operate. The sidebar, the topbar Flixxi widget, the six-module structure — each was an argument about workflow, not just an organizational choice.
THE SYSTEM
THE SYSTEM
THE SYSTEM
originx.studio
originx.studio