The Real Deal with Open Office Floor Plans

Akins IT • August 15, 2017
Connect with us

As most of you know, we recently moved to a new office! And don’t worry, we brought the bar, pool table, and foosball table with us.

The new office is completely open- no assigned desks, just shared workspaces. We did this to decrease clutter in the office and to promote communication between departments like sales and engineering. We recognized, though, that some conversations need to be private and that too many conversations in an open shared space could be distracting so the office also has 7 private workspaces.

THE PROS OF OPEN OFFICE FLOOR PLANS:


  • Creativity increases because it’s easier to collaborate with fellow employees.
  • One of the biggest risk factors in losing an employee is that they don’t have a “best friend” at work or group of people that they are close with there. This setup creates feelings of camaraderie and teamwork, making it more likely that you’ll retain employees.


THE CONS:


  • Things can get a bit noisy without traditional sound blocks like cubicles!
  • Germs! Embrace hand sanitizer in all corners of the office because this floor plan means that you’re going to be exposed in a higher degree to your coworker’s seasonal flu.
  • Lack of privacy: Everyone can hear everything on the office floor.


HOW WE HAVE MADE IT WORK


We wanted to embrace the office floor plan for its perks but also put some things in place to avoid the negatives. We’ve done this in a couple of ways- developing office rules and offering several private, quiet office areas for people who need to have a confidential conversation, have some uninterrupted work time, join a conference call, etc.


Office Rules


Most importantly here, because people are working in open areas, they have to be respectful of others to avoid causing unnecessary distractions. Here are a few of the rules we have come up with:


  • Leave each room cleaner than it was
  • Keep conversations down in shared areas
  • Be respectful of others
  • If you're sick, work from home!


Private Workspaces


We had fun with these and gave each its own theme. They can be reserved or checked out and certain groups and departments have priority for particular rooms.


The Library- an old school lair of sorts with old fashioned decanters, books, and leather chairs and couch.

Thunderdome- This is our original meeting room name at our previous office. We’ve migrated it over as is to the new space!


Bat Cave – Batman themed room that our solution architects have dibs on.


Board Room- Our largest conference room with an oversized reclaimed wood table


Babe Cave – a chic girly glam room and as the name implies…. Girls Only!

By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts