Mon Dada Operating System
August 1, 2024
Mon Dada needed more than just a place to store files; they needed a Single Source of Truth. I designed a complete internal operating system that connects distinct business units—sales, production, and marketing—into one fluid ecosystem.
The goal was to move from scattered spreadsheets to a “Linked Database” architecture where information flows automatically between departments.
System Architecture
Instead of isolated pages, the workspace is built on a “Master Database” logic. Here is the structural hierarchy of the workspace:
The Interface
I prioritized a visual-first interface to ensure high adoption rates among the team. The dashboard serves as a central hub, reducing the “where did I save that?” friction.
Key Workflows Solved
Connected Corporate CRM
I created a robust database for gathering corporate clients using relational properties. By linking clients directly to their specific projects and meeting notes, I ensured that all relevant account history is retrievable in seconds. As well as making clear which clients have current projects, which ones are prospects, and which ones are irrelevant.
Social Media Planner
To manage Mon Dada's digital presence, I built a content planner. It acts as my central command center for drafting and scheduling, ensuring our social media strategy remains organized and consistent.
Centralized Meeting Hub
To improve transparency, I implemented a master meeting database. This allowed the team to easily find and filter notes by date or participant (solving a key navigation issue prior to Notion's "Home" update).
Company Resource Wiki
I expanded the workspace to act as a complete intranet, building specific pages for HR (employee data), a digital Brand Stylebook to enforce design standards, and launch hubs for New Collections.
Adoption Strategy
A tool is only useful if people use it. To ensure success:
- Templates: Created templates for “New Client” or “New Meeting Note” to lower resistance.
- Training: Conducted hands-on workshops to transition the team from email-based workflows to Notion-based collaboration.
