1. Executive Summary
Mindbody needed specialized tooling to manage content across a large franchise network. The system had to let corporate teams create reusable marketing content, group content by tags, distribute it across many child studio accounts, and still allow local studios to customize content for their own location.
The design problem was governance, not content editing. Users needed to understand who controlled what, which studios inherited which content, how tags connected content and companies, when changes were pushed, and how centralized content became locally relevant.
2. System Context
Mental model:
Mindbody Admin -> Corporate Users -> Studio / Staff Users
Content types included journeys, segments, email templates, campaigns, brand assets, sign-up units, and brand-kit values.
The system connected parent companies, corporate companies, studio companies, tags, content groups, content items, company variables, push/publish actions, sync status, and history.
3. The Real Problems
Enterprise hierarchy made content ownership hard to understand. Corporate users needed to know which level controlled content, which level received content, and which local edits remained under studio control.
Tags created tiered content membership. Tags could classify content and companies across tiers, appointment types, regions, languages, verticals, or franchise-specific needs.
Centralized content still needed local relevance. Studios needed editable drafts and local variables such as booking URLs, phone numbers, location names, and social links.
Governance actions had downstream consequences. Adding a tag, removing a tag, adding content, or publishing changes could affect many child studios.
4. Design Principles
- Enterprise platform design depends on making relationships visible.
- Governance should be explicit before changes are distributed downstream.
- Central control and local autonomy can coexist when variability is structured.
- Tags can act as governance metadata, not just labels.
- Publishing actions should explain consequences before they happen.
- Sync visibility and source indicators build operational trust.
5. Major Decisions
Make Tags The Connective Tissue
One-off content-to-company assignment would not scale across many studios and changing franchise structures. Tags became the relationship layer between content and companies.
This made the system flexible, but also more abstract. The interface needed to show which content and companies were connected by a tag and what would happen when membership changed.
Balance Central Governance With Local Autonomy
Fully locked corporate content would be too rigid. Fully local content creation would be too hard to govern.
The model pushed content to studios as editable drafts, with company variables or macros providing local details. This created controlled variability: centralized templates plus structured local values.
Make System Consequences Visible
The design needed to show sync status, source indicators, tag history, and prompts explaining what would happen before changes were pushed.
Complex admin systems need previewable consequences, not only completion states.
Support Manual Push / Publish
Automatic sync on every change could create confusion or accidental downstream changes. Explicit push/publish behavior created a deliberate checkpoint before high-impact changes were distributed.
6. System Evolution
Requirements / RFC
-> hierarchy and tag model
-> content/company IA
-> push/publish workflow
-> sync visibility and operational trust
The model moved toward Content and Companies as primary concepts, with tags managed in context as the relationship layer.
7. Collaboration Model
I worked with product, backend engineering, frontend engineering, Mindbody admin stakeholders, Mindbody product stakeholders, and Solutions Engineering.
The RFC captured many technical and business requirements. My design challenge was translating those requirements into a product model that Mindbody Admins and Corporate Users could understand, trust, and operate.
8. Results
Product outcomes:
- Helped define enterprise franchise content governance workflows.
- Translated hierarchy, tags, sync, source, and publishing requirements into a usable product model.
- Moved the IA toward Content and Companies as primary concepts with tags managed in context.
Business outcomes:
- Supported tooling for onboarding and managing a large franchise network.
- Supported corporate control while preserving local studio customization.
9. Reflection
This project sharpened a platform design principle: governance is often metadata plus consequences.
Tags, source indicators, publish actions, sync status, and history are not administrative details. They are the user's mental model for how control moves through the system.
10. Reusable Patterns
- Tag-based inheritance.
- Parent/child hierarchy model.
- Controlled variability.
- Editable draft distribution.
- Company variables and macros.
- Manual push/publish.
- Source indicators.
- Sync status.
- Governance through metadata.
- Consequence-preview prompts.
11. Lessons That Carried Forward
Mindbody reinforced a lesson that also appears in integration work, EDS, and Data Health: users need to understand relationships and consequences before they can trust a system.