Internal Workspace
Internal Workspace
A shared space for project continuity and design learning
A shared space for project continuity and design learning
Ofek Cohen || UX Researcher & Designer
Year 2025
Overview
About
During my internship at MouseUX, I identified a recurring challenge: documentation across projects was scattered, inconsistent, and difficult to retrieve. Valuable information—such as client feedback, design rationale, and technical decisions—was often stored in separate files, conversations, or presentations, making it hard for team members to stay aligned or build on past work.
In response, I designed an internal documentation platform tailored to the team’s real needs. The system centralizes all relevant project materials in one structured and searchable interface, including feature breakdowns, client conversations, design iterations, and version history. It enables clearer communication, smoother handoffs, and easier access to knowledge throughout the project lifecycle.
The platform was built to reflect how designers actually work: by capturing the logic behind decisions, tracking changes over time, and surfacing key information when it's needed most. Beyond organization, it aims to strengthen collaboration, reduce dependency on individuals, and ensure that the insights gained in one project can actively support the next.
UX Research
Journey Mapping
Information Architecture
Responsive Design
Sketching
Visual Communication
FigJam
Figma
Google Forms
Overview
About
During my internship at MouseUX, I identified a recurring challenge: documentation across projects was scattered, inconsistent, and difficult to retrieve. Valuable information such as client feedback, design rationale, and technical decisions was often stored in separate files, conversations, or presentations, making it hard for team members to stay aligned or build on past work.
In response, I designed an internal documentation platform tailored to the team’s real needs. The system centralizes all relevant project materials in one structured and searchable interface, including feature breakdowns, client conversations, design iterations, and version history. It enables clearer communication, smoother handoffs, and easier access to knowledge throughout the project lifecycle.
The platform was built to reflect how designers actually work: by capturing the logic behind decisions, tracking changes over time, and surfacing key information when it's needed most. Beyond organization, it aims to strengthen collaboration, reduce dependency on individuals, and ensure that the insights gained in one project can actively support the next.
UX Research
Sketching
Journey Mapping
Information Architecture
Information Architecture
Information Architecture
Responsive Design
Visual Communication
FigJam
Figma
Google Forms
define
The Problem
The Problem
Teams struggled to access and reuse knowledge across projects due to scattered, inconsistent, and unstructured documentation.
Teams struggled to access and reuse knowledge across projects due to scattered, inconsistent, and unstructured documentation.
My Solution
To address the lack of structure and visibility in project documentation, I designed an internal platform that centralizes all key project elements in one place. The system includes dedicated sections for client conversations, design versions, feature documentation, and decision tracking—allowing team members to follow the progression of a project from start to finish. By organizing information around real workflows rather than generic folders, the platform helps reduce confusion, improves team alignment, and supports smoother collaboration. Beyond accessibility, the system was built to promote continuity and knowledge reuse. Projects are documented in a way that surfaces the logic behind past decisions, making it easier for new team members to onboard and for designers to build on previous work. Each project is treated as a resource—not just a deliverable—enabling the team to learn, iterate, and grow more effectively over time.
My Solution
To address the lack of structure and visibility in project documentation, I designed an internal platform that centralizes all key project elements in one place. The system includes dedicated sections for client conversations, design versions, feature documentation, and decision tracking—allowing team members to follow the progression of a project from start to finish. By organizing information around real workflows rather than generic folders, the platform helps reduce confusion, improves team alignment, and supports smoother collaboration. Beyond accessibility, the system was built to promote continuity and knowledge reuse. Projects are documented in a way that surfaces the logic behind past decisions, making it easier for new team members to onboard and for designers to build on previous work. Each project is treated as a resource—not just a deliverable—enabling the team to learn, iterate, and grow more effectively over time.
Focus
Designing a system that turns scattered project work into structured, reusable knowledge—supporting clarity, continuity, and team alignment.
Focus
Designing a system that turns scattered project work into structured, reusable knowledge—supporting clarity, continuity, and team alignment.
Research Insights
During my internship, I observed a complex landscape of documentation habits across the team. While some designers kept detailed records of their process—client meetings, design decisions, and project changes—others documented only partially or used formats that were informal and inconsistent. This created fragmented knowledge, made it harder to track project logic over time, and complicated transitions between team members.
There was no shared structure or documentation logic across the team. Each person used different tools—Google Drive, slides, Zeplin, Figma comments, or internal notes—and organized content based on personal habits. As a result, understanding the reasoning behind past decisions became inefficient and often depended on asking the original designer.
Junior team members were particularly affected. Without prior context or access to clear project histories, they relied heavily on more experienced colleagues for explanations. In some cases, even when documentation existed, it lacked coherence or was buried in tools they didn’t know to check—slowing down their onboarding and increasing dependency.
Client feedback was recorded inconsistently and often stored separately from the design process itself. This made it harder to trace how the team responded to feedback or to verify whether all requests were addressed—especially in long-term projects with multiple feedback rounds.
Design iterations and feature-level insights were rarely documented in a reusable or searchable way. Files were versioned without explanation, and design decisions were often made in conversation or Slack threads without being captured for future reference. This limited the team's ability to reflect, learn, or apply insights across projects.
These patterns revealed that the core issue wasn’t the absence of documentation—but the absence of shared, structured, and accessible knowledge. The team needed a system that could make the design process transparent, traceable, and valuable beyond the moment it happened.
Research Insights
During my internship, I observed a complex landscape of documentation habits across the team. While some designers kept detailed records of their process—client meetings, design decisions, and project changes—others documented only partially or used formats that were informal and inconsistent. This created fragmented knowledge, made it harder to track project logic over time, and complicated transitions between team members.
There was no shared structure or documentation logic across the team. Each person used different tools—Google Drive, slides, Zeplin, Figma comments, or internal notes—and organized content based on personal habits. As a result, understanding the reasoning behind past decisions became inefficient and often depended on asking the original designer.
Junior team members were particularly affected. Without prior context or access to clear project histories, they relied heavily on more experienced colleagues for explanations. In some cases, even when documentation existed, it lacked coherence or was buried in tools they didn’t know to check—slowing down their onboarding and increasing dependency.
Client feedback was recorded inconsistently and often stored separately from the design process itself. This made it harder to trace how the team responded to feedback or to verify whether all requests were addressed—especially in long-term projects with multiple feedback rounds.
Design iterations and feature-level insights were rarely documented in a reusable or searchable way. Files were versioned without explanation, and design decisions were often made in conversation or Slack threads without being captured for future reference. This limited the team's ability to reflect, learn, or apply insights across projects.
These patterns revealed that the core issue wasn’t the absence of documentation—but the absence of shared, structured, and accessible knowledge. The team needed a system that could make the design process transparent, traceable, and valuable beyond the moment it happened.
Together, these insights pointed to the need for a unified system that could capture not only the outputs of design—but also the reasoning behind them. Without structure and traceability, even the best ideas couldn’t be carried forward.
This highlighted the need to design for onboarding—making context easy to access, minimizing uncertainty, and helping new designers integrate into existing projects faster and with more confidence.
During my internship, I observed a complex landscape of documentation habits across the team. While some designers kept detailed records of their process—client meetings, design decisions, and project changes—others documented only partially or used formats that were informal and inconsistent. This created fragmented knowledge, made it harder to track project logic over time, and complicated transitions between team members.
There was no shared structure or documentation logic across the team. Each person used different tools—Google Drive, slides, Zeplin, Figma comments, or internal notes—and organized content based on personal habits. As a result, understanding the reasoning behind past decisions became inefficient and often depended on asking the original designer.
Junior team members were particularly affected. Without prior context or access to clear project histories, they relied heavily on more experienced colleagues for explanations. In some cases, even when documentation existed, it lacked coherence or was buried in tools they didn’t know to check—slowing down their onboarding and increasing dependency.
Client feedback was recorded inconsistently and often stored separately from the design process itself. This made it harder to trace how the team responded to feedback or to verify whether all requests were addressed—especially in long-term projects with multiple feedback rounds.
Design iterations and feature-level insights were rarely documented in a reusable or searchable way. Files were versioned without explanation, and design decisions were often made in conversation or Slack threads without being captured for future reference. This limited the team's ability to reflect, learn, or apply insights across projects.
These patterns revealed that the core issue wasn’t the absence of documentation—but the absence of shared, structured, and accessible knowledge. The team needed a system that could make the design process transparent, traceable, and valuable beyond the moment it happened.
Design Overview
The platform is built around a modular structure, with each project documented in a consistent, traceable format. The interface includes distinct areas for project background, client communication, feature tracking, and key decisions—designed to reflect real team workflows and reduce reliance on memory or scattered files.
Each page presents a focused slice of the project: from a central dashboard, to editable forms, feedback summaries, and a visual archive of deliverables. Together, these tools support clarity, collaboration, and long-term usability.
Key FEATURES
The platform supports documenting each feature as a standalone element, including its status, logic, design choices, and attached files. This allows team members to understand decisions at a granular level, revisit solutions from past projects, and hand off work with full context—no matter who picks it up next.
Beyond project work, the platform includes open content spaces where the team can browse curated resources—such as design inspiration, tools, articles, and case studies. Each user can privately save personal favorites, supporting independent growth without exposing individual activity.
This feature creates a lightweight, non-intrusive way to promote learning and professional development across the team—while keeping the environment open, flexible, and respectful of personal work styles.
Appreciation
Thanks for checking it out!
Reach out on
Key FEATURES
The platform supports documenting each feature as a standalone element, including its status, logic, design choices, and attached files. This allows team members to understand decisions at a granular level, revisit solutions from past projects, and hand off work with full context—no matter who picks it up next.
Beyond project work, the platform includes open content spaces where the team can browse curated resources—such as design inspiration, tools, articles, and case studies. Each user can privately save personal favorites, supporting independent growth without exposing individual activity.
This feature creates a lightweight, non-intrusive way to promote learning and professional development across the team—while keeping the environment open, flexible, and respectful of personal work styles.
Appreciation
Thanks for checking it out!
Available for new projects