<?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 The 6Q Team on Medium]]></title>
        <description><![CDATA[Stories by The 6Q Team on Medium]]></description>
        <link>https://medium.com/@team6Q?source=rss-b5150d64421e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Sn31VVsKGP5hdLz1.png</url>
            <title>Stories by The 6Q Team on Medium</title>
            <link>https://medium.com/@team6Q?source=rss-b5150d64421e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 10:01:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@team6Q/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[Top 50 Company Culture Articles on Medium by Popularity]]></title>
            <link>https://medium.com/@team6Q/top-50-company-culture-articles-on-medium-by-popularity-75b96dde9753?source=rss-b5150d64421e------2</link>
            <guid isPermaLink="false">https://medium.com/p/75b96dde9753</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[employee-engagement]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[company-culture]]></category>
            <dc:creator><![CDATA[The 6Q Team]]></dc:creator>
            <pubDate>Tue, 03 Jul 2018 08:02:04 GMT</pubDate>
            <atom:updated>2018-07-03T08:30:04.853Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r-pfcMOvcQr4H8sjAw47wQ.png" /></figure><p>As a team focussed on building positive company cultures, we’re naturally obsessed with reading other perspectives on the topic.</p><p>Our favourite blog platform is Medium, so we couldn’t resist running some tools and creating a list of the top 50 Medium posts that cover company culture, ranked by total social shares.</p><blockquote>Have a favourite article in this list? Highlight it or leave a note — we’re keen for your feedback!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/214/1*MwMV7uwWVPMIz87JMAfDHQ.jpeg" /></figure><h3>Top 50 articles by social popularity</h3><p><a href="https://medium.com/s/company-culture/breaking-bad-why-good-people-become-evil-bosses-6be7a25835ca">Why Good People Become Bad Bosses — Your Company Culture Is Who You Hire, Fire, and Promote</a><br><em>(1840 shares, 2,370 words)</em></p><p><a href="https://medium.com/@invoker/how-2-000-random-coffee-dates-changed-our-company-culture-1e417b2bad55">How 2,000+ random coffee dates changed our company culture</a><br><em>(1720 shares, 773 words)</em></p><p><a href="https://medium.com/s/company-culture/your-company-culture-is-who-you-hire-fire-promote-part-2-anatomy-of-an-asshole-dba4f801b9f5">Anatomy of a Workplace Jerk — Your Company Culture Is Who You Hire, Fire, and Promote</a><br><em>(1560 shares, 2,228 words)</em></p><p><a href="https://medium.com/s/company-culture/your-companys-culture-is-who-you-hire-fire-and-promote-c69f84902983">Your Company Culture is Who You Hire, Fire, and Promote</a><br><em>(1530 shares, 2,678 words)</em></p><p><a href="https://medium.com/nestle-usa/company-culture-doesn-t-happen-inside-an-office-building-f59e2b81898e"><em>‘</em>Company Culture’ Doesn’t Happen Inside an Office Building</a> <br><em>(950 shares, 804 words)</em></p><p><a href="https://medium.com/initialcommit/why-company-culture-makes-or-breaks-remote-work-59c257ae4673">Why company culture makes or breaks remote work — initial commit</a><br><em>(940 shares, 1,550 words)</em></p><p><a href="https://medium.com/@admios/creating-a-healthy-company-culture-614483e6155f">Creating a Healthy Company Culture — Admios</a><br><em>(690 shares, 907 words)</em></p><p><a href="https://medium.com/avocado-culture/what-if-you-could-see-your-company-culture-quantified-8e07245320c7">What if you could see your Company Culture Quantified?</a><br><em>(650 shares, 1,046 words)</em></p><p><a href="https://medium.com/catena-media-rnd/company-culture-the-seed-that-sows-success-74d91708db4d">Company Culture — The Seed that Sows Success — Catena Media RnD</a><br><em>(470 shares, 1,126 words)</em></p><p><a href="https://medium.com/@katieaburke16/10-tactical-ways-to-build-a-company-culture-your-employees-love-793e503f53a1">10 Tactical Ways to Build a Company Culture Your Employees Love</a><br><em>(460 shares, 2,910 words)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/214/1*i8Z2A_cSgubAT_VA8MrUwA.jpeg" /></figure><p><a href="https://medium.com/swlh/the-very-best-company-culture-decks-on-the-web-5a3de60c0bb9">The very best company culture decks on the web — The Startup</a><br><em>(460 shares, 819 words)</em></p><p><a href="https://medium.com/@conductal/three-layers-to-design-your-company-culture-7f0a436810de">Three Layers to Design Your Company Culture — Daniel Ospina</a><br><em>(340 shares, 1,161 words)</em></p><p><a href="https://medium.com/high-alpha/five-aspects-of-a-great-company-culture-95ccf1630c0">Five Aspects of a Great Company Culture — High Alpha</a><br><em>(330 shares, 1,147 words)</em></p><p><a href="https://medium.com/iglu-thailand/company-power-dynamic-matters-more-than-company-culture-3a82d793bc2f">Company power dynamic matters more than company culture</a> <br><em>(330 shares, 1,005 words)</em></p><p><a href="https://medium.com/the-mission/how-leaders-can-build-or-destroy-your-startup-company-culture-32d2037b8d66">How Leaders Can Build or Destroy Your Startup Company Culture</a> <br><em>(320 shares, 821 words)</em></p><p><a href="https://medium.com/@peerfit/how-to-grow-company-culture-as-a-startup-b294ab5baedd">How to Grow Company Culture as a Startup — Peerfit</a><br><em>(260 shares, 1,505 words)</em></p><p><a href="https://medium.com/@peerfit/treating-company-culture-like-business-3-goals-for-2018-8e483fecd7a4">Treating Company Culture Like Business: 3 Goals for 2018</a> <br><em>(220 shares, 906 words)</em></p><p><a href="https://medium.com/maptio/build-a-company-culture-of-responsibility-and-focus-without-traditional-management-hierarchy-2d2d2981262f">Build a company culture of responsibility and focus without traditional management hierarchy</a> <br><em>(210 shares, 2,004 words)</em></p><p><a href="https://medium.com/swlh/7-things-i-learned-about-company-culture-from-working-at-a-rapid-growth-startup-3cf27ae2b5e3">7 Things I Learned About Company Culture from Working at a Rapid-Growth Startup</a> <br><em>(210 shares, 1,344 words)</em></p><p><a href="https://medium.com/@nabila_farhat/why-company-culture-should-matter-to-you-6f413a274544">Why should company culture matter to you? — Nabila Farhat</a><br><em>(200 shares, 820 words)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/214/1*3nG_HEgC1zss4os6FgJo1w.jpeg" /></figure><p><a href="https://medium.com/marketing-and-entrepreneurship/how-leadership-can-affect-your-startup-company-culture-54242ee37128">How Leadership Can Affect Your Startup Company Culture</a> <br><em>(200 shares, 835 words)</em></p><p><a href="https://medium.com/pymetrics/5-habits-any-employee-can-develop-to-scale-company-culture-86919fe231f2">5 habits any employee can develop to scale company culture</a><br><em>(190 shares, 1,316 words)</em></p><p><a href="https://medium.com/shareddone/your-company-culture-is-broken-fix-it-ddc1bec6c682">Your company culture is broken. Fix it. — shareddone</a><br><em>(170 shares, 653 words)</em></p><p><a href="https://medium.com/swlh/what-i-would-do-if-i-ran-the-zoo-5-ways-to-create-positive-company-culture-f94efa43b80a">5 Ways to Create Positive Company Culture in Tech — The Startup</a><br><em>(170 shares, 1,955 words)</em></p><p><a href="https://medium.com/@craigjanssen/7-things-i-learned-about-company-culture-from-someone-who-left-ours-406ede1d83d7">7 things I learned about company culture from someone who left ours</a> <br><em>(160 shares, 1,159 words)</em></p><p><a href="https://medium.com/@nmsanchez/are-your-one-on-ones-helping-or-hurting-your-company-culture-55ea52781e2d">Are your one-on-ones helping or hurting your company culture?</a> <br><em>(160 shares, 617 words)</em></p><p><a href="https://medium.com/@paulmusters/rtl-news-article-great-company-culture-is-crucial-to-success-c9c58c1ca255">Company culture is exactly what you have left once you remove the fancy office</a> <br><em>(160 shares, 694 words)</em></p><p><a href="https://medium.com/@susanjcoaching/how-do-we-build-on-company-culture-ceb0cb328270">How To Build on Company Culture? — Susan J Hilger</a><br><em>(150 shares, 305 words)</em></p><p><a href="https://medium.com/fluxx-studio-notes/what-we-learned-about-company-culture-by-running-a-startup-lab-cc7b6b18ea8c">What we learned about company culture by running a startup lab</a> <br><em>(150 shares, 1,884 words)</em></p><p><a href="https://medium.com/@stingsthlm/what-your-company-culture-is-doing-for-you-fbb25fadfd33">What your company culture is doing for you? — Sting</a><br><em>(130 shares, 1,407 words)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/214/1*bj3xDgS0IYcQhgDCQrjpEA.jpeg" /></figure><p><a href="https://medium.com/costanoa-ventures/how-to-keep-company-culture-healthy-when-youre-growing-100-y-y-11591ebc3fb5">How to keep company culture healthy when you’re growing 100% Y/Y</a> <br><em>(130 shares, 856 words)</em></p><p><a href="https://medium.com/habits-are-your-destiny/6-attributes-of-a-future-proof-company-culture-5f7bad7ef410">6 Attributes of a Future Proof Company Culture — Habits are Your Destiny</a><br><em>(130 shares, 1,842 words)</em></p><p><a href="https://medium.com/@Mari.Hopkins/company-culture-4-things-you-can-learn-from-richard-sheridan-and-menlo-innovations-to-promote-and-ae0e53eff924">Company Culture: 4 Things You Can Learn From Richard Sheridan and Menlo Innovations to Promote and…</a> <br><em>(120 shares, 1,615 words)</em></p><p><a href="https://medium.com/culture-as-a-product/lessons-learned-about-shaping-company-culture-at-realtimeboard-8102920a63bd">Lessons learned about shaping company culture at RealtimeBoard</a> <br><em>(120 shares, 1,823 words)</em></p><p><a href="https://medium.com/the-mission/built-not-bought-25-examples-of-great-company-culture-9b2d1fa9ee31">Built, Not Bought: 25 Examples Of Great Company Culture</a><br><em>(120 shares, 3,794 words)</em></p><p><a href="https://medium.com/zalando-design/as-a-product-designer-one-of-the-skills-we-have-to-have-is-the-ability-to-observe-the-environment-ea03216c0217">Design and Company Culture — Zalando Design</a><br><em>(120 shares, 942 words)</em></p><p><a href="https://medium.com/@lfrodriguesit/why-having-real-values-is-essential-for-a-thriving-company-culture-be613064c8b1">Why having real values is essential for a thriving company culture</a> <br><em>(100 shares, 1,346 words)</em></p><p><a href="https://medium.com/@standardoftrust/designing-a-company-culture-of-meaning-675331fa68df">Designing A Company Culture Of Meaning — Rob Peters</a><br><em>(90 shares, 1,171 words)</em></p><p><a href="https://medium.com/startup-grind/3-ways-to-improve-your-company-culture-today-a-chat-with-the-co-founder-of-15five-37544af36b0b">3 Ways to Improve Your Company Culture Today ~ A Chat with the Co-Founder of 15Five</a> <br><em>(80 shares, 1,007 words)</em></p><p><a href="https://medium.com/@iammarcthomas/these-5-factors-are-the-indicators-of-healthy-company-culture-d74b538da999">These 5 factors are the indicators of healthy company culture</a> <br><em>(70 shares, 1,754 words)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/214/1*qahZQqytC5b5I2d-wZdE5A.jpeg" /></figure><blockquote>It’s tempting to think that, when you’re doing work you love and you’re working for yourself, you don’t need to worry about your working environment.</blockquote><p><a href="https://medium.com/help-yourself/no-matter-how-big-or-small-your-business-is-company-culture-matters-ee753ce8bac5">No Matter How Big (Or Small) Your Business Is: Company Culture Matters</a> <em>(70 shares, 2,039 words)</em></p><p><a href="https://medium.com/saas-revolution/how-michael-litt-adjusted-company-culture-while-keeping-core-values-d0a7ad6ea60d">How Michael Litt adjusted company culture while keeping core values</a> <br><em>(70 shares, 2,179 words)</em></p><p><a href="https://medium.com/swlh/why-company-culture-is-an-integral-part-of-successful-startups-today-df89a7dfa8bb">Why Company Culture is an Integral Part of Successful Startups Today</a> <br><em>(70 shares, 653 words)</em></p><p><a href="https://medium.com/beyond/company-culture-its-in-the-little-things-6a4663811b1c">Company culture: it’s in the little things — Beyond</a><br><em>(60 shares, 1,165 words)</em></p><p><a href="https://medium.com/swlh/two-sweet-spots-for-when-startups-should-implement-company-culture-84dc51aeba11">Two sweet spots for when startups should implement company culture</a> <br><em>(60 shares, 497 words)</em></p><p><a href="https://medium.com/@debng/i-want-your-job-not-your-culture-e8e8653e4c1">I’m Too Old for “Company Culture” — Deborah Ng</a><br><em>(50 shares, 821 words)</em></p><p><a href="https://medium.com/@samarbirwadker/if-you-want-a-successful-company-culture-dont-copy-someone-else-s-385761eb8031">If You Want a Successful Company Culture, Don’t Copy Someone Else’s</a><br><em>(50 shares, 1,067 words)</em></p><p><a href="https://medium.com/@Zoe_Guiraudon/what-do-i-look-for-in-a-company-culture-e191b56178c0">What do I look for in a company culture? — Zoé</a><br><em>(50 shares, 983 words)</em></p><p><a href="https://medium.com/light-creative/active-support-a-framework-for-strengthening-our-culture-8afd0462391a">Active Support: strengthening our company culture — Light Creative</a><br><em>(50 shares, 1,144 words)</em></p><p><a href="https://medium.com/taking-note/podcast-taking-note-of-company-culture-with-jess-lee-ff6190d7d64e">Podcast: Taking Note of Company Culture with Jess Lee</a> <br><em>(50 shares, 3,888 words)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/214/1*K3cKfAz3rAh7NbEWJh4wvw.jpeg" /></figure><h4>Crunching the numbers</h4><p>These 50 articles equal a <strong>whopping 69,335 words in total</strong>, or 1,387 words per article on average. According to Wikipedia, a novel is <a href="https://en.wikipedia.org/wiki/Word_count#In_fiction">typically over 40,000 words</a>.</p><p>There were <strong>a total of 16,990 social shares</strong> (to date), which works out to an average of 340 shares per article.</p><h4>A quick favour?</h4><p>If you found this research and links interesting, we’d appreciate a clap or two, just click the icon below, thanks!</p><p>Also, if you want to know our thoughts on creating a positive company culture, we encourage you to take a look <a href="https://inside.6q.io/">at our own blog</a>. ;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75b96dde9753" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Our Book: Creating a Company Culture that Rocks!]]></title>
            <link>https://medium.com/@team6Q/announcing-our-book-creating-a-company-culture-that-rocks-1df8d5a1c890?source=rss-b5150d64421e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1df8d5a1c890</guid>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[The 6Q Team]]></dc:creator>
            <pubDate>Tue, 15 Nov 2016 07:53:47 GMT</pubDate>
            <atom:updated>2017-03-07T06:22:57.077Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*m542HJXEb-o1dqYD6xnfpA.png" /></figure><h4>I’m pleased to announce that we’ve finished writing our first ebook, Creating a Company Culture that Rocks! and have just released it to the world.</h4><p>After many hours of writing, editing, designing and preparing, we are excited to say that our first ever book, available for free as a PDF, is now available for downloading <a href="http://www.startupculturebook.com/">right here on the book’s own website</a>.</p><p>This 107 page book, covers everything that a startup or established business needs to know about creating a great company culture within their team.</p><p>Featuring quotes from the founders of some of the world’s great startups, such as Twitter, Buffer, Moz, 500px and more, we cover the topic across 14 chapters, including how to create company values, how to hire for cultural fit and employee retention strategies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/1*kbFHRwx9KpnAMZNxmz3pBA.png" /></figure><p><em>Creating a Company Culture that Rocks!</em> Book spreads</p><p>We asked two fellow startup founders to give us a review of the preview book. Justin Davies, Co-Founder of Prezentt, said</p><blockquote><em>Once again, Miles cracks it with a ripping, clear and simply expressed book that gets to the heart of what’s important. Do yourself a favour, read it and implement it.</em></blockquote><p>Then there was our good friend, Todd Sainsbury from Smartbeat, who stated;</p><blockquote><em>Confucius says ‘Choose a job you love, and you will never have to work a day in your life.’ Company culture is a big part of making each working day ROCK &amp; Miles has some solid gold riffs in this easy to read number.</em></blockquote><p>In our aim to improve the team morale and culture of teams across the globe, we are giving the book away absolutely free as a PDF. That’s right; zero cost to you, other than providing us an email address and signing up to our monthly newsletter (which you can, of course, unsubscribe from at any time).</p><p>Get your own copy of <a href="http://www.startupculturebook.com/">Creating a Company Culture that Rocks!</a> now. Enjoy the reading!</p><p>Tags:<a href="https://inside.6q.io/tags/creating-a-company-culture/">Creating a Company Culture</a> <a href="https://inside.6q.io/tags/startup-culture-book/">startup culture book</a></p><p><em>Originally published at </em><a href="https://inside.6q.io/new-book-creating-company-culture-rocks/"><em>inside.6q.io</em></a><em> on November 15, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1df8d5a1c890" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Startup Model Success: Scratching Your Own Itch]]></title>
            <link>https://medium.com/@team6Q/startup-model-success-scratching-your-own-itch-e50d546f5f07?source=rss-b5150d64421e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e50d546f5f07</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[The 6Q Team]]></dc:creator>
            <pubDate>Thu, 08 Sep 2016 09:12:17 GMT</pubDate>
            <atom:updated>2017-06-21T03:33:01.274Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*LTXKfc5nWyNgAzly8n1Dig.png" /></figure><h4>There are benefits and pitfalls to the startup model of ‘scratching your own itch’. In this, I talk about why 6Q was born from scratching our own itch, and why we’re happy that we did take the risk it was only ours (and how we actually avoided that).</h4><p>The startup model of ‘scratching your own itch’ is simple; find a problem you have internally at your current business or employer, and find a way to solve it. In my mind though, the difference between success and failure, is the ability to find others with the same itch.</p><p>If you don’t read any further, remember this takeaway: the pain you set to solve shouldn’t be yours, otherwise you risk building a product just for you.</p><h3>Quick thoughts behind 6Q</h3><p>Before 6Q appeared, I had 12 people working in the same physical office, which I had face to face meetings with for 5 minute apiece once a week. Doing the math that’s around an hour of my time.</p><blockquote><em>The pain you set to solve shouldn’t be yours, otherwise you risk building a product just for you.<br> — Miles Burke, 6Q</em></blockquote><p>The problem I had was I often found myself asking the same questions, and taking notes, but not measuring these responses week on week, to see if they were improving, staying the same or getting worse.</p><p>I would ask a question such as ‘Are you feeling productive this week?’, however I didn’t have the data be able to compare their responses to historical answers.</p><p>The idea of these face to face meetings was well received by other managers with far bigger teams that I spoke with. They thought it was a great idea, however at 100 people, the idea didn’t practically scale for a CEO or Managing Director to be sitting in these 5 minute meetings for hours on end.</p><p>That works out to 100 x 5 minute meetings, or roughly 9 hours a week spent asking similar questions to their team members.</p><p>Then there were others who had remote teams; how do they do face to face meetings? They don’t; they use free for all text, voice or video to ask these questions. Same problems existed though; both how do you measure responses over time and reduce the time investment for managers <em>(see our article, </em><a href="http://inside.6q.io/how-to-grow-a-positive-company-culture-with-a-remote-team/"><em>How to Grow a Positive Company Culture with a Remote Team</em></a><em>)</em>.</p><p>So that’s a simple explanation why our solution, 6Q, was born.</p><p>Our product allows me as the Managing Director, to ask my team six questions every week, and then elaborate on their answers further in our five minute face to face sessions, which we still undertake. Using 6Q allows me to review the responses as visual trends over time, which is extremely valuable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TpFgAeprB55HwGLulhfGjQ.jpeg" /></figure><h3>Pros of scratching your own itch</h3><p>The startup model of solving a problem you have experienced yourself isn’t actually limited to startups. It has been something that entrepreneurs have done for centuries. The benefits of following the ‘scratch your own itch’ method are great;</p><p><strong>You have a deep understanding of your target customers pain</strong></p><p>Having the problem yourself means that you have a very deep understanding of the pain and what it does to affect you or your business.</p><p><strong>You know the benefits</strong></p><p>You know that your solution actually works, because you inevitably use your own product. This means you have a great understanding and appreciation of the benefits that your solution provides.</p><p><strong>You are a true believer in your product</strong></p><p>Having the problem yourself, and working on what you consider the absolutely best solution means that you have a deep belief in your solution (or at least you should). This motivation and drive can be infectious to those around you.</p><p><strong>You likely have a better understanding of the market</strong></p><p>Being in the same market yourself, it is very likely you understand your market position, and those of your competitors, than an outsider.</p><blockquote><em>The best startups generally come from somebody needing to scratch an itch.<br> — Michael Arrington, TechCrunch.</em></blockquote><p>There are loads of examples of successful companies that started based on this startup model. For example, the very successful <a href="http://www.airbnb.com/">Airbnb</a> started this way. In an interview with The Telegraph, titled <a href="http://www.telegraph.co.uk/technology/news/9525267/Airbnb-The-story-behind-the-1.3bn-room-letting-website.html">Airbnb: The story behind the $1.3bn room-letting website</a> they stated;</p><p><em>“Airbnb started in 2007 when Joe Gebbia and Brian Chesky, then both 27, who had met five years earlier at Rhode Island School of Design, were struggling to pay their rent.</em></p><p><em>There was a design conference coming to San Francisco and the city’s hotels were fully booked, so they came up with the idea of renting out three airbeds on their living-room floor and cooking their guests breakfast.</em></p><p><em>The next day they created a website; six days later they had a 30-year-old Indian man, a 35-year-old woman from Boston and a 45-year-old father of four from Utah sleeping on their floor. They charged $80 each a night.”</em></p><p>Other examples of the scratch your own itch startup model, include the story of Zach Sims, Founder of the popular learning site, CodeAcademy. In this article, <a href="http://www.businessinsider.com.au/startup-lessons--zach-sims-codecademy-2014-6?r=US&amp;IR=T">9 Startup Lessons From The Founder Of Codecademy</a>, they write;</p><p><em>“Sims got the idea for Codecademy when he tried to learn how to code from books and realised the knowledge never clicked with him. He knew the best way to learn was by working on real projects and building real things. As a result, he integrated this experience into Codecademy, so people could learn by doing.</em></p><p><em>Since Sims himself didn’t know how to program, he was patient zero for the product. He recalls, “If I could learn how to program well from Codecademy, that means a lot of other people could learn from it, too.” Although many of his previous ideas didn’t work out, what was different about Codecademy was that they were building it for Sims.</em></p><p><em>Sims says, “It’s much easier to build for yourself. You know what works and what doesn’t.”</em></p><h3>Cons of scratching your own itch</h3><p>As much as there are some very valid reasons to follow the startup model of uncovering your own issues and solving them, there are also a few reasons not to take this approach. These include</p><p><strong>Being alone with your problem</strong></p><p>You may just assume everyone in your position perceive your pain as an issue; it could be true that they don’t see it the same way as you. The goal of building a product is to sell it to somebody else, not to yourself — make sure there are others just as motivated to fix the same issue.</p><p><strong>Thinking the pain is far larger than it is</strong></p><p>It is very easy for most people to exaggerate the problems they face in their personal or professional lives. Some things can feel absolutely overwhelming until you stand back and assess the literal impacts.</p><p><strong>Being too focussed on yourself</strong></p><p>You could end up being too focussed on yourself; on your own experience and objectives. You could get a sense that you are the only one solving this pain and that your solution is the obvious fit. That doesn’t mean that others with the same issue may feel the same.</p><p><strong>Ignoring the real competition</strong></p><p>Perhaps you’ve seen others trying to solve your problem, yet you personally didn’t adopt them, because they weren’t the right fit for you — this doesn’t naturally mean they aren’t a great fit for others in your predicament.</p><p>I personally found other solutions to the pain we are out to solve (not understanding your team morale or getting enough feedback from employees) that I initially discounted as being inefficient (such as emailing a custom survey out to the team, which can be costly and time intensive, and without <a href="https://www.6q.io/tour/">the great features we have</a>, such as global benchmarking, etc).</p><p>It actually turns out that many people with the pain we are solving actually feel these solutions are fine by them. We just need to ensure we adeuqately explain why we are a better solution than these other methods.</p><p>In this article published by the Harvard Business Review, <a href="https://hbr.org/2014/05/when-scratch-your-own-itch-is-dangerous-advice-for-entrepreneurs">When “Scratch Your Own Itch” Is Dangerous Advice for Entrepreneurs</a>, the writer states;</p><p><em>“But scratching your own itch will lead you astray if you are a high-performance consumer whose problem stems from existing products not performing well enough — in other words, if the itch results from a performance gap.</em></p><p><em>Building a company around a better-performing product means competing head-on with a powerful incumbent that has the information, resources, and motivation to kill your business.”</em></p><p>As stated, it is very important to understand what and who you will be up against before starting your new venture. If it’s just a better version of an existing product, you may find yourself in a very uphill battle, where the stakes can be huge for the incumbent, and they’ll do their best to outspend and outperform and keep their share.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sa1QQVPI2LlJvOx_WJY5xw.jpeg" /></figure><p>Image: 401(K), Flickr</p><h3>Five ways to validate in a short period of time</h3><p>So you’ve found a problem that you or your organisation has, that you feel you can solve. Not only solve, but sell the solution to others in the same situation. The first step to success with this startup model is to understand if there are others with the same problem.</p><p><strong>Weigh up this pain you have</strong></p><p>Is the problem you are considering solving, actually worth solving? As humans, we can often perceive a pain point as being far larger than it actually is. If it is really not as significant as you first thought, ask yourself would you pay for a solution yourself?</p><p>For example, if you could create a $5 solution to the problem, would there be a large enough market to sell these solutions to, or is there a recurring purchase required, so you could sell this $5 solution many times over?</p><p>Maybe this big pain point actually isn’t as large as you first considered?</p><p><strong>Research your potential competitors</strong></p><p>Before you start planning your business out much further, you should spend plenty of time asking yourself ‘How is it currently solved?’ and discovering all the alternative solutions or potential competitors as you can.</p><p>I have found that competitors or alternatives to your solution aren’t naturally obvious either; one of our competitors, for example, could be the simple spreadsheet or email. Whilst we know that our solution is far more effective, it doesn’t mean your market will feel the same way.</p><p><strong>Plan out your solution</strong></p><p>I don’t suggest spending dozens of hours creating a business plan at this point, however I do suggest either completing a lean canvas or creating some form of wireframes/sales material to explain the solution.</p><p>When we began, we had a single page website that explained what we were setting out to do, which collected email addresses. I spoke to a number of those early registrations to flesh out exactly how they imagine solving their pain.</p><p><strong>Speak to potential customers</strong></p><p>Your next step is to demonstrate or explain your suggested solution to as many potential customers as you can find.</p><p>You need to be careful to approach this validation carefully — don’t just explain your solution, explain the problem and ask if they have this issue too. Then ask them if the problem is large enough for them to look at ways to solve it, and if so, what would they like to see in a solution.</p><p><strong>Ask if they would pay for your solution</strong></p><p>Once you’ve successfully validated that others share your pain, and would be open to a solution such as yours, the next step is to ask them if they are interested enough to consider purchasing your solution. This is the true test of validation — its easy to get people to say they would use your product or service, it can be entirely different to get them to agree to hand money over for it.</p><p>If you have managed to get through the above five steps of startup model validation unscathed and still positive, then there is a chance your idea may actually have a chance of success.</p><h3>In Summary</h3><p>So there you have it; some very valid reasons why you should, and why you shouldn’t, build your next business based on solving a problem that you have yourself (also known as ‘scratching your own itch’).</p><p>In creating 6Q, I found the startup model of scratching my own itch worked for me — every situation is vastly different though; your mileage may vary.</p><p>Ensure you do enough pre-planning, solution brainstorming and most importantly, customer validation, before spending much time or money on creating that next big business.</p><p><em>Originally published at </em><a href="https://inside.6q.io/startup-model-success-scratching-your-own-itch/"><em>inside.6q.io</em></a><em> on September 8, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e50d546f5f07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[16 SaaS Tools We Use to Grow Our Startup]]></title>
            <link>https://medium.com/@team6Q/16-saas-tools-we-use-to-grow-our-startup-c024ff6e7871?source=rss-b5150d64421e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c024ff6e7871</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[bootstrapping]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[The 6Q Team]]></dc:creator>
            <pubDate>Wed, 22 Jun 2016 10:01:27 GMT</pubDate>
            <atom:updated>2017-02-03T05:25:38.503Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*QSUFVirrdjO1P2Rde6Of3w.png" /></figure><h4>It’s always fascinating to see what different tools startups use to manage their business or growth. We list 16 products we use to manage our startup, and what we use them for.</h4><p>As a Software as a Service (SaaS) business, we embrace similar SaaS tools and products to help us with the smooth sailing of our business. We may be biased, however studies have shown the benefits of SaaS tools over typical desktop software;</p><p><strong>Lower cost of ownership</strong><br> Because the license is typically monthly or annually, the costs are greatly reduced over a one-time initial payment.</p><p><strong>Quicker access to new features</strong><br> SaaS products are ever evolving. For example, at 6Q, we release new features at a monthly frequency. These aren’t charged at additional rates, and our customers get access to them immediately.</p><p><strong>Faster adoption uptake</strong><br> Because SaaS doesn’t involve the typical software installation process, users in customer environments normally can access them within minutes, not days or weeks.</p><h3>Our 16 Favourite SaaS Products</h3><p>So, with this in mind, here are some of our favourite products that we use to coordinate, communicate and collaborate, in alphabetical order.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/0*738ZDjoxn54jqvhZ.png" /></figure><p><a href="https://buffer.com/"><strong>Buffer</strong></a><br>We can’t go past Buffer for social media scheduling. We love their product, and their company transparency and blog are two of the main reasons we decided to use them.</p><p>Buffer allows us to pre-schedule social media posts across our Twitter, Facebook and LinkedIn presences, which means we can spend more time building our product.</p><p><a href="https://buffer.com/">https://buffer.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*M63gAxTflyCLfqDpQGpuAg.png" /></figure><p><a href="https://calendly.com/"><strong>Calendly</strong></a><strong><br></strong>To coordinate booking into calendars, we use Calendly. We love the simplicity of the booking process that people undertake to make a time with us to chat. It then emails us an alert and we can add these straight to our calendars.</p><p><a href="https://calendly.com/">https://calendly.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*XauNdpWlAWedClbv.png" /></figure><p><a href="https://www.campaignmonitor.com/"><strong>Campaign Monitor</strong></a><br>We’ve been big supporters of Australian email marketing platform, Campaign Monitor since before 6Q was even a vision.</p><p>We use their super easy to use email campaign builder for our monthly email newsletters, and we love supporting fellow Australian innovation.</p><p><a href="https://www.campaignmonitor.com/">https://www.campaignmonitor.com/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/230/0*BMFlSOGs7bIpam6S.png" /></figure><p><a href="https://customer.io/"><strong>Customer.io</strong></a><br>This is a fantastic tool for segmenting and understanding user behaviour. We use customer.io on a daily basis, to see what new customers and trial users we have, as well as to trigger a series of emails, based on user behaviour or segmentation.</p><p>For example, we send a drip series during the trial period, which changes according to what actions users have performed within 6Q, such as adding segments, etc.</p><p><a href="https://customer.io/">https://customer.io</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/301/1*6-Lwt31NSiVGYt-TxPvWeg.png" /></figure><p><a href="https://analytics.google.com/"><strong>Google Analytics</strong></a><br>Who could live without Google Analytics? We watch our analytics regularly, to see what articles are being viewed, and what our audience growth is like.</p><p>We use their goals feature, to monitor conversions to free trials from our main website, landing pages and blog posts.</p><p><a href="https://analytics.google.com/">https://analytics.google.com/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*bRs0PmX5O_CspfWWvTPREw.png" /></figure><p><a href="https://drive.google.com/"><strong>Google Drive</strong></a><br>We share internal documents between the team using Google Drive. Even with the free account, they give you plenty of storage space.</p><p>This way, even if I am on the road, like my recent trip to a conference in Hong Kong, I can still access and collaborate on pertinent files.</p><p><a href="https://drive.google.com/">https://drive.google.com/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*9zrQJNCu1tNKdF1N.png" /></figure><p><a href="https://www.helpscout.net/"><strong>Help Scout</strong></a><br>We use Help Scout for both our knowledge base area, as well as for support ticketing.</p><p>Help Scout allows us to gain insights into what people are searching for in our hosted knowledge base (they call this ‘docs’) and they also give us reports on average response times and other metrics for our support email account.</p><p><a href="https://www.helpscout.net/">https://www.helpscout.net</a></p><h3>homeslice.in</h3><p><a href="http://homeslice.in/"><strong>Homeslice</strong></a><br>It can be tricky when you’re an always connected business, to know the best times to connect with others in different time zones.</p><p>This is where free, browser based Homeslice comes into being. Just add the cities you want to keep an eye on, and it does it all neatly in the browser.</p><p><a href="http://homeslice.in/">http://homeslice.in</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*0hMOZiS8M2x9QvYO.png" /></figure><p><a href="http://www.join.me/"><strong>Join.me</strong></a><br>When we are doing screen sharing during support or sales calls, we rely on join.me.</p><p>Join.me is really easy to set up and get going, and it saves customers having to download large browser plug ins. The quality of screen sharing is great, regardless if it’s to an adjacent city, or across the world.</p><p><a href="http://www.join.me/">http://www.join.me</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*MHLSb-LSA6HJgYDFfrZ8Dg.png" /></figure><p><a href="https://notify.ly/"><strong>Notify</strong></a><br>This is a great way to keep an eye on social media mentions.</p><p>We use Notify to alert us in our Slack team #socialmedia channel, about certain keywords and shares of our content. That way, we can answer any feedback or questions promptly, and know what content is resonating well on social media.</p><p><a href="https://notify.ly/">https://notify.ly</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*8jCgYjDS_YVhGEvhjlvEsg.png" /></figure><p><a href="https://pin.net.au/"><strong>Pin Payments</strong></a><br>For our payment subscriptions handling, we use Australian payment gateway, Pin Payments. They have an office right here in the same city as us, and we’ve been known to socialise with their team.</p><p>They’re a great bunch, and make handling subscriptions with various tiers, easy.</p><p><a href="https://pin.net.au/">https://pin.net.au</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*0ZxvDZDHbiuKw5Mh.png" /></figure><p><a href="http://sendgrid.com/"><strong>Sendgrid</strong></a><br>For email delivery of our must-be-delivered emails, being our survey polls and subsequent reports, we rely on Sendgrid. They send billions of emails for some of the world’s largest brands, so we feel safe in their care.</p><p><a href="http://sendgrid.com/">http://sendgrid.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*S5wVeaJsiSlC6UAc.jpg" /></figure><p><a href="https://www.skype.com/en/"><strong>Skype</strong></a><strong><br></strong>For our internet to landline calls across the globe, we use Skype. Having tried a number of providers, we still feel that Skype gives us the best quality bandwidth for voice calls.</p><p><a href="https://www.skype.com/en/">https://www.skype.com/en/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*kD_Z7UQ3R36-wpfn.png" /></figure><p><a href="https://slack.com/"><strong>Slack</strong></a><br>We use Slack very frequently; more than twice hourly, for internal team communications, as well as automated notifications from tools that we’ve integrated, such as Trello, Helpscout and Notify.</p><p>We even have a Slack ‘bot’ set up for our office Spotify account, so that we can skip and change music without walking over to our music streaming machine (It’s very important, honest).</p><p><a href="https://slack.com/">https://slack.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*egwxXEtJr_yDS-KtMMQ5Ag.png" /></figure><p><a href="https://trello.com/"><strong>Trello</strong></a><br>We are power users of Trello, embracing their kanban system for three main boards, being our internal product road map, the customer facing product road map (read more about that here) and our content marketing planning.</p><p>Everyone in the team uses Trello to refer to prioritisation, planning and what’s being currently worked on, and who these tasks are assigned to. Their checklists are fantastic, and Trello also integrates with Slack to alert us of new cards.</p><p><a href="https://trello.com/">https://trello.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*9DHzt5gQNQQ4q15v-RGiQA.jpeg" /></figure><p><a href="https://wordpress.org/"><strong>WordPress</strong></a><br>The immensely popular open source blogging platform is what powers this very blog you are reading. We use WordPress to post our articles, and we find it super search engine friendly to boot.</p><p><a href="https://wordpress.org/">https://wordpress.org</a></p><p><strong>Bonus tool: 6Q</strong><br>Of course, we’d be hypocrites if we didn’t “dog food” our own product. We use 6Q every week, to see how our team of 12 people are going.</p><p>We have our 6Q set to individual mode, meaning there’s no anonymity, and we change questions frequently to gain additional feedback.</p><p><a href="https://www.6q.io/">https://www.6q.io</a></p><h3>In Summary</h3><p>So there you have it; these are 16 of our main go to SaaS tools that the 6Q team use daily, to grow and manage our business. We’re big believers in supporting other SaaS providers, both small and large, as we continue to grow our product.</p><p>I hope I have introduced you to a few tools that perhaps you haven’t tried, and look forward to hearing your thoughts. Let us know your ‘cannot-live-without’ tools by tweeting <a href="https://twitter.com/team6q">@team6Q</a>.</p><p><em>Originally published at </em><a href="https://inside.6q.io/16-saas-tools-we-use-to-grow-our-startup/"><em>inside.6q.io</em></a><em> on June 22, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c024ff6e7871" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bad Boss Behaviour Made My Startup]]></title>
            <link>https://medium.com/@team6Q/bad-boss-behaviour-made-my-startup-e044a28940c8?source=rss-b5150d64421e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e044a28940c8</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[The 6Q Team]]></dc:creator>
            <pubDate>Wed, 08 Jun 2016 10:43:06 GMT</pubDate>
            <atom:updated>2017-01-31T01:00:30.662Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*mbvraDaB1gVaTT6sWll1zQ.png" /></figure><h4>I would like to personally thank all the bosses I’ve had in my career for leading me to building a great culture in my own company, which subsequently produced 6Q as a result.</h4><p>Let me explain. I’ve been out of school now for 30 years <em>(wow, that makes me feel OLD!)</em>. During my first 16 years, when I was working for other people, I met and worked with some fantastic managers. I also got my fair share of bad boss behaviour.</p><p>When I started my company in 2002, I promised myself that I’d be different. I would learn from all my previous experience as an employee, and treat my employees right. I’ve spent the last 14 years working on being a better boss than some of the others I’ve come across, although I don’t say I’m perfect (far from it!).</p><p>So, what were some of the lessons I walked away with, after 16 years and a number of different jobs in different industries?</p><h3>Managers can be great</h3><p>I have worked in many different roles, with a number of different managers, all of whom had their own unique personality traits. The ones I most resonated with, were the ones who displayed a human side as well, and didn’t display a ‘I’m far better than you’ attitude.</p><p><strong>Displaying beliefs through actions, not words</strong></p><p>Thanks to the manager who used to start his day by doing something typically considered ‘below him’. He would come in, empty office bins, clean the toilets or whatever needed doing. His belief was that we were all a team; important words, and even more important actions.</p><p><strong>Being a mentor as well as a manager</strong></p><p>Thanks to the boss who spent their time often mentoring their employees on being better people, generally. Their displays of kindness and constant push for all of us (including themselves) to be better was a great inspiration.</p><p><strong>Building great lifelong relationships</strong></p><p>Thank you to the managers who I am still friendly with. I have a few on social media as connections, who still communicate with me, and I have others I see socially from time to time, more than 15 years after I worked with them. These lifelong friendships show that we had a mutual good relationship.</p><h3>Managers can also be less than great</h3><p>Managers are human, I get that. I’m human too. I feel we often look up to managers as people who never make mistakes, however we do. If we accept that we’re not infallible, and we explain to those we affect when something does go wrong, it’s far better, and we can sleep soundly at night.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*bfWNQfk-pXHrX6EViqE1ig.jpeg" /><figcaption>Image: <a href="https://www.flickr.com/photos/breatheindigital/">Ryan Hyde</a>, Flickr</figcaption></figure><p>I’ve had a number of managers though, who would never admit to making mistakes. Some of these are pretty colourful too. This motivated me to never be a bad boss.</p><p><strong>The manager who had a sexual relationship with a colleague</strong></p><p>Not only that, he made jokes about it to fellow employees, and wasn’t at all trying to keep it a secret. The fact that he was married, and so was his subordinate wasn’t nice at all. Nor was the promotions of the said employee, when she certainly didn’t deserve it professionally.</p><p><strong>The manager who lost his temper weekly</strong></p><p>Two heart surgeries before the age of 45 years should have told him to relax, but he was wound up tight. Two bad boss situations I witnessed are still clear to me, twenty years later.</p><p>Literally smashing all the employee coffee cups on the concrete at the back of the store, because he was sick of seeing dirty dishes in the sink. He followed up with a rule we had to bring our own cups in, and take them home to wash. The office sink was now officially out of bounds.</p><p>The time he wasn’t happy with the way a junior employee was stacking a milk fridge, and decided to pour milk all over said employee, and throw the empty cartons across the store.</p><p><strong>The boss with no empathy at all</strong></p><p>When my wife became pregnant, I took lunch breaks off once a month to attend the doctors appointments. I was always first to the office, one of the last to leave, and rarely ever took a lunch break (like maybe once a month). I had a doctors appointment at 11am one day, and he explained that it wasn’t good enough to take an hour outside of the ‘lunch hour’. He refused to let me go. I ignored this bad boss, and went anyway.</p><p>When my first child was born, he was upset I wanted a week off. I had booked it two months beforehand, and even offered to work remotely a few hours a day. He was childless himself at the time, as you can imagine. Two years after I left that organisation, he had his first child. He took a month off to be with his new child.</p><p><strong>The annual performance review</strong></p><p>A few bosses had an annual performance review with me. That’s great, however in between, I never heard a thing from them about my performance. I regularly requested even 5 minutes of verbal feedback, and rarely ever got it. To me, not ever giving feedback is a personality trait of a bad boss.</p><h3>Lessons from good and bad bosses</h3><p>These are just a few of the stories I have been a character in. When I started my own business, I promised to work on a number of things, including;</p><ol><li>Always treating employees like humans</li><li>Never asking someone to do something I wasn’t willing to do, myself</li><li>Providing feedback (good or bad) regularly (we do quarterly face to face performance reviews)</li><li>Asking of feedback constantly too, on my management techniques, the business direction, etc</li><li>Empowering the team to feel like they are part of the journey</li></ol><p>6Q is a result of this culture. We built 6Q for ourselves initially, wanting a tool that allows the entire team to give suggestions, to let managers know how they feel about certain topics, and to be inclusive.</p><p>It has been a great tool for me, as a manager, and for the team, to feel like they are being heard and more importantly, for taking action with the feedback.</p><p>If you are keen to read more about how we created 6Q, initially in a one day hackathon, I encourage you to read my previous article, <a href="http://inside.6q.io/the-short-long-history-of-our-start-up/">The short (&amp; long) history of our start-up</a>.</p><h3>In Summary</h3><p>Being a manager is often a thankless job. We need to constantly remind ourselves that we’re not perfect, and look for ways to personally improve.</p><p>The biggest achievement you can have is to create a company culture that is inclusive and a pleasure to work in. Never stop trying to improve your communication, feedback and display your commitment through actions, not just words.</p><p>Work on being a Great Boss, not a Bad Boss.</p><p><em>Originally published at </em><a href="https://inside.6q.io/bad-boss-behaviour-made-startup/"><em>inside.6q.io</em></a><em> on June 8, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e044a28940c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why We Share Our Product Roadmap]]></title>
            <link>https://medium.com/@team6Q/why-we-share-our-product-roadmap-d92362ef44be?source=rss-b5150d64421e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d92362ef44be</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[The 6Q Team]]></dc:creator>
            <pubDate>Fri, 06 May 2016 11:21:11 GMT</pubDate>
            <atom:updated>2017-01-17T01:51:53.537Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*Jp9hmmmAlfPTTbLGZYG93Q.png" /></figure><p>A product roadmap is a powerful method to describe how a product is likely to grow, with planned features, stakeholder input, etc. This helps align the team working on the product, and to set expectations on priorities and timelines.</p><h3>Why do we have a product roadmap?</h3><p>Since starting <a href="https://www.6q.io/">6Q</a>, we’ve been juggling feature requests and bug reports from customers, our own team and other stakeholders. Having a product roadmap is vital to be able to understand what is being worked on next, and what the medium term product direction looks like.</p><p>We use ours to prioritise where time should be spent, and to collect ideas and suggestions.</p><p>We collate feature requests, and add them to a list in Trello, and then assign importance, based on factors such as repeat requests, size of customer, impact on customers, impact on possible benefits to use in sales, and our overall product direction and philosophy.</p><p>These then get moved to lists as we progress these tasks towards becoming part of a future product release. We average a release each week, with some weeks having 3–4 releases, and other releases are larger, and take multiple weeks to progress through testing and QA before being available on our live environment.</p><h3>What are we sharing?</h3><p>We have our internal roadmap, which is full of comments and acronyms and not overly useful for customer consumption. So, we’ve created a more palatable one, which features a subset of features we are working on, or plan to work on. We’ve previously discussed our own internal roadmap and feature planning, in the post <a href="http://inside.6q.io/how-our-start-up-handles-feature-requests/">How our startup handles feature requests</a>.</p><p>The roadmap is filed on <a href="http://www.trello.com/">Trello</a>, a software tool that we use hourly here, and is broken down by three categories, being current, medium term and long term. These terms should be fairly evident.</p><p>Sure, we know that some medium or long term features may change, according to customer validation and direction, however we are willing to take that risk, and keep our customers informed. We believe that our customers will understand our reasoning, and openness in discussions.</p><p>We are also careful to only reveal a few of the key features in such a public way. Whilst we don’t believe in ‘spying on the competition’, we are aware that not everyone in our industry may feel the same way. Rather than reveal a competitive advantage, we prefer to take a quieter approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*4OkR666XdBvxEV-yCWDw-Q.png" /><figcaption>6Q Product Roadmap</figcaption></figure><h3>So, why do we share a product roadmap?</h3><p>For us, we believe that sharing our product roadmap affirms our commitment to transparency with our customers, and shows our promise of customer-first thinking.</p><p>We know that we don’t have all the answers, and as real use of our product continues, in various organisations with different cultural backgrounds and requirements, we are collecting valuable information from both customer requests as well as data collation and interaction tracking.</p><p>Whilst we ‘<a href="https://en.wikipedia.org/wiki/Eating_your_own_dog_food">eat our own dog food</a>’ and use 6Q on our own team of 13 people, we are only a very small team, compared to many of our customers, who have hundreds, if not thousands of employees.</p><p>As a result, we are constantly encouraging customer feedback. Having a product roadmap that we share with our customers helps collect feedback and thoughts on what we have planned, and what the direction of our product is.</p><blockquote><em>Software is a great combination between artistry and engineering.<br> — Bill Gates, Founder of Microsoft</em></blockquote><h3>How do I provide feedback?</h3><p>If you are a free trial or paying customer, we are keen to hear your thoughts. We created 6Q to be useful for you, and without input from our customers, we’d feel we are not scheduling the most optimal of our time.</p><p>We ask that you reach out to us via <a href="/service/mailto:support@6q.io">our support email</a>, so we can track and assign the request or feedback. We get back in touch, personally, to every request, and each request is considered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/839/1*Fs3icdhD7GmotxhhFaxKSg.png" /><figcaption>Feature details card</figcaption></figure><h3>In Summary</h3><p>As a software as a service product, 6Q relies on customers to embrace our product vision and help mature our product and business, through both feedback, referrals and funding. Without customers, we would not be in business, and without their feedback, we would be making assumptions on how other organisations would use our product.</p><p>We believe it is vital for any software developers to be constantly questioning what they are doing, and seeking advice from the stakeholders who matter most; the customers actually using the product.</p><p>We strongly encourage any other startups or software developers to do the same, and share their product roadmap with their customers; it’s an insightful and very valuable process.</p><p><em>Originally published on the 6Q blog, at </em><a href="https://inside.6q.io/share-product-roadmap/"><em>inside.6q.io</em></a><em> on May 6, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d92362ef44be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Simple Secret to Improving your Startup]]></title>
            <link>https://medium.com/@team6Q/the-simple-secret-to-improving-your-startup-37d61d5e37a0?source=rss-b5150d64421e------2</link>
            <guid isPermaLink="false">https://medium.com/p/37d61d5e37a0</guid>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[The 6Q Team]]></dc:creator>
            <pubDate>Tue, 13 Oct 2015 09:35:45 GMT</pubDate>
            <atom:updated>2016-12-20T00:46:07.248Z</atom:updated>
            <content:encoded><![CDATA[<p>It is very easy to become so absorbed and close to your product, you become blind to obvious stumbling blocks or on-boarding issues. Spending half an hour with someone not related in any way to your start-up can uncover areas of weakness you hadn’t even considered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*2yMXZAfP61rAHTjE4PQ7ew.png" /></figure><h4>User testing = the secret to improving your startup.</h4><p>I invited a couple of people who have never used or heard of <a href="http://6q.io/">6Q</a>, nor are professional user testers (most of our prospective customers aren’t either) to give me half an hour of their time to ‘have a look over something I am building’ in exchange for the same in reverse.</p><p>We arranged times over email to meet and then we got into the nitty gritty.</p><p>This is what I briefed them with;</p><p><strong>Imagine you have a team and want to run regular employee pulse surveys with them. I’d like you to sign up to 6Q, add a few questions, maybe add a user and then activate the surveys.</strong></p><p>I also made sure to let them know all thoughts and ideas were valuable; there is no such thing as a wrong answer or dumb question here. I told them to think out loud, and feel free to carry on.</p><p>Speaking of questions, I let them know that I won’t be answering anything they need help with; I want to test what a real person is going to discover — the average web user doesn’t get the founder sitting next to them, guiding them, do they?</p><p>Wow, what amazing feedback I discovered in less than 30 minutes.</p><p>Whilst some of the subjects were less forgiving than others, all of the feedback was incredibly useful; even the smallest of items are worth recording and noting for possible changes down the track.</p><p>I didn’t take anything said personally; being a startup founder means that you accept that everything is a constant learning and revision process, whether it be outreach, growth hacking, on-boarding, customer service, selling or product management.</p><p>The outcome of these informal tests were that I discovered oversights with our interface that I kick myself for not noticing, and explored other areas that I had not even considered to be an issue at all.</p><blockquote><em>I discovered oversights with our interface that I kick myself for not noticing.<br> — Miles Burke, Founder</em></blockquote><p>The best part was they were (mostly) easy to address, and within days we had already jumped on to correcting many of them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lji1OhYzuRGaTSygGl9GdQ.jpeg" /><figcaption>Photo: <a href="https://www.flickr.com/photos/baldiri/">baldiri</a>, Flickr.</figcaption></figure><h3>So, what were the big takeaways?</h3><p><strong>We didn’t explain ourselves well enough.</strong> The forms are easy to complete in minutes, if you understand what they are for. Without any inline help or context, we may as well ask users to just randomly choose options.</p><p><strong>We relied too heavily on email.</strong> I love our email onboarding process, and have tweaked it a number of times based on A/B tests and statistics, yet we overlooked the fact it is yet another thing to look at, and who wants to jump between email client and web browser repeatedly?</p><p><strong>Spell. It. Out.</strong> If you use the correct language, your directions or prompts don’t come across as condescending. Be as concise as you can, but helpful. There’s no need to label an ‘email address’ form field with ‘Your email address’ — that is superfluous.</p><h3>Summary</h3><p>The secret to improving your startup starts with getting real life user testing for your product. It is invaluable for your product maturation. It’s an absolute ‘must have’ I believe.</p><p>Sure, there are plenty of user testing tools and platforms out there, including ones that allow you to ‘crowd test’ something, however there is something intangible about being able to watch body language and facial expressions during a user test.</p><p>Recruit people from outside your usual circle, and don’t let them know anything about your project until the day. Make sure you give the exact same brief to each person, and make it fairly easy to achieve.</p><p>Either record or write down everything; no matter how trivial. You will find a consistent message across multiple users which iterates what the most important things to fix are.</p><p>Make sure you thank them sincerely. They are literally helping you build a better, more sustainable product. They are awesome volunteers.</p><p>Do it more than once. Now that we have made a number of changes to the interface, I plan on running a couple more people through this very soon.</p><p>6Q allows leaders to get an understanding on team mood and collect valuable, actionable feedback by using our unique six question surveys. Couple this with our peer-to-peer employee recognition, and 6Q becomes a powerful tool to improve communication and work lives of everyone within an organization. Take us for <a href="http://www.6q.io/">a free trial here</a>.</p><p><em>Originally published on our company blog, </em><a href="https://inside.6q.io/the-simple-secret-to-improving-your-startup/"><em>inside.6q.io</em></a><em> but shared here for all our Medium friends. :)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37d61d5e37a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Short (& long) History of our Start-up]]></title>
            <link>https://medium.com/@team6Q/the-short-long-history-of-our-start-up-723e35300bdf?source=rss-b5150d64421e------2</link>
            <guid isPermaLink="false">https://medium.com/p/723e35300bdf</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[The 6Q Team]]></dc:creator>
            <pubDate>Thu, 02 Apr 2015 14:58:49 GMT</pubDate>
            <atom:updated>2016-11-21T01:25:47.437Z</atom:updated>
            <content:encoded><![CDATA[<p>For many, our little start-up, <a href="http://www.6q.io/">6Q</a>, started 228 days before our 24 March launch, in mid-August 2014, when we ran our first ‘startup sprint’ (more on that shortly).</p><p>In fact, 6Q started back when I first founded <a href="http://www.bam.com.au/">Bam Creative</a>, the digital agency that built, and is a shareholder, in 6Q. Since the start of our journey as Bam Creative, I’ve been working on the theory that employment doesn’t need to suck.</p><p>Over the years prior to starting my own business, I have held plenty of diverse positions, some of which sucked, others that were great. In creating positions for people at my agency, I considered what sucked about my previous jobs, and how to avoid it.</p><blockquote><em>Working does not need to suck. Those of us who love our jobs are the happiest people alive.</em></blockquote><p>Much of it personally came down to a few key points;</p><ul><li>Work needed to be enjoyable,</li><li>I craved regular feedback</li><li>I wanted to feel valued</li><li>I wanted to be respected</li><li>My employer needed to meet my personal values</li><li>I needed to believe in the company values</li></ul><p>When I started my business, I vowed to change how I managed others as we grew.</p><p>I haven’t always been a great leader or manager; I’ve certainly made plenty of mistakes, however a few elements of our culture I believe the team have appreciated, include;</p><ul><li>Quarterly performance reviews that involve both parties being reviewed</li><li>Open door policy with me always being available to the team</li><li>A lateral organization chart, where everyone is encouraged to speak their mind</li></ul><p>We’ve tried many things over the years to ensure we are doing our best as an organization to our employees, and to ensure our team is doing what they can from a performance and productivity perspective</p><p>Experiments we’ve undertaken have included daily stand up meetings, town-hall meetings where everyone has a say, rewards anonymous suggestion box, and a plethora of different software tools.</p><p>During the last 13 years, we’ve stuck mostly to digital projects, and intentionally have stayed small and nimble. We’ve built and extended a few products of our own such as content management, extended modules, and worked on all matters of websites, bespoke web applications and have even worked on elements of (other peoples) products, all in a time and materials arrangement.</p><p>I’ve always had a drive to encourage everyone who worked with me to feel real ownership of the company. In 2010, I took that one step further, and we became employee owned, with a number of employees buying in to become shareholders.</p><p>Some of the many concepts we’ve tried have worked whilst a few have been dismal failures, yet every single one of them proved they were worth trying. No regrets here!</p><blockquote><em>Never stop trying to create the best culture with the best team and awesome ways to keep everyone engaged and happy. We all need to focus on creating jobs that don’t suck.</em></blockquote><p>A process we found worked very well for us has been our weekly ‘Five minute meetings’, which consists of sitting down with each team member for no more than five minutes, to find out how their last week has gone, what the week ahead holds, any roadblocks they encountered, how their happiness was, etc.</p><p>This works well when there’s only 14 in the team, however it’s very hard to scale. A team of 30 would take three hours per week to do the same five minutes with each team member!</p><p>I was considering how to scale this idea, when our first start-up sprint was being planned. I realized we could create a simple polling system that whilst not replicating the face-to-face experience, managed to get some of the key aspects in.</p><p>My concept of a start-up sprint was to set aside a day, gather the team at lunchtime, give them a short brief, and then all of us work as a collective to see how close we could get a minimal viable product by 6.30pm. At this point, we’d stop to review, drink a few beers and eat some fine wood-fired pizza.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*kVaO8lg4UvnKuIX2TnZwBA.jpeg" /><figcaption>Some of the team, hard at work during our startup sprint</figcaption></figure><p>The reasoning for putting on this sprint was that whilst I’m fond of the outcomes of start-up weekend or 24-hour hack-a-thons, I knew it was a little much to ask my team to spend the weekend in the office.</p><p>Our first start-up sprint was a huge success; we had a number of fantastic outcomes besides the actual MVP of 6Q, which included;</p><ul><li>Trialing new processes and workflow</li><li>Pushing creative thinking on team members unused to the concept</li><li>Validating what works, and what didn’t, in a compressed time frame</li><li>Encouraging individuals to work in areas they weren’t usually in</li></ul><p>It was much like many of the projects we’ve regularly work on, except some key areas;</p><ul><li>We did it in seven hours not two or three months</li><li>No clearly defined roles; people chose what they wanted to do</li><li>A focus on agile, fast brainstorming</li></ul><blockquote><em>Internal teams can push for innovation and learn more about each other and our existing systems in one day by doing a similar exercise to a start-up sprint.</em></blockquote><p>The end of the seven hours saw us with a working prototype of 6Q.</p><p>Sure, it looked less than ideal, however there was a logo, blog, twitter account, rough marketing and business plan, and a web application that sent weekly polls, recorded the answers and sent the reports afterwards.</p><p>Importantly, we were building a product for ourselves; not for someone else.</p><p>Over the coming 228 days, we improved the application to allow other users and organisations to be added, created a website to explain it all, tweeted a little, worked on the system another 100 or more times, rewrote the onboarding process and emails many times, wrote up future features, battled over what would and wouldn’t be included at launch, created support documentation and plenty more.</p><p>We found that the competitive landscape for employee feedback surveys was already mature (meaning we had plenty of existing big competitors), we found we had a lot to learn (who knew how far trigger based emails had matured), and we made a number of mistakes (and no doubt, will continue to do so).</p><p>If I had started this project as a product to sell to others from the start, I would have been dismayed by the many other competitors already in this space. Heck, we would have at least done our research.</p><p>Now we’re here today, one week after we publicly launched. 235 days since we spent seven hours playing with a theory we could throw convention out the window, and build something that is interesting.</p><p>It’s been an enjoyable ride so far, and we’re not yet at the finish line. I doubt we’ll ever really be. Its nice to think that 6Q may become profitable and allow us to keep working on improving the product further, and impacting the company culture and team happiness of our customers around the globe.</p><p>I look forward to keeping you updated with some of the lessons we’ve learned on the way to building our first SaaS product, and I trust some of the successes as well.</p><h4>Hey there! Found this article useful, and want to see more? Please consider clicking the ❤️ icon below.</h4><p><em>Originally published on our blog, </em><a href="https://inside.6q.io/the-short-long-history-of-our-start-up/"><em>inside.6q.io</em></a><em>. You should check it out. ;)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=723e35300bdf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>