<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Company Guidelines on Handbook</title>
    <link>https://handbook.gradientmetrics.com/gradient/company-guidelines/</link>
    <description>Recent content in Company Guidelines on Handbook</description>
    <generator>Hugo -- gohugo.io</generator><atom:link href="https://handbook.gradientmetrics.com/gradient/company-guidelines/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Working with Tom</title>
      <link>https://handbook.gradientmetrics.com/gradient/company-guidelines/working-with-tom/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/gradient/company-guidelines/working-with-tom/</guid>
      <description>How to use this document: Use this document to figure out when and whether you should get in touch with me, how you should do so (depending on the task at hand), what you should put in front of me, and how to be impressive in general.
The kinds of things I like to get involved in: By &amp;ldquo;get involved&amp;rdquo; I mean things where I am actively contributing work or direction.</description>
    </item>
    
    <item>
      <title>WTF is a Spec?</title>
      <link>https://handbook.gradientmetrics.com/gradient/company-guidelines/spec-writing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/gradient/company-guidelines/spec-writing/</guid>
      <description>Why Do We Spec?  Remote Collaboration Analogies Galore! Spec&amp;rsquo;ing Is a Sign of Brilliance, Not Weakness   What to Include in a Spec  1. Context: Set the stage 2. Deliverables: Identify the Output 3. Plan: Outline the Steps to Get There   Examples of Spec Features by Type When to Spec  You DO Need a Spec When: You Probably DON&amp;rsquo;T Need a Spec When:   Best Practices and Examples  Spec’ing Mondays Be You!</description>
    </item>
    
    <item>
      <title>Importance of Speed</title>
      <link>https://handbook.gradientmetrics.com/gradient/company-guidelines/speed/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/gradient/company-guidelines/speed/</guid>
      <description>Imagine you run a grocery store, and you are deciding which product to stock on your last unit of shelf space; although they are different products, they are exactly the same in almost all respects: they cost the same to purchase wholesale (let&amp;rsquo;s say $1 each), they are the same size and weight, etc., and they have no interaction with any other products — but you can sell the first product for $5 but the second for only $3.</description>
    </item>
    
    <item>
      <title>High Quality Writing</title>
      <link>https://handbook.gradientmetrics.com/gradient/company-guidelines/high-quality-writing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/gradient/company-guidelines/high-quality-writing/</guid>
      <description>Introduction Writing Tips  You can&amp;rsquo;t do it in one pass Take your reader on a journey Be specific Make the case behind the position, don&amp;rsquo;t just state the position Read carefully If you can&amp;rsquo;t get clear on what you want to say, make that the issue   Some resources     Introduction Writing well is important for at least three reasons: the process of writing, and writing well, helps you think more clearly and develop better, more complete ideas; clear and crisp written communication is the most efficient way to transmit these ideas to someone else, especially when the ideas are complex; finally, leaving behind a written document memorializes a line of thinking that will be available for future people (that future person being you, perhaps) to inspect.</description>
    </item>
    
    <item>
      <title>Correspondence Hygiene</title>
      <link>https://handbook.gradientmetrics.com/gradient/company-guidelines/correspondence-hygiene/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/gradient/company-guidelines/correspondence-hygiene/</guid>
      <description>Networks Are Important Networks Are Non-Linear Principles  Always Follow Up Always Be Helpful Always Care Don&amp;rsquo;t Trust Yourself to Remember Understand Their Problem Better Than They Do Listen, but Guide Always Have a Plan Don&amp;rsquo;t Let the Energy Flag Always Be On-Point Summarize the Meeting You Just Had Always Take Notes Always Guide to Next Steps   Networking Events  Quantity &amp;gt; Quality       Networks Are Important There is no substitute for building a strong personal network.</description>
    </item>
    
    <item>
      <title>Google Calendar Best Practices</title>
      <link>https://handbook.gradientmetrics.com/gradient/company-guidelines/calendar-best-practices/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/gradient/company-guidelines/calendar-best-practices/</guid>
      <description>Introduction Personal Calendar  Out of Office Availability Working Hours Meeting Notifications Meetings with Teammates Recurring Meetings Visibility Slack Integration   Gradient Schedule Calendar Resources     Introduction As a fully remote company with team members all over the world in multiple time zones, it is important that our Google Calendar hygiene is close to impeccable here at Gradient. This document sets out best practices and general guidelines for Google Calendar use.</description>
    </item>
    
    <item>
      <title>How To Run a Meeting</title>
      <link>https://handbook.gradientmetrics.com/gradient/company-guidelines/meetings/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/gradient/company-guidelines/meetings/</guid>
      <description>Start on Time, End on Time Shoot the Shit, But Not for Too Long Have an Agenda, Have a Goal  Formal or Informal Set the Context Know the Goal Going In   Someone Should (Almost Always) Be Sharing Their Screen  Take Notes, Preferably in Public   Use Loom to Record the Meeting Be High Energy, Don&amp;rsquo;t Leave Dead Space  Call on Specific People Versus Asking the Room   It&amp;rsquo;s Okay to Leave Time for the Reading Keep an Eye on the Clock Recap the Next Steps and Who&amp;rsquo;s Doing What     Start on Time, End on Time You should assume that everyone is back-to-back.</description>
    </item>
    
    <item>
      <title>Video Chat Guidelines</title>
      <link>https://handbook.gradientmetrics.com/gradient/company-guidelines/video-chat/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/gradient/company-guidelines/video-chat/</guid>
      <description>Some guidelines for being impressive while on calls:
  If you&amp;rsquo;re typing, please stay on mute. Typing comes out pretty loud and adds a level of background noise that you can&amp;rsquo;t hear.
  Please don&amp;rsquo;t eat when you&amp;rsquo;re on a call, unless we&amp;rsquo;re super close with the client. Please don&amp;rsquo;t eat when there is new business on the line, or we are trying to impress people that will make decisions about whether or not we will be given new business.</description>
    </item>
    
  </channel>
</rss>
