Hello! Welcome to the first lesson in our new module, "Designing People-Centric Systems."
In the previous module, we focused on the core operational systems of a business, culminating in designing an automated workflow that connects your CRM to your project management database. Now, we shift our focus from client delivery to internal, people-focused processes. These systems are just as critical for a company's ability to scale effectively.
Today's learning outcome is to design the database architecture for a scalable, centralized onboarding hub. We will move beyond a simple checklist and design a robust, interconnected system of databases that can manage the entire onboarding journey, accommodate company growth, and provide a great experience for new hires. This aligns directly with your expertise in process improvement, applying it to human resources.
1. The Strategic Foundation: Why a Centralized Hub?
Before we start building, let's make our first architectural decision. A common mistake is to create separate, disconnected onboarding lists for each department or new hire. From a process standpoint, this creates data silos, inconsistencies, and makes tracking impossible.
The superior approach is a centralized hub. This strategy involves creating a single source of truth for all employee and onboarding data, which is then filtered and displayed in different ways depending on the context.
The following article on building knowledge hubs outlines the strategic planning needed for such a system. While it's about knowledge hubs, the principles of planning and architecture are directly applicable to our onboarding hub.
The ultimate guide to AI-powered knowledge hubs in Notion
Read the first section of 'The ultimate guide to AI-powered knowledge hubs in Notion' to understand the strategic planning phase.
Read the section titled 'Set your hub strategy and get stakeholder alignment'. Focus on the key questions: who will use the hub, what information will they find, and why is it being built? This strategic mindset is the starting point for any scalable system.
This planning phase leads us to a clear architectural model: a set of interconnected databases that act as the backbone of our onboarding system.
2. Core Database Architecture
A scalable onboarding hub isn't a single database; it's a constellation of related databases. For our design, we'll plan for three primary databases:
Employees: This will be our central directory and the single source of truth for every person in the organization. Each new hire is an entry here.Departments: A simple database to list all company departments. This allows us to create department-specific onboarding experiences.Onboarding Tasks: A master database of every possible onboarding task, which we can then assign to new hires based on their role and department.
The power of this architecture comes from connecting these databases with relations. This core principle ensures data integrity and avoids redundant work—a concept you may recall from our first module. For a powerful refresher on why this relational approach is superior to keeping everything in one giant table, please review the following video.
3 Principles for Building Notion Databases like a Pro
The video '3 Principles for Building Notion Databases like a Pro' by Julian Post excellently explains the fundamental rules of good database design. We'll focus on the second principle, which is the heart of our architecture.
Watch the segment from 05:43 to 09:20, which covers the principle 'Eliminate redundant work with relations and Roll-Ups.' Pay close attention to how creating a separate database for 'Content Types' and linking it via a relation allows for more powerful and maintainable workflows. We will apply this exact logic to our Departments and Onboarding Tasks.
3. Designing the Employees Database
The Employees database is the heart of our system. It will contain properties that track a new hire's journey and link to other key data.
Here is a visual example of how Employees and Departments databases can be structured and linked.
Based on this model and best practices, here are the essential properties for your Employees database design:
Employee Name(Title property)Status(Select or Status property: e.g., "Pre-boarding," "Onboarding," "Active," "Archived")Department(Relation property, linked to yourDepartmentsdatabase)Start Date(Date property)Hiring Manager(Person property)Onboarding Tasks(Relation property, linked to yourOnboarding Tasksdatabase)Onboarding Progress(Rollup property, configured to show the percentage of completedOnboarding Tasks)
This structure ensures that all critical information about an employee's onboarding is centralized in one place.
Test your understanding!
A client wants to add a "Buddy" system to the onboarding hub. The buddy is an existing employee who helps the new hire. From an architectural standpoint, how would you implement this? What database(s) and property/properties would you add or modify?
Show answer
The most efficient architectural choice is to modify the existing Employees database. You would add a new Person property called "Buddy". When a new hire is added, you can assign an existing workspace member as their buddy in this property. No new database is needed. This keeps the Employees database as the central source of truth for all information related to a person, including their support network.
4. Standardizing for Scale with Templates
With the database architecture in place, how do we ensure a consistent and scalable process for every new hire? The answer is database templates.
We will design a template within the Employees database that automatically sets up a new hire's personal onboarding page. This page becomes their dashboard for their entire first few weeks.
The following guide and video from Notion provide excellent practical examples of what to include in such a template.
Grow with quality using these systems to track applicants ...
Notion's guide 'Grow with quality using these systems to track applicants ...' offers great suggestions for properties and template content for a new hire onboarding system.
Scan through sections 2, 3, and 4. Specifically, focus on the lists under 'More properties & views for your New Hire Onboarding,' the customization options under 'For new hire onboarding' (like to-do lists and linking pages), and the template ideas under 'Templates for your New Hire Onboarding.' This will give you a catalogue of components to include in your design.
This guide mentions creating team-specific templates. The next video demonstrates this powerful concept in action, showing how you can create a base template and then duplicate and customize it for different departments.
How to run onboarding in Notion
The official Notion video 'How to run onboarding in Notion' shows how to create and use database templates to scale the onboarding process.
Watch from 05:31 to 08:54. Observe how a generic onboarding checklist is created and then turned into a reusable template. Pay special attention to the strategy of duplicating this template to create department-specific versions (e.g., for 'Product & Engineering' and 'Marketing'). This is a key technique for scaling your hub.
Your final design for the "New Hire" template should include:
- A welcome message.
- Key information (e.g., a rollup showing their Hiring Manager and Start Date).
- Checklists for key phases (e.g., "Before you Start," "First Week").
- A linked view of the
Onboarding Tasksdatabase, pre-filtered to show only the tasks assigned to "This Page" (the new hire).
Conclusion
In this lesson, you designed the complete database architecture for a scalable, centralized onboarding hub. You've made key strategic decisions and mapped out the interconnected components required to build a system that goes far beyond a simple checklist.
Key Takeaways:
- Centralized Architecture: A scalable onboarding system is built on a centralized
Employeesdatabase as the single source of truth. - Relational Design: Separate databases for
DepartmentsandOnboarding Tasks, connected via relations, are crucial for avoiding data duplication and enabling powerful, flexible features. - The Power of Templates: Database templates are the key to standardizing the onboarding process, ensuring every new hire gets a consistent, high-quality experience with minimal administrative overhead.
- Rollups for Visibility: Using rollups, you can automatically track progress (like percentage of tasks completed), providing at-a-glance visibility for HR and managers.
In our next lesson, we will build upon this architecture. You will learn how to create dynamic dashboard templates that surface personalized onboarding tasks for new team members. We'll take the template you designed today and turn it into a truly interactive and user-friendly experience for your new hires.