Workspace

The ongoing organisation of work into meaningful contexts, transforming a single undifferentiated space into coherent zones that match how attention and responsibility are actually distributed.

Workspaces create boundaries that reflect how work is structured — by ownership (personal, team, organisational), by topic (projects, areas, subjects), or by activity (active work, reference, archive). They mediate the tension between focused attention on a single context and the need to coordinate across multiple concurrent ones, implementing privacy through spatial separation, agency through control over organisation, and collaboration by defining shared and individual work zones.

Problem

Users need to manage work that spans multiple contexts whilst maintaining coherent focus. Working in a single undifferentiated space creates cognitive overload and makes it difficult to separate concerns. Constantly switching between different applications or windows disrupts flow and makes it hard to resume interrupted work. Different contexts require different levels of visibility and access—personal work should remain private, team work should be visible to collaborators, organisational resources should be broadly available.

Solution

Create distinct workspaces that reflect natural boundaries in how work is organised. Enable users to view multiple contexts simultaneously through spatial arrangement, or switch rapidly between contexts whilst preserving state. Make workspace boundaries align with privacy, permission, and organisational structures so visibility and access control feel natural rather than imposed.

Variants

Workspaces organised around ownership and access boundaries:

• Personal workspace: Individual’s private work, organised according to personal taxonomy and priorities. Only the owner can view and modify contents. Supports autonomous work without coordination overhead.
• Team workspace: Shared context for collaborative work within a defined group. Members can view and contribute to shared objects whilst maintaining individual private areas within the team space. Access controlled by team membership.
• Organisational workspace: Company-wide or cross-team contexts with broad visibility. May be read-only for most users, editable by designated roles. Serves as shared resource library or communication space.

These scopes often nest—personal workspaces exist within team contexts, team workspaces exist within organisational boundaries. Users move work between scopes as it progresses from private ideation to team collaboration to organisation-wide sharing.

By persistence

• Project-based: Temporary workspace assembled for specific goal. Disbanded when project completes. Members and resources change as project evolves.
• Persistent: Durable workspace maintained over time. Accumulates shared knowledge and history. Membership stable but may evolve gradually.
• Ephemeral: Short-lived workspace for temporary collaboration or exploration. No expectation of durability. Created and destroyed fluidly as needed.

States

• Empty state: New workspace with no active contexts. May offer templates, recent items, suggested starting points, or creation actions appropriate to workspace scope.
• Single context: One active item fills available space. Workspace navigation chrome may hide to maximise content area. Easy transition to multi-context state.
• Multi-context: Multiple tabs, panels, or windows active. Navigation and organisation controls become prominent. Visual indicators show active context and available alternatives.
• Overflow state: More contexts than comfortably fit available space. Requires scrolling tabs, carousels, hierarchical grouping, or search to access all contexts. May indicate need to archive, close, or reorganise.

Access control and permissions

While detailed TODO:permission managment is separate concern, access control strongly affects workspace boundaries. Personal workspaces are implicitly private. Team workspaces require membership verification. Organisational workspaces may have role-based editing rights.

Resources

• Arvola (2005). Interaction design patterns for computers in sociable use
• Tidwell, Brewer, Valencia (2020) Designing Interfaces, 3rd ed.