Remote work + gym day and 5 ways to stay productive

The beauty of being a remote worker is that you can decide where your office is located. The home office is an obvious choice. But when you have a membership at a gym, which also has a lounge area, then why not mix up your week.

There’s a lot of productivity advice out there, this is not advice. I was simply thinking about how I can stay more productive when not isolated in my home office.

My remote work at the gym tips:

  1. Noise canceling headphones
    Get yourself a good pair of noise-canceling headphones. Most gyms can be noisy places, much more so than your open floor plan office. I often find that during the day gyms are not as busy as after work, but there still can be a good number of people working out.
  2. Work out immediately when you arrive
    The temptation to work out is real. That’s why you’re at the gym in the first place. So I like to get a solid workout in right from the beginning so I feel accomplished and have fatigued my muscles. Really it’s not unlike working out before going into the office. Just that in this case the office is the lounge area.
  3. Take normal breaks and get some exercise
    Going for walks is a normal break exercise. Having a gym full of equipment is even better. When your gym has a bouldering area, it’s easy to get a few quick routes in on a 15-minute break.
  4. Bring your lunch and snacks
    It’s convenient working at home or in an office where you can quickly grab a coffee, a snack, or warm up some leftovers for lunch. By bringing a sack lunch and some snacks, you’ll stay energized while avoiding snacking too much. Also, if there’s not a kitchen available to members, ask if they have a staff microwave you could use.
  5. Don’t do it every day
    Moderation is key. If you turn your gym into your remote office, you’ll end up not wanting to put in long workouts. I aim for 1 – 2 days a week working in the gym. And a lot of the time I work half-days at the gym, meeting climbing friends at the end of the day for a solid session.

Time to send some projects! (to my boss that is).

The RADS framework

I work with a lot of data. Financial data like revenue and costs, business data such as customer retention and churn, and product usage analytics. One of the most difficult aspects of my job is to convince stakeholders that the data is legitimate and trustworthy.

Although we use modern tools and systems like Segment, Mixpanel, and Mode Analytics, those are only tools to produce, access, and visualize data.

A typical data analysis process looks something like this:

  • Step 1: Define Your Questions
    • How many customers created a Dashboard this month and then canceled?
  • Step 2: Set Clear Measurement Goals
    • How has that number changed month-to-month, by cohort, or by subscription plan? Is it a positive change?
  • Step 3: Collect Data
    • Time to write some queries (if you have the data)
    • Additional tracking may be required…
  • Step 4: Analyze Data
    • Apply descriptive statistics and data cleaning methods to summarize the results.
    • Create some great looking charts
  • Step 5: Interpret Results
    • Apply domain knowledge

This process works well when it’s been established, leaving little room for interpretation. Where I often found the process breaking down was during the crucial collect and analyze steps.

Although I personally have a solid understanding of my process and methods used to deliver data, that process was opaque to the end user. Without understanding how I came to the results, the data are not trustworthy.


The RADS framework was created to address the concern with data accuracy and scalability. Like with any agile process, my plan is to implement and test RADS while still in development.

RADS is an acronym for Repeatable, Accurate, Dependable, and Scalable.

Data that represent these qualities have a better chance of being a trustworthy and reliable source of insights for your business.

Let’s dive into each of the qualities.

Repeatable Data

The process to retrieve data should be repeatable while providing consistent results.

Each task required to fetch this data should have these characteristics:

  • A well-defined order of operations.
    • Can be visualized in a flow chart or a numbered list.
  • Simple to understand by a person with limited domain expertise.
    • A SQL query should be well documented and easy to execute, even if the user is not a SQL expert.
  • Be efficient and not use significant computing resources.
    • Is your code well written? Are you running locally or on a cluster?
  • Prevent the introduction of errors or bugs into the systems.
    • Read-only is your friend
    • Do the heavy lifting up front, then write clean data to new tables for use with simplistic queries

Accurate Data

The data queried should be an accurate representation of the source data.

Qualities of accurate data include:

  • The sample data is a normally distributed.
    • If we query events for only 50 customers, do those customers represent our total customer base?
  • The data does not contain unaccounted for null values.
    • Data such as plan price (for paying), account id, or customer status should never be null.
    • Null values indicate no activity ever occurred
  • Results can be reverse engineered.
    • If we have a result, we can view the data that was used to get to that result.

Dependable Data

Systems break. Code has bugs. Data processes should be dependable and have built-in redundancies if possible.

Qualities to achieve for dependable data include:

  • The data is always available
  • The source of data is stored in perpetuity
  • Contingency plans exist for data loss & restoration
  • Data can pass rigorous audits

Scalable Processes

When the process to collect data is Repeatable, Accurate, and Dependable is has a better chance of being a scalable process.

After initial data scoping and implementation, ongoing data usage and maintenance should use little to no resources.

The methods used to collect and analyze data should have these qualities:

  • Be automated if possible
  • Require little user interaction to view data results
  • Require little user input to change variables
  • Be easily accessible
  • Run quickly and produce readable results
  • Be simplistic and well documented

Time to Implement

That’s a quick summary of the RADS framework. From here the process will be developed and tested to ensure the data produced not only provides great insights but instills trust.