Idaratech · ERP / Project Management
2025 - 2026
Designing a Scalable Project Management Platform from 0→1
I led the product design of Idaratech's Project Management platform from 0→1, working across product, engineering, and QA from product definition through implementation. The experience needed to support complex planning and execution workflows while remaining intuitive across roles, flexible enough for different organizations, and ready to scale across the ERP ecosystem.
Overview
Designing the foundation for project operations
The goal was to create a scalable project management experience that could support complex planning and execution workflows while remaining intuitive across different roles and organizations.
I focused on establishing clear interaction patterns and reusable foundations that could scale with the ERP ecosystem.
Scalable Workspace
Make a growing project portfolio easy to scan, shape, and manage
As project portfolios grow, teams need to understand what matters before navigating into individual projects.
I designed the workspace around three principles: surface important information early, let teams shape the workspace around their workflow, and keep project setup focused without limiting future configuration.
Important project information is visible before deeper navigation.
Executable Work
Turn task records into a place where work moves forward
A task should contain enough context for someone to understand what needs to happen, take action, and stay aligned with everyone involved.
I designed Task Details as the working context for execution—bringing ownership, status, priority, dates, description, subtasks, followers, and attachments together without overwhelming the primary workflow.
Centralize the context needed to execute
The task became more than a record of work. It became the place where people could understand ownership, update progress, review supporting information, and continue execution without unnecessary navigation.
Keep collaboration attached to the work
Comments, mentions, files, and activity were designed inside Task Details rather than separated into another destination. This keeps discussion, decisions, and supporting material connected to the work they explain.
Project Visibility
Make project progress easy to understand
Teams need more than a list of tasks to understand whether a project is moving forward. I designed a clear planning layer that connects milestones, progress, and project status so teams can quickly understand where a project stands without reviewing every task.
The goal was to make progress visible without turning project management into another reporting task.
Milestones create the planning layer above individual tasks, while progress connects that view back to the work underneath. Together, they give teams a shared view of delivery without requiring constant manual status updates.
Turn detailed work into clear project signals
Milestones give teams a shared view of important delivery points, while progress makes movement visible at a glance. The result is a simpler way to discuss project health, identify where attention is needed, and stay aligned without losing the detail of the underlying work.
Different Ways of Working
One work model, shaped for different ways of working
Teams don’t all manage work the same way. I designed List and Kanban as different ways to interact with the same underlying work—giving teams a structured view for scanning and organizing tasks, and a visual view for managing flow and status.
The challenge was keeping both views consistent so changing the way work is displayed never changed how the work itself behaved.
A dense, structured view for teams that need to scan, sort, group, and manage work precisely.
A visual view for teams that need to understand work in motion and move tasks through the workflow quickly.
Comments and mentions bring collaboration directly into the task, keeping questions, decisions, and team updates connected to the work they relate to.
Designing for Scale
Build foundations that scale beyond one product
As the product grew, I focused on patterns that could be reused beyond Project Management rather than solving each interaction independently.
This meant creating consistent behaviors for statuses, notifications, components, and RTL while keeping the experience flexible enough for different workflows. The goal was to make new features easier to design, easier to implement, and more consistent as the ERP ecosystem expands.