View on GitHub

Cross-Disciplinary Software Team Spaces

A Pattern Language

Productive Traces Preservation

Summary: Tell the difference between beneficial signs of use and actual problems. Preserve evidence of successful adaptations while addressing genuine issues.

Context

Facilities management often treats all changes from original design as problems to fix. This can eliminate valuable evidence of how teams have successfully adapted their environment to work better.

Problem

Over-zealous cleaning and “restoration” to original state can erase the accumulated wisdom of team adaptations. When maintenance removes all traces of use, teams lose social signals about what changes are acceptable and beneficial.

Solution

Develop nuanced maintenance practices that preserve beneficial traces while addressing genuine problems. Train facilities teams to recognize the difference between productive adaptations and actual issues that need correction.

Preserve beneficial traces:

Address genuine problems:

Create documentation systems:

Decision Framework for Trace Preservation

The SPACE Assessment Matrix:

Criteria Preserve Investigate Remove
Safety No hazards Minor risk, monitor Clear safety violation
Purpose Clear functional benefit Unclear purpose No apparent benefit
Adoption Multiple teams copying Single team using Abandoned by creators
Code Compliance Fully compliant Grey area, review Clear violation
Evolution Builds on previous learning First iteration Regression from better state

Assessment Process:

  1. Document first - Photo and note the trace before any action
  2. Investigate purpose - Ask the team why this modification exists
  3. Evaluate safety - Check for genuine safety or code concerns
  4. Assess adoption - Look for evidence of other teams copying the change
  5. Consider preservation - Decide if this represents valuable organizational learning

Critical Implementation Notes:

Decision Tree:

Trace Discovered
      ↓
Is it safe? → No → Remove immediately, document for learning
      ↓ Yes
Does it serve a clear purpose? → No → Investigate with team
      ↓ Yes
Are others copying it? → Yes → Preserve as organizational learning
      ↓ No
Is it the team's active choice? → Yes → Preserve with monitoring
      ↓ No
      → Remove and support team in finding better solution

Conversation Guide Templates

Team-Facilities Discussion Framework

Initial Discovery Conversation: Natural approaches that respect team autonomy:

Avoid interrogation-style questions that put teams on the defensive. Real conversations happen when people feel their adaptations are valued, not questioned.

Preservation Decision Dialogue:

Removal Discussion Script: “We need to change this because [specific reason]. Before we do:

Regular Check-in Conversations

Monthly Space Walks:

Quarterly Learning Sessions:

Digital Application and Virtual Traces

Digital Workspace Traces

Code Repository Adaptations:

Focus on meaningful adaptations that represent genuine innovation, not routine configuration management.

Collaboration Tool Modifications:

Knowledge Management Evolution:

Digital Documentation Systems

Living Space History:

Team Adaptation Library:

Adaptation: Mobile Whiteboard Cluster
Team: Backend Infrastructure
Problem: Architecture discussions scattered across multiple small whiteboards
Solution: Grouped 4 mobile whiteboards to create large continuous drawing surface
Outcome: Team reports easier system visualization, 2 other teams copied setup
Facilities: Fire egress maintained, requires monthly deep cleaning

Note: Avoid false precision in outcomes. “40% faster” claims without rigorous measurement methods undermine credibility. Focus on qualitative benefits and adoption patterns.

Virtual Trace Analytics:

Hybrid Physical-Digital Preservation

Augmented Documentation:

Community Learning Platform:

Pattern Recognition Tools:

Forces

Addressing the Core Tension

The fundamental conflict: Teams want to adapt their environment to work better. Facilities management wants to minimize maintenance, liability, and complexity. This pattern only works when this tension is explicitly acknowledged and managed.

Prerequisites for Success:

When This Pattern Fails:

Examples

Toyota Production System: Preserves worker improvements to workstations while keeping safety and quality standards.

Research laboratories: Tell the difference between productive changes that improve research capability and changes that create safety risks.

University libraries: Preserve student-created study configurations that improve space use while keeping accessibility and safety.

Software development spaces: Keep team-created information radiators and workflow adaptations while addressing ergonomic or electrical safety issues.

Sources