Architecture teams face challenges with scattered information and complex project coordination, leading to inefficiency and disrupted workflows.
How
An integrated notes for capturing ideas; a task manager for internal and external collaborations; a dynamic Gantt chart for visualizing timelines
Final Design
Internal Community
Internal Library Resources / Project Detail
Project Detail/Tasks
Notes
Users can capture their thoughts effortlessly with Notes, enabling informal, note-taking to fostercreativity and management. Start from scratch or utilize pre-saved templates for quick access to structured formats.
Coordinating long-term architecture projects is challenging, especially for high-rise buildings that can take up to seven years and involve frequent management changes. Keeping project timelines aligned and stakeholders—architects, project managers, engineers, and consultants—synchronized is complex and crucial.
Current workflow metric - Architect Daily
Existing Tool Failed
Insights
Existing workflow and current market solutions failed at Internal-External Collaboration
1
External Key Users Treated as Guest
Tools like Asana and Monday.com are built around internal teams, classifying all non-employees as limited “guests.” But in industries like AEC, external collaborators, consultants, engineers, client reps are treated as outsiders.
2
Information Loss
Hard to track internal responsibilities from emails in a years project Project knowledge is scattered across emails, what’s app, calls. When team members leave, their knowledge and records are lost.
3
Misalignment
In different design stages, project all involves 5+ stakeholders. Keeping all stakeholders aligned is difficult. Misalignment leads to project delays and increased costs.
Address Challenges Challenges in coordinating projects among 5+ stakeholders
Solutions - Project Task Board
Prototype Study
First Round Design
MVP Post Launch User Testing
We conducted a controlled MVP trial with a mid-sized architecture firm consisting of six team members (1 PM, 1 PA, and 4 architects). We extended the trial to include external stakeholders, 2 structural engineers, 1 architecture record, and 1 landscape.
2 week usage activity logging monitor #1 User left the Subtask empty #2 User duplicate the task card for internal use and external updates
Refocus on High-Value Users Position the product as a coordination tool for cross-functional teams
Iteration
Second Round Iteration
Final HiFi
Highlights
Home
Reports
My Tasks
My Tasks offers users a centralized view of all their tasks across projects. Users can also customize task categories to suit their workflow preferences.
Notes
Retrospective
Testable Assumption
Several of our initial key assumptions didn’t meet expectations. This experience taught us that establishing a flexible, testable product lifecycle is essential. It allows us to validate ideas quickly, learn from them, and pivot as necessary.
Product Thinking
Learn to understand how to design an experience that would lead to good business outcome, help user to understand the value of the product, which requires understanding of the user motivation and comprehension.
