<?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 Tom Redman on Medium]]></title>
        <description><![CDATA[Stories by Tom Redman on Medium]]></description>
        <link>https://medium.com/@redman?source=rss-9465bd57b96------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*b9woAMLne1eDFiZEfD5pGg.jpeg</url>
            <title>Stories by Tom Redman on Medium</title>
            <link>https://medium.com/@redman?source=rss-9465bd57b96------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:54:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@redman/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[Site Command is now free for all new and existing customers. Yup, we’re choosing $0 MRR.]]></title>
            <link>https://redman.medium.com/site-command-is-now-free-for-all-new-and-existing-customers-yup-were-choosing-0-mrr-a94308910826?source=rss-9465bd57b96------2</link>
            <guid isPermaLink="false">https://medium.com/p/a94308910826</guid>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[bootstrapping]]></category>
            <dc:creator><![CDATA[Tom Redman]]></dc:creator>
            <pubDate>Wed, 15 Apr 2020 20:37:06 GMT</pubDate>
            <atom:updated>2020-04-15T20:37:06.870Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Site Command is now free for all new and existing customers. We are forgoing all revenue until at least September.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aOJGWIVP1MGMGgpx7ibxjQ.jpeg" /></figure><p>For the past year I’ve been bootstrapping Site Command <a href="https://medium.com/@redman/i-spent-my-evenings-weekends-building-a-construction-management-product-41de1db80a5c">in my evenings and weekends</a> with the goal of helping small home builders and contractors manage their projects.</p><p>A big part of the appeal of bootstrapping is the ability to have full control over your company. I’m not beholden to anything or anybody except for my values and my customers. And with that comes the freedom to make choices that aren’t good for <em>business</em>, but rather, good for <em>people</em>. Choices that put people over profits. Humanity over shareholder value.</p><p>The COVID-19 pandemic has had devastating effects on everybody, and small businesses are especially hurting right now. Since Site Command is built for small businesses, I thought maybe we could help even if it’s in a small way.</p><p><strong>Starting today </strong><a href="https://sitecommandapp.com/"><strong>Site Command</strong></a><strong> is completely free for all new and existing customers.</strong> We will earn no revenue from now until at least September. This policy will last until at least then, but I may decide to extend that down the line depending on how the pandemic plays out.</p><p>By bootstrapping, I’ve been able to keep overhead very low. I’ll cover all operating costs until it feels reasonable to lift this policy. I just don’t want to see any of our customers go out of business while trying to pay us. Things are hard enough for them and we’re in a position where we can float these costs.</p><p>If you know any contractors, please let them know. I’d be happy to help them get setup and maybe Site Command can help support their operations through this crazy time.</p><p>Keep well ❤️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a94308910826" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[More Product Management Mental Models for Everybody]]></title>
            <link>https://redman.medium.com/more-product-management-mental-models-for-everybody-6597559c7a5c?source=rss-9465bd57b96------2</link>
            <guid isPermaLink="false">https://medium.com/p/6597559c7a5c</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Tom Redman]]></dc:creator>
            <pubDate>Wed, 05 Feb 2020 18:11:18 GMT</pubDate>
            <atom:updated>2020-03-05T22:04:56.294Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>More Product Management Mental Models for Everyone</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XjFOKNBldylAUte5l1QPGQ.png" /><figcaption>Manipulated illustration originally by Ben Coy</figcaption></figure><p>Whether you know it or not, you already have a number of mental models about how the world works in your mind. And they’re different from mine, and everybody else’s, because they’re derived from your unique experience and worldview.</p><blockquote>Mental models are simple expressions of complex processes or relationships. These models are accumulated over time by an individual and used to make faster and better decisions.</blockquote><p>These models are tools our brains use to organize patterns of behavior, production and outcomes. They are learned, experienced, internalized and ultimately applied back into the world through our creative and professional outputs.</p><p>These are some of the mental models I’ve collected over the years as they relate to product management.</p><h3>Seeing the Front</h3><p>Minimize faulty decision-making by ensuring you “personally see the front”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L9AZN_ZerW3425YEvVAGeA.png" /></figure><h4>How it’s useful</h4><p>This one is pretty simple: As a product manager, you should always stay in touch with your customers. Never let others’ research fully supplant your own.</p><p>Avoid fully relying on secondhand information which is prone to miscommunication, external biases, and faulty assumptions. Your firsthand information will also serve to improve the quality of your secondhand information.</p><h3><strong>Tendency to minimize energy output</strong></h3><p>Behavior is often governed by a tendency to minimize energy usage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G7bCBu56dlJowLyQYMd9oA.png" /></figure><h4>How it’s useful</h4><p>Deviating from the status quo takes mental energy, if not physical.</p><p>Put another way, behavior modification is hard because of a natural resistance to change.</p><p>The product you build needs to overcome a person’s natural resistance to change, which ultimately stems from a conservation of energy.</p><p>Build things with the simplest interactions and flows possible. Make choices on behalf of the user and double-down on smart defaults. Remove all barriers to engagement that are within your control. If you’re between two options, pick one and don’t offer a toggle.</p><p>Start there, and only include things as they become truly painful to not have.</p><p>If your users have spent the initial energy to try your product, capitalize on that by making the rest easy for them.</p><h3>Don’t rely on users to reading copy</h3><p>A large percentage of users will automatically bypass written copy, so you need guardrails in place to make sure they’re still successful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pV7Qdtq_XYF5l_WVwmajJA.png" /></figure><h4><em>How it’s useful</em></h4><p>Some people will read what you write, many won’t.</p><p>Don’t allow critical information to be passively consumed. You can force acknowledgement or, better, improve the guardrails in your product such that critical paths are navigated organically.</p><p>Note that this doesn’t mean you should remove or neglect copy. Great copy is essential to a great experience, it just shouldn’t be used as the only line of defence.</p><h3><strong>Opportunity costs</strong></h3><p>Literally every choice you make comes with one or more trade-offs as a part of the decision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fvSPtp-6xeCG-aoZNWtKkw.gif" /><figcaption>Frazz by Jef Mallett for June 15, 2010</figcaption></figure><h4><em>How it’s useful</em></h4><p>This is a classic.</p><p>It’s compromises all the way down. Be honest about the compromises that come with any given decision. Acknowledge and understand them. Compare these trade-offs to the other possibilities to get a better picture of the impact of your decision.</p><p>You’ll run into this one almost every day.</p><h3>Team psychology matters</h3><p>Humans are imperfect and irrational beings. This affects your team’s ability to equally deliver otherwise equal products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eyD-ISieqCw9oUw3J6lSEg.png" /></figure><h4><em>How it’s useful</em></h4><p>Imagine you’re deciding which feature to build next. You’ve whittled your options to two choices, each with equal scope and complexity:</p><p><strong>Feature A:</strong> has slightly <em>higher</em> customer value than Feature B, but is related to something the team has done many times in the past.</p><p><strong>Feature B:</strong> has slightly <em>less</em> potential value for the customer, but it’s exciting and new from a product development perspective.</p><p>Because Feature B is more exciting for the team, it actually shifts the value-to-effort ratio in its favor. The net result is that feature B might be shipped sooner because your team is enthusiastic about it. It’s not a slog to build.</p><p>Conversely, it’s possible that boredom will translate into shipping Feature A more slowly. It happens. We’re human.</p><p>And according to the law of <a href="https://blackboxofpm.com/the-time-value-of-shipping-6deaf8d7d565">the time value of shipping</a>, <em>a product shipped earlier is worth more to customers than product shipped at a later time</em>, the realized customer value might end up being equal or even greater with Feature B!</p><h3>Increasing, marginal<strong>, and diminishing utility</strong></h3><p>The value of additional production tends to vary with scale. A unit of additional work has the potential to add either significant value, marginal value, or negative value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FPQ-DVh5Me7ilCtHbOwFbA.png" /></figure><h4>How it’s useful</h4><p>Not all units of work are made equal. For simplicity’s sake, think of a unit of work as a “day of engineering”.</p><p>Some units of work can result in a step function in value by breaking through a “critical point” of utility, unlocking the full potential of all preceding work.</p><p>For example, imagine you’re building a reporting product for marketers. Your team spent the last 4 months perfecting the charts, graphs, typography, and export functionality. It’s perfect!</p><p>Except nobody’s using it. Why?</p><p>It turns out marketers absolutely <em>need</em> the ability to upload their logo to the reports that they send to clients. Without that, everything else is moot.</p><p>Therefore, for any of the team’s prior work to matter, one additional unit of work is required. With one more day of engineering, you are able to unlock the utility of the preceding work and marketers around the world rejoice!</p><p>On the other hand, some units of work will only add marginal utility or worse, no utility at all.</p><p>In the case of marginal utility, you’re just keeping up with inflation. This is not a great place to be. Taking that a step further, units of work that no longer deliver utility are actually diminishing the value of your product due to <a href="https://blackboxofpm.com/the-time-value-of-shipping-6deaf8d7d565">the time value of shipping</a>. This is the worst place to be!</p><p>For example, if you keep working on the logo upload feature beyond its functional utility, your product is actively getting worse because you’re not actively making it better.</p><p>That’s it for now!</p><p>To reiterate a salient point from Brandon’s original post, mental models are useful in some contexts and less so in others. Don’t be too prescriptive with the models I’ve outlined here. Rather, incorporate them into your personal <a href="https://jamesclear.com/great-speeches/a-lesson-on-elementary-worldly-wisdom-by-charlie-munger">latticework</a> of models. Combine, mold, and shape them as a part of your unique contribution to the world.</p><p>And if you do end up writing some of them down, I want to hear about them!</p><p><strong>If you enjoyed this, please spread the word by clapping 👏 💚 and share freely </strong>🙏</p><p>I’d also love to hear from you on <a href="https://twitter.com/redman">Twitter</a>!</p><p>— Tom</p><p><em>Special thanks to </em><a href="https://twitter.com/twanlass"><em>Tyler Wanlass</em></a><em> for giving this an early read over and for our insightful discussions on mental models.</em></p><p><em>This article was inspired by </em><a href="https://medium.com/u/9f35acc581af"><em>Brandon Chu</em></a><em>’s </em><a href="https://blackboxofpm.com/product-management-mental-models-for-everyone-31e7828cb50b"><em>Product Management Mental Models for Everyone</em></a><em>. I highly recommend reading this!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6597559c7a5c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I spent my evenings & weekends building a construction management product.]]></title>
            <link>https://redman.medium.com/i-spent-my-evenings-weekends-building-a-construction-management-product-41de1db80a5c?source=rss-9465bd57b96------2</link>
            <guid isPermaLink="false">https://medium.com/p/41de1db80a5c</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[construction]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[indie]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Tom Redman]]></dc:creator>
            <pubDate>Tue, 10 Sep 2019 13:06:11 GMT</pubDate>
            <atom:updated>2019-10-16T23:46:31.351Z</atom:updated>
            <content:encoded><![CDATA[<h3>For the last six months, I spent my evenings &amp; weekends building a construction management product. Here’s what it looks like &amp; why I built it.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HAq4r5c4U3oR43lHSLOJfQ.jpeg" /></figure><p>I’ve built a few things in the past, like <a href="https://apps.apple.com/app/lessons-invoicing/id717994393">an invoicing app</a>, a Slack-based <a href="https://teambook.io/">automated team directory</a>, and a household inventory program.</p><p>These were each the result of a personal problem I was facing. (Except the inventory program: I was 12 and it was a solution in search of a problem. It never achieved P/M fit.)</p><p>But why would I spend my evenings and weekends building, of all things, <em>construction management software for small teams</em>?</p><p>I’ll tell you why: <strong>it’s an underserved market desperate for modern management tools built specifically for them.</strong></p><p>Last summer, my good friend Josh told me about the operational challenges he faces with <a href="http://ghostreconstruction.com/">his reconstruction company</a>. He said there weren’t any great solutions for operators his size and asked if I could build him a custom software solution.</p><p>Naturally, I was first curious to understand if Josh’s problems were common. If they were, I thought I might be able to build something that would benefit thousands of people, instead of just dozens.</p><p>I was amazed when after talking to ten local construction companies, they nearly all told me a very similar story: keeping projects on track and their team and customers in the loop is a full-time job. It’s manual, it’s tedious, and worst of all, it’s error-prone. Existing solutions are way overpriced for their size, and overkill in terms of features.</p><p>Well, that right there sounds like what the French call<em> a market opportunity</em>.</p><p>Next time you chat with a general contractor or landscaper or tradesperson, ask her how many phone calls she gets a day from clients wanting updates, or how many notes are written or lost on a napkin in their truck. The answer itself doesn’t matter, except that very few will tell you that these things don’t happen.</p><p>This is exciting and all, but simply identifying a problem is not enough to justify building a solution.</p><p>There’s a high opportunity cost when you choose to build something in your spare time. You need more than a problem, <em>you need to make sure you also care about the problem</em>. Otherwise, it’s going to be a real slog and the likelihood of eventually shipping something is very low.</p><p>In this case I feel quite lucky because I love the construction industry. I spent a year after high school as a drywaller and my summers during university doing residential and light commercial construction. Though there were long days, I thoroughly enjoyed the people, the work and the satisfaction that came with <em>building</em>.</p><p>I guess some things never change.</p><h3>Introducing Site Command</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZIxRZ1e-P6gA8Pevfw034A.png" /></figure><p><a href="https://sitecommandapp.com/?utm_source=medium&amp;utm_medium=cta&amp;utm_campaign=about_to_launch">Site Command</a> is a construction management product specifically built for small construction teams. The goal is to improve communication between contractors, their team members and their customers, all in one place.</p><blockquote>👉 If this sounds interesting, you can <a href="https://sitecommandapp.com/?utm_source=medium&amp;utm_medium=cta&amp;utm_campaign=about_to_launch">try Site Command free for 14 days</a>. I’d love to hear your feedback if you give it a try!</blockquote><p>Site Command automatically keeps customers updated about the status of their projects, hopefully reducing the number of “status update” emails and phone calls contractors get every day. It also allows customers to quickly sign-off on change orders and material selections.</p><p>Project managers can create work orders for their crew that include the project location, expected start and end dates, material location, and any other details required to get the job done. Work orders can also be sequenced with each other (e.g., drywalling <em>typically</em> happens after framing).</p><p>Team members and subcontractors can use Site Command on their phone to add notes, photos or documents to a work order, change order or material selection.</p><p>But enough talk. Here are some screenshots of the product itself:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KpwOOlrWfAK83pfKg1Lgpw.png" /><figcaption>The project manager’s home base</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jyj3KokRTSkiRxmsvSCGzA.png" /><figcaption>An example of some work orders</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lG784OF9dW9ZXTUVL7hIFg.png" /><figcaption>Assigned team members will get email notifications for work orders</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Alm7vNEY0l8XgmL2V2E-w.png" /><figcaption>The customer’s project overview</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SeDWnj3CHVTkt9WX3se_Jg.png" /><figcaption>Customers can approve or reject change orders through the app</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j8QYhyD_4yvrNm1CE1HbSQ.png" /><figcaption>Customers can approve change orders via email too</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GYutcpBoE4aqO_5r47rNJQ.png" /><figcaption>Customers can also choose to receive status updates on work orders</figcaption></figure><p>If you’ve made it this far — thank you. Please let me know your thoughts!</p><h3>An ask…</h3><p><strong>If you think Site Command could possibly work for you or somebody you know, I would be eternally grateful for your or their feedback.</strong></p><p>I would be thrilled if you forwarded them this article or <a href="/service/mailto:tom@sitecommandapp.com">emailed me</a> with an introduction. I’m keen to do as much research as possible, and that means talking to as many people as possible and learning from them.</p><p>👉 And don’t forget, you can <a href="https://sitecommandapp.com/?utm_source=medium&amp;utm_medium=cta&amp;utm_campaign=about_to_launch">try Site Command for free</a>! If you refer a paying customer, you’ll also get 10% off Site Command forever. Forever. Forever.</p><p>Feel free to ping me anytime on <a href="https://twitter.com/redman">Twitter</a> or <a href="http://tom@sitecommandapp.com/">email</a>, even just to say hi! 👋</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41de1db80a5c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Specification Example: A Look at Buffer Analyze’s “Answers” Feature]]></title>
            <link>https://redman.medium.com/product-specification-example-a-look-at-buffer-analyzes-answers-feature-8fc42c485929?source=rss-9465bd57b96------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fc42c485929</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Tom Redman]]></dc:creator>
            <pubDate>Mon, 21 Jan 2019 16:47:45 GMT</pubDate>
            <atom:updated>2019-01-21T16:51:03.468Z</atom:updated>
            <content:encoded><![CDATA[<p><em>What follows is an example of a real specification we used in developing a feature for </em><a href="https://buffer.com/analyze"><em>Buffer Analyze</em></a><em>. The specification follows a separate “exploration doc”, which is usually much longer, much messier, and is designed to help the team arrive at the final specification.</em></p><p><em>This is an appendix to my post on how we scope products at Buffer: </em><a href="https://open.buffer.com/product-scope/"><em>Dream Big, Go Small, and the Path to a Minimum Lovable Product</em></a><em>.</em></p><p><em>Eternal thanks to </em><a href="https://twitter.com/moreofmorris"><em>James</em></a><em>, our product designer, for driving this spec.</em></p><h3>Answers 2.0 Specification</h3><p><em>👉 This document is to detail out the designs for the team. It should contain all the information needed to actually build this out. If there is anything missing then please ask!</em></p><h3>Quick look</h3><p>Here are all the chart modules that would feature in the new Answers section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2GQK5GYX_ad_-XmB.png" /></figure><h3>Colors</h3><p>The brand new Answers section feels like a good time to experiment with some new colours. I’ve had these knocking around for a while. They’re meant to feel fresh and vibrant but also that they would compliment each other if used all on one page. I’m still a little unsure on the red-ish colour but let’s just experiment, play and see! 🙂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HtmQo9-gdLfsTnST.png" /></figure><h3>Guides</h3><p>For each main chart to look proportional, the answer part should be 40% of the total width and the bar graph should be 60% of the total width. That should be the same for every chart. The answers part is also vertically centred to the bar chart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MZVxMhrY-H2F0Ovs.png" /></figure><h3>New header?</h3><p>You may notice there is a slightly different header in the charts. There is a slight shadow to create more separation between the chart header and the chart contents. Don’t worry about implementing this yet, it’s something I want to play with myself in the code as it’s part of a little visual experiment 👍</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/0*3qRwnkqN52C06nOJ.png" /></figure><h3>Overview</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Hae4tHP98n1eWg5y.png" /></figure><p>The overview forms part of a new wave of graphs we want to do across Analyze eventually. They’re part of the “assistance” stuff we want to sprinkle through the app. This tells the customer exactly what is best. No need to dig through graphs to find the answers, they’re right here and it’s very direct. I’m trying to match the words in the labels up with the titles of the graphs that sit below this best I can. This can also be included in reports.</p><p>🤔 <em>I tried a few things out with this but ultimately settled on this very simple design. The icons may well change but it’s just to give the items a bit of identity. These answers are always based on the data within the given date period. I’m still unsure of the red-ish colour, this may well change but let’s roll with it for the mo.</em></p><p>There are no tooltips for this module.</p><h3>What Day</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YC-ZkBNqdfowmlEq.png" /></figure><p>This chart aims to answer the question clearly whilst also providing more detailed information. It uses a simple bar chart to show which day of the week is the most engaging. Along the y-axis is the engagement rate and along the x-axis are the days of the week. I did my best to make the title readable but also tie in with the respective label in the overview.</p><p><strong>Tooltip</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qaxiF8JHgaMxIpHu.png" /></figure><h3>What Type</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dPgD4rHp2RZGBAGX.png" /></figure><p>This chart aims to answer the question clearly whilst also providing more detailed information. It uses a simple bar chart to show which type of post is the most engaging. Along the y-axis is the engagement rate and along the x-axis is the types of posts. I did my best to make the title readable but also tie in with the respective label in the overview.</p><p><strong>Tooltip</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nWM9-a2yUryI4UGH.png" /></figure><p><strong>Technical Details</strong></p><p>Right now, we only have “type” data for Facebook. We’ll need to update so we can glean “update type” from all networks. These types will vary between networks as well. <strong>It’ll be worth looking to what it would take to get Stories</strong></p><p>🎥 The good news is that we <strong>can</strong> ingest stories, but we need to subscribe to <a href="https://developers.facebook.com/docs/instagram-api/webhooks">a webhook</a> because Stories — and their stats — disappear after 24 hours!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rd-Cc-ReiEukQeMvgT9VnQ.png" /></figure><h3>What Frequency</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*__xTfSXVb2QATNLS.png" /></figure><p>This chart aims to answer the question clearly whilst also providing more detailed information. It uses a simple bar chart to show which frequency of posting is the most engaging. Along the y-axis is the engagement rate and along the x-axis is the daily posting frequency. I did my best to make the title readable but also tie in with the respective label in the overview.</p><p><strong>Tooltip</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gIxrUn7ZHNHl8Ld9.png" /></figure><h3>Possible Questions 😉</h3><p><strong>Will these graphs be available for all networks?</strong></p><p>Yep, that’s the plan. Please say though if this feels like it’s not gonna work.</p><p><strong>How are we judging what’s the “best” in this context?</strong></p><p>I wanted to simplify a few things and make every graph just refer to engagement rate. It’s what each graph now checks to see which is “best” and which is “worst”. In the future, we could use other variables to gauge this but it feels good to be confident with this and engagement rate is usually considered a good gauge for success with this kind of stuff.</p><p><strong>What is the meaning of life?</strong></p><p>To love, to laugh and be merry. Or “42” depending on what books you read.</p><h3><em>Thanks for reading ✌️</em></h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fc42c485929" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to cope with emotions of shipping an imperfect product]]></title>
            <link>https://redman.medium.com/how-to-cope-with-emotions-of-shipping-an-imperfect-product-93766226ed9d?source=rss-9465bd57b96------2</link>
            <guid isPermaLink="false">https://medium.com/p/93766226ed9d</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Tom Redman]]></dc:creator>
            <pubDate>Thu, 08 Nov 2018 22:17:18 GMT</pubDate>
            <atom:updated>2018-11-09T04:10:32.879Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to cope with the emotions of shipping an imperfect product</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lyrhjupug-Z7bVN2cuJYxA.jpeg" /><figcaption>My products are never as perfect as this photo. And that’s ok.</figcaption></figure><p>I was recently asked an amazing question about the <em>emotions</em> involved during the building of a product.</p><p>To be totally candid, I’ve never given that any real reflection. So I wondered, <em>what </em>are<em> the emotions I contend with when building something?</em></p><p>Like most product managers, I am human and therefore wrangle my emotions — whether or not I think about them explicitly. After considering the question for a couple days, I realized that I clearly experience the full gamut of emotions while building things: 😁, 😨, 😔, 🤩, 😡, 😇, 🤪, 😫, and 😳.</p><p><em>Huh, damn good question!</em></p><p>This particular question was about coping with the emotions when your product isn’t as perfect as you — or others — want it to be before you ship.</p><blockquote>Hi Tom, am currently in the middle of reading <a href="https://open.buffer.com/product-scope/">your post</a> about product scope and I’m learning so much already.</blockquote><blockquote>I absolutely agree about constraints helping with creativity. And I also liked how you say we should deliver value instead of completeness.</blockquote><blockquote>I struggle with that last bit every time. There is always the need to go out perfectly.</blockquote><blockquote>Aside from doing the stages you mentioned, <strong>how do you cope with the emotions?</strong></blockquote><blockquote>Sometimes it’s easy to rationalise these but there’s also the human side of ourselves that normally gets in the way.</blockquote><blockquote>What has worked for you?</blockquote><p>This is a really great question, and one I struggle with personally quite a bit.</p><p>I have a hard time shipping things that are not pixel perfect in every edge case, but the reality is that my designer and I probably feel this pain the most —<em> our customers often don’t need these things to get the value</em>. I’d probably categorize this emotion as frustration or pride (or lack thereof).</p><p>Especially with B2B products, the little delightful details are simply unimportant relative to the value the tool delivers. B2C is different: those details are part of making an experience lovable, and a great experience might even be your innovation or competitive advantage. But with B2B: 90% of the delight comes from getting the job done reliably, intuitively and efficiently.</p><p>To combat urges for perfection, and reign in my frustration and pride of the issue, <strong>I often remind myself that I’m not building this for me</strong>. Our customers are finding relief, satisfaction and real value in my non-perfect product. My customers’ happiness grounds my desire for perfection.</p><p>And if I were building a consumer app, I’d be looking to achieve a lot more “perfection”, since the details and polish contribute more directly to the experience. In this world, you can reduce functionality but can’t skip on the nice.</p><p>Back to <a href="https://buffer.com/analyze">my current product</a>: ultimately, seeing my customers finally obtain relief through efficient tooling is enough to keep me from delaying launch due to the nice-to-haves (we’re in the social analytics space).</p><p>I’ve found that in the very early days, you must be very real with yourself about what’s actually valuable and what’s just your quest for awesome pixels.</p><p>But as your product matures and its survival becomes slightly more likely, you can breathe a little and include some of your perfect pixels during regular development cycles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/234/1*WmOdN_Z2kC5P1z34x0b6MQ.gif" /><figcaption>We waited for a year before adding this hover state</figcaption></figure><p>For example, the product I’m building didn’t have hover/active states on interactive components like buttons and dropdowns for almost a year. While it drove me a little crazy every day, I needed our engineers working on must-have functionality since we didn’t even know if what were building was the right thing.</p><p>We just recently got 100 customers, and finally added hover states, and it’s awesome. We have a <em>little</em> more breathing room now and I look forward to peppering in these polish items along the way. Over time, these will also pay dividends, but dividends don’t matter if the thing you’re building doesn’t solve a key problem in the first place.</p><p>Thoughts? Questions? Puns? Get in touch with me on Twitter <a href="https://twitter.com/redman">@redman</a> :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93766226ed9d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Something Is Not Better Than Nothing: Embracing Negative Space In Your Product Development Process]]></title>
            <link>https://medium.com/buffer-stories/something-is-not-better-than-nothing-embracing-negative-space-in-your-product-development-process-2fbde9f80902?source=rss-9465bd57b96------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fbde9f80902</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Tom Redman]]></dc:creator>
            <pubDate>Wed, 12 Apr 2017 17:27:52 GMT</pubDate>
            <atom:updated>2017-04-18T15:49:44.311Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QZ7mHw10xVywcdpOCAQdbQ.jpeg" /><figcaption>Art by the amazing <a href="http://www.itsnicethat.com/articles/shigeo-fukuda">Shigeo Fukuda</a></figcaption></figure><p>You’ve heard the idiom “less is more,” and that’s precisely the path you should consider when building your product. Negative space is a well known concept used in traditional art, design, interior decorating, and other disciplines to effectively convey <em>something </em>through<em> what is not there</em>.</p><p>When I refer to negative space in the product development process, I mean the temptation to <em>just do this</em>, or <em>just do that</em> to the product because the space to do so simply exists.</p><p>Instead, leverage that negative space as a reminder to stay disciplined. Do not give in to the continued temptation to <em>just do something because you can. </em>Acting on this temptation is a lot more expensive than you might think.</p><p>It sounds painfully obvious, I know. But herein lies the truth: as a Product Manager, it’s natural to over-trust your intuition, and even more difficult to identify when you’re doing so. Couple this with the fact that you have the means to execute, and soon we see that the struggle is real! What’s a little change here, or an completely intuition-based feature there?</p><p>Resisting filling this negative space is not quite as easy as it sounds and requires discipline to achieve fully over time. When you get the <em>because you can</em> itch (and successfully identify it as such), use the negative space itself to remind you to refocus that energy on pursuing validated, permanent and measurably higher impact tasks. The benefits are two-fold: this will provide your users with more long-term value and you’re maximizing your opportunity cost.</p><p>When designing a product, I often have to remind myself <em>what it is not</em>. This helps to keep things focused, scoped and understood. It makes prioritizing things easier and it provides clear constraints, which are very important when it comes to being able to ship.</p><p>In the context of product development, alarm bells start ringing when I hear the phrase “but something is better than nothing!”. And when you hear this, they should ring for you too.</p><p>First of all, that nothing is <em>not</em> nothing — it’s negative space we can leverage into higher impact work! Second, something is not better than nothing when that something is reactionary, not fully validated or its reverberations not fully understood. Third and finally, builder beware: once you have real users, it’s a lot harder to remove something from your product than to add it.</p><p>I really appreciate you checking this out! If you enjoyed this, feel free to recommend or share with your friends. You can also reach out and say hi on Twitter, I’m <a href="https://twitter.com/redman">@redman.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fbde9f80902" width="1" height="1" alt=""><hr><p><a href="https://medium.com/buffer-stories/something-is-not-better-than-nothing-embracing-negative-space-in-your-product-development-process-2fbde9f80902">Something Is Not Better Than Nothing: Embracing Negative Space In Your Product Development Process</a> was originally published in <a href="https://medium.com/buffer-stories">Buffer Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Most Valuable Thing We’ve Done for Our Product Managers in the Last Six Months]]></title>
            <link>https://medium.com/buffer-stories/the-most-valuable-thing-weve-done-for-product-managers-in-the-last-six-months-f9fab523a687?source=rss-9465bd57b96------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9fab523a687</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[churn]]></category>
            <dc:creator><![CDATA[Tom Redman]]></dc:creator>
            <pubDate>Sun, 12 Feb 2017 17:06:11 GMT</pubDate>
            <atom:updated>2017-02-15T09:20:04.133Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OVAguQYDoiC2wovqrb8UEQ.png" /><figcaption>This is a real example of an email we send to all Product Managers at Buffer when a user churns.</figcaption></figure><p>A few months ago, all the Product Managers at <a href="http://open.buffer.com/">Buffer</a> started receiving a direct email each time somebody churned from a paid plan at Buffer.</p><p>This is arguably the most valuable thing we’ve done for our product team in the past six months, and I expect its value to compound over the coming months and years.</p><p>But these emails weren’t new: the leadership team have been receiving these automated messages for a long time as a way of keeping a finger on the pulse of churned users. By sharing this with the PMs (and anybody at the company who wants to receive them), we’ve helped further reduce the chasm of understanding between a PM and their product.</p><p>These emails allow us to build our intuition into the patterns and trends of churning customers. For each churn email, we ask ourselves some questions. Are they our target customer? Do they mention some specific functionality, or lack thereof? Do they mention billing or pricing? Do they sound frustrated? Happy?</p><p>Over time, we’re able to internalize various patterns and use that <em>developed intuition</em> in guiding product decisions. In many cases, we’ll also reach out directly, not to ask for their business back — that ship has sailed — but for help.</p><p>Here’s a real-life example of how I might follow up to a churn email (names have been changed):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JcxU0iO4sgcVpLkYa6XYyg.png" /><figcaption>I get one response for about every 10–15 of these emails I send. Remember, these users are no longer invested in Buffer. I think there’s an <a href="https://www.youtube.com/watch?v=ZXvzzTICvJs">Ed Sheeran song</a> about this relationship dynamic.</figcaption></figure><p>At this point in a customer’s relationship with Buffer, they’re no longer invested in us and may even be frustrated or angry with us, so responses are few. But there are responses, for which I’m eternally grateful, and these are another tool to help us further refine our intuition:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9uV3u4JLfqpAMS7CXRyEhQ.png" /><figcaption>“Jennifer” churned, but was very gracious in providing us with extra information about why, which helps us drive future product decisions.</figcaption></figure><p>I can’t recommend enough sharing this type of information widely and regularly with at least your product team, and ideally with everybody in the company who might benefit from building their product intuition this way.</p><p>If you like this, please recommend or share freely! As always, you can get in touch with me on Twitter <a href="https://twitter.com/redman">@redman</a>. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9fab523a687" width="1" height="1" alt=""><hr><p><a href="https://medium.com/buffer-stories/the-most-valuable-thing-weve-done-for-product-managers-in-the-last-six-months-f9fab523a687">The Most Valuable Thing We’ve Done for Our Product Managers in the Last Six Months</a> was originally published in <a href="https://medium.com/buffer-stories">Buffer Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My advice to aspiring Product Managers]]></title>
            <link>https://medium.com/buffer-stories/my-advice-to-aspiring-product-managers-bdfc24e4ba9a?source=rss-9465bd57b96------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdfc24e4ba9a</guid>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Tom Redman]]></dc:creator>
            <pubDate>Sat, 11 Feb 2017 18:04:00 GMT</pubDate>
            <atom:updated>2019-10-17T14:06:40.477Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lRCHyYCgSz_BXDbXpqVnMg.jpeg" /><figcaption>This is me chatting product at Toronto’s first #buffermeetup in February, 2017 (Photo: <a href="https://twitter.com/_pioul">Philippe Masset</a>)</figcaption></figure><p>A few months ago, I received an email asking for advice on the best skills and qualifications to break into a product management position at a tech company.</p><p>Since then, I’ve received some similar requests so I thought it might be worthwhile to share some of that advice more widely, for anybody who is interested.</p><p>Because I was specifically asked about getting a product management position at a tech startup, my advice tends to skew a little on the technical side.</p><blockquote>Hi Tom,</blockquote><blockquote>The main reason I am reaching out is because I am currently in a financial analyst role, however I am trying to transition into a product management position (ideally for a tech startup). I have some Java programming experience, but am still very much a novice. I am therefore planning to take some night classes on UX design and coding, but am a little unsure as to what the best starting point may be. I therefore wanted to get your opinion on the following:</blockquote><blockquote>— Which programming language you find to be the most useful in the tech start-up world</blockquote><blockquote>— Recommendations of other courses that may be helpful</blockquote><blockquote>— Qualifications that you find most necessary to succeed in a product management position</blockquote><blockquote>Again, thank you for lending time from your busy schedule to speak with me, it is very much appreciated.</blockquote><p>Hey there, thanks for the message!</p><p>It’s awesome to hear you’re interested in shifting roles — it’s super important to chase the things that might bring you the most fulfillment. And for me, doing product management for the last few months has been challenging, interesting and fulfilling to say the least.</p><p>It’s really great you’ve stretched yourself to learn some Java and start thinking about UX on a deeper level. These are very strong starting points.</p><p>While you don’t need to be an engineer, technical acumen is very important for a PM, so you’ve got the right idea. It’s important in gaining the trust of your developers, to know what truly is and isn’t easily possible, and to fully grasp the technical nuances and consequences of certain product decisions.</p><p>I’d recommend to keep learning coding, and the best way to do that is to <em>build something</em>. Even if it’s quite simple. Night classes and online courses will help get you there.</p><p>Keep in mind that programming can have a steep-ish learning curve which can be discouraging at times. Though if you stick through, you’ll hit a point where everything “clicks”. This is different for each person, anywhere from a few months to a few years. Irrespective of language, solid understanding of programming fundamentals and design patterns will take you the furthest as a PM.</p><p>In terms of the other skills that are the most useful for effective product management, it helps to think about why product management is a role in the first place. Our biggest task is to identify and deeply understand the problems to solve. We do that by understanding data and by <em>listening</em> to customers. Empathy is a very important skill, used internally with the team and externally when chatting with customers (or potential customers).</p><p>We then understand which of these problems are worth solving in terms of offering the most value, coupled with their alignment to the company’s values and goals. You’ll need to justify your decisions to the whole team: you need to be able to persuade the research, marketing, design and engineering teams that <em>this is the best thing to build right now</em>.</p><p>Typically, you’ll then work with a Product Designer, whose job it is to <a href="https://medium.com/the-year-of-the-looking-glass/building-products-91aa93bea4bb#.yeiaugiep">ideate 5, 10, 20 potential solutions</a> to the problem you’ve identified as valuable and worth solving.</p><p>You don’t have to be (and probably won’t be) the <em>expert</em> on UX and UI — that’s the Product Designer’s role. However, you are the expert on the user, “who you are designing for” and it’s your job to make sure the Designer is keeping that user in mind. You’ll hone a “final” solution with the Designer, and then show a prototype of that to users — again an exercise in listening and empathy. Rinse and repeat until you, your researcher and designer feel like you’re ready for implementation.</p><p>At the implementation step, you’ll want to provide engineers with as much distraction-free time as possible. Usually this means being the point of contact for most things and filtering out the signals from the noise, and only passing along the signals.</p><p>During this part of a project, you’re kind of the glue between everything, and you need to keep everything on track — coordinate with engineers (How’s everything going? Are we on track?), coordinate with Marketing (Should this have a launch? What kind of timeline is required?) and all the while making sure you’re still building the right thing.</p><p>To break it down, the top skills required are: technical depth, data analysis, listening and empathy, specific product expertise, strong UX knowledge, and organizational and people management.</p><p>I’d also recommend to start thinking critically about products, software and non-software, that you use in your daily life. I love to do this with non-software products. When I come across a product I love, I think a bit about why I feel that way. Why is this awesome? What decisions were made to get here? What might have been some of the tradeoffs? How could it be improved? This will prime you not just for thinking on a higher product level in general, but also for product-related conversations and questions you might face when seeking out your new role.</p><p>Good luck with your new journey!</p><p>If you liked this, feel free to recommend or share! And as always you can get in touch with me on Twitter <a href="http://twitter.com/redman">@redman</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdfc24e4ba9a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/buffer-stories/my-advice-to-aspiring-product-managers-bdfc24e4ba9a">My advice to aspiring Product Managers</a> was originally published in <a href="https://medium.com/buffer-stories">Buffer Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What it’s like to be a new Product Manager]]></title>
            <link>https://medium.com/buffer-stories/what-its-like-to-be-a-new-product-manager-ba0274362b95?source=rss-9465bd57b96------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba0274362b95</guid>
            <category><![CDATA[buffer]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Tom Redman]]></dc:creator>
            <pubDate>Mon, 04 Jul 2016 19:44:39 GMT</pubDate>
            <atom:updated>2016-08-19T07:49:00.169Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Disclaimer</em>: <em>Since I’ve only been a PM for three months, these thoughts may turn out to be slightly, wildly or completely inaccurate.</em></p><p>Here are a few things I’ve learned as a new Product Manager:</p><p><strong>I do a little of everything but not a lot of anything.</strong></p><p>For any given project, be it a feature or product, I kick off a little customer research myself, then hand it off to somebody who’s better than me at customer development. I find the basic growth data I think is relevant, and hand it off to somebody who’s better than me at growth. I design the feature to the fringes of my ability, then hand it off to somebody who’s better than me at product design. Rinse and repeat for the technical, marketing and business disciplines as well.</p><p>As a Product Manager, I’m often not the best at any single discipline, but I try to be really good at being the glue between them, keeping the whole picture in my mind and using that mental model to encourage action in specific areas.</p><p><strong>I am wholly responsible for the final experience.</strong></p><p>When a customer experiences a bug in the wild, or poor UX, or limited accessibility, or nobody experiences anything at all because nobody uses the feature, the buck starts and stops with me. It is never the fault of the designer or the researcher or the engineer. Ever.</p><p>Directly related to user experience, as a PM, my expectations of quality are likely the highest on the team. This isn’t just because I desperately want to delight our users (I do), but also because — more selfishly — I will (and should) feel it the most when things go wrong. There’s at least a small aspect of self-preservation to the high level of my expectations. Fortunately, my incentives here align with our users’.</p><p>This means that getting to the level at which I’m personally happy with a project often means doing <em>a lot</em> of QA and very regular contact with engineering in the final days before launch.</p><p><strong>I am constantly talking to users to make sure we’re building something they care about.</strong></p><p>Every week I chat with existing and potential users about what we’re building in order to give me sustained confidence that we’re building the right thing. The longer I go without talking to users, the less confidence I have in what we’re building.</p><p>It’s an easy trap to <em>think</em> I’m building the right thing. I ask myself regularly, Do I <em>know</em> we’re building the right thing? This requires me to shed any ego I have around what I think is right in light of the truth, and get to the point where I can answer myself, Yes I know we’re building the right thing.</p><p><strong>I include the team in decision making.</strong></p><p>I work with very smart people, and try to embrace that. I encourage product conversations across the team and the company by providing context around an idea or problem or solution, and then listening to the thoughts of people who are much smarter than me. This also allows the whole team to invest early in a feature, which pays dividends later. For example, by including an engineer in the research phase, they’re empowered to make research-backed decisions during implementation, resulting in faster execution.</p><p><strong>If everybody’s busy, I do it myself.</strong></p><p>“It didn’t get done because we didn’t have enough resources” doesn’t ring as a great excuse in my mind. Obviously you can’t build something with nothing, but in most projects, there is usually more to do than there are resources.</p><p>As PM, part of fostering the most productive team is removing distractions, passing through signals from the noise, and minimizing context switching. The result of this filtering is that I’m left with quite a lot of small tasks that don’t pass the ‘<em>Should I bother them with this right now?’</em> threshold. Of these remaining tasks, I will complete all of the ones that are within my ability. If a given task is beyond my ability, I’ll triage it for the appropriate person to get to in due time.</p><p><strong>More to come…</strong></p><p>I’ll share more thoughts as I experience different facets of Product Management. If you found this interesting or useful, consider hitting the green heart to help increase its visibility :) If you have any thoughts or comments, please leave them here or hit me up on Twitter, <a href="https://twitter.com/redman">@redman</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba0274362b95" width="1" height="1" alt=""><hr><p><a href="https://medium.com/buffer-stories/what-its-like-to-be-a-new-product-manager-ba0274362b95">What it’s like to be a new Product Manager</a> was originally published in <a href="https://medium.com/buffer-stories">Buffer Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Brief History of Mobile at Buffer and What’s Next: Transforming Buffer into a Mobile First…]]></title>
            <link>https://medium.com/buffer-posts/a-brief-history-of-mobile-at-buffer-and-what-s-next-transforming-buffer-into-a-mobile-first-7fbfc5f7b043?source=rss-9465bd57b96------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fbfc5f7b043</guid>
            <category><![CDATA[vision]]></category>
            <category><![CDATA[buffer]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Tom Redman]]></dc:creator>
            <pubDate>Wed, 30 Mar 2016 15:19:48 GMT</pubDate>
            <atom:updated>2016-08-15T14:05:41.546Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k9uynJ5Ud8eBXjijRmJLLw.jpeg" /></figure><h3>A Brief History of Mobile at Buffer and What’s Next: Transforming Buffer into a Mobile First Company</h3><p><a href="http://buffer.com/">Buffer</a> has always been a web-first service, starting in 2010 with <a href="http://joel.is/">Joel</a>’s <a href="https://blog.bufferapp.com/idea-to-paying-customers-in-7-weeks-how-we-did-it">first version</a>. Even today we don’t have a responsive version of the web app. While we build and maintain native Android and iOS apps, in the past the mobile side of Buffer has generally been about establishing feature parity with its web-based counterpart and less about driving new features or products.</p><p>And this made sense given the nature of Buffer’s services: While social content is largely consumed on mobile, large-scale content generation and administration is still well-suited for the increased screen real estate and granular control afforded by a desktop.</p><p>Another factor driving our web-first approach was that in the early days of Buffer, the mobile team had very limited bandwidth: Joel himself created Buffer’s <a href="https://blog.bufferapp.com/discover-the-brand-new-buffer-for-android">first Android app</a> (it was initially a webview wrapper). In 2012, <a href="https://twitter.com/sunils34">Sunil</a> took over development of the Android app and made incredible progress converting it from an admittedly crude tool to a much more feature rich, native app. However, Sunil was soon promoted to CTO and, as they do, those responsibilities often pulled his attention elsewhere, leaving the Android app to wait patiently for its forever owner.</p><p>As development on Buffer for Android stagnated, Buffer had been incredibly privileged to have Andy Yates steadfastly developing Buffer for iOS. As Buffer employee #1, Andy has been a constant at Buffer from the very start, and is a wonderfully talented iOS developer. In 2014, the state of the iOS and Android apps reflected this: iOS was modern, stable and had a high degree of feature parity while Android fell behind in features, design and user experience.</p><p>At this point in 2014, we were very fortunate that Buffer was growing as a company. Buffer was experiencing strong growth in active users, revenue and team size. The Happiness Heroes were hiring, front-end and back-end engineering teams were growing, as were the data and growth teams. But there was one notable exception: the mobile team. During this growth Andy remained our only mobile engineer.</p><p>I applied to Buffer in April 2014 as an iOS developer. I was very fortunate to make it through the interview process and in my offer, Sunil mentioned they needed help elsewhere:</p><blockquote>“I know you mentioned to me that you’d love the opportunity to work a bit more on Android, even though your experience has been mostly iOS (I loved that!). We desperately need some help with our Android app, so we were thinking of having you join to help us out there first.”</blockquote><p>And just like that, <a href="https://medium.com/@redman/how-i-accidentally-became-an-android-developer-my-journey-from-ios-to-android-52438ca4fd0#.7ve2xl9oc">I became an Android developer</a> . This turned out to be the best opportunity of my career, and I’m forever grateful to Sunil for the faith that I could do it!</p><p>With two full-time mobile developers, things started to move faster at Buffer. We started to dream about what mobile could look like in six months or a year, or further. We started to ask bigger questions of the platforms than we had in the past. What does mobile mean for Buffer? What does it mean for our users? Why haven’t we done much (if anything) mobile-first?</p><p>This is where our vision for mobile at Buffer starts to find legs. We are now a team of five mobile developers and one UX Researcher and QA Analyst. We are privileged to have the bandwidth and the ability to execute on the right ideas.</p><p>My job right now involves a lot of things: I’m a developer, I hold regular 1:1 meetings with the mobile squad, I try to help the team perform at their best, and I advocate for mobile within Buffer. I am also trying to develop our long-term vision for mobile. I spend time imagining what mobile should and could look like for Buffer, what it means beyond our current offerings.</p><p>Admittedly, this is where I struggle the most. It’s hard to sit down and “develop a vision.” It’s hard to know where to start, what it means, or even what the goal is. I prefer to think in concrete terms, and ‘visions’ often feel abstract to me.</p><p>So I’ve tried to approach this problem from a more concrete perspective. What do we know (or think we know), and how can that guide us? We know mobile usage will be growing for the foreseeable future, taking desktop share as far as it can reasonably go, probably until all tasks completed on a desktop can only be completed on a desktop. To me, this is a huge revelation. I think mobile will continue to evolve, until everything that can reasonably be done on mobile is done on mobile. There are just so many benefits to having tools and products with <em>low friction accessibility</em>. This is where I see the potential for long-term opportunity: We need to be building more.</p><p>We currently only offer one mobile product at Buffer, that is, <a href="https://play.google.com/store/apps/details?id=org.buffer.android&amp;hl=en">Buffer for Android</a> and <a href="https://itunes.apple.com/ca/app/buffer-for-twitter-pinterest/id490474324?mt=8">Buffer for iOS</a>. In my heart of hearts, I know there is so much more opportunity for us here. We need to think more creatively, to imagine products far beyond what Buffer currently looks like. As I mentioned, we’re in a privileged position at Buffer in that we can execute on our ideas, both in terms of bandwidth and autonomy within the company. It would be a shame to let that opportunity go untapped.</p><p>Armed with this undeniable potential, my goal is to transform Buffer into a mobile-first company. I want push our limits, find more successes, fail more often, incite excitement and advocate for mobile like I haven’t been doing. In a few years, I’d love to see Buffer have a full suite of mobile tools and products, software that genuinely makes peoples’ days better.</p><p>To do that, we need to identify real opportunities for solutions and act on them. While that sounds vague, these opportunities are around us every day and it’s on us to carve out the space to act on them. We need to be paying attention, and afford ourselves the forgiveness to fail as long as we try.</p><p>We are still in the early days of finding ourselves as a mobile shop within Buffer. If some of this resonates with you, or you have any ideas or thoughts, please leave a comment below or <a href="http://twitter.com/redman">hit me up on Twitter</a>!</p><p>And if you’d like to join us on this journey and help guide its direction, <a href="https://buffer.com/journey/android-developer">the mobile team is hiring</a> :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fbfc5f7b043" width="1" height="1" alt=""><hr><p><a href="https://medium.com/buffer-posts/a-brief-history-of-mobile-at-buffer-and-what-s-next-transforming-buffer-into-a-mobile-first-7fbfc5f7b043">A Brief History of Mobile at Buffer and What’s Next: Transforming Buffer into a Mobile First…</a> was originally published in <a href="https://medium.com/buffer-posts">Buffer Posts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>