Ninox Navigation Redesign 

Transforming a Database Tool into a Unified Software Experience

Ninox, a low-code development platform, was evolving from its origins as a flexible database tool into a comprehensive ERP solution provider. As Head of Product Design, I was tasked with reimagining the platform's navigation and information architecture to support this strategic shift while preserving the core principles that made Ninox unique. This case study explores how we transformed a collection of disconnected database projects into a cohesive software suite experience without compromising the platform's founding philosophy.

Problem

Ninox's customers were increasingly building sophisticated ERP solutions on a platform originally designed for discrete database projects. The existing navigation structure couldn't scale to handle this complexity, making the platform feel like a disjointed collection of databases rather than a unified software suite. While separating developer and end-user experiences seemed logical, this approach would violate the platform's core WYSIWYG principles.

Solution

We developed a flexible navigation framework that preserved direct manipulation while allowing developers to create experiences that felt like complete, custom-built software to end-users. The new architecture unified previously disconnected database projects into a coherent system while honoring the platform's founding principles of direct manipulation and WYSIWYG editing.

Results

• Increased enterprise adoption without sacrificing the platform's identity
  
• Enhanced user experience for both developers and end-users
  
• Created a scalable framework that could accommodate growing feature complexity
  
• Preserved the core differentiating factors that made Ninox unique in the market

Understanding the Challenge

When I joined Ninox in 2023, the platform was at a critical inflection point. What had started as a flexible no-code database builder had evolved as customers began using it to create increasingly sophisticated business applications. Enterprise clients were building entire ERP systems across multiple linked databases, but the interface still treated each component as a separate project.

End-users struggled with context-switching between different databases that were functionally parts of the same application. Meanwhile, developers found it challenging to create experiences that felt like cohesive software solutions rather than collections of connected databases.

The most obvious solution—creating separate modes for developers and end-users—had already been considered but never implemented. My first task was to understand why.

Uncovering the Core Philosophy

Through conversations with the CEO/founder, long-time customers, and by reviewing available documentation, I discovered that the direct manipulation approach was central to Ninox's identity. The founder had a clear vision that users should always be working with the actual product, not abstractions or separate building environments.

This WYSIWYG philosophy wasn't just a feature—it was Ninox's key differentiator in the market. Creating separate "builder" and "user" modes would fundamentally alter what made the platform special, even if it solved our immediate navigation challenges.

I documented these core principles to guide our design process:

• Direct manipulation of the final product
  
• No separation between building and using
  
• Visual programming without code
  
• The flexibility to create custom solutions without technical expertise

Research: Understanding User Workflows

With these constraints in mind, I conducted research to understand how different user types actually used the platform:

1. Customer Interviews
   I spoke with developers who had built complex solutions on Ninox and the end-users who worked with those solutions daily.
   
2. Usage Analysis
   Working with limited analytics (due to privacy constraints), we identified patterns in how users navigated between databases and features.
   
3. Workflow Mapping
   We documented the most common user journeys, identifying where navigation created friction versus where it supported natural workflows.
   

A key insight emerged: While developers needed to think in terms of database structure, end-users thought in terms of tasks and processes that often spanned multiple databases. Our navigation needed to support both mental models simultaneously.

Iterative Design Process

I created a series of prototypes, starting with simple wireframes and progressing to high-fidelity mockups. Key design decisions included:

• Simplified Availability Creation:
  Pastors could create a single multi-day entry and select multiple cemetery options
  
• Cemetery-Specific Rules:
  Each cemetery's operating hours were pre-configured in the system
  
• Resource Integration:
  The system checked for conflicts with church spaces, not just pastoral schedules
  
• Language Sensitivity:
  Using "booking inquiries" rather than "bookings" to reinforce pastor autonomy
  
• Follow-up Automation:
  Building in requests for additional documentation like death certificates

After several iterations and usability tests with pastors, we refined the interface to balance comprehensive functionality with intuitive use.

The Solution: A Unified Framework

Rather than creating separate modes, we developed a flexible navigation framework that could adapt to different contexts while maintaining the direct manipulation approach:

1. Unified Global Navigation
   Instead of a collection of databases, we created a unified global navigation system that could be customized by developers to give their end-users the sense that they are using a cohesive software and not a solution developed on a different platform. 
   
2. Context-Aware Navigation
   The navigation adapted based on the current workflow, showing relevant tools and connections without forcing users to understand the underlying database architecture.
   
3. Consistent Interface Elements
   We standardized navigation patterns, ensuring that moving between different areas of the application felt seamless rather than disjointed.
   
4. Customization Options
   Developers gained tools to customize the navigation experience for their end-users through color and logos, creating the appearance of purpose-built software while preserving direct editing capabilities.

Implementation and Results

The new navigation framework was implemented over several releases, allowing for user adjustment and ongoing refinement. The results were substantial:

1. Increased Enterprise Adoption
   The more cohesive experience appealed to enterprise clients looking for comprehensive business solutions.
   
2. Improved User Experience
   End-users reported feeling like they were using a single, purposeful application rather than jumping between database projects.
   
3. Faster Development
   Developers could create more sophisticated solutions that felt like custom software without sacrificing the direct manipulation approach.
   
4. Preserved Platform Identity 
   Most importantly, we achieved these improvements while maintaining the core WYSIWYG philosophy that made Ninox unique.

Key Learnings

This project reinforced several important principles that I've carried forward in my design leadership:

1. Philosophy and Practicality
   Understanding a product's core philosophy is essential when evolving its experience. The most obvious solution isn't always aligned with what makes a product special.
   
2. Research Adaptability
   When traditional analytics aren't available due to privacy constraints, creative research approaches become essential.
   
3. Mental Models Matter
   Supporting different mental models simultaneously is challenging but possible with thoughtful architecture.
   
4. Continuity in Change
   Even significant experience transformations must maintain enough continuity that existing users can adapt easily.
   

This navigation redesign established design as a core strategic function at Ninox, giving it parity with product and engineering teams, and positioned the platform for its next phase of growth in the enterprise market.