Abstract
Modern design studios increasingly operate in a distributed fashion, relying on a diverse array of digital tools for communication, file sharing, and project management. However, this reliance often leads to "information fragmentation," where critical project data is scattered across multiple platforms. This paper introduces Peepdeck, a specialized dashboard designed to aggregate data from existing tools into a single, glanceable interface. Through a user-centered design process involving 14 professional designers, we demonstrate that a "source-agnostic" approach to information display can enhance collaboration awareness and reduce the cognitive load associated with tool-switching.
Introduction
The contemporary design landscape is characterized by distributed teams working across various time zones and platforms. While general-purpose tools like Slack, Dropbox, and Trello are powerful, their collective use often results in a fragmented workflow. Designers frequently struggle to maintain a holistic "overview" of their projects, spending significant mental effort navigating between applications to find files, track deadlines, or gauge teammate activity. Peepdeck addresses this challenge not by replacing these tools, but by acting as a unified lens that aggregates their outputs into a cohesive dashboard.
Methodology
The development of Peepdeck followed a User-Centered Design (UCD) methodology across two primary iterations:
- Theoretical Mapping: The research team mapped common design activities—such as ideation and project management—onto McGrath’s Task Circumplex. This framework helped identify specific gaps where current general-purpose tools fail to support the unique needs of design collaboration.
- Iteration 1 (Low-Fidelity): Initial concepts were explored through wireframes and paper prototypes featuring a vertical column layout. Formative testing with seven professional designers utilized "thinking-aloud" protocols to identify usability issues and refine the information architecture.
- Iteration 2 (High-Fidelity): Feedback from the first round informed the creation of an interactive prototype built in Axure RP. This version introduced integrated search, availability indicators, and refined visual segmentation. A second round of testing with seven additional designers focused on UI clarity and the effectiveness of the dashboard's organizational logic.
Design Principles and Insights
The research yielded several key insights into the requirements for a successful design dashboard:
- Appropriation over Replacement: Designers are generally satisfied with their existing toolsets and are reluctant to adopt a new "all-in-one" platform. Peepdeck succeeds by layering on top of familiar tools rather than attempting to replace them.
- Source Agnosticism: User testing revealed that designers prioritize the type of information (e.g., a message or a file) over its origin. Peepdeck treats assets from different sources (like Google Drive and Dropbox) with visual consistency, reducing the search friction caused by platform silos.
- Glanceability: In high-pressure environments, information must be consumable at a glance. Peepdeck employs color-coding, strategic spacing, and familiar iconography to allow users to scan for updates without interrupting their deep work.
- Mandatory Customization: Because design workflows vary significantly between individuals and project phases, the dashboard must support flexible management, such as drag-and-drop column prioritization.
The Four-Column Model
The final design converged on a structured UI consisting of four primary views:
- Today: Focuses on personal deadlines and immediate local tasks.
- Project: Provides shortcuts to shared assets, project-specific milestones, and team member status.
- Team Activity: A live, aggregated stream of collaborative actions, such as file edits or task completions.
- Timeline: A linear, chronological view of upcoming events and long-term project milestones.
Results and Discussion
Evaluation of the high-fidelity prototype indicated high learnability; participants navigated the interface with ease, often drawing parallels to familiar operating systems and social media platforms. The centralized access to files and people significantly reduced the "search friction" typical of fragmented workflows.
However, several challenges remain. The current prototype relies on simulated data, and the technical implementation of real-time API integrations across dozens of services presents a substantial engineering hurdle. Furthermore, long-term studies are required to assess how the dashboard handles information overload over the duration of multi-month projects. Finally, the balance between transparency for collaboration and individual privacy remains a critical area for future design refinement.
Conclusion
Peepdeck demonstrates the potential of a specialized, aggregate dashboard to mitigate the effects of information fragmentation in distributed design studios. By focusing on glanceability and source-agnostic information architecture, the system enhances team awareness and streamlines the complex workflows of modern design practice.
Summary updated