Gus Grimstad on the Nuances of Property Management Inside a Tech Company

How to work with developers, align facilities with product cycles, and keep spaces reliable

Gus Grimstad has seen that property management inside a tech company is less about “keeping the lights on” and more about running an environment that supports speed, uptime, security, and constant change. Whether the space is an HQ office, a hybrid hub, a lab, or a light data and hardware footprint, the expectations are different from traditional commercial management. Your stakeholders often think like product owners, engineers, and operators. They want systems, metrics, and clear ownership.

This is where property management overlaps with operations in a way that can feel familiar to software teams: backlog management, incident response, root cause analysis, and continuous improvement. If you can align your facilities approach with that mindset, you earn trust fast.

Why tech-company property management feels different

In many industries, facilities is measured by cost control and general comfort. In tech, facilities is also measured by how well it enables productivity and reduces friction. Small problems become loud problems because the company runs on focus.

Common traits of tech environments include:

• Rapid team growth or reorgs that change space needs quickly
• Hybrid schedules that make utilization unpredictable
• Higher reliance on secure access and visitor controls
• Equipment density that stresses power, cooling, and noise expectations
• Employees who expect self-service tools and fast response times

You are not just managing a building. You are managing an internal service that people compare to the tools they use every day.

Working with developers means learning their operating language

Developers and technical teams tend to respect clarity, prioritization, and accountability. If your updates feel vague, trust drops. If you can explain a facilities issue the way an engineer explains a bug, you will get better collaboration.

Practical ways to “speak dev” without forcing it:

• Define the problem precisely (what, where, who is impacted, when it started)
• Share a realistic timeline and the dependencies (vendor availability, parts, approvals)
• Separate symptom from root cause (the conference room is hot vs the HVAC zone control is failing)
• Document decisions and next steps in one place

A simple shift helps a lot: treat facilities requests like tickets, and treat improvements like roadmap items.

Ticketing, triage, and SLAs for facilities requests

Tech teams often live inside Jira, ServiceNow, Zendesk, or similar platforms. Even if your facilities group uses a different system, you can mirror the same structure: intake, triage, priority, and resolution notes.

A clean facilities workflow usually includes:
1) Standard categories
Examples: HVAC, electrical, access control, cleaning, furniture, A/V, safety, plumbing.

2) Priority levels with clear meaning

• P0: safety risk or critical outage (power loss, flooding, access failure)
• P1: major productivity impact (network closet cooling issue, large area HVAC failure)
• P2: standard request (minor repairs, comfort issues, small moves)
• P3: nice-to-have (cosmetic, non-urgent improvements)

3) Service-level targets that match reality
Set expectations for response and resolution separately. You can respond quickly even when a fix takes longer.

Developers do not expect miracles. They expect honest status, visible progress, and predictable handling.

Facilities change management, planned work, and release windows

In tech, timing is everything. The week before a product launch is not the week to shut down half the floor for loud construction. Property managers who coordinate planned work like “maintenance releases” avoid conflict and reduce last-minute escalations.
Habits that work well:

• Maintain a rolling 4 to 8 week “facilities change calendar”
• Schedule disruptive work during low occupancy windows when possible
• Publish clear notices with what will be affected (noise, temperature, access)
• Provide rollback plans when a change could break critical areas (server rooms, badge access)

This mirrors the way technical teams plan deployments and it signals operational maturity.

Incident response: when facilities becomes “on-call”

Sometimes facilities issues behave like production incidents. A cooling failure in a server room, a badge system outage, or a water leak is urgent and cross-functional.
Borrow a few practices from engineering operations:

• Assign an incident lead and a clear comms channel
• Provide updates on a schedule (every 30 to 60 minutes during a major outage)
• Track decisions and actions live so there is one source of truth
• Run a short post-incident review to prevent repeats

Post-incident reviews do not need to be formal. A one-page summary can be enough: what happened, what fixed it, what will prevent it, and who owns the follow-up.

Security, compliance, and physical access as part of trust

Tech companies often care deeply about security, including physical controls. That can include visitor logs, restricted areas, camera coverage, key management, and badge access policies. Even when compliance frameworks are owned by another team, facilities is typically responsible for execution on the ground.

Key principles:

• Least privilege access (only the spaces someone needs)
• Clear offboarding steps (badge deactivation, key return, equipment rooms)
• Visitor processes that are simple, consistent, and auditable
• Maintenance vendor access rules (escorts, time windows, logging)

The goal is not to make the workplace feel restrictive. The goal is to reduce risk while keeping the process smooth.

Space planning for hybrid teams and fast growth

Hybrid work changes the math. Empty desks Monday can become packed spaces Tuesday. Tech teams also scale unevenly, which creates pressure on conference rooms, collaboration zones, and quiet areas.

A practical space planning approach includes:

• Tracking utilization patterns rather than relying on opinions
• Prioritizing room types that relieve pressure (phone rooms, small meeting rooms)
• Designing for flexibility (movable furniture, modular layouts, reservable desks)
• Creating norms for shared space (clean desk expectations, room reset standards)

Good space planning is not about perfection. It is about reducing daily friction so teams can do their work.

Smart building data that actually helps

Tech companies often want data, but property management data is only valuable if it changes decisions. Instead of collecting everything, focus on metrics tied to outcomes:

• Work order volume and time-to-first-response
• Repeat issues by location (signals root cause)
• HVAC comfort complaints by zone (signals tuning needs)
• Cleaning issues by area and time (signals scheduling gaps)
• Space utilization by day and hour (signals right-sizing opportunities)

When you can show trends and fixes, you stop arguing about anecdotes.

Vendor management with engineering-style expectations

Developers respect vendors who are accountable and predictable. Facilities vendors should be held to the same standard. Clear scopes, clear acceptance criteria, and clear communication prevent churn.

Effective vendor management looks like:

• Defining “done” in writing (what must be tested, cleaned up, documented)
• Requiring closeout notes and photos for significant work
• Reviewing recurring failures and changing vendors when patterns persist
• Maintaining a preferred vendor bench so emergencies do not become scramble mode

The mindset shift that makes it all work

Property management in a tech company is successful when facilities is treated as an internal product: reliable, measurable, and continuously improving. You are building trust by being clear, fast to respond, thoughtful in planning, and disciplined in follow-through.

Learn more at Gus Grimstad.