<?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 Sumit Suman on Medium]]></title>
        <description><![CDATA[Stories by Sumit Suman on Medium]]></description>
        <link>https://medium.com/@sumitsuman?source=rss-1a4621689da5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4Z4ZXdJmc8izvhUlw5TVTQ.jpeg</url>
            <title>Stories by Sumit Suman on Medium</title>
            <link>https://medium.com/@sumitsuman?source=rss-1a4621689da5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:40:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sumitsuman/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[Async-first Communication: Are You Ready For It?]]></title>
            <link>https://medium.com/pacohq/async-first-communication-for-slack-are-you-ready-for-it-add0554ae6a6?source=rss-1a4621689da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/add0554ae6a6</guid>
            <category><![CDATA[slack-apps]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[async]]></category>
            <category><![CDATA[context-switching]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Sumit Suman]]></dc:creator>
            <pubDate>Sat, 26 Jun 2021 12:54:33 GMT</pubDate>
            <atom:updated>2021-06-28T17:28:15.270Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z683IJY_rxj2cY3KkqvLRQ.png" /></figure><p>Async-First communication is a fairly new trend, and we’re seeing companies adopt it to boost employee productivity and efficiency.</p><p>In this post, we’ll take a look at what Async-first means as well as explore tips to practice asynchronous-first communication with Slack.</p><h3>What is Async-first Communication?</h3><p>The Async-first approach involves defaulting to asynchronous communication, but also finding the right balance with synchronous usage wherever possible.</p><p><strong>Asynchronous communication</strong> doesn’t require that all of your team members are present or available at the same time. With asynchronous communication, you can manage your workload more efficiently, communicate with coworkers across multiple locations and time zones, and free up calendars allowing for better scheduling. It allows us to be more flexible in our work.</p><p>On the other hand, with <strong>Synchronous communication</strong> you expect responses in near real-time. You can think of it as a face-to-face conversation you have with someone.</p><h3>Why use Async Communication?</h3><p>Let’s consider an example that might resonate with many of you.</p><p>When you’re in a global organization, it’s logical for employees to want to hold a meeting across time-zones often. Attending or hosting a meeting across 3 time-zones isn’t fun!</p><p>Have you dealt frequently with the challenge of finding the “right” time-slot for such meetings?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CdL_W3xsScnWYC1A" /></figure><h3>Differences: Asynchronous vs. Synchronous Communication</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5zXfDTiF9bppj93H" /></figure><h3>Pros and Cons of Async Communication</h3><h3>Pros</h3><ul><li>Makes it <strong>easier to work with a globally distributed team</strong> from different locations and time zones. Mitigates the challenges of scheduling and coordinating that dreaded meeting slot across countries.</li><li><strong>More flexibility</strong>: Asynchronous communication gives you the time you need to think before responding. You can always respond when it’s convenient for you, instead of having the pressure of instant responses. This translates to more employee engagement.</li><li><strong>Fewer interruptions and lesser </strong><a href="https://pacohq.com/blog/Guide/the-high-price-of-context-switching-for-developers"><strong>context switching</strong></a>: you can work with fewer distractions and focus on one thing. This facilitates <a href="https://pacohq.com/blog/Guide/deep-work-how-to-get-started">Deep work</a> and increased productivity.</li><li><strong>Improved response quality: </strong>Team members have to formulate more thoughtful and higher-quality responses. Translates to Quality improvement and better documentation for future reference.</li><li><strong>Eliminates the need to be always online:</strong> with Async communication, you can set the availability and response expectations. No need to stay online all the time.</li></ul><h3>Cons</h3><ul><li><strong>Requires more discipline in communication</strong> to avoid disconnects and misunderstanding: With asynchronous communication comes the need for much more clarity and detail because the conversation isn’t happening in real-time.</li><li>Async communication is <strong>not suited for topics requiring urgency</strong>. The Async-first rule of thumb is: only go Async when you need to.</li><li><strong>Spillover beyond traditional fixed-schedule work hours</strong>: As there is no hard meeting schedule, people choose their convenient timings. This often leads to a spillover beyond the traditional fixed-schedule work hours.</li></ul><h3><strong>Finding the right balance: when to go Async and when to go Sync</strong></h3><p>The best part about an Async-first approach is that it provides enough flexibility to choose synchronous communication depending on your use-case needs. Finding the right balance between both types of communication is the key.</p><p>Do not hesitate to decline that synchronous meeting invitation where you are expected to be a passive listener — and replace it with an Async conversation instead.</p><p>It is important to identify situations in which face-to-face (synchronous) communication is required and then establish lines of direct communication between coworkers.</p><p><strong>Use Asynchronous communication when:</strong></p><ul><li>The topic is not very urgent, and you do not need an immediate response</li><li>The other person is in a different time-zone</li><li>The conversation group is fairly large to accommodate in a single meeting</li></ul><p><strong>Switch to Synchronous communication when:</strong></p><ul><li>You and the other person need to get something urgent done immediately, and doing a video/phone call or a face-to-face chat is an available option</li><li>When you’re participating in a long asynchronous exchange with multiple back-and-forth messages</li></ul><h3><strong>Power Tips: How to go Async-first on Slack</strong></h3><p>We love Slack for its easy-to-use and powerful team collaboration capabilities that combines chat, audio, video, file sharing, search and more. But at the same time, the constant sync chatter on Slack can interrupt our ability to do focused work.</p><p>Here are some tips on going Async-first with Slack and boost your productivity:</p><ul><li><strong>Set very clear expectations</strong> within the team on <em>when </em>to go Synchronous on Slack vs. when to stay Async. There are use-cases when the topic is urgent and the response cannot wait, and for the rest an immediate response is not always required</li><li><strong>Promote the right Slack usage culture</strong>. A culture of <em>I-need-a-response-right-now</em> and expecting everyone to be online round-the-clock will only decrease productivity and engagement over time. Promoting a culture where the team knows what needs your immediate attention on Slack and what can wait is the key</li><li><strong>Use </strong><a href="https://pacohq.com/blog/Guide/how-to-tame-the-chaos-and-make-slack-calm-and-productive-2"><strong>Slack power tips</strong></a> on enforcing the optimum Channel usage, sidebar customization for prioritizing important messages and muting notifications for all but important channels</li><li><strong>Use crisp and clear wording in your Slack messages. </strong>A lot of back-and-forth sync messaging can be avoided if your original ask was clear and easy to understand. This is especially helpful when trying to go Async with remote colleagues distributed across time zones</li><li><strong>Make use of Slack’s powerful availability &amp; status options</strong> — the availability &amp; status options make it easy to let others know how quickly you can respond to messages and when you are available.</li></ul><p><strong>About Paco: </strong><a href="https://pacohq.com/">Paco</a> is the new Slack productivity app that is designed to enable deep-work, avoid context switching and go Async-first on Slack. Add Paco to your Slack workspace for deeper concentration, zero task slippages, and happier remote culture!</p><p>Webpage: <a href="https://pacohq.com/">https://pacohq.com</a> | <a href="https://twitter.com/intent/follow?screen_name=pacofetch">Follow Paco on Twitter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=add0554ae6a6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pacohq/async-first-communication-for-slack-are-you-ready-for-it-add0554ae6a6">Async-first Communication: Are You Ready For It?</a> was originally published in <a href="https://medium.com/pacohq">pacohq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to tame the chaos and make Slack calm and productive: The Definitive Guide]]></title>
            <link>https://medium.com/pacohq/how-to-tame-the-chaos-and-make-slack-calm-and-productive-2e958ac7f78c?source=rss-1a4621689da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e958ac7f78c</guid>
            <category><![CDATA[developer-productivity]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[copa]]></category>
            <category><![CDATA[slack-apps]]></category>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Sumit Suman]]></dc:creator>
            <pubDate>Tue, 08 Jun 2021 20:51:29 GMT</pubDate>
            <atom:updated>2021-06-09T14:17:31.942Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published on </em><a href="https://pacohq.com/blog/guide/how-to-tame-the-chaos-and-make-slack-calm-and-productive-2/"><em>Paco</em></a><em> | </em><a href="https://pacohq.com/"><em>www.pacohq.com</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TbLK-g6sQun7i0LvGvq80g.png" /></figure><p>Do you feel overwhelmed by the constant stream of information Slack gives you? As your team grows, Slack becomes more crowded with streams, channels, and conversations. It becomes a never-ending source of noise, and hard to keep up with. With so many updates, messages, and files, it’s easy to get lost in the noise.</p><p>Here are some 🔥 tips and tricks to take back control of your Slack life, and turn Slack into a calmer, more productive environment.</p><h3>Set up Slack right</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7F0z4i5HcIWPQI2A.png" /></figure><p>Slack is highly configurable — so make sure to get the most out of your workspace and channel setup.</p><p><strong>Use Workflows in your Slack workspace</strong></p><p>Workflows help you automate routine processes and easily trigger them based on events or commands — without any coding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/0*V0kbH0vdnvXDRCWD" /><figcaption>Slack Workflow Builder</figcaption></figure><p>Slack has some handy templates that you can use straight out of the box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/0*GJkQLzgmqYRBa8F0" /><figcaption>Slack Workflow Builder- Default Templates</figcaption></figure><p><strong>Use these </strong><a href="https://slack.com/intl/en-us/blog/collaboration/how-to-use-slack-channels-to-organize-your-work"><strong>best practices</strong></a><strong> for optimally configuring Slack channels.</strong></p><p>It’s always a good idea to set and enforce rules for creating new channels. Create a customized onboarding message and add sticky for the channels. This can either be done via the Workflow Builder or by using a <a href="https://slack.com/intl/en-us/help/articles/205239997-Pin-messages">pinned message</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rB5u-mWBycL5Wdmc" /><figcaption>Image courtesy: Slack</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3lxbk6053LF-8PRo" /><figcaption>Pinning a message to a Channel</figcaption></figure><p>Lay down some ground rules and expectations, and make it visible to new users. Pin it for everyone to see and refer.</p><h3>Narrow down on the default channels for new Workspace users</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rDrLP8ExNutoDc1w.png" /></figure><p>The default channels are a list of channels that get automatically joined by users when they join the Slack workspace. Keep the default list of channels to the minimum to avoid information overload. An example candidate is a channel where announcements relevant to all company workspace users are broadcasted.</p><p>To modify default channels, open up the Slack workspace “Settings &amp; Administration” tab and go to the workspace settings. Select the “Default Channels” option and then make your modifications to the list of channels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/0*LwyqTpMQ-mT_RYBj" /><figcaption>Default Channel Settings are under Settings &amp; Administration &gt; Workspace Settings</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/0*H8UvHHwbdcAE_dLU" /><figcaption>Choose the default Channels and then save</figcaption></figure><h3>Customize the Sidebar and prioritize your important Slack Channels / Messages</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ExKCztpyB9HZQWjk.png" /></figure><p>Slack offers a very flexible customization option for the Sidebar. From the ‘Preferences’ menu, you can choose to edit the sidebar.</p><p>Select sort by most recent and to reduce the sidebar clutter, check the “Show unread conversations, plus your starred section”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/0*Fpt3mpOcQj-XRpol" /><figcaption>Sidebar Customization Menu</figcaption></figure><p>Additionally, for Slack’s Pro, Business+, or Enterprise Grid plan users: there is an option to create custom sections for your channels and DMs in the sidebar.</p><ul><li>Custom sections are only visible to you and won’t affect what your teammates see in their sidebars.</li><li>Custom sections can only be created in Slack from your desktop, but you can view and move conversations in and out of your custom sections from both your desktop and mobile devices.</li><li>In an Enterprise Grid organization, your custom sections will apply to all your workspaces.</li></ul><h3>Turn off notifications on all except the most important channels</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xKTk3aLp0Z2hk_DY.png" /></figure><p>Slack channel notifications can be a distraction and can sometimes be overwhelming when you’re working on other tasks. Luckily, you can choose to remain focused on the most important channels and stop other lesser important channel notifications from distracting you.</p><p>Here is how to customize the Slack notification preferences:</p><ul><li>Right click on the Channel name and select the ‘Change Notifications’ tab</li><li>For low priority channels, either select ‘Nothing’ (meaning notifications fully muted) or ‘Just @ mentions’</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/0*uWChPACbL2I9nl6n" /><figcaption>Channel Notification Customization</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/0*qSn1biFluxUQt_5z" /><figcaption>Channel Notification Customization</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/384/0*7w6_yWrXtSX8cpvc" /><figcaption>Channel Notification Customization</figcaption></figure><h3>Cut out ambiguity — use crisp and clear communication in your Slack messages</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mSVXQ8pxLiAzf1nf.png" /></figure><p>Ambiguous or difficult to understand messages can lead to wasted time as people try to figure out what another person is communicating, or leads to back-and-forth messages.</p><p><a href="https://saylordotorg.github.io/text_human-relations/s08-01-verbal-and-written-communicati.html">Here</a> is a great guide to think strategically about written (and verbal) communication.</p><h3>Work smarter with Slack’s threaded conversations</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QNqv9ZX34j28PGZs.png" /></figure><p>Slack threads let you make ordered, category-based collections of your Slack messages and group them in the channel or DMs.</p><p>Result? Less clutter in the channel or DMs, and referencing information is a lot easier.</p><p><strong>How to use threads in Slack?</strong></p><ul><li>Hover your mouse over any DM or Channel message</li><li>Click on the “Reply to thread” icon and respond there</li><li>To respond to someone who is not in message thread, use the @ name mention</li></ul><p><em>There is more: </em>you can even turn on or turn off notifications to every thread using the “more actions” extended menu when you click on the three dots.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/0*sY60G_TaYBeE-3k6" /><figcaption>Slack Thread usage in DMs or Channels</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/436/0*jv3Tcp2YJtYcY8U3" /><figcaption>Slack Threads: turn on or turn off the notifications</figcaption></figure><h3>Use the Slack /remind to stay on task</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CKF6jkWZ9B2nAdVx.png" /></figure><p>Reminders are set by default in the time-zone your Slack profile is configured for.</p><p><strong>Setting a personal reminder via the Slack interface</strong></p><ul><li>Click on “Set yourself a reminder” via the shortcuts menu</li><li>Select the date/time and write a short description of the reminder</li><li>Once done, you will see a quick confirmation message via the Slackbot</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/401/0*KKwdJ9X1QAEFkpBu" /><figcaption>Slack Reminder: setting a personal reminder via the GUI</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/0*jjOklT1IX2xr-9I_" /><figcaption>Slack Reminder: setting a personal reminder via the GUI</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/734/0*fsy1qgHqEYOJlw71" /><figcaption>Slack Reminder: personal reminder confirmation via Slackbot</figcaption></figure><p><strong>Setting a reminder for another person or channel via /remind slash command</strong></p><ul><li>Type the reminder message in the message box in the following format:</li></ul><pre>/remind [<a href="http://twitter.com/someone">@someone</a> or #channel] [what] [when]</pre><ul><li>Send the message to schedule the reminder. Slackbot will send the reminder in a DM to the person you selected, or trigger a message to the channel you specified.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/0*jEPFJnYHTgwy9_Cg" /><figcaption>Slack Reminder: setting a channel or person reminder using slash /remind command</figcaption></figure><h3>Favorite (Star) Important Direct Messages or Channels</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*krkK_igy17jvkmtO.png" /></figure><p>Starring (or favoriting) a Slack channel or DM is an easy way to mark it as important and keep track of it. Starred items show up within a new “Starred” section in your Sidebar.</p><p>Simply do a right click and select “Start channel” or “Star conversation” from the menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/0*YAUSEazbIE-jw7p7" /><figcaption>How to star a Slack Direct Message</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/458/0*RqbQAfHUYM-hoOmA" /><figcaption>How to star a Slack Direct Message</figcaption></figure><p>A starred DM or Channel shows up in the Starred Section in the Sidebar</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/266/0*G1-kL-QD8ZSePJtP.png" /></figure><h3>Avoid frequent Context Switching</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RaHN1dfW6Asll7Eb.png" /></figure><p>Context switching is when you’re in the middle of something and have to switch activities in order to complete another task. Stop jumping around in Slack.</p><p>Focusing on one task at a time will get you further ahead. It’s time to stop context switching and get focused. Read more <a href="https://pacohq.com/blog/Guide/the-high-price-of-context-switching-for-developers">here</a>.</p><h3>Clean-up! Mute or get rid of the Slack channels you rarely use</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zey8TcuU4UJEkotm.png" /></figure><p>If you have so many Slack channels, you can easily feel overwhelmed and it’s easy to get distracted from what matters. Get rid of the Slack channels you rarely use or mute them in the channel settings.</p><p><strong>How to mute a Slack channel:</strong></p><ol><li>Open the channel you’d like to mute and click on the ‘Show Channel Details’ icon to the top right</li><li>Select More (three dots)</li><li>Select Mute &lt;#channel name&gt;</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/488/0*TxPRWGz_YL0qg8fS" /><figcaption>Muting a Slack Channel</figcaption></figure><h3>Always set and update your Slack availability and status — and go Async!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2OeR9MVCOWfV8KBZ.png" /></figure><p>Let your team know when they can reach you and when they should be patient!</p><p>Slack’s availability and status options make it easy to let others know how quickly you can respond to messages and when you’re available.</p><p>Defining your own <em>Asynchronous Communication</em> rules is an easy way to keep your team informed about the level of responsiveness you want to offer and help them choose the best time to reach out.</p><ul><li>Indicate your availability</li><li>Update your status: let others know if you’re in a meeting or about to take a break</li><li>Set your Async Communication expectations loud and clear</li></ul><p><strong>How to set your Slack availability and status?</strong></p><ul><li>Click on the Slack profile icon to the top right and set the availability</li><li>Click on the ‘Update your status’ button to set a status message</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/301/0*KebWlz1GqnTdJV1b" /><figcaption>Setting your Slack Availability</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*Nr9Ev8k3gAM6FNwa" /><figcaption>Setting your Slack Status</figcaption></figure><h3>Limit Distractions &amp; Practise Deep Work — set DND (Do Not Disturb) when you need to! Reclaim your calm time</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mgBNmsdSPOT6vUtJ.png" /></figure><p>The Slack Do Not Disturb (DND) is a very powerful feature to provide you with uninterrupted time to focus on specific tasks or just rest and recharge. It pauses all your instant notifications and helps you stay focused.</p><p><strong>How to configure Slack DND?</strong></p><ul><li>Click on your profile icon in the top right of the Slack window</li><li>Select ‘Pause Notifications’ and chose the desired DND duration (or set a custom duration)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/0*8UE_riVUcGElNzB_" /><figcaption>Configuring Slack Do Not Disturb (DND)</figcaption></figure><h3>Use Slack as scratchpad — DM yourself!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OTVgNY5n8d5DhqOo.png" /></figure><p>Ever wondered why Slack provided us the option to DM ourselves?</p><p>Need to take a note, save a message, write a draft or just jot down something for future reference? Simply DM it to yourself — it’s really that simple! Slack DM is a simple but powerful scratchpad for your own personal usage.</p><h3>Make use of Slack’s official integrations — there are some nifty productivity apps available in the Slack App Directory!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-T6pBd6rG9ZFR3Mg.png" /></figure><p>Want to get something fancier than Slack’s native capabilities for your productivity needs? Head off to Slack’s <a href="https://slack.com/apps">official app directory</a>, and pick something nifty to fit your needs!</p><p>A bit of shameless self-promotion: I recommend checking out <a href="https://pacohq.com/"><strong>Paco</strong></a>, the new trending 🔥 Slack productivity app that helps you control the Slack chaos and be more calm and productive.</p><p><em>Originally published on </em><a href="https://pacohq.com/blog/guide/how-to-tame-the-chaos-and-make-slack-calm-and-productive-2/"><em>Paco </em></a><em>| </em><a href="http://www.pacohq.com/"><em>www.pacohq.com</em></a><em> | Follow on Twitter: </em><a href="https://twitter.com/pacofetch"><em>https://twitter.com/pacofetch</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e958ac7f78c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pacohq/how-to-tame-the-chaos-and-make-slack-calm-and-productive-2e958ac7f78c">How to tame the chaos and make Slack calm and productive: The Definitive Guide</a> was originally published in <a href="https://medium.com/pacohq">pacohq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The high price of Context Switching for Makers & Ways to Avoid It]]></title>
            <link>https://medium.com/pacohq/the-high-price-of-context-switching-for-makers-ways-to-avoid-it-9697b011eadc?source=rss-1a4621689da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/9697b011eadc</guid>
            <category><![CDATA[context-switching]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[slack-apps]]></category>
            <category><![CDATA[copa]]></category>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Sumit Suman]]></dc:creator>
            <pubDate>Fri, 23 Apr 2021 10:44:00 GMT</pubDate>
            <atom:updated>2021-06-25T08:12:28.359Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published by </em><a href="https://www.linkedin.com/in/npande/"><em>Nitin Pande</em></a><em> on </em><a href="https://pacohq.com/"><em>Paco</em></a><em> &gt; </em><a href="https://pacohq.com/blog/Guide/the-high-price-of-context-switching-for-developers"><em>The high price of context switching for developers &amp; ways to avoid it</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BV_wTZB1JwtwRgMqMjadPg.png" /></figure><p>Developers don’t like to be interrupted. Ever wonder why? Well, the one-line answer is, “Context Switching is super hard!”</p><h3>Context switching is expensive</h3><p>Ever wonder why developers don’t like to be interrupted? Because switching contexts has a very high cost on people who do deep work. Jason Heeris illustrates with an example what damage a simple ping can do to the developer’s flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*CkGnv8FEisw-5lUSWvUBEQ.png" /><figcaption>Source: <a href="https://heeris.id.au/2013/this-is-why-you-shouldnt-interrupt-a-programmer/">Jason Heeris</a></figcaption></figure><h3>Cost of interruptions</h3><p><a href="http://blog.ninlabs.com/2013/01/programmer-interrupted/">Chris Parnin</a> looked at the cost of interrupting developers, and made some powerful observations:</p><ul><li>A programmer takes between 10–15 minutes to start editing code after resuming work from an interruption.</li><li>An interrupted task is estimated to take twice as long and contain twice as many errors as uninterrupted tasks.</li><li>A programmer is likely to get just one uninterrupted 2-hour session in a day.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*euJanWEXEO-6ntQ2.png" /></figure><h3>Meetings are the biggest source of interruptions</h3><p>As Paul Graham wrote in his <a href="http://www.paulgraham.com/makersschedule.html">seminal 2009 essay:</a></p><blockquote><em>“A single meeting can blow a whole afternoon, by breaking it into two pieces each too small to do anything hard in. Plus you have to remember to go to the meeting. For someone on the maker’s schedule, having a meeting is like throwing an exception. It doesn’t merely cause you to switch from one task to another; it changes the mode in which you work.”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Szp46v5ZU9zxQGcy.jpeg" /><figcaption>Image Credit: Whyarentyoucoding.com</figcaption></figure><h3>Techniques to minimize context switching</h3><p>We can find flow in the world of constant interruptions. Here are some approaches, used by the most productive developers across the world, that we like:</p><p><strong>Time blocking</strong></p><p>Divide your workday into blocks of time. Each block should have the goal of completing a specific task.</p><p>Eg. “Catching up on email and slack messages”, “Doing deep work”, “Office hours and meetings”.</p><p>Time blocking helps give a clear structure to your day.</p><p><strong>Time batching</strong></p><p>Doing similar tasks together in a batch reduces context switching and increases efficiency. Eg. Doing all code reviews together, or answering all emails and slack messages together once or twice a day.</p><p><strong>Turning off notifications during deep work</strong></p><p>Get in control of your attention. Kill notifications from email, Slack, WhatsApp, social media, and other communication systems.</p><p>For eg. enabling the DND mode on Slack is especially effective when you are trying to get some uninterrupted maker time.</p><p><strong>Prioritization</strong></p><p>Focus on tasks that can have the most meaningful impact. Don’t get lost trying to tackle a laundry list of seemingly urgent tasks. Jeff Bezos says that his secret is making fewer, better decisions, and thinking long-term.</p><p><strong>Eating that Frog</strong></p><p><a href="https://www.amazon.in/Eat-That-Frog-Great-Procrastinating/dp/152309513X">Brian Tracy</a>, author of Eat That Frog, author of Eat That Frog, recommends tackling the biggest task first thing each morning. You must develop the routine of “eating your frog” before you do anything else. Frog is a metaphor for your biggest, most important task. Also if you have two frogs, eat the ‘ugliest’ one first.</p><p><strong>Adopt asynchronous communication</strong></p><p>It is important to focus on the quality of communication rather than speed. Help your entire team understand the benefits of async communication. Exert your influence to create a culture of not giving an immediate response to chats.</p><h3>Apps to help you stay in flow</h3><p>We have compiled a list of eight interesting productivity tools/apps that help developers minimize context switching.</p><p><a href="https://www.forestapp.cc/"><strong>Forrest App</strong>:</a> Helps you stay off your phone. Whenever you want to focus for a chunk of time, you ‘plant a tree’ in this app. The tree grows while you are working, and dies if you leave the app. Sounds amazing right!</p><p><a href="https://www.codestream.com/"><strong>CodeStream</strong>:</a> An open-source extension for VS Code, Visual Studio, and JetBrains. It puts collaboration tools in your IDE. It has integrations with GitHub, BitBucket, GitLab, Jira, Trello, Asana and provides code discussion that ties it all together.</p><p><a href="https://tuple.app/"><strong>Tuple App</strong>: </a>Distraction free remote peer programming app. It is fast, lightweight tool built for developers that fades into the background and lets you focus on being a great pair.</p><p><a href="https://www.brain.fm/"><strong>Brain.fm</strong></a><strong>: </strong>AI generated music to improve focus. This is for you if music / ambient noise helps you focus better.</p><p><a href="https://www.rescuetime.com/"><strong>RescueTime:</strong> </a>Analytics on your daily habits and productivity. RescueTime helps you see exactly where your time goes. You can block your worst distractions, and see powerful charts to make your day more productive.</p><p><a href="https://www.tecmint.com/the-silver-searcher-a-code-searching-tool-for-linux/"><strong>The Silver Searcher</strong>: </a>A Code Searching Tool. As developers, more than the time spent to write code is the time that goes into reading code or searching for a specific code. Code-searching tools like Silver Searcher can help save a significant amount of time.</p><p><a href="http://habitica.com/"><strong>Habitica</strong>: </a>This is a fun, habit-building app that turns your whole life into a role-playing game. It helps you concentrate on the tasks you actually want to get done.</p><p><a href="https://pacohq.com/"><strong>Paco</strong></a><strong>: </strong>This is our product. A bit of shameless self-promotion: I recommend checking out Paco, the new trending 🔥 Slack productivity app that helps Makers to go async on Slack, hence reducing the need to interrupt their flow. Paco was developed to help out with the Context Switching problem.</p><p>As we get more used to remote working, our work culture should evolve to recognize the cost and impact of context switching. We can all do our part by helping socialize these techniques and tools at our workplaces.</p><p>— -‍</p><p><em>Originally published at </em><a href="https://pacohq.com/blog/Guide/the-high-price-of-context-switching-for-developers"><em>https://pacohq.com</em></a><em> on April 23, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9697b011eadc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pacohq/the-high-price-of-context-switching-for-makers-ways-to-avoid-it-9697b011eadc">The high price of Context Switching for Makers &amp; Ways to Avoid It</a> was originally published in <a href="https://medium.com/pacohq">pacohq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Easy Guide to Getting Started With Deep Work]]></title>
            <link>https://medium.com/pacohq/the-easy-guide-to-getting-started-with-deep-work-6168f9a113a9?source=rss-1a4621689da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/6168f9a113a9</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[copa]]></category>
            <category><![CDATA[productivity-hacks]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[deep-work]]></category>
            <dc:creator><![CDATA[Sumit Suman]]></dc:creator>
            <pubDate>Tue, 20 Apr 2021 11:22:00 GMT</pubDate>
            <atom:updated>2021-06-09T22:06:29.609Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published at </em><a href="https://pacohq.com/blog/Guide/deep-work-how-to-get-started"><em>Paco </em></a><em>| </em><a href="https://pacohq.com/"><em>www.pacohq.com</em></a></p><p>Are you intimidated by the idea of deep work? Here is an easy guide to get started today. Understand when you need deep work, create a schedule, and a routine for it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8dZ46H-d5j2b-MPA0BvdHA.png" /></figure><p>One of the best things to come out of the seminal book, <a href="https://www.calnewport.com/books/deep-work/">Deep Work — Rules for Focused Success in a Distracted World</a>, by Cal NewPort is the wide recognition of the benefits of deep work. I knew it had made it when I heard it in the boardroom of a consulting client recently. Deep work has always been the default preferred mode of working for developers. Newport’s book gave us a vocabulary to protect our maker time.</p><p>There is a side effect of a productivity system becoming a cult hit. Earlier, I could say that I want to work uninterrupted for a few hours as a routine, lock myself in a room, and just do it. Now, I would research the types of deep work schedules and the most optimal environment for my work desk first. More reasons for the procrastinator in me to delay getting started.</p><p>Not anymore. Here is my attempt to help anyone start practicing deep work today.</p><h3>Step 1: Understand whether what you are doing needs deep work</h3><p>Use this simple worksheet to figure it out for yourself. If your graph trends towards the right, then, “Voila! Congrats!”, you are eligible to do deep work :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TsuMtfPlZid4EtW6.png" /></figure><h3>‍Step 2: Decide your deep work schedule</h3><p>There are 4 kinds of deep work schedules defined in the book.</p><ul><li><strong>Monastic Schedule: </strong>Reject all shallow work and only focus on deep work. All day, every day. Highly recommended for those with an EA and a chief-of-staff, at least.</li><li><strong>Bi-Modal Schedule:</strong> Practice deep work like seasons. Spring is for deep work, winter is for shallow work. A more realistic bi-modal schedule could be to divide your week into deep-work and shallow-work days.</li><li><strong>Rhythmic Schedule: </strong>Divide your day into chunks of deep work and shallow work. The most practical schedule for most knowledge workers. Choose this schedule if you are getting started.</li><li><strong>Journalistic Schedule: </strong>Practice deep work whenever you can. Sounds about right for most managers.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PN88pjz5dvc75-gr.png" /></figure><h3>Step 3: Create your deep work routine</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tW-lyve4pp5cZR1V.png" /></figure><p>This is my favorite part. Be intentional with your deep work. I do it for every session but if your work allows, you can do this as a standing commitment.</p><ul><li><strong>Define what is success for the session. </strong>Decide which ugly frog will you eat and that you won’t stop until you have chewed every bone.</li><li><strong>Create a conducive working environment</strong>. A quiet room (if you have access to it) or a nice pair of headphones should suffice for most of us.</li><li><strong>Define how long will be your deep-work session.</strong> This is important to keep you going in a single stretch. You are allowed to take small breaks.</li><li><strong>Lay some ground rules for yourself.</strong> Our minds are evil — we give it an inch and it grabs the whole mile. Kill notifications, no peeking on emails and messages are the most common ones.</li><li><strong>Take care of yourself while you do deep work.</strong> Get some water, your favorite snacks, some nice music. Maybe ask your kid to give you a hug after your session is over (I do this).</li></ul><p>That is all you need to get started. Good luck!</p><p>You can download the slides as a <a href="https://bit.ly/3griwQK">printable PDF here</a>. If you liked this, <a href="https://twitter.com/pacofetch">follow us on Twitter!</a></p><p><em>Originally published at </em><a href="https://pacohq.com/blog/Guide/deep-work-how-to-get-started"><em>https://pacohq.com</em></a><em> on April 20, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6168f9a113a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pacohq/the-easy-guide-to-getting-started-with-deep-work-6168f9a113a9">The Easy Guide to Getting Started With Deep Work</a> was originally published in <a href="https://medium.com/pacohq">pacohq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An email app for me]]></title>
            <link>https://sumitsuman.medium.com/an-app-for-me-a4a338f32cc1?source=rss-1a4621689da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4a338f32cc1</guid>
            <category><![CDATA[email]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Sumit Suman]]></dc:creator>
            <pubDate>Sun, 13 Aug 2017 23:30:44 GMT</pubDate>
            <atom:updated>2017-08-19T10:16:28.051Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3JNrvKfRQp66YzM4wcekyQ.jpeg" /></figure><p>It started with the realization that I don’t receive personal emails on my personal email ID anymore. When was the last time you got one? While you are at it, do you also remember the last time you received a personal snail mail letter from a friend?</p><p>Is our personal email app up-to-date with that new reality? Or is it still stuck in the world of trying to weed personal email out of updates, promotions, forum, and social messages :D.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gBFv4KHNbMkJZlYI8Ep1vw.png" /></figure><p><strong>I decided to do a prototype for a personal email app that I’ll use. </strong>I ignore work-email for this exercise. I have developed a fairly good workflow for it and lots of interesting new products are addressing that space.</p><p>Designing for our own self is an interesting exercise. We define our biases. We learn to appreciate that uncovering the needs of a user is not trivial. Even when we know them quite well <a href="https://www.headspace.com/">;)</a>.</p><h3>I don’t receive personal emails anymore</h3><p>I started with an audit of my personal email inbox. I realized that I don’t receive personal emails anymore there. That ship sailed to the messaging port long time ago. But I do get a lot of emails:</p><ul><li>Emails from my bank.</li><li>Email confirmation for the tickets I booked</li><li>Consulting offers</li><li>Messages from recruiters</li><li>Customer service communication with a wide range of companies</li><li>Password resets</li><li>2FA Pins</li><li>Personal networking messages</li><li>Newsletters</li><li>Updates &amp; notifications from a from a variety of services / products I use</li><li>Engagement emails from the same services / products I use</li><li>Bills</li><li>Marketing emails from services / products I don’t use</li><li>Spam</li><li>Forwards from my dad</li></ul><p>I often reply to networking messages, interesting consulting offers, recruitment emails when I’m looking for jobs, customer service communication, direct communication with my bank, etc.</p><p>I open the ticket confirmation to ensure I got the right thing, and hope to find them again when I’m traveling. I also look at bills.</p><p>I pay attention to notifications from the bank. I open them, read them, take action if needed. I scan the notifications &amp; updates from the products/services I use for something useful/actionable.</p><p>I obviously engage with password resets and 2FA codes.</p><p>I read about 20% of newsletters I get.</p><p>I ignore all engagement &amp; marketing emails. I mark and delete spam.</p><p>I do, sometimes, read the forwards from my dad :).</p><p><strong>To summarize my use case</strong>:</p><ul><li>Personal email is the trusted place to receive sensitive information. Things I asked for — tickets, bills, invoices, 2FA codes or non-work professional contact.</li><li>Personal email is a file store for important documents that I may need to reference later.</li><li>Personal email is my sane replacement for push notifications.</li><li>Personal email is low fidelity RSS reader for content that I opted into.</li><li>Everything else is probably unwelcome crap.</li></ul><h3>The app for me</h3><p>The prototype I came up with for me is an app with a tabbed interface. It gets four primary tabs — conversations, documents, newsletters, and notifications. Conversations tab has a sub-tab for conversation requests. Email that is not categorized under any of these categories, is not of interest and gets thrown under “All Emails”.</p><h4>Conversations</h4><p>This tab is the most important of the four tabs. It contains the emails I replied to or received a reply for. I want to engage most actively in this tab, hence the app opens on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*3sHi_oEoTG13lWqj5ZPN5g.png" /><figcaption>Screen 1: Active Conversations</figcaption></figure><h4>Conversation Requests</h4><p>I have separately categorized emails that would become new conversations only after I reply to them. I often receive emails that meet the criteria for having a conversation but I never get around to replying to them. They are as good as dead until the sender follows up or I’m cleaning my inbox. I don’t want them to crowd my active conversations window, hence I have put them in a separate sub-tab. The unread count, however, does include requests. The neurotic email user in me can’t ignore that for too long.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*I4lrLs_l0FSxSnV45IQhUA.png" /><figcaption>Screen 2: Requested Conversations</figcaption></figure><h4>Documents</h4><p>The tab is self-explanatory. I receive documents that I want to reference later. The attached PDFs are the most important part of the email, hence they get a prominent view. I can click and expand them for a quick view. I can pin them for easy access. Of course, I can access the full email by going inside it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*ogJp1K_bH9Ktl1h8Jr63cw.png" /><figcaption>Screen 3: Documents</figcaption></figure><h4>Newsletters</h4><p>This tab satisfies my newsletter use case. I subscribe to a bunch of them and read a few of them religiously. Easy and dedicated access to them would be nice. I should be able to bookmark or unsubscribe as needed as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*7wQFtUXRD5wSDFbgjYUwWg.png" /><figcaption>Screen 4: Newsletters</figcaption></figure><h4>Notifications</h4><p>It would be a bliss to have all email notifications in one place. I should be able to clear them all in one go. Just like we do for push notifications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*1T7Vj4sIw_UJl8xBbl8aeA.png" /><figcaption>Screen 5: Notifications</figcaption></figure><h3>Real world feedback</h3><p>If you made it so far, I invite you to check out the clickable prototype on <a href="https://projects.invisionapp.com/share/WAD0LX6ZQ#/screens/248427102">Invision</a> and leave your feedback in comments (or message me):</p><p><a href="https://invis.io/WAD0LX6ZQ#/248427102_1">Click here to view the project `Email app for me`</a></p><p>I’d love to see where other users diverge from my personal view.</p><p>I will document the feedback diligently and then pack this up.</p><p>While time consuming, this exercise will provide a ready documentation for my biases if I had to develop a real email app for real. . In the worst case, I have a good set of ideas to begin with (see what I did there).</p><p><em>Big mirror photo by </em><a href="https://unsplash.com/photos/K04ykMnmQxw?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Enrico Carcasci</em></a><em> on </em><a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Unsplash</em></a></p><p><em>A disclaimer — the prototype is a wireframe that just focuses on primary use cases. It is obviously not a complete interface. I used Adobe Comp so it looks better than hand drawn.</em></p><h3>Edit: Comments</h3><p>Got some interesting comments, compiling them here:</p><p><strong>SG writes:</strong></p><blockquote>Like the idea that we need an email app which is designed for the non conversation centric world we live in with Facebook, WhatsApp. I wasn’t sure Why do you need a conversation tab as the most important element in this UI if most of your personal emails are matter of fact and very few are consulting offers/recruiters that you care about.</blockquote><blockquote>Secondly wouldn’t it better if all confirmation email for bookings attachment automatically get tagged and saved in google drive or another cloud storage solution, you might just get a notification that such and such confirmation is received. Alternatively do you want a world where all your communications can be routed to a single app (though it will be almost impossible to replicate all the rich features of individual apps)</blockquote><p>I found that conversations are what I most engage with. Even if the messages are not personal in nature, the fact that I reply to them and the recipient replies back leads to an investment from my end which is missing in the other categories. Hence I gave it the prime importance.</p><p>For sending attachments to other apps — I think two reasons why it did not occur to me upfront. Firstly, I’m a conservative app user. Unless I really need it, I don’t use it. I never felt the need to save my attachments outside the email app (maybe I should, for a different backup reason). Also, I think that while the attachments are what I engage with most, the context provided by the email body is important as well. There is time, sender, subject, and text. Drive or Dropbox, or other similar file sharing apps still don’t do a good job of preserving that context well (that is another whole area of under-optimized product innovation).</p><p><strong>SP writes:</strong></p><blockquote>What is Email? <br>My minimalist instinct says that an email (address) is a virtual reference to you. The job of the Inbox should be a smart triager — that’s it. Hopefully to be replaced by an AI very soon.</blockquote><blockquote>The triager should:<br>1) Triage automatically<br>2) Allow me to easily Triage where it gets stumped and learn from me</blockquote><blockquote>The result of the triaging should:<br>- Send 90% of mail I get to garbage<br>- Connect/act as a very good filing/organizing system for all the banking, social etc. alerts<br>- Keep Live actionable conversations (does mode matter — what if i want to reply on whatsapp, facebook, linked in)<br>- Connect to my calendar<br>- Connect to my to-do list (things I am actively working on)<br>- Connect to my saved files (photos, documents etc.)</blockquote><blockquote>Would like to see your thoughts on how this new email system will do a better job at acting as my incoming information master and connect easily to all the other apps I use.</blockquote><p>Triaging is and will become bread and butter for email apps. Gmail does a fairly good job at it, Inbox adds a few more categories, <a href="https://superhuman.com/">Superhuman</a> is claiming to reverse engineer Spam filters for triaging, <a href="https://www.sanebox.com/">Sanebox</a> thrives on it. Since it will need to be trained, will look for patterns, will learn — it will make use of AI. And that’s the thing with AI, if the use case demands it, it will be used — claiming AI to be a differentiator does not appeal to me as a user.</p><p><strong>AS writes</strong></p><blockquote>I am still not able to grasp the value of the 2 tabs ‘Conversations’ and ‘Requests’. For simplicity, if you consider just one ‘Conversations’, then it also caters to the needs of the user. 2 Tabs are just adding to the complexity.</blockquote><blockquote>Do we still need this? Where will ‘All emails’ link take us? I feel that by disrupting the mails through this app, the need of this goes away.</blockquote><p>I realized that I don’t reply to many emails, primarily because I just don’t get around to it or it is not really wanted. These emails would become more important if I did reply to them. I did not want them to clutter my conversations view, hence the separation.</p><p>‘All emails’ is a catch all if the triaging fails. I like it on Gmail, when I get lost in the categorization I just move to the all mail view.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4a338f32cc1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This 30 minute routine will help you focus on the most important stuff]]></title>
            <link>https://sumitsuman.medium.com/the-most-important-stuff-62513bc73e92?source=rss-1a4621689da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/62513bc73e92</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[gtd]]></category>
            <dc:creator><![CDATA[Sumit Suman]]></dc:creator>
            <pubDate>Mon, 16 May 2016 01:26:22 GMT</pubDate>
            <atom:updated>2016-05-16T01:58:06.059Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/785/1*UAB7_1Trsv7_hd6V3xEMtg.png" /></figure><h3>The Routine</h3><p>30 minutes on Sunday night helps me avoid chaos during the week. My routine is to look at everything on my plate and note down the most important ones. Usually, 6–10 items. Everyday, before I start something new, I see this list to make sure I spend most of my day on the most important stuff. This is all the project management that my teams and I need. This system relies on 3 pillars:</p><h4>1. Big Needle(s) to Move</h4><p>I must always know what big needle(s) we are trying to move. Without that explicit knowledge, I can never identify the most important items. The big needle could depend on the goal for my team; it could be an impending milestone; or be driven by a crisis. Knowing what to focus on wins half the battle.</p><h4>2. Method to Process Inputs</h4><p>I must have a method of efficiently processing all the inputs I get in form of emails, IMs, meeting notes, todos, or white-boarding ideas. Aspects of GTD system are helpful. I try to finish quick things immediately; send stuff to others if I can’t do it; file and tag stuff on my plate so I can access them on demand. <a href="http://sumitsuman.com/master-the-tools-you-use">Tools are of-course helpful</a>.</p><h4>3. Stamina to Survive Noise</h4><p>In most of knowledge roles, we get inundated with inputs. The noise is bound to overwhelm us. It is a never ending battle. It needs stamina, patience, and tact to keep focus. As companies grow, it becomes harder. I follow a simple rule: I’ll spend most of the day on the most important stuff. As for rest of the time, let’s just say that a lot of good can happen in that :).</p><p><a href="http://iceage.wikia.com/wiki/File:Scrat_(character_model).jpg"><em>Image credit</em></a><em>; </em><a href="http://sumitsuman.com/most-important-stuff"><em>Original post</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62513bc73e92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Managers and Product Marketing Managers]]></title>
            <link>https://sumitsuman.medium.com/product-managers-and-product-marketing-managers-cd30cf800e43?source=rss-1a4621689da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd30cf800e43</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-marketing]]></category>
            <dc:creator><![CDATA[Sumit Suman]]></dc:creator>
            <pubDate>Mon, 17 Aug 2015 02:42:20 GMT</pubDate>
            <atom:updated>2015-08-17T02:43:45.601Z</atom:updated>
            <content:encoded><![CDATA[<p>A successful product needs strong product development and strong go-to-market. For most B2B and Enterprise products, that means successful collaboration between product managers and product marketing managers. This collaboration begins with a clear definition of roles:</p><p><a href="http://www.svpg.com/product-management-vs-product-marketing/">As Marty Kagan puts it</a>,</p><blockquote>The product manager is responsible for defining — in detail — the product to be built, and validate that product with real customers and users. The product marketing person is responsible for telling the world about that product, managing the product launch, providing tools for the sales channel to market and sell the product, and for leading key programs such as online marketing and influencer marketing programs.</blockquote><p>i.e. product managers own the product development lifecycle, and product marketing managers own the go-to-market lifecycle.</p><p><strong>Product development lifecycle consists of:</strong></p><ol><li>Concept phase, where initial hypothesis is validated</li><li>Growth phase, where the product grows out of its minimal avatar</li><li>Maturity phase, where product finds its place, and the change slows down</li><li>End-of-life phase, where the product is headed for sunset</li></ol><p><strong>Go-to-market lifecycle consists of:</strong></p><p>a. Pre-launch phase, where the value proposition is discovered</p><p>b. Launch phase, where the product is introduced to the world</p><p>c. Continued market engagement phase, where the product battles it out in the market</p><p>d. End-of-life phase, where the product is gracefully put to rest</p><h4>1 + a: Concept &amp; pre-Launch</h4><p>Product manager leads this stage bringing the concept to life through experimentation, prototyping, or developing an MVP. Product marketing manager plays a critical supporting role by helping gather market inputs, conduct customer research, or interpreting field feedback.</p><h4>b: Launch</h4><p>Product marketing manager leads this critical part of go-to-market with input from the product manager. They prepare the messaging, prep the marketing team, engage analysts, and conducts sales training where needed. Support training is led by the Product manager.</p><h4>2 or 3 + c: Growth or maturity phase hand-in-glove with continued market engagement</h4><p>A product that keeps on evolving (e.g. most SaaS products) stays in the growth phase much longer than a product which is mostly defined upfront (e.g. single function APIs). In the growth phase, the product is the product manager’s baby — every ounce of market feedback goes into the product’s evolution. In the maturity phase, the product is a revenue generator, and can live with reduced attention from the product manager. Product marketing manager remains important for both phases.</p><h4>4 + d: Product retires</h4><p>Opinion differs on who should lead in this phase — both product and product marketing managers play a critical role in making sure that the product retires gracefully — customers are communicated to properly, their data is taken care of, and internal communication and training is managed effectively.</p><p>This is just one model. Different companies follow a variation, with varying degrees of success. There are other roles, for example Product Operations, which play a hand as well. I’d love to hear more if you seen something different.</p><p><em>This was first published </em><a href="http://sumitsuman.com/product-managers-and-product-marketing-managers/"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd30cf800e43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Managers and Developers]]></title>
            <link>https://sumitsuman.medium.com/product-managers-and-developers-8645bbfc088b?source=rss-1a4621689da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8645bbfc088b</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Sumit Suman]]></dc:creator>
            <pubDate>Mon, 17 Aug 2015 02:34:45 GMT</pubDate>
            <atom:updated>2015-08-17T02:34:45.498Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*4qK40_l-96qkJGU2d3mvwQ.jpeg" /></figure><p>I have had the good fortune of working with a terrific bunch of developers and software engineers on my team. I am well aware that my success as a product manager depends on how well I work with them. Overall, it is no different than any other working relationship, which thrives on context, trust, communication, and empathy. But I’ve learned a few things that, perhaps, others can learn from.</p><p>To influence a team smarter than me, I have to work hard. To convince them to spend tens of hours of effort into developing something, I have to do my homework well. There is a trick though: I don’t have to do the homework in isolation.</p><p><strong>As a team we share every idea</strong>, every customer feedback, every complaint — and we do it early. New product features are borne out of these discussions. My job is to take the crux of this throbbing-thriving idea exchange and give it some structure — to discover, socialize, validate, prototype, rinse, repeat.</p><p>All this happens in front of the team and with <a href="http://www.druva.com/blog/watching-druva-grow-employee-retrospective/">their active participation</a>. I take <strong>no product decisions behind closed doors</strong>. The team sees the idea take shape. It’s their baby, too, when it finally comes to them for development.</p><p><strong>When and how we communicate</strong> is particularly important. While the team needs context, I do my best to be careful about separating <em>reference-able</em> information from <em>actionable</em> information. We use persistent chat tools for reference-able communication (Hipchat’s been our choice) so anyone can tune in or out as per their focus schedule. E-mail and Trello boards work better for actionable communication.</p><p><strong>Ownership and handoff are critical</strong>. During the product design and validation phase, I’m the owner. The dev team provides input and recommendations, but the decision lies with me. The role reverses when I hand-off the product requirements for development.</p><p>This model works only when the team can trust that I have done my best, and vice-versa. I have to earn that trust — and only then can I demand it back. It is hard. For example, I did miss a few test cases on a couple of features, and we had to go back to the drawing board. But I gave my best effort, and the team saw it. We got better.</p><p>One more thing. Despite all our best intentions, <strong>things do go wrong. It is not the end of the world</strong>. In a high-pressure delivery environment we can’t make a trend of this; if that happens, it probably points to a deeper rot.</p><p>Thankfully, it is quite possible to rally back from most setbacks. Delivery dates do get missed. Bugs get shipped. Customers get pissed. Sometimes. We do a post-mortem, correct our course based on what we learn, and we move on.</p><p>I hope this post reaches product managers and developers who have had a far greater and varied experience than me. I’d love to learn from you. Please do share your experiences.</p><p>A plug for the wonderful developers who helped me understand their mindset better:</p><ul><li><a href="http://twitter.com/nitin_pande"><em>Nitin</em></a><em>, the swiss knife of a person. A developer, designer, product manager rolled into one package.</em></li><li><a href="https://www.linkedin.com/pub/andrew-lazarus/9/455/737"><em>Andrew</em></a><em>, the builder turned engineer and probably the smartest person I have interacted with.</em></li><li><em>My (past) Druva team — </em><a href="http://in.linkedin.com/in/achinmay"><em>Chinmay</em></a><em>, </em><a href="http://in.linkedin.com/in/sameertamsekar"><em>Sameer</em></a><em>, </em><a href="http://in.linkedin.com/in/vaidyaabhijit"><em>Abhijit</em></a><em>, Saurabh, </em><a href="http://in.linkedin.com/pub/agniswar-bakshi/4a/173/434"><em>Agni</em></a><em>, </em><a href="https://www.linkedin.com/pub/alok-ranjan/7a/677/3b1"><em>Alok</em></a><em>,</em><a href="http://in.linkedin.com/pub/naveen-agrawal/4b/443/148"><em>Naveen</em></a><em>. With folks like them, no wonder Druva produces the #1 product in a cutting edge market.</em></li></ul><p><em>This post was first published </em><a href="http://sumitsuman.com/working-with-developers/"><em>here</em></a><em> and then </em><a href="http://www.druva.com/blog/product-managers-guide-working-developers-everybodys-happy/"><em>here</em></a><em>.<br>Image credits: </em><a href="https://flic.kr/p/6XidPL"><em>Seattle Municipal Archives</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8645bbfc088b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>