<?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 Justin Goodhew on Medium]]></title>
        <description><![CDATA[Stories by Justin Goodhew on Medium]]></description>
        <link>https://medium.com/@justingoodhew?source=rss-2e1cb31c2b5d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gM1LDWwAuZyt0dvOO47J5w.jpeg</url>
            <title>Stories by Justin Goodhew on Medium</title>
            <link>https://medium.com/@justingoodhew?source=rss-2e1cb31c2b5d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:22:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@justingoodhew/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[Impact Simplified]]></title>
            <link>https://medium.com/trellis-org/impact-simplified-1565badc3ec1?source=rss-2e1cb31c2b5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1565badc3ec1</guid>
            <category><![CDATA[charity]]></category>
            <category><![CDATA[impact-investing]]></category>
            <category><![CDATA[social-enterprise]]></category>
            <category><![CDATA[nonprofit]]></category>
            <category><![CDATA[impact]]></category>
            <dc:creator><![CDATA[Justin Goodhew]]></dc:creator>
            <pubDate>Fri, 13 Oct 2017 16:11:22 GMT</pubDate>
            <atom:updated>2017-10-13T16:14:08.359Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is impact?</h3><p>Impact is the longterm outcome(s) of a set of activities completed by a certain social enterprise.</p><p>Social enterprises (SEs) complete certain activities with specific inputs and outputs to create desired outcomes. These outcomes can either combine or be impactful (long lasting and important) enough on their own to become impacts.</p><h3>Impact is the single most important aspect you need to know about your social enterprise.</h3><h3>Why is Impact the most important measurement?</h3><p>Simply put, it is the reason you are in the social sector; it is the differentiator. Impact allows you to understand:</p><ul><li>Your effect on the cause you are supporting</li><li>Market and talk about your social enterprise</li><li>Identify the reason/why/core value/mission of your social enterprise</li><li>Benchmark for measurement to optimize, improve and grow</li></ul><p>Without understanding and measuring your impact you have no way of telling how you are making a difference in your cause.</p><h3>Breaking it Down</h3><p>Below is a simple diagram and definitions of terms and how they relate to Impact.</p><p><strong>Input:</strong> is the resource(s) needed for an activity to occur.</p><p><strong>Activity:</strong> is the event or exercise that occurs when a group of inputs come together.</p><p><strong>Output:</strong> Is a direct result(s) of an activity, commonly misunderstood as an outcome.</p><p><strong>Outcome:</strong> Is an indirect result of a certain activity. When an indicator is triggered due to a combination of outputs, an outcome is achieved.</p><p><strong>Indicator:</strong> a measure of success that tells you when an outcome has been reached from a certain set of outcomes.</p><p><strong>Impact:</strong> Is the longterm outcome(s) or combination of outcomes from an activity or set of activities</p><p><strong>Here is a diagram below:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2q9tXmZ7VRAzbw9xxV8hJQ.jpeg" /><figcaption>Impact Map</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1565badc3ec1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trellis-org/impact-simplified-1565badc3ec1">Impact Simplified</a> was originally published in <a href="https://medium.com/trellis-org">Trellis.org</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop donating, start investing. The future of Giving]]></title>
            <link>https://medium.com/trellis-org/stop-donating-start-investing-the-future-of-giving-c758eaa27789?source=rss-2e1cb31c2b5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c758eaa27789</guid>
            <category><![CDATA[impact]]></category>
            <category><![CDATA[impact-investing]]></category>
            <category><![CDATA[nonprofit]]></category>
            <category><![CDATA[charity]]></category>
            <category><![CDATA[trellis]]></category>
            <dc:creator><![CDATA[Justin Goodhew]]></dc:creator>
            <pubDate>Fri, 13 Oct 2017 16:09:24 GMT</pubDate>
            <atom:updated>2017-10-13T16:09:24.602Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the biggest issues the social sector faces stems from the differences between the for profit and non profit space. Dan Pallotta, author of Uncharitable and <a href="https://www.ted.com/talks/dan_pallotta_the_way_we_think_about_charity_is_dead_wrong">Ted talk speaker</a> outlines these issues very well. One of the main differences is how the social sector attains capital. The for profit space receives their capital through investments and in the non profit space it is through donations.</p><p>Currently, the word donation, although still regarded as a good thing, is not taken as seriously. It says that you will never see a return on that money, once you part with it; you receive your sense of fulfillment, know that you helped out and you move on. But, people giving want more; they want to be involved, engaged with and updated on what their money did or is doing. That is why we need to start talking about our giving in terms of investing.</p><p><strong>What if we were to start investing into charities?</strong> That doesn’t mean expecting a monetary return necessarily but it does mean expecting a social return. The future of giving needs to be investing, where individuals can invest in a charity or NFP and receive a certain return in impact to the cause they care about. <strong>People are starving for a greater understanding in how much impact their giving creates.</strong></p><p>So next time you are asked to donate, put on your investor hat. Take a look and see what return you will get for your dollar. What sort of impact yield you can receive on your charitable investments. If everyone started to give like that we would be getting a lot more social returns. Maybe even make some real change.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c758eaa27789" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trellis-org/stop-donating-start-investing-the-future-of-giving-c758eaa27789">Stop donating, start investing. The future of Giving</a> was originally published in <a href="https://medium.com/trellis-org">Trellis.org</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Trellis.org: Changing the way we give back]]></title>
            <link>https://medium.com/trellis-org/introducing-trellis-org-changing-the-way-we-give-back-eaa3653e6a5e?source=rss-2e1cb31c2b5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/eaa3653e6a5e</guid>
            <category><![CDATA[charitable-giving]]></category>
            <category><![CDATA[charity]]></category>
            <category><![CDATA[impact-investing]]></category>
            <category><![CDATA[nonprofit]]></category>
            <category><![CDATA[trellis]]></category>
            <dc:creator><![CDATA[Justin Goodhew]]></dc:creator>
            <pubDate>Fri, 13 Oct 2017 16:05:07 GMT</pubDate>
            <atom:updated>2017-10-13T16:05:07.264Z</atom:updated>
            <content:encoded><![CDATA[<p>Yearly giving has stayed at 2% of GDP for the last 20 years, yet everyone seems to agree that we “care” more. The current social sector is dated, based on old principles, morphed into a short sighted, resource deprived sector that society has put in a box and hasn’t allowed it to grow.</p><p>So why has giving stayed stagnant? The answer is easy: marketing and engagement. No one can get our attention, no one is getting it in the right way or on the right platforms. If they are getting our attention, it is not using the correct messaging.</p><p>We need to change our perspective, we need to start talking about the social sector in terms of social enterprises instead of nonprofits. Nonprofits literally say ‘no profit’ in the title. Second term we need to change is donation, we need to change it to social investing. That doesn’t mean expecting a monetary return necessarily but it does mean expecting a social return.</p><p>Our goal at Trellis is to be the best at helping the social sector measure and showcase their impact. Giving social investors, everyday people like you and I, a place to give back that is engaging and impactful.</p><p>As a new company, we feel that it is important to showcase what we believe in. Below is our vision and mission:</p><h3>Vision:</h3><p>Enable Impact. Change the World.</p><h3>Mission:</h3><p>Improve the world we live in by connecting the social sector to everyday people on a platform focused on impact. Allowing people to invest their money for social return in a modern, transparent and engaging way. Trellis will lead the social sector into more sustainable and impact focused future by reframing how our society thinks about charity, giving and measuring success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eaa3653e6a5e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trellis-org/introducing-trellis-org-changing-the-way-we-give-back-eaa3653e6a5e">Introducing Trellis.org: Changing the way we give back</a> was originally published in <a href="https://medium.com/trellis-org">Trellis.org</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lean App Development 103: Breaking it Down]]></title>
            <link>https://medium.com/biznas/lean-app-development-103-breaking-it-down-ad522a542abd?source=rss-2e1cb31c2b5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad522a542abd</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[lean-startup]]></category>
            <dc:creator><![CDATA[Justin Goodhew]]></dc:creator>
            <pubDate>Thu, 01 Dec 2016 21:17:50 GMT</pubDate>
            <atom:updated>2016-12-01T21:17:50.963Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wWJR_tIG-l7lxCd7tpuPqA.jpeg" /></figure><p>There are 6 steps in the lean app development process, or at least 6 steps we’ve identified so far. When we started 8 months ago there were only 3…. Oh how I miss the days of hopeful optimism… but with 6 steps we feel we’re being a little more realistic.</p><p>While we always managed to hit our goals, the pain felt by all parties along the way decreased drastically as the lean app development process grew. Here’s how it all unfolded.</p><h3>Where we started</h3><p><strong>Steps in Process: </strong>3</p><p><strong>Overall Experience: </strong>Satisfactory. Goals achieved but lots of bumps along the way.</p><ol><li>Discovery</li><li>Design</li><li>Develop</li></ol><p>Sounded great, clear, and concise but it led to a lot of potential for misalignment, poorly defined expectations, and less predictable results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/0*KqGmhAtTNGTT8FTJ." /></figure><h3>Then we added QA</h3><p><strong>Steps in Process: </strong>4</p><p><strong>Overall Experience: </strong>Great. All goals were achieved but still some bumps along the way.</p><ol><li>Discovery</li><li>Design</li><li>Develop</li><li><strong>QA (quality assurance)</strong></li></ol><p>Adding in QA was a HUGE leap forward, everyone respects and anticipates development time but QA is often an afterthought. Projects with proper QA always turn better than those without. <strong>Don’t skip QA!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/0*DIXMaD8LR6_ERlgp." /></figure><h3>Where we’ve ended up</h3><p><strong>Steps in Process: </strong>6</p><p><strong>Overall experience: </strong>Amazing (hopefully, as it is untested). All goals achieved with minor to no glitches.</p><ol><li><strong>Project Idea</strong> (untested — send us your thoughts)</li><li>Discovery</li><li>Design</li><li>Develop</li><li>QA</li><li><strong>Delivery</strong> (untested — send us your thoughts)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/0*IDZvO7fiem1vndSS." /></figure><p>Since our last project we’ve decided to add a phase at each end. Here they are:</p><ol><li>Project Idea — A well crafted questionnaire and initial meeting to formalize the initial understanding of the project by both parties. Clients ask us for increased clarity on scope, price, timeline BEFORE paying and therefore ‘defining the ballpark’ we are playing in is a huge help for their decision making. This step will allow both parties to begin the alignment process, without too much time and resources spent on our side.</li><li>Delivery — We’ve broken down the development process even further, not only by adding a QA step but also adding a Delivery step. The Delivery step takes many forms depending on the project but usually entails handoff, training, code overview, documentation, and code migration. Essentially handing off the project from Biznas to the customer in whatever form they require, sometimes it is as simple as performing ongoing support. Other times there is an internal tech team that takes over.</li></ol><p>In the next set of blogs we want to go into depth on each of these 6 steps, share successes, and the failures that brought us to this point. Feel free to leave comments on your process and how it has evolved as you and your customers have grown.</p><p>Make sure to <a href="https://medium.com/@biznasapps">Follow Us</a> as we build out the Lean App development process!</p><p><a href="https://biznas.io/">Biznas.io</a><a href="https://twitter.com/biznasapps"><br>Biznas on Twitter</a><br><a href="https://www.facebook.com/BiznasApps/">Biznas on Facebook</a><br><a href="https://www.linkedin.com/company/10871824?trk=tyah&amp;trkInfo=clickedVertical%3Acompany%2CclickedEntityId%3A10871824%2Cidx%3A2-1-2%2CtarId%3A1475705404220%2Ctas%3Abiznas">Biznas on LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad522a542abd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/biznas/lean-app-development-103-breaking-it-down-ad522a542abd">Lean App Development 103: Breaking it Down</a> was originally published in <a href="https://medium.com/biznas">Biznas</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lean App Development 102: The Best of Both Worlds]]></title>
            <link>https://medium.com/biznas/lean-app-development-102-the-best-of-both-worlds-6850ddd27c0a?source=rss-2e1cb31c2b5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6850ddd27c0a</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Justin Goodhew]]></dc:creator>
            <pubDate>Thu, 01 Dec 2016 21:16:21 GMT</pubDate>
            <atom:updated>2016-12-01T21:17:14.730Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7w7RhMvYxQSNYk1ykU7KgA.jpeg" /></figure><p>Our <a href="https://medium.com/@biznasapps/lean-app-development-101-getting-started-f77db49772ba#.6vk7tggik">first blog post in this series</a> touched on the three golden rules of lean app development. To expand on that idea, we need to dive into how we ended up on lean app development.</p><h3>In the beginning</h3><p>Traditional development is also known as a waterfall process. Longer cycles that are very plan driven is the name of the game — you define and plan, then spend a lot of time building the software before releasing it the world. And this could take months to a year or two, depending on what you’re building.</p><p>After that came the Scrum-Agile wave which focused on sprints, allowing for iterative and incremental development. Sprints were often set as two week time periods — you had to define, plan, build, and release something within two weeks. Then you would work on a new part of the product for the next two weeks, or improve on what you just released based on feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*vZX-Rm_hfzgLvmTAtNjb8g.png" /></figure><h3>Where we took it</h3><p>We liked items from both waterfall and scrum but we also wanted to look at them through a ‘lean startup’ or ‘MVP’ approach.</p><p>In order to do this we need to ‘eat our own dog food’ and follow the three golden rules of lean app development:</p><p><strong>Rule 1 = Identify a clear goal</strong></p><p>This new process needs to enable the, “fastest, most predictable, and reliable software”. A slightly crazy and audacious goal, but at least it’s clear.</p><p><strong>Rule 2 = Core functionality</strong></p><p>This new process needs to be simple. Each step is documented in a living document, which is being tested with our current clients.</p><p><strong>Rule 3 = User Needs/Wants</strong></p><p>Lastly, we need to ensure this process focuses on customer wants. Enterprises always want faster, more predictable and reliable app development. Hence the goal for the project.</p><p>What are the traits of each of these processes?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/933/1*8EGKmSSrETjUukPCsT9tAg.png" /></figure><p>To help give you an idea of the difference in results between Traditional vs. Scrum-agile vs. Lean we drew up this handy diagram:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/1*q_gjkLFvYrQJ6pnE4O9m5g.png" /></figure><p>You can see that traditional methods tend to have a more predictable end product as opposed to the scrum-agile approach. And that is hugely important when you’re building applications for businesses — they’re spending money on building an app, they need to know what the end product is going to be. The major benefit of scrum-agile though is that it provides high customer feedback. You’re getting input every two weeks instead of at the end of a very long process. So the end product is better, and is better aligned to the customer wants/needs.</p><h3>Best of both worlds</h3><p>We took the best from both the traditional and the agile/scrum world by looking at both processes at a high level through a lean methodology lens. Combine that with a lot of customer feedback and you get a process that is predictable, fast, reliable, MVP defined, and has high customer feedback.</p><p>This process will do amazing things for development. Keeping our developers happy and working on the code that matters, and keeping our clients happy with providing them an amazing product. We’ll be a lean, mean app developing team!</p><p><a href="https://biznas.io/">Biznas.io</a><a href="https://twitter.com/biznasapps"><br>Biznas on Twitter</a><br><a href="https://www.facebook.com/BiznasApps/">Biznas on Facebook</a><br><a href="https://www.linkedin.com/company/10871824?trk=tyah&amp;trkInfo=clickedVertical%3Acompany%2CclickedEntityId%3A10871824%2Cidx%3A2-1-2%2CtarId%3A1475705404220%2Ctas%3Abiznas">Biznas on LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6850ddd27c0a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/biznas/lean-app-development-102-the-best-of-both-worlds-6850ddd27c0a">Lean App Development 102: The Best of Both Worlds</a> was originally published in <a href="https://medium.com/biznas">Biznas</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lean App Development 101: Getting Started]]></title>
            <link>https://medium.com/biznas/lean-app-development-101-getting-started-9dce161b7117?source=rss-2e1cb31c2b5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9dce161b7117</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[minimum-viable-product]]></category>
            <category><![CDATA[lean-startup]]></category>
            <dc:creator><![CDATA[Justin Goodhew]]></dc:creator>
            <pubDate>Thu, 01 Dec 2016 21:13:26 GMT</pubDate>
            <atom:updated>2016-12-01T21:13:26.348Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bD-ShI9fbooxscP8Yk7KOw.jpeg" /></figure><p>App development can seem daunting. But we’re all about cutting those calories, working out, and getting lean. And because motivation and support are key to any workout program we thought we’d take you with us, and share our journey to building the fastest and most predictable app development process.</p><h3>First steps</h3><p>So how does an app development team even get started? And what is Lean App Development anyways?</p><p>Lean app development is simple (<em>says the developer who’s been in the industry for over 20 years</em>). Lean app development = lean startup + agile. <em>Huh?</em> Well, you take the lean startup methodology and then add in the agile development approach. <em>Okay…</em> Then, apply it to building modern and scalable applications in an iterative (but well structured) environment. Easy right? We thought so too.</p><h3>Three golden rules</h3><p>Let’s break it down. There are three golden rules of lean app development:</p><ol><li>Identify a tangible, clear, and concise end goal of the project, then always ensure every decision serves that goal</li><li>Focus on building only core functionality first using the Minimum Viable Product (MVP approach)</li><li>Focus on the key users needs/wants/pains/motivations and what they care about, not the wishes of others (such as clients/boss/investors)</li></ol><h3>Questions at every step</h3><p>Whenever we take on a new project these three golden rules always have to be considered, written down, and agreed upon. And all that needs to be done before a single line of code is written. During every aspect of the build, we come back to three key questions:</p><ol><li>Does it serve the end goal?</li><li>Is this part of the MVP?</li><li>Does it answer a key need/want/pain/motivation?</li></ol><p>We know app development isn’t as simple as it sounds, and the idea of lean app development may be new to a lot of people. So we’re going to use this blog post to kickstart a series, taking you through everything you need to know about lean app development and how we use the Lean App Development process to build apps. In the next post we’ll dive into Agile and Lean processes and show you how to use the best parts of each methodology. Stay tuned for more!</p><p><a href="https://biznas.io/">Biznas.io</a><a href="https://twitter.com/biznasapps"><br>Biznas on Twitter</a><br><a href="https://www.facebook.com/BiznasApps/">Biznas on Facebook</a><br><a href="https://www.linkedin.com/company/10871824?trk=tyah&amp;trkInfo=clickedVertical%3Acompany%2CclickedEntityId%3A10871824%2Cidx%3A2-1-2%2CtarId%3A1475705404220%2Ctas%3Abiznas">Biznas on LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9dce161b7117" width="1" height="1" alt=""><hr><p><a href="https://medium.com/biznas/lean-app-development-101-getting-started-9dce161b7117">Lean App Development 101: Getting Started</a> was originally published in <a href="https://medium.com/biznas">Biznas</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>