Weaving the Greenjoy Matrix: A Conceptual Workflow for Comparing Adjacency Logic Audit to Proximity Scoring in Site Planning

Site planners often face a choice between two analytical lenses: adjacency logic audit and proximity scoring. Both examine spatial relationships, but they ask different questions and produce different answers. This guide presents a conceptual workflow for comparing these methods, enabling you to select the right approach—or blend them—for your project. We will define each framework, outline a step-by-step comparison process, and discuss common mistakes. Along the way, we use anonymized scenarios to illustrate key points. Our goal is to help you weave a "Greenjoy Matrix" that aligns method with purpose.

Why the Comparison Matters: Stakes and Reader Context

In site planning, every decision about space allocation affects operational efficiency, user experience, and cost. Two methods—adjacency logic audit and proximity scoring—are commonly used to evaluate relationships between functional areas. However, teams often conflate them, leading to suboptimal layouts. Understanding the difference is not academic; it directly impacts how you interpret data and justify design choices.

The Core Distinction

Adjacency logic audit focuses on the necessity of closeness: it asks which departments or functions must be adjacent for workflow, safety, or regulatory reasons. Proximity scoring, by contrast, measures the desirability of closeness, often using weighted criteria to rank pairwise connections. One is binary or categorical; the other is continuous and trade-off oriented.

Why This Guide Exists

Many planning teams default to proximity scoring because it produces neat numerical rankings. But when critical adjacencies are overlooked—such as emergency exits near assembly areas—the results can be costly. Conversely, relying solely on adjacency logic may miss opportunities for efficiency gains from strategic co-location. We wrote this guide to help you navigate the tension between necessity and optimization.

In a typical project, a planner might start with adjacency logic to identify non-negotiable connections, then use proximity scoring to fine-tune the layout among remaining options. But the reverse order can also work, depending on context. The key is to be intentional about which method drives which decision.

Throughout this article, we use composite scenarios drawn from common planning challenges. No specific company or project is referenced; instead, we synthesize patterns observed across industries such as healthcare, manufacturing, and office design. This approach keeps the advice generalizable while grounded in real-world constraints.

Core Frameworks: How Each Method Works

Before comparing, we need a clear understanding of each method's mechanics. This section defines adjacency logic audit and proximity scoring, explains their underlying logic, and highlights their typical outputs.

Adjacency Logic Audit: The "Must-Have" Lens

An adjacency logic audit is a systematic review of functional relationships to determine which pairs of spaces must be adjacent. The audit typically involves:

• Listing all functional areas (e.g., reception, offices, storage, shipping).
• Identifying mandatory connections based on workflow, safety codes, or operational dependencies. For example, a hospital emergency department must be adjacent to the trauma bay; a factory's raw material storage must adjoin the production line.
• Documenting constraints such as physical barriers, security zones, or regulatory separation requirements (e.g., chemical storage away from food preparation).

The output is often a matrix or diagram showing binary (yes/no) adjacency requirements. This method is deterministic: if a connection is mandatory, the layout must accommodate it.

Proximity Scoring: The "Nice-to-Have" Lens

Proximity scoring assigns numerical weights to pairwise relationships based on how beneficial closeness would be. Common steps include:

• Identifying all pairs of functional areas.
• Defining criteria such as communication frequency, material flow, or shared resources. Each criterion gets a weight (e.g., 1–5).
• Scoring each pair by summing weighted criterion scores.
• Ranking pairs from highest to lowest score.

The result is a prioritized list of desirable adjacencies. This method is probabilistic—it suggests where closeness adds value but does not mandate it.

When to Use Each

Adjacency logic audit is best when safety, regulation, or workflow dictates layout. Proximity scoring shines when you have flexibility and want to optimize for efficiency, collaboration, or user experience. Many projects benefit from a hybrid: start with the audit to fix non-negotiable connections, then apply scoring to the remaining space.

Execution: A Repeatable Comparison Workflow

This section provides a step-by-step process for comparing adjacency logic audit and proximity scoring in a real project. We break it into phases: preparation, data collection, analysis, and decision.

