<?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[Whispir - Medium]]></title>
        <description><![CDATA[Who we are and how we work — Come and work with us: https://boards.greenhouse.io/whispir/ - Medium]]></description>
        <link>https://medium.com/whispir?source=rss----ea0b714f83a2---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Whispir - Medium</title>
            <link>https://medium.com/whispir?source=rss----ea0b714f83a2---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:22:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/whispir" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Visualising Trade-Offs in Software Development]]></title>
            <link>https://medium.com/whispir/visualising-trade-offs-in-software-development-82cd0b00072d?source=rss----ea0b714f83a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/82cd0b00072d</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[opportunity-cost]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[technical-debt]]></category>
            <dc:creator><![CDATA[Brian Oakley, PhD]]></dc:creator>
            <pubDate>Tue, 07 Sep 2021 22:53:12 GMT</pubDate>
            <atom:updated>2021-09-08T23:48:34.268Z</atom:updated>
            <content:encoded><![CDATA[<h4>Marshmallows for Product Managers</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*If8oqjcUgV6YIRNh0nkQUA.png" /><figcaption>Illustration by the Author</figcaption></figure><p>You might have heard of the famous <a href="https://en.wikipedia.org/wiki/Stanford_marshmallow_experiment">Stanford marshmallow experiment</a> from 1972, where children were given a single marshmallow on a plate, with the promise of a second one if they could wait some time before eating it. If the child couldn’t bear to <a href="https://en.wikipedia.org/wiki/Delayed_gratification">delay gratification</a> for 15 minutes (and many could not!) they would forfeit the second marshmallow</p><p>This experiment highlights something we all understand intuitively — sometimes it is difficult to forgo short-term gains in exchange for some delayed, but much greater, long-term gain. Even when the benefits are clearly defined and unambiguous, like compound interest on retirement savings, we often find ourselves instead prioritising the <em>here-and-now. </em>I suspect this is why <a href="https://www.abc.net.au/news/2021-02-26/kim-kardashian-afterpay-millennials-zip-buy-now-pay-later/13194484">AfterPay is so popular among jaded millennials</a>, myself included.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jT9cmgo7HVTMHz7J9h7GWA.png" /><figcaption><strong>Human beings kinda suck at delaying gratification, even if the opportunity cost is large and unambiguous.</strong> Image modified by the Author. Source: <a href="https://knowyourmeme.com/memes/distracted-boyfriend">https://knowyourmeme.com/memes/distracted-boyfriend</a></figcaption></figure><h3>The tech-debt bog</h3><p>The speed at which a company can develop software is a function of <em>resources</em>, <em>requirements</em> and <em>tech-debt</em>. That third parameter <a href="https://adhoc.team/2021/06/02/tech-debt-interest-rate/">slowly and inevitably increases with time</a>, and like driving through a muddy bog, the deeper in it you are, the slower you move.</p><p>This leads to a common dilemma for PMs:</p><blockquote>Continue delivering features (albeit slowly, due to accumulated technical debt)?</blockquote><p><em>OR</em></p><blockquote>Press pause on delivering features and focus on addressing the problem, which will increase our velocity long-term?</blockquote><p>The <em>right</em> answer varies business to business, and also changes with time depending on available resources, level of tech-debt, etc. The answer today may be different to the answer in 6 months time, and it’s likely to create some tension within the business — where the priorities of different functions pull the decision-maker in multiple, competing directions.</p><p>Perhaps your devs are fully on-board with multiple sprints dedicated to code refactoring and clean-up (<em>“it will make my life so much easier going forward”</em>), while other stakeholders may balk at the idea of an extended feature drought (<em>“how do I justify delaying this feature yet again?”</em>). If you’re the one tasked with deciding, how do you choose a path? And perhaps more importantly, how do you convince people that your choice was the right one?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*STi9ejl1rSYnuUqA-ZyhXA.png" /><figcaption>Source: <a href="https://vincentdnl.com/drawings/">https://vincentdnl.com/drawings/</a></figcaption></figure><h3>Q<em>uantify and visualise</em> the trade-off</h3><p>While it may be much easier to argue for one option or another in the abstract, it is often said “a picture is worth a thousand words” — so <em>let’s draw a picture</em>.</p><h4>Consider the current situation</h4><p>We can visualise <em>Option One</em> (the path where development continues, but slowly due to tech-debt) by drawing a simple line using the equation:</p><blockquote><strong>y = mx</strong></blockquote><p>… where <strong><em>y</em></strong> is your <em>measure of the outcomes/output</em> (for example, “average number of features delivered”), <strong><em>x</em></strong> is your <em>measure of time </em>(e.g. “months”), and <strong><em>m</em></strong> is your current<em> speed</em> (“the number of features delivered per month”). These are just examples, use whichever measures make the most sense for your given situation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NjcJstsB2ynw0eHWrnoXQg.png" /><figcaption><strong>Even small changes in speed (<em>m</em>) result in large differences in outcomes over time.</strong></figcaption></figure><p>Using this equation, you can very easily calculate the <em>expected</em> number of features delivered after <strong><em>x</em></strong> months, by multiplying by <strong><em>m</em></strong><em>.</em> If, on average, you deliver <strong>2.5 features per month</strong>, in <strong>24 months</strong> you should have delivered <strong>60 features</strong> (2.5 <em>multiplied by</em> 24 = 60).</p><h4>Consider the alternative</h4><p>Drawing the second option (the one where development is temporarily halted) is slightly more complex, since we have a few extra parameters to consider.</p><p>First you need to estimate how long the “pause” will last — let’s call this parameter <strong><em>p</em></strong>. This will depend on your particular situation, but I’d suggest leaning towards <em>over</em>-estimating here (you’ll see why later).</p><p>For this example, let’s say it will take <strong>4 months</strong> to sort out the tech-debt (therefore <strong><em>p</em></strong> = <strong>4</strong>), and during that time you expect <strong>zero</strong> features to be delivered (<strong><em>m</em></strong> = <strong>0</strong>). Because anything multiplied by zero equals zero, this period of time looks like a horizontal line from the origin to where <strong><em>x </em></strong>= <strong>4</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sc96qm63Pg4PkYX7teHAKA.png" /><figcaption><strong>Immediately it is clear the green path comes at at a cost, at least in the short-term.</strong></figcaption></figure><p>It may be the case that some proportion of the team <em>can</em> continue to develop new features while the tech-debt is being addressed. If so, you can adjust the slope of the line accordingly (<em>see left</em>). You can even use a negative value to represent work that will need to be re-done (i.e., you’ve gone backwards a bit) as a result of the pause. In any case, make sure to cut the line off at <strong><em>p</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bKb38DV0eYsC-R65K7EgVw.png" /><figcaption><strong>Outputs during the pause don’t need to be zero.</strong></figcaption></figure><p>Finally, you need to estimate your <em>speed after the pause</em>. This is challenging because you’re essentially trying to predict how the work done during the pause will change productivity in the future. I’m not going to get into the details of how to find this number (maybe in a future post if anyone is interested?), but again I’d suggest using a conservative estimate here.</p><p>For now, lets say you’ve spoken to your tech leads and they expect that after the tech-debt is dealt with, average development time per feature should halve (therefore, speed should double). In this scenario, the slope of the line, <strong><em>m</em></strong>, is double that of <em>Option One</em> (2 * 2.5 = 5, so <strong><em>m = </em>5</strong>).</p><p>Draw <em>this</em> line originating at the end of the line representing the pause, and you <em>should</em> see that it crosses over the line for <em>Option One</em> — <em>this is the “break-even point”</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MOotxw8iLBfV4rtlk1WSGg.png" /><figcaption><strong>Option One in pink, Option Two in green. The break-even point is highlighted in blue.</strong></figcaption></figure><p>In the chart above, you can clearly see the short-term losses associated with <em>Option 2</em> are paid back in full at the 8 month mark. From that point onwards, the increase in speed <em>compounds</em>.</p><p>This is particularly dramatic when taking the long-term view:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ivUzE2Xmg2R6BBFEeh8DJQ.png" /><figcaption><strong>Zoom-out a bit to see the long-term gains (i.e. the opportunity cost of choosing Option One).</strong></figcaption></figure><p>At the 3 year mark, choosing <em>Option One</em> would result in around 90 features being delivered. In contrast, choosing <em>Option Two</em> would mean developing 90 features would take only 22 months (just under 2 years), and at the 3 year mark, 160 features will be delivered.</p><p>In this example case, the long term compounding benefits are dramatic. This is why earlier I suggested using conservative estimates. Another approach is to draw two lines for <em>Option Tw</em>o— a “best-case” and a “worst-case” scenario — and consider the range of possible break-even points when making your decision.</p><h3>So which is the right option?</h3><p>After visualising both options, you will still need to weigh the costs and benefits before coming to a decision. If your situation <em>requires</em> some outcome before development can resume, then you may need to stick with Option One. If the expected short-term losses can be tolerated, and the long-term gains are attractive — Option Two is the way to go. If you’ve followed these steps and found that the two paths<strong><em> do not</em></strong> cross over (i.e. no break-even point), congratulations! Your decision has been made for you and should be plainly apparent in your chart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4k1Fz40rclqvZZLIMixwSQ.png" /><figcaption><strong>Your decision will depend on how your business can tolerate the short-term losses.</strong></figcaption></figure><h3><strong>TL;DR:</strong></h3><blockquote>The closer the break-even point, the stronger the argument for taking Option Two.</blockquote><blockquote>If no break-even point exists, choose Option One.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*8GspI-Fesy0pJKymDboTCQ.jpeg" /></figure><p><strong><em>If you’re curious…</em></strong></p><p>I work in the <strong>Product Intelligence</strong> team at Whispir, and my job is to help our teams make better decisions using my expertise in statistics, neuroscience and data visualisation.</p><p>This blog post came into being because recently some of our teams were considering a large technical project which might delay features, and we needed a quick and easy way to consider the options, and communicate the impact. I built a simple trade-off visualisation tool so that teams could “see” the long-term benefits (or lack thereof!) and have a conversation anchored by numbers, rather than gut-feel.</p><p>Admittedly, the method I’ve described here is pretty basic, and could easily be extended by adding non-linearities (to account for accelerating/decelerating productivity) or time-dependent confidence intervals (because near-term projections are more reliable than those further out).</p><p>However, in the spirit of Tim Peters’ “<a href="https://www.python.org/dev/peps/pep-0020/">The Zen of Python</a>”:</p><blockquote>If the implementation is hard to explain, it&#39;s a bad idea.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82cd0b00072d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/whispir/visualising-trade-offs-in-software-development-82cd0b00072d">Visualising Trade-Offs in Software Development</a> was originally published in <a href="https://medium.com/whispir">Whispir</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Putting your colleagues into boxes — how to understand them better]]></title>
            <link>https://medium.com/whispir/putting-your-colleagues-into-boxes-how-to-understand-them-better-ed87cb3d4ebb?source=rss----ea0b714f83a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/ed87cb3d4ebb</guid>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[productmanagment]]></category>
            <dc:creator><![CDATA[Grace Halim]]></dc:creator>
            <pubDate>Tue, 31 Aug 2021 06:01:59 GMT</pubDate>
            <atom:updated>2021-08-31T06:01:09.656Z</atom:updated>
            <content:encoded><![CDATA[<h3>Putting your colleagues into boxes — how to understand them better</h3><p>Do you know how when you buy a new fridge or washing machine, you are given a user manual so you know how to operate it? Turns out <a href="https://www.atlassian.com/team-playbook/plays/my-user-manual">Atlassian</a> came up with one for humans/colleagues.</p><p>Given the pandemic and the realisation that the future of work is remote, leaders are asking how they can create a positive culture and get a better understanding of their team members. This is especially relevant for somewhere like Whispir where the speed of growth is almost exponential (not true technically because it’s not infinite), but we have new people join us every week (we’re tracking at a rate of about 5 people each week across our global team).</p><p>I thought it’d be great to give newcomers and existing staff an insight into the preferences of each person in the product team. This can act as a bit of a shortcut for new people. It’s popular enough that other departments have taken to doing up their own user manuals for their teams.</p><p>Each person in the team filled out a slide deck to talk about their preferences when it comes to working (location, hours, etc), giving and receiving feedback, hours for meetings, etc. We took turns presenting our user manuals to each other and have stored them on the team Confluence. This way, any new person to the team can come in and read up about their colleagues. The presentation sessions are actually great bonding opportunities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/774/0*5fLJZrzLTrmvnyf0" /><figcaption>Meme from the movie Elf: “sorry you’re sleepy but mornings are my favorite”</figcaption></figure><p>Some key themes that emerged were:</p><ul><li>people in the product team like to uncover for themselves and understand why we’re doing things and are not happy to be told “it’s how we’ve always done things”</li><li>people like collaborating and bouncing ideas off of each other</li><li>people really dislike email</li><li>audio-only calls are “rad”, video calling while immediate and better than email, can tire people out (Zoom fatigue is a real thing)</li><li>feedback is best when in person, 1 on 1, about specific events, and as close to the event as possible</li></ul><p>It’s important to try and have a better understanding of your colleagues and how they prefer to work. It builds greater empathy and makes you a better leader and colleague. I’m also a big proponent in diversity in teams just so your blind spots are covered so it’s really good when your team are diverse in their preferences. It creates more debates for sure and decisions tend to take longer, but that is something we deeply encourage in our product team at Whispir — I guess this is why we are over-indexed in people with a “Questioner” tendency. I just wish we had more night owls in the team so people are have the same level of enthusiasm during afternoon meetings as they do during morning meetings (when I’m at my lowest energy level).</p><p>Somewhat controversially, each team member also disclosed their <a href="https://www.16personalities.com/free-personality-test">MBTI</a> profiles — I acknowledge that the science behind the Myers Briggs Type Indicator is shoddy at best but it’s just a bit of fun. The alternative that was floated was: which Harry Potter house do you belong to or <a href="https://medium.com/@ryancollingwood/which-ninja-turtle-are-you-f608e4bc5f65">which Ninja Turtle are you</a> (written by our very own <a href="https://medium.com/u/6ec0a2bc8b37">Ryan Collingwood</a> against the MBTI).</p><p>Below is a quick snapshot of our team’s preferences. One of our team mates has opted to do a visualisation of a heat map of when people prefer to do meetings. We have found that some people are more alert/receptive in meetings depending on what times they are. I, myself am not a morning person so my brain is usually sub-par before 10am. This goes against the majority of the team as we’ve somehow over indexed in morning people. I’ve always identified more with engineering teams in this regard. Did I mention how much I dislike morning meetings?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/1*B_vS_U5nn-Avz04URcTnaw.png" /><figcaption>Table showing the product team’s user manuals and preferences</figcaption></figure><p>Anyway, I’ll leave you with an image that I put in my user manual at the very end — it’s from a tv show called Archer — I remember seeing it on an episode that aired many years ago and screenshotted because it resonated with me so much:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G70kgq9KadsSc9My" /><figcaption>An image of a man behind a service window with a sign that says: lack of planning on your part does not constitute an emergency on my part</figcaption></figure><p>Have a go with your team so you can gain a better understanding of each team member — I truly believe this is a step towards creating a culture with remote workforces — you don’t need to force people to come into the office to create a positive culture. Most people just want to be understood and this is one way you can start to build empathy towards your colleagues. I’m interested in hearing how you go!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed87cb3d4ebb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/whispir/putting-your-colleagues-into-boxes-how-to-understand-them-better-ed87cb3d4ebb">Putting your colleagues into boxes — how to understand them better</a> was originally published in <a href="https://medium.com/whispir">Whispir</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How social contracts made our product team more human]]></title>
            <link>https://medium.com/whispir/how-social-contracts-made-our-product-team-more-human-3eeb527b85ba?source=rss----ea0b714f83a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/3eeb527b85ba</guid>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[ways-of-working]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Grace Halim]]></dc:creator>
            <pubDate>Mon, 21 Jun 2021 06:07:18 GMT</pubDate>
            <atom:updated>2021-06-21T06:43:20.264Z</atom:updated>
            <content:encoded><![CDATA[<p>I joined Whispir about 10 months ago and I noticed that when discussions got animated, people would interrupt each other in meetings. As you may know, Zoom melts down whenever two or more people speak at once. This isn’t a big problem in person or when you use something like Discord, but alas, having multiple people talking at the same time is terrible for our brains.</p><p>I was interested in why this was happening and wanted to solve this. I thought about introducing a social contract to the team — how we were going to interact and work with each other, what’s acceptable and what isn’t — but I held off, seeing as I’d been in the team for all of 2 seconds.</p><figure><img alt="Starting a new PM role and logging into Jira for the first time. Mound of backlog items" src="https://cdn-images-1.medium.com/max/768/0*wvpQqWC9O1C8tRXw.jpeg" /><figcaption>Source: <a href="https://productcoalition.com/20-product-management-memes-to-brighten-your-day-ba63b7ccc5a2">https://productcoalition.com/20-product-management-memes-to-brighten-your-day-ba63b7ccc5a2</a></figcaption></figure><p>I left it alone but then another meeting took place where some of my teammates were spoken over, and I found out that it was quite a regular occurrence (not just during heated debates ) — just because people are so passionate, so we made a “pact” to try and bring attention back to the person who was interrupted when this happens.</p><p>I decided to just come up with a “Product Team Social Contract” and shared it around with the team and newcomers. It was to form the basis of cultural norms we expected of one another and something we could talk with new hires about as they joined.</p><p>I’d seen social contracts work well at a previous job where an external consultant came into a project I was working on and suggested we use one as a way of building better cohesion within a newly formed team. One of the things that stuck with me was being conscious about not setting up meetings over lunch time.</p><figure><img alt="Busy calendar" src="https://cdn-images-1.medium.com/max/322/0*yrn9LTUBcd3UFA7S.png" /><figcaption>Source: <a href="http://www.mindstoreaustralia.com/wp-content/uploads/2013/06/busy-outlook-calander.png">http://www.mindstoreaustralia.com/wp-content/uploads/2013/06/busy-outlook-calander.png</a></figcaption></figure><p>At the time, I worked with a remote team in Chengdu, China, so we had some engineers in Melbourne and China which meant timezones were tricky to manage. This meant that we couldn’t have meetings over 12–2 Melbourne time (because it was lunch in Melbourne and people had lunch between 12–1pm or 1–2pm) and 2–4 Melbourne time (lunch time over in Chengdu). This just meant scrum rituals couldn’t take place during that time. In all honesty, the engineers also didn’t like starting work before 10am, so we really only had cross functional team meetings after 2pm Melbourne time. You can still have meetings with your colleagues / stakeholders / customers in Melbourne during Chengdu non meeting times. Admittedly, it became tricky when you added Brisbane engineers and daylight savings to the mix but it was still manageable.</p><p>Our current social contract at Whispir makes it clear what we expect from one another around meetings — we all know meetings are expensive and most of the time, can be done asynchronously. So we made a point about minimising the amount of meetings we have as a team and I’m consciously trying to push back on meetings set up by stakeholders and questioning in a gentle way “could this be an email/Slack thread instead”.</p><figure><img alt="“This meeting could’ve been an email” mug" src="https://cdn-images-1.medium.com/max/1024/0*d1qBMSl17SaWIdOT" /><figcaption>Source: <a href="https://www.yellowoctopus.com.au/products/this-meeting-couldve-been-an-email-mug">https://www.yellowoctopus.com.au/products/this-meeting-couldve-been-an-email-mug</a></figcaption></figure><p>If you’re interested, below is the living document that is the Whispir Product Team Social Contract — it’s living in the sense that anyone in the team can add/modify/edit specific parts. At the end of the day, we all have to agree that this is how we are going to operate/work with each other.</p><p>— — — — — — —</p><h3><em>1. Inclusivity</em></h3><p>We create an inclusive and respectful environment for everyone that we work with. This includes doing things like:</p><ul><li>Creating space for others — support less heard voices and differing opinions</li><li>Being wary of when our colleagues are interrupted and bringing attention back to them. Try and do it ourselves if we feel comfortable</li><li>Being able to disagree respectfully and coming at topics from a curious perspective and trying to understand the other party.</li><li>Spell out acronyms the first time we use them in any given session/piece of communication and try and avoid using jargon if we can.</li></ul><h3><em>2. Meetings</em></h3><ul><li>Meetings are blockers — respect people’s time</li><li>Be wary of setting up too many meetings</li><li>Avoid booking meetings over lunch or after hours</li><li>Keep meetings short — 15–30 mins ideally</li><li>Send out an agenda ahead of time where possible</li><li>Solicit opinions from the whole group, especially quieter and less heard members</li></ul><h3><em>3. Encourage feedback</em></h3><p>Giving feedback one on one after an event — positive and constructive. eg.</p><blockquote><em>Hey I really liked how you handled that meeting or hey just curious as to why this was done, I would’ve done it this way.</em></blockquote><h3><em>4. Embrace newcomers</em></h3><p>Go out of our way to make new members feel welcome — can be as simple as dropping a Slack message to see how they are going every week once they start and see if they need anything</p><h3><em>5. Reliability</em></h3><p>Being reliable and consistent is key to developing trust with your team and contributes greatly to high performing teams. If you say you will be somewhere, please arrive on time and be ready to go or if you are going to be late — let people know ahead of time. It’s important to show up for your peers when it counts.</p><p>— — — — — — —</p><p>Feel free to copy/paste (this is what some other departments have done) or come up with your own or use it as a foundation for an improved version. I’d love to hear what’s in your social contract.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3eeb527b85ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/whispir/how-social-contracts-made-our-product-team-more-human-3eeb527b85ba">How social contracts made our product team more human</a> was originally published in <a href="https://medium.com/whispir">Whispir</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The world needed a distraction free messaging platform — so we started building one]]></title>
            <link>https://medium.com/whispir/the-world-needed-a-distraction-free-messaging-platform-so-we-started-building-one-30da3e697fee?source=rss----ea0b714f83a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/30da3e697fee</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[social-media]]></category>
            <dc:creator><![CDATA[Brad Dunn]]></dc:creator>
            <pubDate>Sat, 05 Jun 2021 06:09:31 GMT</pubDate>
            <atom:updated>2021-06-05T06:11:28.389Z</atom:updated>
            <content:encoded><![CDATA[<h3>The world needed a distraction-free messaging platform — so we started building one</h3><p>For those of you who have seen the Netflix documentary, <a href="https://www.netflix.com/title/81254224">The Social Dilemma</a>; my words here will mean something. I work for <a href="http://whispir.com/">Whispir</a> (ASX:WSP), a messaging platform that’s used for all kinds of things, but in essence, we send messages, under certain conditions — If <em>this </em>happens, send <em>that </em>message. It’s used for sending critical, life-saving messages that navigate people away from live bushfires, to sending COVID-19 updates via SMS, which many of you will <a href="https://www.itnews.com.au/news/victoria-ramps-up-covid-19-contact-tracing-using-whispir-539850">have seen already.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M-dtRmsSrmSmAFX8" /></figure><p>I started as the Chief Product Officer here less than a year ago because I saw an opportunity to do some good. Our CEO Jeromy had a passionate vision to really engage humanity, and it was an earnest cause I thought I could lean into. Once I found my feet, the team and I <a href="https://www.whispir.com.au/blog/building-the-worlds-best-communications-intelligence-platform">crafted a totally new 5 year product vision</a> for Whispir, based on a concept known as a <a href="https://medium.com/@jesterhoax/finding-a-blue-ocean-10b0b8c95d4b"><em>Blue Ocean Strategy</em></a><em>, </em>putting us on a path to becoming a <strong>communications intelligence company</strong>. To reach that goal, and in service of our mission to really<em> </em>change the way the world communicates, I knew we needed to hire some smart people. <a href="https://www.whispir.com.au/blog/new-leadership-appointments-to-accelerate-growth-strategy-1">So we did.</a></p><p>I reached out to someone I knew and respected, <a href="https://twitter.com/fionascottym?lang=en">Fiona Milne</a>, to seek her counsel on our strategy. I showed her the plan and soon after, <a href="https://www.whispir.com/blog/new-leadership-appointments-to-accelerate-growth-strategy">Matt Lambie</a>, our new CTO and I asked her to join Whispir as our <a href="https://www.whispir.com/blog/astrophysicist-and-mathematician-appointed-as-whispirs-new-head-of-ai-and-data">Head of AI &amp; Data</a> and lay the groundwork for a very ambitious plan.</p><p>I also knew that if we <em>really</em> wanted to build a great company, we had to create the kind of company people didn’t just want to work <em>for</em>, but create the kind of place people wanted to be <em>from. </em>To do that,<em> </em>we would have to solve problems our competition couldn’t. That’s what gets people up everyday. Solving hard problems that make a difference in the world around them.</p><p>Fiona and I talked about tackling one of the greatest challenges in communications today, and it is a dark and malevolent problem— messaging companies are mostly predatory towards the public, and it’s lead to everyone being totally addicted and distracted by their phones.</p><p>We thought that was worth fixing.</p><p>I told our story to investors and the general public (<a href="https://www.whispir.com.au/blog/building-the-worlds-best-communications-intelligence-platform"><em>Which you can watch if you like</em></a>), stating that I thought this was a huge problem and one that, if we could solve it, would not just help us grow and assist our customers, but allow us to solve a huge societal problem that was starting to keep me up at night.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pRkf_t1UHduXneZytcHoUg.png" /><figcaption>Whispir plans to become the leading communications intelligence company within 5 years</figcaption></figure><h4><strong>The tide is turning</strong></h4><p>A few months back,<a href="https://medium.com/@jesterhoax/without-a-phone-for-30-days-65ccbdfd63c3"> I wrote a story about giving up my phone for 30 days.</a> It was one of the most rewarding things I’ve done and the experiment showed me how deep the hooks go. I quickly learned that liberating myself from my device occasionally appears to reboot the brain in the most beautiful way possible.</p><p>To call this a movement is premature, but something <em>is</em> going on. The <a href="https://www.netflix.com/title/81254224">Netflix documentary</a> comes ahead of the US election and people are acutely aware of how much influence technology companies can have on real world events, all driven, at least in part, by what messages arrive to us on our phones and which ones we pay attention to. Messaging companies have a responsibility to do better, and Whispir, I assure you, has decided to make this a priority moving forward.</p><p><a href="https://en.wikipedia.org/wiki/Cathy_O%27Neil">Cathy O’Neil</a>, the author and data scientist who also appears in the Netflix documentary discusses towards the back of her book, <a href="https://www.amazon.com.au/Weapons-Math-Destruction-Increases-Inequality-ebook/dp/B01LDFCP0S/ref=sr_1_1?crid=2834WKAGYZQ42&amp;dchild=1&amp;keywords=weapons+of+math+destruction&amp;qid=1599877270&amp;s=digital-text&amp;sprefix=Weapons+of+math%2Cdigital-text%2C348&amp;sr=1-1">Weapons of Math Destruction</a>, a corrective idea for those who build the machines that run our lives. She encourages data scientists to embody a kind of Hippocratic oath, similar to doctors, that guides us in building algorithms that do not discriminate, that does not destroy, that do no harm. Fiona’s team is writing such an oath today at Whispir.</p><p>It is perhaps a sobering moment in time to realize that Nir Eyal’s book <a href="https://www.amazon.com.au/Hooked-How-Build-Habit-Forming-Products-ebook/dp/B00NW01MKM">Hooked</a>, often used as a practical guide on how to build habit-forming tech products was followed up by a sequel called <a href="https://www.amazon.com.au/Indistractable-Control-Your-Attention-Choose-ebook/dp/B07QCC61Y3/ref=sr_1_1?dchild=1&amp;qid=1599874952&amp;refinements=p_27%3ANir+Eyal&amp;s=digital-text&amp;sr=1-1&amp;text=Nir+Eyal">Indistractable</a>, a book on how to undo the damage the first book may have inflicted. I am not sure how responsible Eyal feels, or that he should, but his first book really showed most of us how to build behavioral economics and psychology into software, and it is unfair to cite it as the only contributing factor, but its publication and success do speak to the industries obsession with engaging users and it’s passion for using hard science to do it. It feels like those of us who work at the bleeding edge of this stuff are fast becoming both arsonist and the fire-fighter.</p><p>When I arrived at Whispir and looked at the competitive landscape, what worried me most was the existing products on market are geared towards messaging the public about things they don’t need or want, and customers have no intelligent way of helping them solve this problem without impacting their bottom line. Customers lack the tools to really understand how people engage with messages (or if they will at all) and so are left in situations where their activities are focused on building lists, blasting content out, and hoping for the best.</p><p>The fact the industry tolerates engagement rates so low says a lot about how we respect those we are talking to. To see 2% open rates shows most of the industry is fine with abusing 98% of the public with messages they never wanted in the first place.</p><p>Most messages that organizations send are, by the numbers, a waste of time. They distract us from our purpose in life, they distract us from our families and after watching <a href="https://www.netflix.com/title/81254224">The Social Dilemma on Netflix</a>, I realized the problem was vastly worse than I was willing to admit. And it’s time we really started to talk about this more openly as an industry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tBRyHhsyUsiBqbfSr7_kSA.png" /></figure><h3>Distraction-free messaging</h3><p>Our new direction at Whispir aims to deliver on three promises, one of which is this idea of <strong>distraction-free messaging</strong>. The concept is simple. If you send a message through Whispir, we want to ensure that you’re encouraged and coached only to send messages to those who really need and want the particular content, reducing down the noise for the public and getting you a much better return on investment per message.</p><p>To make it a bit more real, think along these lines. Let’s say you’re a small software company getting started that doesn’t want to spend a lot of money messaging prospects. With Whispir, we’re building a way to predict which recipients inside your distribution list have a high probability of opening this message <em>before </em>you send it, allowing you to really dial in the effectiveness of your messaging campaigns and reducing waste.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RQgTCGtaxNKpvQDo" /></figure><p><em>How</em> we do this is where the magic happens, and where Fiona’s team fits into the story. It’s also why we’ve started hiring roles from lateral disciplines, physics, and neuroscience to name names. Predicting the future is no easy task, but as I said, if you want to solve hard problems, you need smart people, or at least ones that can do complex math.</p><p>As the product comes to life (which is currently in the beta stage and referred to as Whispir Workflows - you can <a href="https://www.whispir.com.au/workflows"><strong>try it for free if you like</strong></a>) the goal is to perform some of the following tasks.</p><h4>Neurologically suitable message layouts</h4><p>Our messages team is working on a way customers can layout message designs that are suitable for people that grew up speaking different languages other than English. Studies show that when people were raised speaking different languages as children, whereby the direction of writing follows a specific orientation if the message you show them is written the counterintuitive way to their native language, the probability of them absorbing this message goes down.</p><p>The science behind this was covered in-depth during <a href="https://www.preposterousuniverse.com/podcast/2020/03/23/89-lera-boroditsky-on-language-thought-space-and-time/">a recent podcast</a> between Caltech Physicist, Sean Carroll and Lera Boroditsky, a PH.D in cognitive psychology at Stanford University. Boroditsky talks to a good example of this research as it relates to people who read from right to left and how it alters what one expects from a message.</p><p>When we read from right to left, like those who read Arabic, we most likely anticipate events that happen <em>before</em> to appear on the right, and what happens <em>after</em> on the left. If you picture the following phrase,</p><blockquote>“Bob hands Alice a bunch of flowers,”</blockquote><p>people who read right to left will visualize Bob on the right with a much higher probability. If you lay this message out in <em>reverse</em> — you have a problem and less of the message is absorbed.</p><p>By being able to detect the preferred language of a recipient in our new intelligent message designer, we can ensure the messages we send out are arranged in the most appropriate way for the end-user. The goal is to show our customers <em>how</em> to design messages that are more appropriate to the audience and if the content has a low probability of landing well, help remove those users from the campaign so we don’t unnecessarily bother them, or even better, customize the message for each type of recipient.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-QblH1FpoM-J0JBy" /></figure><h4>Paths that work for the user</h4><p>Another concept we talk about is called <em>Dynamic Paths</em>. This is the idea that effective communication requires we use channels that work for the end-user. We all have different preferences. Some of us love WhatsApp, some love email and others only want to get messages via Telegram or Signal, apps that are becoming more popular with those who value a greater level of control over their privacy and personal information.</p><p>The dynamic path functionality is designed to predict which path is going to work for the end customer before the message goes out. From a functionality point of view, imagine you’re a Whispir customer and you log into the platform. Effort-wise, we just want you to design the message you want to send, then leave the rest up to us. We’ll work out the right channel, the right time, and the right layout arrangement of the message, all designed to ensure we’re not distracting users unnecessarily with content they don’t need.</p><p>This means 20% of the messages might go via WhatsApp, but 15% might go via SMS, and we will send these messages at times that work for the end recipient.</p><h4>Greater controls for the user</h4><p>Finally, we want to put much more control in the user&#39;s hands. Right now, if you’re on some vendor&#39;s distribution list, you’re caught in the net. You have very little control over what you want to see and how often you want to be communicated with.</p><p>If you click ‘manage notification settings’ on any messaging platform, the options are all tipped in the casino&#39;s favor. ‘<em>I want no marketing messages’</em> you might say, but what <em>kind </em>of messages are we talking about? And when you try unsubscribing from these lists, some companies use dark patterns, a technique in User Experience aimed at confusing you into not really knowing if you’ve unsubscribed or not. The fact these patterns exist speaks a lot to the intent of the platforms.</p><p>At Whispir, we aim to give end-users vastly more control by allowing them to not just update things like how often they want to be contacted or what kind of messages they want to see but give them vastly more specific control that helps us learn which messages they don’t want to see again.</p><p>They’ll be able to set things like what times of the day they are with their families, or even what kind of topics they have no interest in hearing about.</p><p>We’ll then use these preferences to inform our algorithms with the aim we can greatly reduce down the unnecessary noise that is flying into the end-users inbox, giving them a distraction-free experience.</p><blockquote>If you want to provide feedback or have questions about this article, <a href="https://twitter.com/jesterhoax">please reach out via twitter.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30da3e697fee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/whispir/the-world-needed-a-distraction-free-messaging-platform-so-we-started-building-one-30da3e697fee">The world needed a distraction free messaging platform — so we started building one</a> was originally published in <a href="https://medium.com/whispir">Whispir</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>