<?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 Spencer Johnson on Medium]]></title>
        <description><![CDATA[Stories by Spencer Johnson on Medium]]></description>
        <link>https://medium.com/@spencerjohnson?source=rss-46d0befc42d0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rR8HddE4Hef7BH2KvA17Cw.jpeg</url>
            <title>Stories by Spencer Johnson on Medium</title>
            <link>https://medium.com/@spencerjohnson?source=rss-46d0befc42d0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:59:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@spencerjohnson/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[Headcount: Re-thinking Group Chat]]></title>
            <link>https://medium.com/@spencerjohnson/headcount-re-thinking-group-chat-d85d3e0a870a?source=rss-46d0befc42d0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d85d3e0a870a</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Spencer Johnson]]></dc:creator>
            <pubDate>Tue, 09 May 2017 13:20:51 GMT</pubDate>
            <atom:updated>2017-05-09T13:20:51.523Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kCMc8SQ015b_89MEalStjg.png" /></figure><h3><strong>Headcount: Rethinking Group Chat</strong></h3><p>A year ago, I moved into a one bedroom apartment in Washington, DC. It was the first time I had ever lived alone, and after 25 years of constant company, I was blindsided by the frustration of coordinating my social life without friends down the hall. I leaned on iMessage, Facebook Events, and GroupMe to make plans but found they were <em>not</em> designed for getting answers and acting on them. This is my take on the problems that the existing solutions cause and an overview of my solutions.</p><h3>The Problems</h3><p>After countless conversations with other reluctant facilitators, most could empathize with three scenarios:</p><h4><strong><em>The Hostage Situation</em></strong></h4><p>You’re in a group chat and somebody asks, <em>“Are you around for memorial day?” </em>Most people are around, but you are not one of them. The conversation continues, and it looks like you’re along for the ride. Welcome to notification hell! You’re left with three options: mute it, leave it, or take the bullets.</p><blockquote><strong>Problem:</strong> Leaving or muting conversations when the discussion becomes irrelevant is common when planning in perpetual group chats.</blockquote><h4><strong><em>The Time-💣</em></strong></h4><p>Getting answers for a time-sensitive question is a pain in the ass. Outside of caps lock, it’s difficult to emphasize the urgency of a question in a text. Booking an AirBnB in a group chat is the perfect example. The host of the conversation needs a headcount before you even know what to look for. Yes, Memorial Day is months away, but you better book something soon unless you enjoy meth labs. This is a conversation that would benefit from time-boxing.</p><blockquote><strong>Problem: </strong>It is difficult to communicate urgency in a group chat and impossible to enforce it.</blockquote><h4><strong><em>The 👻 Group</em></strong></h4><p>Here’s another group chat scene: somebody sends a question out in a group chat. People either say “yes” or stare at a white wall and calculate an inoffensive “no.” Of course, there is a third, more attractive option: ghost. Closing the gap between the ease of not responding and the difficulty of saying “no” would result in more honest communication.</p><blockquote><strong>Problem: </strong>It’s much easier to ghost than say “no”</blockquote><h3><strong>The Solutions</strong></h3><h4>Initiate group chats with a temporary, binary poll</h4><ul><li><em>Organizing conversations by subject</em> enables users to leave without losing a long conversation history or missing out on future plans.</li><li><em>Time-boxing response selection </em>enforces the subject’s urgency and enables users to visualize it clearly.</li><li><em>Providing only two responses </em>allows for the possibility of using sender’s user-generated responses as custom actions on push notifications. This makes it quick and easy to respond without entering the application or typing.</li></ul><h4>Message people based on their responses</h4><ul><li>In a group chat, hosts can hop into <em>answer group conversations</em> to speak only to people who selected a specific response (e.g. Yes’s or No’s). As a host, this is also valuable if you are collecting subjective opinion and would like to have an open conversation with a specific answer group.</li></ul><h4><strong>Create new groups from the responses of a previous conversation</strong></h4><ul><li><em>Filtering people by answer </em>allows hosts to quickly create new groups based on poll responses.</li></ul><h3>Design and Implementation</h3><p>Over the past 5 months, I’ve set aside my weeknights to wire-frame, prototype, develop, and iterate my way from user stories to a tangible product: <a href="http://tryheadcount.com/"><strong>Headcount</strong></a>. To spare you from another mobile app case study, I will share brief justifications for how I implemented the app’s core actions and features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*WNsCjU8-q4ot-Mz3xIOvWg.gif" /><figcaption>Composing &amp; Sending a Poll</figcaption></figure><h4><strong>Poll Creation</strong></h4><p>Because it is a core action in the application, poll creation has to be quick and versatile. By canning the answer options with “Yes” and “No” and providing <strong>quick answer pairs</strong>, users have the option to immediately proceed or customize their responses quickly.</p><h4><strong>Time-Boxing</strong></h4><p>Mobile decisions require timely, contextual responses. The time frames for most of the responses in my group chats are <em>right now</em>, <em>an hour from now</em>, <em>tonight, </em>or <em>this weekend.</em> The four expiration options map to those use cases: 5 minutes, 1 hour, 1 day, or 1 week.</p><h4><strong>Selecting Recipients</strong></h4><p>There are three groups that facilitators end up organizing with: circumstantial assortments of friends, friends frequently asked together, and groups of friends based on a previous response they gave to another question. These groups map to each section on the <strong>Send To</strong> view: “From Poll Responses”; “Quick Groups”; and “Friends.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*m-CgjbDnca4E1L7Ei5LgRQ.gif" /><figcaption>Group Chat Interface</figcaption></figure><h4><strong>Contextual Group Chat</strong></h4><p>Once a poll has been started, a corresponding group chat is created. Within the group chat are answer conversations where friends can talk to others who responded the same way.</p><h4>Host Privileges</h4><p>Facilitators often need to give specific information to people based on their responses. With that in mind, I allow the host to join <strong>any</strong> <em>answer conversation</em> to speak directly to any answer group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*0qvcc5qWgSgNhjD5fKDk7g.gif" /><figcaption>Actionable Push Notifications</figcaption></figure><h4>Responding</h4><p>Within the application, responding requires a single tap. However, outside an application is where engagement goes to die. So, I implemented push notifications with custom actions that allow the user to vote without entering the app. This is the first step in the Headcount’s reach outside the application. Building the solution for Android and extending the polling features to other platforms is a necessary next step and an immediate priority.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*sAjK77c8FELUDEXeTNFUUQ.gif" /><figcaption>User Profile and Group Management</figcaption></figure><h4>User Profile</h4><p>As a facilitator, I like to have a hold on my responsibilities and commitments. In Headcount, a user can view their engagements from their profile in the form of two feeds:</p><ul><li><strong>Hosting: </strong>The<strong> </strong><em>live</em> decisions you are hosting</li><li><strong>Answered:</strong> Every poll you’ve answered. This provides you with a receipt of the commitments you’ve made (or didn’t.)</li></ul><h3>Wrapping Up</h3><p>So, that’s my first go at solving my group chat woes. It’s taken ~5 months of late nights to translate sketches to sketchy Swift. I’ve been collecting feedback throughout the development process but I would like to put the app in more critical hands.</p><p>If you like to tear dreams apart and have an iPhone, <a href="https://twitter.com/spencajawnsen">give me a shout</a> and I’ll add you to the beta. Otherwise, feel free to kick around the ideas I’ve laid out here or visit <a href="http://tryheadcount.com/">tryheadcount.com</a> for more.</p><p>Thanks for reading!</p><p>-Spencer</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d85d3e0a870a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>