Phase 1: Define Scope and Constraints

Begin by listing all functional areas and any fixed constraints (building columns, existing walls, utility connections). Also note regulatory requirements (e.g., fire codes, accessibility). This phase ensures both methods operate on the same canvas.

Phase 2: Perform Adjacency Logic Audit

Create a pairwise matrix with rows and columns for each area. For each cell, mark "M" (mandatory), "R" (required by regulation), or blank (no requirement). Use input from operations, safety, and compliance teams. For example, in a warehouse, shipping and receiving might be mandatory adjacencies; break room and restrooms are not.

Phase 3: Conduct Proximity Scoring

Define 3–5 criteria (e.g., frequency of interaction, material flow volume, shared equipment). Assign weights based on stakeholder priorities. Score each pair on a 1–5 scale per criterion, then compute weighted totals. For instance, if design and engineering teams collaborate daily, that pair might score 4.8 out of 5.

Phase 4: Compare and Overlay

Overlay the mandatory adjacency map from Phase 2 onto the scored ranking from Phase 3. Identify where mandatory adjacencies align with high-scoring pairs (these are easy wins). Where mandatory adjacencies conflict with low-scoring pairs, you must honor the mandate but can later optimize within the constraint. Where high-scoring pairs are not mandatory, you have freedom to co-locate if space permits.

Phase 5: Iterate and Validate

Produce two or three layout alternatives using the combined insights. Simulate workflows or conduct walkthroughs with stakeholders. Adjust weights or re-audit if new constraints emerge. This iterative loop ensures the final layout balances necessity and desirability.

Tools, Stack, and Economics

Implementing these methods requires tools for data collection, analysis, and visualization. This section covers practical considerations: software options, team skills, and budget trade-offs.

Software and Templates

For adjacency logic audit, a simple spreadsheet or diagramming tool (e.g., Lucidchart, draw.io) suffices. Create a matrix with conditional formatting to highlight mandatory cells. For proximity scoring, you need a weighted scoring model; Excel or Google Sheets with formulas works well. More advanced users might use specialized facility planning software like AutoCAD with space programming modules, but that adds cost and learning curve.

Team Skills

Adjacency logic audit requires domain knowledge (operations, safety, compliance) to identify mandatory connections. Proximity scoring needs analytical skills to define criteria and weights, plus facilitation skills to gather stakeholder input. Ideally, a cross-functional team includes planners, operations managers, and a facilitator.

Cost and Time

A basic comparison can be done in 2–4 weeks with a small team using spreadsheets. If you need detailed scoring with many criteria and stakeholders, budget 4–8 weeks. External consultants may accelerate the process but add cost. The investment pays off when it prevents costly rework after construction.

Maintenance Realities

Adjacency requirements can change (new regulations, process changes). Proximity scores shift as workflows evolve. Plan to review the matrix annually or after major operational changes. Keep the original file editable and document assumptions so future planners can update it.

Growth Mechanics: Positioning and Persistence

Once you have a comparison workflow, how do you institutionalize it? This section covers how to build organizational buy-in, refine the process over time, and ensure it survives staff turnover.

Building Buy-In

Start with a pilot project where the stakes are moderate. Demonstrate how the combined approach revealed a non-obvious layout improvement. Share the story in a lunch-and-learn or internal newsletter. When stakeholders see tangible results (e.g., reduced travel distance, improved collaboration scores), they become advocates.

Documenting the Method

Create a standard operating procedure (SOP) that includes templates, criteria definitions, and a decision tree for when to use each method. Store it in a shared repository. This reduces reliance on any single expert and speeds up onboarding for new team members.

Continuous Improvement

After each project, conduct a retrospective: Did the adjacency logic audit miss any mandatory connections? Were the proximity scoring weights accurate? Update the criteria and weights based on lessons learned. Over time, your organization builds a "Greenjoy Matrix" that encodes institutional knowledge.

Scaling to Multiple Sites

