<?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 ✌ Dave Slocombe ✌ on Medium]]></title>
        <description><![CDATA[Stories by ✌ Dave Slocombe ✌ on Medium]]></description>
        <link>https://medium.com/@daveslocombe?source=rss-896fd9223e3d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZzLfzd4DCSBfst9MIZUOnw.png</url>
            <title>Stories by ✌ Dave Slocombe ✌ on Medium</title>
            <link>https://medium.com/@daveslocombe?source=rss-896fd9223e3d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:22:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daveslocombe/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[Iteration Vs Planning]]></title>
            <link>https://medium.com/@daveslocombe/iteration-vs-planning-654afd150293?source=rss-896fd9223e3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/654afd150293</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[creativity]]></category>
            <dc:creator><![CDATA[✌ Dave Slocombe ✌]]></dc:creator>
            <pubDate>Tue, 20 Oct 2015 23:02:01 GMT</pubDate>
            <atom:updated>2015-10-20T23:02:01.883Z</atom:updated>
            <content:encoded><![CDATA[<p>The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality. His procedure was simple: on the final day of class he would bring in his bathroom scales and weigh the work of the “quantity” group: fifty pounds of pots rated an “A”, forty pounds a “B”, and so on. Those being graded on “quality”, however, needed to produce only one pot — albeit a perfect one — to get an “A”.</p><p>Well, came grading time and a curious fact emerged: <strong>the works of highest quality were all produced by the group being graded for quantity</strong>. It seems that while the “quantity” group was busily churning out piles of work — and learning from their mistakes — the “quality” group had sat theorising about perfection, and in the end had little more to show for their efforts than grandiose theories and a pile of dead clay.</p><p>via <a href="http://nodaysoffmag.com/quantity-vs-quality-do-it-fail-and-do-it-some-more/">http://nodaysoffmag.com/quantity-vs-quality-do-it-fail-and-do-it-some-more/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=654afd150293" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meetings are no joke]]></title>
            <link>https://medium.com/@daveslocombe/meetings-are-no-joke-3b716796f614?source=rss-896fd9223e3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b716796f614</guid>
            <dc:creator><![CDATA[✌ Dave Slocombe ✌]]></dc:creator>
            <pubDate>Tue, 23 Jun 2015 23:09:33 GMT</pubDate>
            <atom:updated>2015-06-23T23:09:33.838Z</atom:updated>
            <content:encoded><![CDATA[<p>Today someone said to me,</p><blockquote>Sorry i had to rush through that in 30mins, we usually take an hour.</blockquote><p>Take that in for a moment. 4 people, 30mins. To take in at most 5 information points and barter over two actions to be taken.</p><p>There should be no ‘meetings’. The mere self description of a ‘meeting’ suggests that by being co-located something useful will be achieved. Which is nonsense. It rarely is.</p><h3>Kill meetings. Only workshops.</h3><p>So what to do? Stick to facts and actions. If you can, use walls and whiteboards to centre the conversation, use gamestorms or mapping frameworks to keep it engaging and draw insights from everyone in the room. Its working time, a time share and be creative, to solve problems.</p><h3>Be radical.</h3><p>Demand meetings are no longer than 15mins. This way everyone must be prepared beforehand. If they are longer its automatically a workshop!</p><p>Remove chairs, even tables if you have to.</p><p>Disarm monologging team members by using a talking stick or a chess timer.</p><p>Remember, every minute in a meeting room is another minute closer to death having achieved nothing other than deepening the illusion of control.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*LWv6gcP7cYQzKGcNjVMn3w.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b716796f614" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Apps are Friction]]></title>
            <link>https://medium.com/@daveslocombe/apps-are-friction-e9586abec96?source=rss-896fd9223e3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9586abec96</guid>
            <dc:creator><![CDATA[✌ Dave Slocombe ✌]]></dc:creator>
            <pubDate>Tue, 23 Jun 2015 00:47:32 GMT</pubDate>
            <atom:updated>2015-06-23T00:47:32.197Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*_1ZsH8EZjRTRSD85Wr2fKQ.jpeg" /></figure><p>If you see your app or software as anything but friction between a person and their goal, then you dear friend are deluded.</p><p>In the first year in my current role, we have removed as many features as we have added. Once you begin to see minimalism, simplicity and the results it brings, you are in danger of becoming addicted to weilding the razor to your scope.</p><p>Tomorrow, go to work, look at the data for your product features, remove a feature that less than 80% of customers use. Measure the response. Repeat.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9586abec96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Definition of an MVP]]></title>
            <link>https://medium.com/@daveslocombe/definition-of-an-mvp-53602850d9f1?source=rss-896fd9223e3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/53602850d9f1</guid>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[mvp]]></category>
            <dc:creator><![CDATA[✌ Dave Slocombe ✌]]></dc:creator>
            <pubDate>Wed, 17 Jun 2015 21:55:29 GMT</pubDate>
            <atom:updated>2015-06-17T21:55:29.548Z</atom:updated>
            <content:encoded><![CDATA[<p>The minimum viable product is de-rigueur in enterprise and startup world, my least favourite twist is the ‘minimal lovable product’ to justify feature bloat and design pron, urgh. But what is an MVP?</p><p>Depends on where you stand.</p><p>From lean startup, it means the minimum amount of work to validate or invalidate a hypothesis. This is often intertwined with validating a value proposition but it need not. It may merely be validating a customer problem exists or if a solution to that problem is of interest to customers.</p><p>The golden rule of MVPs: <strong>If it doesn’t hurt, its not minimal enough.</strong></p><p>Think about that, then take a sharp razor to your scope, to the point you say we can do any less without compromising the validation, then its minimal. An MVP is about gathering data to generate insight.</p><p>In Enterprise its become a new name for the first release. Which is utterly pointless and nowhere near minimal enough. An MVP could be best described as Minimal Viable Test, rather than product, stick to that and your cycle time to insight will accelerate from where you are today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53602850d9f1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>