<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Scott Carleton on Medium]]></title>
        <description><![CDATA[Stories by Scott Carleton on Medium]]></description>
        <link>https://medium.com/@scotterc?source=rss-657bfe4de777------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*u--pz8SgQGqBfhytPAxIXw.jpeg</url>
            <title>Stories by Scott Carleton on Medium</title>
            <link>https://medium.com/@scotterc?source=rss-657bfe4de777------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:43:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@scotterc/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Principles: Great Work ∞ Great Learning Part 3]]></title>
            <link>https://medium.com/@scotterc/principles-great-work-great-learning-part-3-2db9f15edcb4?source=rss-657bfe4de777------2</link>
            <guid isPermaLink="false">https://medium.com/p/2db9f15edcb4</guid>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Scott Carleton]]></dc:creator>
            <pubDate>Wed, 12 Sep 2018 19:42:47 GMT</pubDate>
            <atom:updated>2018-09-12T19:42:47.094Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Note:</strong><br> This is the third post of a multipart series about the relationship of work and learning, and how it goes together for individuals and for companies. I recommend <a href="http://scottcarleton.com/principles-great-work-is-great-learning">starting at the beginning.</a></p><h3>Act 2: The Lab aka “Alright. I’ll just do it myself”</h3><p>I left BigCo because I wasn’t learning as fast as I wanted to. I was impatient and believed there had to be a better way. Starting my own company wasn’t my first choice. I explored less risky options. MBA program, early startup employee, VC associate. But I ran into a common blocker. These options were all <a href="https://steveblank.com/2018/04/11/why-entrepreneurs-start-companies-rather-than-join-them/">underestimating my value</a>. I (thought) I could do better on my own.</p><p>I’m grateful for my arrogance because it turns out that starting your own company is the equivalent of an educational firehose. My rate of learning was completely within my control. How fast can you learn? Well, how many endeavors can you juggle at one time? Every step forward in creation was its own fount of knowledge. Legal, Accounting, Engineering, Product, Marketing, Sales, Operations, Hiring, Firing, Team Building. You must wear every hat and become competent enough in each to (hopefully) hire someone better.</p><p>After a year I realized I accomplished my initial goal. I was learning a lot — faster than I ever had before. I loved it. I was maximizing my learning but the clock was ticking. I needed a new goal, focused on keeping this going. How do we become successful so that we all can keep learning — to continue doing what we love?</p><p>This would all go away if we didn’t figure out a method to sustain it. But, I didn’t want that method to sacrifice my own learning rate.</p><p>I was fortunate to learn about <a href="http://theleanstartup.com/principles">Lean Startup principles</a>. It clicked. Learning about your customers and eliminating business risks incrementally was perfectly aligned with the work we needed to do to become successful. I became rabidly focused on validated learning to overcome obstacles.</p><p>Incorporating these ideas, a high functioning product development team emerged. Business success required fast iterations. Hypothesizing, executing, reflecting and then repeat. Work and learning coexisted harmoniously with a positive feedback loop. And, the best part was it was fun and addictive!</p><p>A new axiom was beginning to form in my mind:</p><blockquote><em>If you can construct an environment where the team is maximizing their learning then it will maximize business benefits as well</em></blockquote><p>Benefits of this mindset didn’t stop at product development. As this work and learning relationship evolved, we attracted talent who were interested in maximizing their personal work and learning. Since our environment required learning in order to succeed, the highest potential people performed the best and contributed the most to our learning culture. I had required myself to get up to speed on subjects I had never encountered before and because of this, I found a deep belief that others could as well. We focused on growing our people quickly to take on ever greater challenges in the competitive market. Business output and individual output were linked and yielded a strong desire to continue working hard.</p><p>The culture emerged to reflect its people and their values. Collaboration was the default in order to get better ideas into the foreground and learn from them. These collaborations yielded better learning, which further feeds the learning addiction and also created real human bonds between everyone in the office.</p><p>Through this process, and a lot of reflection, I learned that a team can have a happy marriage of individual and business incentives, where each team member’s learning is a win-win.. The positive link between work and learning was now cemented in my mind.</p><p>Despite our talent and virtuous alignment of work and learning. We did not succeed in finding a way to sustain it. One big question remained for me. Could this work at scale? For that, I needed to jump back into larger teams to learn yet again….</p><p><em>To be continued</em></p><p><em>Originally published at </em><a href="http://scottcarleton.com/principles-great-work-great-learning-part-3"><em>scottcarleton.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2db9f15edcb4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Principles: Great Work ∞ Great Learning Part 2]]></title>
            <link>https://medium.com/@scotterc/principles-great-work-great-learning-part-2-6c8041a30ffa?source=rss-657bfe4de777------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c8041a30ffa</guid>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Scott Carleton]]></dc:creator>
            <pubDate>Thu, 12 Jul 2018 19:01:01 GMT</pubDate>
            <atom:updated>2018-07-12T19:01:01.439Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Note:</strong><br>This is the second post of a multipart series about the relationship of work and learning and how it goes together for individuals and for companies. I recommend <a href="https://medium.com/@scotterc/principles-great-work-great-learning-fae5d5e4b5aa">starting at the beginning.</a></p><h3>Act 1: Big Co</h3><p>Entering the working world with a mental model based on maximizing my own learning, I was enamored by my initial experience in a large engineering company. There was so much to learn and absorb! However, this faded as I got up to speed and quickly, I became frustrated. I loved the initial steep learning curve. Once it leveled off, the work didn’t continue to evolve at a high rate. I wanted to keep sprinting up the hill but found that it had plateaued.</p><p>Why was this daily rate of growth so slow? Companies need to innovate and evolve to be competitive. To my dismay, I found my company’s ability to innovate was not based on the desire or ability of it’s most earnest employees to learn. Shouldn’t these employees be encouraged to drive innovation and evolve? Apparently not.</p><p>Reflecting now, I see that in many larger companies, the rate of learning is limited by the organization’s systematic rate — which is set by the company’s lowest common denominator (or at best, average) and not by its most talented people.</p><p>These large companies have become a series of 3-legged races. You have to work together, but you are also dependent on whomever you are tied to. Just like a chain is only as strong as its weakest link, an interconnected engine will only operate as quickly it’s slowest sub-component.</p><p>How does this happen? Does it have to be like this?</p><p>As a company grows, speed and innovation become secondary to consistency. Consistency enables strategic decision making and efficient resource allocation. Consistency also makes the future more predictable, which creates market reliability.</p><p>The least resistant path to consistency is scaling “what we know already works,” which means replicating successful processes. As process begins to dominate, individual learning suffers. Learning is an unnecessary side product, left behind for more efficiency. An increase in process reduces the need for an employee to learn on their own.</p><p>The result of this is that BigCos get reliable output and employees get a reliable job with a set rate of personal growth¹. Bureaucracy, the collection and centralization of process, increases and begins to direct the culture².</p><p>The culture might not be entirely dysfunctional, but it’s not a hotbed of collaboration either because the overriding system discourages risk taking. For an employee, the culture will fit if it aligns with her values, but if her primary goal is learning she’ll become frustrated by spending her time learning BigCo’s particular flavor of process and bureaucracy; not fundamental truths. Sometimes policy/process appear to defy logic, and an employee feels helpless to fix it. “That’s just the way it is around here” you might hear — which only reinforces the lack of autonomy for individuals and demoralizes those who want to learn.</p><p>You can see why BigCos may not be able to retain the most talented candidates who are optimizing for their personal learning and growth.</p><p>I began to fear a future where I would be a cog in this inefficient machine indefinitely. I was struggling to find faster paths of learning within the system, to no avail.</p><p>The moment I realized I wasn’t learning as fast as I wanted to, I started looking towards the door. I had no idea what I wanted to do next. Even so, I took the plunge, trusting that I’d figure out something just like my <em>entrepreneurship</em> professor had…</p><p><em>To be continued</em></p><p>[1] Dictated by the initial learning curve and then the rate of learning dictated by the limiting sub-component of their immediate organization.</p><p>[2] Culture is what is perceived to be rewarded and punished. At BigCo, following process is perceived to be rewarded and vice-versa.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c8041a30ffa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Principles: Great Work ∞ Great Learning]]></title>
            <link>https://medium.com/@scotterc/principles-great-work-great-learning-fae5d5e4b5aa?source=rss-657bfe4de777------2</link>
            <guid isPermaLink="false">https://medium.com/p/fae5d5e4b5aa</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Scott Carleton]]></dc:creator>
            <pubDate>Wed, 11 Jul 2018 21:41:04 GMT</pubDate>
            <atom:updated>2018-07-11T21:41:04.933Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Note:</strong><br>This is the first post of a multipart series about the relationship of work and learning and how it goes together for individuals and for companies.</p><h3>Inception</h3><p>The concept was initially seeded in my mind over a decade ago by a guest lecturer in my university entrepreneurship class. “My first job out of college was with the Ford motor company” he said. “I had great pay, a solid job for life — if I stayed around for the next 40 years I could have had a pension and a nice gold watch. However, after 4 years I left.”</p><p>“You go and work for someone, what’s the exchange? You exchange your time and sweat and they pay you money. Is that a fair trade? No. Here’s what’s missing. Your time can never be recovered. However, money can always be created. You’re giving your most precious asset in return for something ephemeral. What makes it all worth it?“</p><p>Nobody responded.</p><p>“You get to learn. When you put your time and sweat in, you are compensated with money — but what really balances out the equation is the education you receive as a part of that work. The moment I stopped learning at Ford was the day I quit.”</p><p>Until this point, I imagined that I’d always be ‘working to live’ — working to make ends meet while I pursued what I really wanted to do in my remaining time. But, what I wanted to do in my remaining time was to <em>learn</em>, to invest in myself, to improve across a variety of dimensions. My paradigm shifted. Work wasn’t just about money. Work could provide a scaffold for growth. Now I understood how work itself could be fulfilling.</p><p>Going forward, I decided to optimize my work for learning. ‘Am I learning?’ became a guiding question in my life choices. A question that answered ‘no’ a few years later when I quit my first job.</p><p>To be continued…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fae5d5e4b5aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developing People in a Distributed Environment]]></title>
            <link>https://medium.com/hackernoon/developing-people-in-a-distributed-environment-6dac6f639b48?source=rss-657bfe4de777------2</link>
            <guid isPermaLink="false">https://medium.com/p/6dac6f639b48</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Scott Carleton]]></dc:creator>
            <pubDate>Mon, 01 May 2017 14:17:53 GMT</pubDate>
            <atom:updated>2019-05-14T05:36:18.508Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OORAnyXiOn7baW5bxN8v2g.jpeg" /></figure><p><em>This is Part II of a three-part series, </em><a href="https://www.linkedin.com/pulse/engineering-managers-guide-future-work-scott-carleton"><em>An Engineering Manager’s Guide to the Future of Work.</em></a></p><p>Engineers want to believe that distributed relationships can work perfectly; that you can just do your work and not be bothered with the people aspect. That’s false. In a distributed <a href="https://hackernoon.com/tagged/enviroment">environment</a>, it’s even more critical to form human relationships and prioritize “noise” so that we can all better calibrate the signal.</p><h3>Embrace the Noise</h3><p>As <a href="http://randsinrepose.com/archives/the-update-the-vent-and-the-disaster/">many have said</a>, one-on-ones are essential. Currently, I have weekly one-on-ones with my direct reports, and bi-weekly ones with all of their direct reports. That face time is so valuable, for pairing, for collaborating and especially for getting to know each other. These one-on-ones are time spent fostering ‘noise’ which is the key for building trust and calibrating the signals in your relationships.</p><p>Just like mastering anything, the more you improve the more you’re aware how far you have to go. In my early one-on-ones, I was totally allergic to the notion of talking through progress or team dynamics for a half hour. You think: “Shouldn’t I be building, or strategizing, or blogging, or clarifying our direction?” Or: “They’re just going to complain, and I’d rather avoid that.”</p><p>Wrong. Whereas your first inclination in a remote one-on-one may be to run down the list of tasks and blockers, digging into how productive and empowered your direct reports feel is often a better use of your time.</p><blockquote>Not only are one-on-ones absolutely critical for building trust, but they double as an early warning detection system within your organization.</blockquote><p>Not only are one-on-ones absolutely critical for building trust, but they double as an early warning detection system within your organization. As a manager, actively seeking out issues is fundamental — if there’s something you don’t know, you need to race toward it as quickly as possible. If you can become the lightning rod for issues, you become the person who can triage these issues. The earlier you have these signals, the earlier you can move from fire-fighting to fire prevention.</p><h3>What’s your VDAP?</h3><p>Once you’ve made time and embraced the “noise,” I’m finding it’s important to create a system or protocol where you’re able to get the <em>right</em> signals through all of that noise. “VDAP” — Velocity, Direction, Acceleration, Position — is something we’re trialing <a href="https://andela.com/what-we-do">at Andela</a> to facilitate productive relationships within teams.</p><p><strong>Velocity</strong> is meant to gauge an individual or project’s current progress. Do you feel like you or your product is moving well this week? Are you getting things done and overcoming blockers?</p><p><strong>Direction</strong> captures a broader understanding of the project and the team’s goals. Do you know where you’re going? Do you know what the goal of the current project is — and how it fits into the company’s goals?</p><p><strong>Acceleration</strong> is a measurement of learning and growth. Is this week better than last week? Are you or your team moving more quickly than you were last week?</p><p><strong>Position</strong> focuses on the current and future state of not only the project, but more importantly the individual’s role on the team. Are you happy with your progress? Do you like your current role? Do you understand where you’re at, where you want to be, and the difference between the two?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RNYc1j2dA6iJZQD-.jpg" /></figure><p>It’s absolutely critical to understand how your team sees and feels about their work. VDAP is a really helpful, concise method to <a href="http://randsinrepose.com/archives/bored-people-quit/">detect boredom</a>, drowning or blockers.</p><p>It can be a nice, casual protocol such as “hey, what’s your V-Dap?” with quick responses. Or, you can go in-depth on a project and break down each piece accordingly.</p><p>The goal of VDAP is to isolate key signals and burrow down into them to get a regular cadence. It borrows a bit from physics — literally, an object moving through space — as well as agile concepts, mainly Velocity and Direction. At Andela, we prioritize getting people pointed in the right direction and accomplishing things every day, and use small course corrections over time to steer the ship.</p><p>Distributed teams benefit from VDAP because it provides a framework for thinking about your work and how to communicate it upwards in a compact format. If you can recognize when a team is getting things done but not moving faster each week, you have a good signal to dive deeper into how to optimize. If they’re getting things done but not sure where they’re heading, it’s a signal to step in and help that team plan out the roadmap.</p><blockquote>The ideas coming from the bottom are good ones — and as a distributed manager, it’s your job to expose the larger business goals and challenges to your team.</blockquote><p>Ultimately, the people building the application and the code have a lot more information about the problem than you do as the manager. The ideas coming from the bottom are good ones — and as a distributed manager, it’s your job to raise them upward. It’s also your job to expose the larger business goals and challenges to your team so that they’re able to think about how to break down those problems. And chances are, their solutions will be much better than what you (the manager) could come up with. To put it simply, they see what you can’t.</p><h3>The Zone of Proximal Development</h3><p>Great work is great learning — if you’re truly delivering, you’re learning constantly. If your VDAP is high, you’re in a position to maximize both output and learning velocity simultaneously. Now we can optimize the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JFHEHgpWJ8tJx6q5.jpg" /></figure><p>The “Zone of Proximal Development,” or “ZPD,” is a place where an individual can level up consistently. It’s that goldilocks zone where whatever you’re working on isn’t too easy, and it’s not too hard — it’s attainable but also challenging enough for you to build. In the same way that smaller pull requests are easier to review and merge, tasks in the right ZPD are easier to level up on.</p><p>In order to speed up learning velocity we need two things: a developer’s ZPD and a task’s relative difficulty level for that developer. Neither of these problems are simple. Determining a developer’s ZPD — a moving target — requires a historical record of output and some methodology to determine if a person already ‘knows’ something. Determining a given task’s relative difficulty requires categorizing and understanding it at a granular level, taking a best guess approach and then iterating on it as you collect more data. Thankfully, this leads to a system that improves over time. The more data we collect, the better we can match types of tasks to developers and then improve their learning velocity.</p><blockquote>But what about determining if someone ‘knows’ something? It’s more challenging than it sounds.</blockquote><p>But what about determining if someone ‘knows’ something? It’s more challenging than it sounds. You can’t ask if someone knows something and expect any real accuracy. Universities solve for this by administering tests that ask students to provide an output that’s congruent with the knowledge they’re supposed to have. <a href="https://hackernoon.com/tagged/engneering">Engineering</a> interviews tend to fall on the same crutch using whiteboard questions as a proxy. Our methodology is a bit different and it revolves around the latest advancements in learning sciences.</p><p>Instead of tests, assessments or whiteboarding, we’re looking to observe behaviors or beliefs to confirm whether an individual has a certain knowledge set. By collecting data points on these behaviors and beliefs that we’ve been observing for each of our developers, every day for the past three years, we can create a probabilistic model to determine confidence in someone’s knowledge. Leveraging this in the future, we will soon be able use machine learning and other AI techniques to give us predictors of current knowledge levels and determine what feedback is necessary at what time to help someone improve.</p><p>For instance: If I have a GitHub pull request of JavaScript, I can statically parse that and have a pretty good sense of whether you understand prototypal inheritance — and we can figure out the probability and the accuracy of that. If we determine that you don’t fully grasp the intricacies of prototypal inheritance, then we can look at your past knowledge and how you’ve learned to determine if it’s in your ZPD. If it isn’t, we can identify the gaps, fill them and prepare you better to try and tackle it.</p><p>At Andela, we’re building the systems that allow us to understand when a task is in the right ZPD for an engineer. We’re in the early days, but the potential impact for engineering organizations that are able to leverage the learning sciences to develop their individual contributors at scale is massive.</p><p>But more on that to come. Stay tuned for next week’s post, where we’ll discuss how to scale efficient, distributed teams across all parts of the organization.</p><figure><a href="http://bit.ly/HackernoonFB"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hqOaABQ7XGPT-OYNgiUBg.png" /></a></figure><figure><a href="https://goo.gl/k7XYbx"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgw1jkA6hgnvwzTsfMlnpg.png" /></a></figure><figure><a href="https://goo.gl/4ofytp"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKBpq1ruUi0FVK2UM_I4tQ.png" /></a></figure><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a> family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35tCjoPcvq6LbB3I6Wegqw.jpeg" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6dac6f639b48" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/developing-people-in-a-distributed-environment-6dac6f639b48">Developing People in a Distributed Environment</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Engineering Manager’s Guide to the Future of Work]]></title>
            <link>https://medium.com/hackernoon/an-engineering-managers-guide-to-the-future-of-work-2d139eb3137e?source=rss-657bfe4de777------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d139eb3137e</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Scott Carleton]]></dc:creator>
            <pubDate>Tue, 18 Apr 2017 15:17:46 GMT</pubDate>
            <atom:updated>2019-05-14T05:38:00.219Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dDDn3TWe_MVe3dTWUFmdsw.jpeg" /><figcaption>Andela &lt;&gt; Zapier team meeting or Brady Bunch intro?</figcaption></figure><p>Last month, Stack Overflow released its <a href="https://stackoverflow.com/insights/survey/2017">annual Developer Survey</a>, which polled over 64,000 developers across the globe about their favorite technologies, coding habits and work preferences. One of the key highlights was a strong preference for distributed work. A majority of developers (64%) reported working remotely at least one day a month, and 11% reported working remote full-time. Even more telling is that developers ranked “remote options” as a top priority — <a href="https://qz.com/950973/remote-work-for-programmers-the-ultimate-office-perk-is-avoiding-the-office-entirely/">the ultimate office perk</a> — second only to number of vacation days when assessing new job opportunities.</p><p>If you believe that <a href="https://www.joelonsoftware.com/2016/12/09/developers-are-writing-the-script-for-the-future/">developers are writing the script for the future</a>, these results would indicate that the next act is going to be remote-first. Factor in the severe <a href="http://www.ciodive.com/news/skills-gap-clear-as-lack-of-software-talent-has-a-direct-revenue-impact/438544/">shortage of U.S. technical talent</a> and <a href="https://www.bloomberg.com/news/articles/2017-04-03/new-h-1b-guidelines-crack-down-on-computer-programmer-jobs">recent restrictive work policies</a> on top of that, and it would appear that the distributed “<a href="http://observer.com/2016/03/the-future-of-work-will-be-distributed/">future of work</a>” might arrive much sooner than anticipated.</p><p>Distributed, however, is very hard to do well — it requires a lot of thoughtful strategy, much more than just setting up remote employees on Slack. And if tech companies want to effectively leverage this model, they’ll have to commit 100%. It might result in some growing pains at first, but it will ultimately result in processes and systems that will improve communication and efficiency across the entire organization.</p><p>During the last six months as VP of Technology at <a href="https://andela.com/">Andela</a>, I’ve been running a team of nearly 40 people — spread out across New York, Lagos, and Nairobi — who are building out the systems and tools we need to make distributed teams excellent and scale. For Andela, that means growing from 500 people to over 100k in less than 10 years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cCJsjHOR4ErrjvSk87CpzQ.jpeg" /><figcaption>Andela’s Lagos, Nigeria HQ</figcaption></figure><p>GitHub and consequently the pull request was a huge inflection point for distributed engineering teams — it decoupled the ‘work’ required from the ‘integration’ of it. Now, the challenge at hand is building off that to come up with the “pull request” that works for the shared context of a company. Can any one of our 500+ employees, whether an engineer or an operations associate, get up in the morning and figure out exactly what they need to get done, do the work, submit the request, benefit from continuous integration, and know that they’re improving the system daily — even if they’re in a time zone that’s 8 hours away from their other locations?</p><p>We’re getting there, but it’s not easy. Over the next three blog posts, I’ll dig into how to build dynamic systems and controls for distributed teams, how to develop people in a distributed environment, and how to scale distributed teams in a high-growth <a href="https://hackernoon.com/tagged/startup">startup</a>. Stay tuned!</p><h3>Part I: Building Dynamic Systems and Controls for Distributed Teams</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uz-xi20q1J_14QIU6SPHcA.png" /></figure><p>Great processes lead to great distributed work. But guess what? Very few teams, especially in the startup world, have great processes. Unless you’re old and stodgy and have had the same processes forever, which never happens, things are probably changing too quickly.</p><h4>A Results-Only Work Environment</h4><p>There isn’t a playbook that works for all distributed companies, whether we’re talking about partially distributed (i.e. two of your engineers decided to move to Portland) or fully distributed (i.e. Automatic, the $1B company with 400 global employees <a href="https://www.inc.com/glenn-leibowitz/meet-the-ceo-running-a-billion-dollar-company-with-no-offices-or-email.html">working from wherever they please</a>).</p><p>There’s also a difference between the company that’s been building distributed processes from day one (where I’m coming from with Andela), and the company that’s trying to go distributed at day 500. The latter, as you might imagine, presents a greater challenge, as managers are tasked with altering existing processes to accommodate their new remote team members. In both cases, however, it’s essential to build out processes one by one that help everyone exchange feedback, elevate challenges, and communicate clearly without relying on face time.</p><blockquote>Ultimately, a distributed work environment forces managers to relinquish control.</blockquote><p>Ultimately, a distributed work environment forces managers to relinquish control. When you’re working asynchronously, you can’t have nearly as many interactions back and forth to figure out a problem. You can’t have team members blocked. As a result, distributed forces you to push out autonomy and decision making to your team.</p><p>How do you do this? You create systems of measurement where everyone has buy-in and understands explicitly the KPIs that they’ll be measured on. The measurements should be as simple as possible, so you’ll need to break down problems into smaller pieces to make solving them easier. At the end of the week, your goal should be to have one number for each engineer and one number for each of your teams, so you can objectively know how well a team is doing and how much of your attention they need.</p><p>Once you’ve chosen the measurement, and decided on a benchmark, you throw the team out the door and see how it goes.</p><p>This only works if you recognize that these systems of measurement are totally fallible and that they’ll change as you grow. These aren’t do-or-die measurements, they’re ways to gather information about what’s wrong — and inform future systems of measurement. You’ll probably feel like you’re giving up a lot of control, but if you’re still getting the results you want, then who cares?</p><h4>Signal vs. Noise</h4><p>The major challenges around remote work come down to signal versus noise. When you’re relying solely on Slack, email and Google Hangouts, all of that information is signal, and it carries the same sense of urgency or severity. This presents a challenge for managers, because when a colleague says, “you know what, this was frustrating,” you need to know whether that frustration is at the bottom of their mind or the top — in which case, it’s something you need to deal with immediately.</p><p>In a distributed work environment, in other words, you don’t have the noise that helps you calibrate how serious the signal is. Getting a beer with a team member is wonderful noise because you get to know that person well enough to understand what’s important to them and therefore calibrate your communication.</p><blockquote>Teams that are new to distributed tend to react to everything, which leads to a common problem: signal overload</blockquote><p>Teams that are new to distributed tend to react to everything, which leads to a common problem: signal overload. These teams suffer from an overload of information across their Slack channels, Google docs, GitHub, Trello, etc. Discovery of information is chaotic and time consuming, and friction rises in communication when information doesn’t have a place to settle.</p><p>As a distributed manager, you have to make sure that information is flowing openly and that support requests coming in have a place to live. When you get feedback, it’s essential to have the processes in place to distill that information into something valuable and not forget about it. For instance, once a GitHub issue is created, it’s really easy to collaborate and have a focused conversation around that issue — this is because this issue serves as a shared context, an ‘artifact’ if you will. Trello is a great tool to capture disparate information, localize a conversation around it and then assign a process for resolving it. Consistent retrospectives, explicitly documented on <a href="https://hackernoon.com/tagged/google">google</a> docs, are wonderful for making sure all voices are heard and working through systemic issues as a team.</p><p>In a world of signal overload, you need to make sure you’re not missing the right signals in your communications.</p><h4>Managing Slack Overload</h4><p>Slack is incredibly overwhelming, and it’s all signal. I’m sold on Slack, and our entire team uses it, but it’s a tool — and like any other tool, you can easily abuse it.</p><p>In its worst form, chat allows us this <a href="https://m.signalvnoise.com/is-group-chat-making-you-sweat-744659addf7d">“always on meeting”</a> where nothing is defined and action items aren’t carried forward. At its best, it’s an asynchronous tool to keep everyone apprised and stop the back-door, one-to-one conversations. <a href="https://hackernoon.com/tagged/chatops">ChatOps</a>, as a development technique, is fantastic — for instance, using bots to deploy so everyone knows what’s happening.</p><p>As with most technologies, you need the tool to be able to create the behavior you want, but you need a culture change and belief change in order to use the tool effectively. Slack is a tool to hash things out, but the result has to live in a designated place where it can be acted upon and solved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*y4b4U9xACF0RyxPM05sDXg.png" /><figcaption>A place for information to live: i.e using GitHub issues for major decision making</figcaption></figure><p>Using Slack effectively means getting everything into public channels — which helps reduce the one to one to one direct messages which serves only to obfuscate problems. I believe the health of an engineering team could be measured by how many issues are raised and resolved in a given time period, and how fast that iteration is. The goal, then, is to get those issues to be public immediately, and broken into small enough pieces so that they’re resolved as quickly as possible.</p><p>The more things that are discussed in public channels, the more resolutions are happening and the greater circle of people who can participate and witness those resolutions which acts as a feedback loop — who doesn’t want to resolve issues collaboratively? If things stay in private, they tend to stay unresolved for longer.</p><p>It’s not as simple as it sounds. If you’re operating in an organization with over 500 people, like Andela, channels are good to set topics, but they get tough to manage. We’re still in the early days of understanding how to cultivate these communities and how to set KPIs to get the team focused on improving our chat behaviors.</p><blockquote>Great distributed teams are the result of good processes.</blockquote><p>To tie it back: Great distributed teams are the result of good processes. Good processes are focused on results, finding the right home for information to live, and making sure your team surfaces problems publicly so that they can be dealt with. In the next post, I’ll speak to the particularly difficult challenge of developing people in a distributed environment.</p><figure><a href="http://bit.ly/HackernoonFB"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hqOaABQ7XGPT-OYNgiUBg.png" /></a></figure><figure><a href="https://goo.gl/k7XYbx"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgw1jkA6hgnvwzTsfMlnpg.png" /></a></figure><figure><a href="https://goo.gl/4ofytp"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKBpq1ruUi0FVK2UM_I4tQ.png" /></a></figure><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a> family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35tCjoPcvq6LbB3I6Wegqw.jpeg" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d139eb3137e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/an-engineering-managers-guide-to-the-future-of-work-2d139eb3137e">An Engineering Manager’s Guide to the Future of Work</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m Joining TpT]]></title>
            <link>https://medium.com/@scotterc/im-joining-tpt-d9b758a4ef31?source=rss-657bfe4de777------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9b758a4ef31</guid>
            <dc:creator><![CDATA[Scott Carleton]]></dc:creator>
            <pubDate>Tue, 17 Feb 2015 20:18:42 GMT</pubDate>
            <atom:updated>2015-02-17T20:19:07.708Z</atom:updated>
            <content:encoded><![CDATA[<p>February 14, 2015</p><p>Over the past 4 years I’ve been building <a href="http://www.artsicle.com/">Artsicle.com</a>. It has evolved through many versions into an amazing community of artists — a place to showcase their work, connect with others and better allow the world at large to discover them. As part of that evolution, we have started the process of turning Artsicle into a non-profit organization. I’ll be sharing more about this decision and what it means for us soon, but today I want to share another big announcement.</p><p>I am joining <a href="https://www.teacherspayteachers.com/">Teachers Pay Teachers</a> — or TpT as we like to call it — as Engineering Lead. If you haven’t heard of TpT, think Etsy for lesson plans, curriculums, and educational resources. Teachers can find the materials they need to better serve their students or, better yet, share and sell their own resources with peers. TpT is putting valuable time back into the hands of teachers who can use every <a href="https://www.facebook.com/TeachersPayTeachers/posts/10152949983501874">spare minute</a> — while putting <a href="http://blog.teacherspayteachers.com/moffatt-girls-new-year-new-tpt-millionaire-teacher/">dollars</a> into the pockets of highly-deserving educators. It’s <a href="https://www.teacherspayteachers.com/About-Us">working</a>, it’s a hell of a mission, and it’s an incredible place to be.</p><p>I see a huge opportunity for TpT to lead the education space to make the changes that the tech world has made in recent years. On your next application, you wouldn’t build a web server or database from scratch. No, you would “stand on the shoulders of giants” and take advantage of everything that open source has to offer. In many ways, TpT is the open source of the education community. Everyday teachers are asked to re-invent the wheel and create their curriculums from scratch, while catering to dozens of different student needs. This results in an incredible amount of duplicated work — but it doesn’t need to be. When I’ve visited classrooms, I’ve seen that the real art of teaching is engaging students and helping them overcome their individual obstacles. TpT has the potential to free up teachers’ time to focus on students. By leveraging the global teaching community, TpT can give them the <em>exact </em>materials they need for the problems at hand with a single click.</p><p>As you might expect, there are huge technical challenges to be overcome and I’m putting together a tech dream-team to design solutions for our educational future. We’re building a fantastic engineering culture that is focused on the same ideals our community has taught us: a culture of respect, collaboration and learning.</p><p><a href="http://grnh.se/ef17dr">Come join us</a>.</p><p><em>Originally published at </em><a href="http://scottcarleton.com/joining-tpt"><em>scottcarleton.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9b758a4ef31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Codebase Velocity]]></title>
            <link>https://medium.com/@scotterc/codebase-velocity-1ccc73fce93b?source=rss-657bfe4de777------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ccc73fce93b</guid>
            <dc:creator><![CDATA[Scott Carleton]]></dc:creator>
            <pubDate>Wed, 12 Feb 2014 04:42:34 GMT</pubDate>
            <atom:updated>2014-02-12T04:42:34.965Z</atom:updated>
            <content:encoded><![CDATA[<p>Compiled vs dynamic? Loose vs static typing? To rebase or not to rebase? Tabs or spaces? Pursuing high codebase velocity at a startup tends to center around technology choices. However, most forget the importance of learning to “take out the trash” efficiently.</p><p>Clearly deprecating code, removing unused code or adding tests for untested code are all important. But equally important is diligently reshaping of codebase methodologies on a consistent basis. For example, if you change from using onclick to unobtrusive JS, how do you make sure the whole codebase is converted in a timely manner? It might seem like premature optimization at first, but it’s absolutely key that new team members have good examples to work from on day one. A “trash free” environment means velocity stays high with each new hire, instead of losing hours (or days!) figuring out which methodology is up-to-date or which stylistic format we’re following this month.</p><p>When hiring, I’ve learned to look for engineers who will want to be “cleaners”. When they find a better way of doing something, they update the entire codebase (or as much as possible) to use the new methodology. This cleaner mentality is a great indicator of a team player who is in it for the long haul with the team, willing to do the dirty work to make everyone’s job better.</p><p>So lead by example. Make sure you have a process in place to actively reshape your methodologies. I guarantee the result will have more impact on your velocity than any technology choice you make this year.</p><p>How do you maintain high velocity with your team?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ccc73fce93b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>