Analyzing Segment’s commute time · Segment Blog
At Segment we pride ourselves on being data-driven. Wherever we can use data to solve or surface problems, we do. Among other things, we use surveys to measure our engagement, motivation, happiness and ability to focus.
Last year, one of our surveys showed that we were having a tough time focusing in the office, mostly due to noise. So we launched a
More recently, our burgeoning team needed to make the jump to a new, larger office in downtown San Francisco. As we began digging into this project, one area of concern was the effect this move would have on the team’s commute since studies show that there is a direct connection between commute time and health: shorter commutes reduce stress, create a stronger sense of connection with family and friends, and increase your ability to focus.
We feel very strongly about improving on all these dimensions for our team, so when it came time to begin our new office search, our data-driven approach to problem solving kicked into high gear once again.
First, we needed to determine what area of the city to focus our office search efforts. By doing a quick scan of our teammates addresses, we found that the majority lived within the city, with a small percentage in adjacent counties. So we knew we wanted to stay within San Francisco. But a quick scan didn’t exactly help us pin-point what neighborhood of SF; so we took it a step further.
By doing a quick export of all our team’s home addresses we used the Google Maps API to determine the areas with minimal average commute time. The shortest average commute times are shown in dark green here:
With this handy map, our office search team hit the ground running, zero-ing in on available offices in the dark green zone. Going further, we knew that this was our “target area”, but it didn’t tell us exactly how this change would impact our team’s distribution of commutes. So, after we narrowed the search to a couple final possibilities, we did a detailed analysis.
We ran everyone’s addresses through the Google Maps API once more to generate the distribution of commute times, comparing new and old offices:
Based on our analysis, we determined that the move from 101 15th St to 100 California St would decrease the median commute time from 29 minutes to 24 minutes, with an average drop from 32 minutes to 27 minutes and that overall the new office would save the existing team, in aggregate, about 16 hours per day (at 140 people, more as we double this coming year!)
As a final measure, before announcing the new office location to the company, we asked all the team leads to sit down with teammates whose commutes were negatively affected, walk them through the new office decision and address any concerns. And while it was hard to say goodbye to our much beloved home in Potrero Hill, the proximity to the Caltrain, Bart, Ferry Building, and even the iconic SF Cable cars that our new home provides assured everyone that long term, it was the best move for our company.
If you’re looking to move your team soon, we’ve open-sourced the analysis code so you can run it for your team and city too. You can find the code here.
相關推薦
Analyzing Segment’s commute time · Segment Blog
At Segment we pride ourselves on being data-driven. Wherever we can use data to solve or surface problems, we do. Among other things, we use surveys to me
Segment Open Fellowship 2017 · Segment Blog
Today we’re proud to announce the Segment Open Fellowship. The Fellowship is a three month long program supporting three to five open-source developers wit
Is Personas compatible with Segment’s GDPR features? Documentation
Yes! Personas is compatible with Segment’s GDPR features. Personas was designed with the GDPR principles and end-user privacy in mind, and is powered by fi
[Puppeteer] Get a Page's Load Time with Puppeteer (window.profermence.timing)
cli nav await put org download pup sso ref In this lesson we are going to use Google‘s Puppeteer to gather metrics about a page‘s load ti
aaron8219's Oracle&Linux Technology Blog
InnoDB: Progress in percents: 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
It’s probably time to learn Chinese
It’s probably time to learn ChineseFor over a century, learning English has been one of the highest ROI things a non-English speaker could do. English went
AI Weekly: AI is getting political in Washington, and it's about time
Amid rage brewing on both sides of the political spectrum over testimony by Christine Blasey Ford and Judge Brett Kavanaugh, it would be understandable if
Keeping the smartphone in its place with iOS 12’s Screen Time feature
For years, I have struggled with the burden of owning a smartphone. My two years working as a Carphone Warehouse salesman started the long process of openi
Wenxy's computer science technology blog
績效管理=績效+管理+管理人員. 大公司小公司的績效管理方案不相同,業務部門和研發部門的績效管理方案也不相同。 程式設計師選擇工作機會的目標:工作環境,薪水,發展平臺。 wind river一個研發部門的做法是: 基本上是量化和人性化結合, 會有一些硬的指標來打分給每個人
aspectj's load-time instrumentation
Aspectj implements the functionality also using the asm tool. As it provides neat aspect grammars and is supported extensively by the com
Bob Loblaw’s Log Blog · Segment Blog
Today we’re excited to open source the various pieces of our logging pipeline. We’ve released a rate-limiting-syslog proxy, a journald fanout service, and
Driving Adoption of a Design System · Segment Blog
Design systems are emerging as a vital tool for product design at scale. These systems are collections of components, styles, and processes to help teams d
How Does Mobile App Size Affect Installs? · Segment Blog
When it comes to your app, size makes a difference. Bigger apps have fewer downloads, worse reviews, and a harder time penetrating the international market
Why We Chose QueueFile for Reliable Request Batching on Android · Segment Blog
Segment’s mobile SDKs are designed to track behavioral data from your app and translate and route that data to hundreds of downstream integrations. One of
Continuous Integration at Segment · Segment Blog
As part of our push to open up what’s going on internally at Segment – we’d like to share how we run our CI builds. Most of our approaches follow standard
Delivering billions of messages exactly once · Segment Blog
The single requirement of all data pipelines is that they cannot lose data. Data can usually be delayed or re-ordered–but never dropped. To satisfy this re
Secure access to 100 AWS accounts · Segment Blog
Segment receives billions of events from our customers daily and has grown in to dozens of AWS accounts. Expanding in to many more accounts was necessary i
The right way to manage secrets with AWS · Segment Blog
The way companies manage application secrets is critical. Even today, improper secrets management has resulted in an astonishing number of high profile bre
A brief history of the UUID · Segment Blog
Today we’re releasing ksuid, a Golang library for unique ID generation. It borrows core ideas from the ubiquitous UUID standard, adding time-based ordering
Spotting a million dollars in your AWS account · Segment Blog
Recently we shared the techniques we used to save more than a million dollars annually on our AWS bill. While we went into detail about the various problem