If you plan layouts for multiple facilities, develop a parametric approach: define standard adjacency requirements by facility type (e.g., warehouse, office, lab) and proximity scoring templates with adjustable weights. This allows consistent comparison across sites while accommodating local constraints.

Risks, Pitfalls, and Mitigations

Even with a solid workflow, common mistakes can undermine the comparison. This section identifies five frequent pitfalls and how to avoid them.

Pitfall 1: Overweighting Proximity Scores

Teams sometimes treat a high proximity score as a mandate, overriding adjacency logic. Mitigation: always honor mandatory adjacencies first. Use scoring only within the remaining flexibility.

Pitfall 2: Ignoring Negative Adjacencies

Some pairs should be separated (e.g., noisy machinery near quiet offices). Adjacency logic audit often omits these. Mitigation: include a "separation required" category in your audit, or add a negative weight in proximity scoring.

Pitfall 3: Using Too Many Criteria

Proximity scoring with 10+ criteria becomes unwieldy and dilutes impact. Mitigation: limit to 3–5 criteria that capture 80% of the value. Use sensitivity analysis to check if weights change rankings significantly.

Pitfall 4: Confusing Correlation with Causation

A high proximity score may reflect existing layout rather than true desirability. Mitigation: collect data on actual workflows (e.g., observation, sensor data) rather than relying solely on subjective stakeholder ratings.

Pitfall 5: Not Updating the Matrix

After construction, the original analysis is often forgotten. Mitigation: schedule a post-occupancy evaluation 6–12 months after move-in to compare planned vs. actual adjacency benefits. Use findings to refine future projects.

Decision Checklist and Mini-FAQ

This section provides a quick-reference checklist and answers to common questions about the comparison process.

Decision Checklist

Before starting a comparison, confirm the following:

• Have we listed all functional areas and their square footage requirements?
• Have we identified all regulatory and safety adjacency requirements?
• Have we defined 3–5 proximity criteria with stakeholder input?
• Have we assigned weights that reflect organizational priorities?
• Have we planned for a post-occupancy review?

Mini-FAQ

Q: Can we skip the adjacency logic audit and just use proximity scoring?
A: Only if there are no mandatory adjacencies—rare in practice. Skipping the audit risks non-compliance or workflow breakdowns.

Q: How do we handle conflicting stakeholder opinions on weights?
A: Use a facilitated workshop to reach consensus, or average weights from multiple stakeholders. Document disagreements for future reference.

Q: Should we use the same criteria for every project?
A: No. Criteria should reflect project-specific goals. A hospital prioritizes patient safety; an office prioritizes collaboration. Tailor your matrix.

Q: What if the mandatory adjacency map leaves no room for proximity optimization?
A: That is a valid outcome. It signals that the layout is heavily constrained. In such cases, focus on optimizing within each mandatory cluster.

Q: How often should we revisit the comparison?
A: At least annually, or after any major operational change (new product line, reorganization, regulatory update).

Synthesis and Next Actions

We have walked through a conceptual workflow for comparing adjacency logic audit and proximity scoring in site planning. The key takeaway is that these methods are complementary, not competing. Adjacency logic audit ensures you meet non-negotiable requirements; proximity scoring helps you make the best use of remaining flexibility. By weaving them together, you create a "Greenjoy Matrix" that balances necessity and optimization.

Immediate Steps

For your next project, start with a simple adjacency audit using a spreadsheet. Then add a basic proximity scoring model with three criteria. Compare the outputs and see where they align or conflict. Use that insight to generate layout alternatives. This low-cost pilot will build confidence in the method.

Longer-Term Actions

Document your process and share it with colleagues. Consider developing a standardized template for your organization. Over time, refine the criteria and weights based on post-occupancy feedback. The goal is to make this comparison a routine part of your planning workflow, not a one-off exercise.

Remember that site planning is inherently uncertain. No method guarantees a perfect layout, but a structured comparison reduces the risk of overlooking critical adjacencies or missing efficiency gains. We invite you to experiment with the workflow and adapt it to your context.