<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.9.5">Jekyll</generator><link href="https://jbryanscott.com//feed.xml" rel="self" type="application/atom+xml" /><link href="https://jbryanscott.com//" rel="alternate" type="text/html" /><updated>2024-04-13T21:24:16+00:00</updated><id>https://jbryanscott.com//feed.xml</id><title type="html">JBS</title><subtitle>Blog of J. Bryan Scott (JBS)</subtitle><entry><title type="html">Test</title><link href="https://jbryanscott.com//test/" rel="alternate" type="text/html" title="Test" /><published>2023-07-26T17:25:22+00:00</published><updated>2023-07-26T17:25:22+00:00</updated><id>https://jbryanscott.com//test</id><content type="html" xml:base="https://jbryanscott.com//test/"><![CDATA[]]></content><author><name></name></author><category term="test" /><summary type="html"><![CDATA[]]></summary></entry><entry><title type="html">My new hire reading list from Square</title><link href="https://jbryanscott.com//my-new-hire-reading-list-from-square/" rel="alternate" type="text/html" title="My new hire reading list from Square" /><published>2016-01-14T02:58:52+00:00</published><updated>2016-01-14T02:58:52+00:00</updated><id>https://jbryanscott.com//my-new-hire-reading-list-from-square</id><content type="html" xml:base="https://jbryanscott.com//my-new-hire-reading-list-from-square/"><![CDATA[<p>I’m often asked by friends or startups I advise for a practical reading list that provides context, expected skills, and common vocabulary for the new job. Below is the reading list I gave to my new hires at <strong>Square</strong> when I led the risk, data science, and Square Capital teams. For each section the list is deliberately short—because I’m picky about signal-to-noise when requiring others to read. Hope you find this helpful:</p>

<h3 id="general-business">General Business</h3>
<ul>
  <li><a href="https://www.amazon.com/dp/B00L1TPCKW">Business Adventures</a>: the ubiquitous moral failings of executives when given improper incentives</li>
  <li><a href="https://www.amazon.com/dp/B005OVTMAY">Understanding Michael Porter</a>: cogent summary of Porter’s famous five forces</li>
</ul>

<h3 id="making-good-investments">Making Good Investments</h3>
<ul>
  <li><a href="https://www.amazon.com/dp/B000FC12C8">The Intelligent Investor</a>: see sections on Mr. Market and intrinsic value</li>
  <li><a href="https://www.amazon.com/dp/B00BUBALZW">The Essays of Warren Buffett</a>: Warren Buffett’s business philosophy and case studies in autobiographical format</li>
  <li><a href="https://www.youtube.com/watch?v=PHe0bXAIuk0">How The Economic Machine Works</a>: Ray Dalio’s economic model of credit cycles and asset prices</li>
</ul>

<h3 id="startups">Startups</h3>
<ul>
  <li><a href="https://www.amazon.com/dp/B00J6YBOFQ">Zero to One: Notes on Startups</a>: the best of Peter Thiel</li>
  <li><a href="https://pmarchive.com/">Marc Andreessen’s Blog Archive</a>: the best of Marc Andreessen (free!)</li>
</ul>

<h3 id="product-management">Product Management</h3>
<ul>
  <li><a href="https://www.amazon.com/dp/B00DB3D81G">Crossing the Chasm</a>: defines a market as a group of similar customers, and other fundamentals of startup understanding customers and selling</li>
  <li><a href="https://www.amazon.com/dp/B0047GMERK">The Entrepreneur’s Guide to Customer Development</a>: optimization method product-market fit</li>
  <li><a href="https://www.amazon.com/dp/B002C949KE">Predictably Irrational</a>: memorable examples of irrational human behavior</li>
</ul>

<h3 id="data-science">Data Science</h3>
<ul>
  <li><a href="https://www.amazon.com/dp/B00SRYUW5O">Cartoon Guide to Statistics</a>: intuitive guide to fundamentals in statistics</li>
  <li><a href="https://www.amazon.com/dp/B00E6EQ3X4">Data Science for Business</a>: helpful non-technical business overview; essential for data scientists who communicate to non-technical partners</li>
  <li><a href="https://www.amazon.com/dp/1461471370">An Introduction to Statistical Learning</a>: like <a href="https://www.amazon.com/dp/B00475AS2E">ESL</a> but more pragmatic, written by the the same authors</li>
</ul>

<h3 id="successful-interactions-with-people">Successful Interactions With People</h3>
<ul>
  <li><a href="https://www.amazon.com/dp/B003WEAI4E">How to Win Friends and Influence People</a>: the 1936 Dale Carnegie classic still applies today</li>
  <li><a href="https://www.amazon.com/dp/B003GIPEAE">Winning Body Language</a>: helpful modern theory on body language</li>
  <li><a href="https://www.amazon.com/dp/B00AC26KUU">Impro</a>: Improvisation and the Theatre: see the chapter on Status</li>
