10 min read
Toggle for a short version
New Conceptualized Module Template
New Conceptualized Module Template
From Chaos to Clarity: Simplifying 3K+ Construction Tasks
From Chaos to Clarity: Simplifying 3K+ Construction Tasks
1. Introduction
In this project, I led the complete overhaul of the Module Template—starting with user interviews to uncover pain points, followed by back-and-forth discussions with the PM, founder, and team to refine the solution.
In this project, I led the complete overhaul of the Module Template—starting with user interviews to uncover pain points, followed by back-and-forth discussions with the PM, founder, and team to refine the solution.
Company
Company
LivSYT
LivSYT
Type
Type
Revamp & Enhancement
Revamp & Enhancement
Platform
Platform
Web Application
Web Application
2. The Discovery Phase
Before jumping into solutions, we needed to understand why the existing Module Template was failing.
Before jumping into solutions, we needed to understand why the existing Module Template was failing.
2 (a). User Feedback with overall Audit
After reviewing the existing system and with some user interviews, several key usability flaws were identified, directly impacting task management efficiency and user experience.
After reviewing the existing system and with some user interviews, several key usability flaws were identified, directly impacting task management efficiency and user experience.
First
Second
Third
No Clear Timeline View & Flow of Task
Kanban-based workflows are not scalable for construction, where projects often involve 3,000+ tasks.
Users struggle to prioritize tasks due to a lack of clear categorization or hierarchy.
First
Second
Third
No Clear Timeline View & Flow of Task
Kanban-based workflows are not scalable for construction, where projects often involve 3,000+ tasks.
Users struggle to prioritize tasks due to a lack of clear categorization or hierarchy.
First
Second
Third
No Clear Timeline View & Flow of Task
Kanban-based workflows are not scalable for construction, where projects often involve 3,000+ tasks.
Users struggle to prioritize tasks due to a lack of clear categorization or hierarchy.
2 (b). User Expectations vs. Reality
While the Module Template promised to streamline project planning, our research revealed a gap between what users needed and what the system delivered. Here’s how real-world usage fell short of expectations:
While the Module Template promised to streamline project planning, our research revealed a gap between what users needed and what the system delivered. Here’s how real-world usage fell short of expectations:
3. The Problem
"So... how exactly are you going to make handling 3K+ construction tasks easier while reducing errors?"
—my manager asked, arms crossed, eyebrows raised. It wasn’t just a casual question—it was a challenge.
—my manager asked, arms crossed, eyebrows raised. It wasn’t just a casual question—it was a challenge.
"The Module Template struggled to handle large-scale construction projects—manual setup, rigid dependencies, and the lack of a clear timeline led to inefficiencies, errors, and constant workarounds"
4. Defining Success
How do we know if we have solved anything?
5. Research
We studied platforms like JIRA, Monday.com, and ClickUp, along with construction-specific solutions like Planera, to identify best practices and potential improvements.
We studied platforms like JIRA, Monday.com, and ClickUp, along with construction-specific solutions like Planera, to identify best practices and potential improvements.
5 (a). Key Focus Areas in Competitive Analysis
5 (b). Findings
We studied platforms like Monday.com, and ClickUp, JIRA, along with construction-specific solutions like Planera, Gantt Pro to identify best practices and potential improvements.
We studied platforms like Monday.com, and ClickUp, JIRA, along with construction-specific solutions like Planera, Gantt Pro to identify best practices and potential improvements.
i). Flexible Task Hierarchy
Platforms allow seamless creation and modification of tasks, subtasks, and activities with clear parent-child relationships.
ii). Dependency Management
iii). Quick Actions
iv). Multiple Views
v). In line properties mapping
i). Flexible Task Hierarchy
Platforms allow seamless creation and modification of tasks, subtasks, and activities with clear parent-child relationships.
ii). Dependency Management
iii). Quick Actions
iv). Multiple Views
v). In line properties mapping
i). Flexible Task Hierarchy
Platforms allow seamless creation and modification of tasks, subtasks, and activities with clear parent-child relationships.
ii). Dependency Management
iii). Quick Actions
iv). Multiple Views
v). In line properties mapping
6. Design
Armed with insights from our audits, & industry research, the next step was to iterate.
Armed with insights from our audits, & industry research, the next step was to iterate.
The Design Answer to ‘How Do We Make 3K Tasks Effortless?
The Design Answer to ‘How Do We Make 3K Tasks Effortless?
New Module Template Page
New Module Template Page
a). Table or Gantt View—Your Choice
a). Table or Gantt View—Your Choice
We gave users the freedom to choose how they manage projects. Whether it's the structured table view for quick task creation or the Gantt view for a clearer timeline, switching between them is seamless—offering the best of both worlds.
We gave users the freedom to choose how they manage projects. Whether it's the structured table view for quick task creation or the Gantt view for a clearer timeline, switching between them is seamless—offering the best of both worlds.
Problem Solved
By offering both Table and Gantt views, we gave users the flexibility to create tasks in a familiar table format while visualizing dependencies and project flow in a clear timeline.
Problem Solved
By offering both Table and Gantt views, we gave users the flexibility to create tasks in a familiar table format while visualizing dependencies and project flow in a clear timeline.
Problem Solved
By offering both Table and Gantt views, we gave users the flexibility to create tasks in a familiar table format while visualizing dependencies and project flow in a clear timeline.
b). Main Table View
b). Main Table View
We moved from a limiting Kanban board to a more dynamic table view—giving users a bird’s-eye view of every task, subtask, and activity in one place. Now, you can effortlessly scroll through and manage key details like roles and dependencies without the hassle of diving into multiple screens.
Plus, users can easily convert any subtask into an activity (or vice versa) without starting from scratch.
We moved from a limiting Kanban board to a more dynamic table view—giving users a bird’s-eye view of every task, subtask, and activity in one place. Now, you can effortlessly scroll through and manage key details like roles and dependencies without the hassle of diving into multiple screens.
Plus, users can easily convert any subtask into an activity (or vice versa) without starting from scratch.
Problem Solved
Kanban made it difficult to track and manage large-scale projects. The new table view provides a clearer, more organized way to navigate complex task structures, improving visibility and reducing friction.
Problem Solved
Kanban made it difficult to track and manage large-scale projects. The new table view provides a clearer, more organized way to navigate complex task structures, improving visibility and reducing friction.
Problem Solved
Kanban made it difficult to track and manage large-scale projects. The new table view provides a clearer, more organized way to navigate complex task structures, improving visibility and reducing friction.
c). Gantt View
c). Gantt View
We introduced a Gantt view that mirrors the task hierarchy—Tasks → Subtasks → Activities—while offering a clear visual timeline of the project. This view helps users understand the flow of work, track dependencies, and manage schedules without losing sight of task details.
We introduced a Gantt view that mirrors the task hierarchy—Tasks → Subtasks → Activities—while offering a clear visual timeline of the project. This view helps users understand the flow of work, track dependencies, and manage schedules without losing sight of task details.
Problem Solved
Kanban and tables showed the "what," but not the "when." The Gantt view adds a time dimension, giving users a clear picture of task sequences and project timelines.
Problem Solved
Kanban and tables showed the "what," but not the "when." The Gantt view adds a time dimension, giving users a clear picture of task sequences and project timelines.
Problem Solved
Kanban and tables showed the "what," but not the "when." The Gantt view adds a time dimension, giving users a clear picture of task sequences and project timelines.
d). Separate Checkpoints
d). Separate Checkpoints
We introduced a dedicated Checkpoints table to handle the unique, non-linear nature of construction milestones. Users can now create and manage multiple checkpoints independently and link them to any Task, Subtask, or Activity without backend intervention. This provides greater flexibility and ensures critical milestones are always tracked accurately.
Problem Solved
Previously, managing checkpoints within the task structure was messy and required backend hacks for complex workflows. By separating checkpoints, we gave users the freedom to map and track milestones across any stage, reducing errors and making the system far more adaptable.
Problem Solved
Previously, managing checkpoints within the task structure was messy and required backend hacks for complex workflows. By separating checkpoints, we gave users the freedom to map and track milestones across any stage, reducing errors and making the system far more adaptable.
Problem Solved
Previously, managing checkpoints within the task structure was messy and required backend hacks for complex workflows. By separating checkpoints, we gave users the freedom to map and track milestones across any stage, reducing errors and making the system far more adaptable.
e). Introducing Smart Dependencies
e). Introducing Smart Dependencies
We enabled all four dependency types—Finish-to-Start (FS), Start-to-Start (SS), Finish-to-Finish (FF), and Start-to-Finish (SF)—allowing users to create accurate task relationships directly within the platform.
We enabled all four dependency types—Finish-to-Start (FS), Start-to-Start (SS), Finish-to-Finish (FF), and Start-to-Finish (SF)—allowing users to create accurate task relationships directly within the platform.
Problem Solved
Previously, teams relied on backend workarounds to set task dependencies, making the system rigid and error-prone. With smart dependencies, users can now map real-world project flows seamlessly, ensuring better planning and smoother execution.
Problem Solved
Previously, teams relied on backend workarounds to set task dependencies, making the system rigid and error-prone. With smart dependencies, users can now map real-world project flows seamlessly, ensuring better planning and smoother execution.
Problem Solved
Previously, teams relied on backend workarounds to set task dependencies, making the system rigid and error-prone. With smart dependencies, users can now map real-world project flows seamlessly, ensuring better planning and smoother execution.
f). Advanced Search
f). Advanced Search
We introduced a powerful search feature that lets users filter and locate information across all columns—whether it's tasks, activities, roles, or dependencies.
We introduced a powerful search feature that lets users filter and locate information across all columns—whether it's tasks, activities, roles, or dependencies.
Problem Solved
Finding specific data in large project plans was tedious and time-consuming. With advanced search, users can quickly access the exact information they need, enhancing efficiency and reducing errors.
Problem Solved
Finding specific data in large project plans was tedious and time-consuming. With advanced search, users can quickly access the exact information they need, enhancing efficiency and reducing errors.
Problem Solved
Finding specific data in large project plans was tedious and time-consuming. With advanced search, users can quickly access the exact information they need, enhancing efficiency and reducing errors.
g.) Quick Actions for Faster Execution
g.) Quick Actions for Faster Execution
We added a quick action menu on each line item, allowing users to instantly create tasks below, duplicate (with or without child items), delete, or add new entries and etc.
We added a quick action menu on each line item, allowing users to instantly create tasks below, duplicate (with or without child items), delete, or add new entries and etc.
Problem Solved
Previously, making changes required multiple steps and manual inputs. With quick actions, users can now modify project plans faster, reducing repetitive work and improving overall efficiency.
Problem Solved
Previously, making changes required multiple steps and manual inputs. With quick actions, users can now modify project plans faster, reducing repetitive work and improving overall efficiency.
Problem Solved
Previously, making changes required multiple steps and manual inputs. With quick actions, users can now modify project plans faster, reducing repetitive work and improving overall efficiency.
h). Bulk Edit
h). Bulk Edit
We introduced bulk editing through checkboxes, allowing users to select multiple line items and update shared attributes like roles or durations simultaneously.
We introduced bulk editing through checkboxes, allowing users to select multiple line items and update shared attributes like roles or durations simultaneously.
Problem Solved
Editing tasks one by one was time-consuming and error-prone. With bulk edit, users can now make large-scale updates quickly, saving time and ensuring consistency across project plans.
Problem Solved
Editing tasks one by one was time-consuming and error-prone. With bulk edit, users can now make large-scale updates quickly, saving time and ensuring consistency across project plans.
Problem Solved
Editing tasks one by one was time-consuming and error-prone. With bulk edit, users can now make large-scale updates quickly, saving time and ensuring consistency across project plans.
7. The Conclusion
7. The Conclusion
"Amit, this is exactly what we wanted!"—these words from our Chief of Operations hit differently.
"Amit, this is exactly what we wanted!"—these words from our Chief of Operations hit differently.
Preview: Before Vs After
Preview: Before Vs After
Impact
The revamped Module Template significantly improved efficiency—cutting down the time to configure new templates by over 50%.
We eliminated the need for constant backend support, giving more power to our clients and internal teams.
Both the operations and our clients praised the update for its intuitive flow, useful shortcuts, and how easy it became to use—a true shift from friction to flow.
I asked to my COO, “Can you create tasks more efficiently now? Are those backend workarounds finally gone?”
I asked to my COO, “Can you create tasks more efficiently now? Are those backend workarounds finally gone?”
COO said, “Not only can I create tasks effortlessly, but I’m actually enjoying it. It’s fast, intuitive, and feels on par with the best tools out there. And yes—no more calls to the backend team!”
COO said, “Not only can I create tasks effortlessly, but I’m actually enjoying it. It’s fast, intuitive, and feels on par with the best tools out there. And yes—no more calls to the backend team!”
This was one of the most complex design challenges I’ve faced. It pushed me to my limits—but I wasn’t alone. My manager, PV, was a constant guide, providing clarity when things got messy. The thorough audit and extensive research became the bedrock of our success, allowing us to design not just for today but for the future.
This was one of the most complex design challenges I’ve faced. It pushed me to my limits—but I wasn’t alone. My manager, PV, was a constant guide, providing clarity when things got messy. The thorough audit and extensive research became the bedrock of our success, allowing us to design not just for today but for the future.
Since the design and solution were quite complex, it took nearly 3 months of repeated UI reviews and QA testing before we could finally release the feature to all clients. My role didn’t end at just the design—I was actively involved throughout the process, ensuring the feature met expectations until the final release
Since the design and solution were quite complex, it took nearly 3 months of repeated UI reviews and QA testing before we could finally release the feature to all clients. My role didn’t end at just the design—I was actively involved throughout the process, ensuring the feature met expectations until the final release