</ul>

<h3 id="people-management">People Management</h3>
<ul>
  <li><a href="https://www.amazon.com/dp/0679762884">High Output Management</a>: the definitive guide on effective people management techniques; comes across as a bit dry / unempathetic so make sure to balance with HTWFAIP</li>
  <li><a href="https://www.amazon.com/dp/B00DQ845EA">The Hard Thing About Hard Things</a>: the best of Ben Horowitz; practical advise from a startup manager who learned on the job</li>
  <li><a href="https://sive.rs/book/ChecklistManifesto">The Checklist Manifesto</a>: create, refine, and adhere to checklists to improve performance (link is to a free summary rather than the actual book)</li>
</ul>]]></content><author><name></name></author><category term="startups" /><summary type="html"><![CDATA[I’m often asked by friends or startups I advise for a practical reading list that provides context, expected skills, and common vocabulary for the new job. Below is the reading list I gave to my new hires at Square when I led the risk, data science, and Square Capital teams. For each section the list is deliberately short—because I’m picky about signal-to-noise when requiring others to read. Hope you find this helpful:]]></summary></entry><entry><title type="html">Make your metrics easy to memorize</title><link href="https://jbryanscott.com//make-your-metrics-easy-to-memorize/" rel="alternate" type="text/html" title="Make your metrics easy to memorize" /><published>2012-10-29T06:44:00+00:00</published><updated>2012-10-29T06:44:00+00:00</updated><id>https://jbryanscott.com//make-your-metrics-easy-to-memorize</id><content type="html" xml:base="https://jbryanscott.com//make-your-metrics-easy-to-memorize/"><![CDATA[<p>One of the most important responsibilities of an analytics team inside a startup is to evangelize key performance metrics to decision makers elsewhere in the company. This boils down to:</p>

<ol>
  <li>Defining and focusing on a few great metrics</li>
  <li>Ensuring that decision makers understand roughly how these metrics are calculated and why they are the best metrics</li>
  <li>Ensuring that decision makers know the approximate value of these metrics <strong>at all times</strong></li>
</ol>

<p>I focus on #3 in this post.</p>

<p>Why is #3 so important? In startups, decision makers are constantly making decisions. Members from the analytics team usually won’t be there. Therefore, unless decision makers have a persistent idea of their performance metrics, they will inevitably make decisions that are data-ignorant. And a major goal of the analytics team is to avoid the company making data-ignorant decisions.</p>

<p>Phrased another way: When metrics—products of a good analytics team—are easier to use, customers—decision makers around the company—will use them more.</p>

<p>So what qualifies metrics as easy to use? You need to check off #1 and #2, but I won’t address those in this post.</p>

<p>A successful tactic I’ve seen is to make your metrics easy for decision makers to memorize. Once decision makers memorize metrics, they become more comfortable with them, use them more often, and apply them more correctly. This increases the leverage of the analytics team and makes it more effective.</p>

<p>Because your audience is not the type to memorize 68,000 digits of π, you have to simplify your metrics. But how?</p>

<p>For broad consumption, I like to communicate four pieces of information in a metric:</p>

<ul>
  <li>Unit (e.g. users, dollars, days)</li>
  <li>Order of magnitude (e.g. thousands, millions, billions)</li>
  <li>Rounding to two significant digits</li>
</ul>

<p>Examples (from 2012 data):</p>

<ul>
  <li>The decimal value of π: 3.1 (unit-less)</li>
  <li>United States GDP: $15 trillion</li>
  <li>World Population: 7.0 billion people</li>
  <li>Expected odds of being killed in a plane crash in one year for an American: 1 in 11 million (unit-less)</li>
</ul>

<p>I think it’s obvious why units and order of magnitude are important pieces. But why two significant digits?</p>

<ul>
  <li>For memorization’s sake, fewer digits is better. Most everyone can recount that π is about 3.1 or 3.14 but few people can remember more. Worse, more digits can distract the reader from the highest order digits. People also tend to transpose digits of big numbers in their heads. So I’ll take the bare minimum number of digits, please.</li>
  <li>One digit is often not enough to do meaningful calculations for decisions that are within 10%. And for startups, almost all of your atomic metrics-based decisions are calls within 10%.</li>
  <li>Two digits is almost always sufficient for meaningful calculations.</li>
  <li>Three digits doesn’t add nearly as much incremental value, so we’ve already reached diminishing returns on a continuously decreasing function (average value per digit as a function of number of significant digits).</li>
</ul>]]></content><author><name></name></author><category term="startups" /><summary type="html"><![CDATA[One of the most important responsibilities of an analytics team inside a startup is to evangelize key performance metrics to decision makers elsewhere in the company. This boils down to:]]></summary></entry></feed>