{"id":345,"date":"2013-08-20T13:17:24","date_gmt":"2013-08-20T13:17:24","guid":{"rendered":"http:\/\/securityroots.com\/blog\/?p=345"},"modified":"2013-08-20T13:17:24","modified_gmt":"2013-08-20T13:17:24","slug":"software-quality-creating-a-product-you-can-live-with","status":"publish","type":"post","link":"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/","title":{"rendered":"Software quality: creating a software product you can live with"},"content":{"rendered":"

When creating a software business there are a lot of things to consider and many decisions to be made. One of the most important ones, especially if you are by yourself<\/a>, is: how high are you going to put the software quality bar?<\/p>\n

Giving the day-to-day pressures to build up the business (do you have a business or do you just think you do?), the multiple feature requests by your users, the support requests you have to tend to, the pile of ideas you’ve got in the roadmap and the limited time in each day, it is clear that some compromises must be made. You’ve got to strike a balance between having enough features that your tool is compelling and making sure that what you have actually works (otherwise people that you worked so hard to convince of using your tool will be frustrated and abandon it).<\/p>\n

In the early stages<\/h2>\n

Remember the classic essay by Joel Spolsky Good Software Takes Ten Years. Get Used To it<\/a>, yes it takes time to create a great product, but you need to make sure that your company is going to survive long enough to get there and<\/strong> you need to make sure you’re still enjoying what you are doing years down the line \ud83d\ude42<\/p>\n

During the early stages, not every feature we’ve pushed in a release of Dradis Pro<\/a> was as polished as I’d have liked, but at the time we thought it was the right choice: push the feature out and let our users start benefiting from it. However we’re not in the early stages any more. We’ve been two years in business, with a growing client base and heathy amount of new sign ups every month. Now it’s the time to take two steps back and look at the big picture, to prepare ourselves for the next ten years.<\/p>\n

One of the most important things to learn and keep in mind, even more important to those of us coming from an engineering background is that your users don’t care about your product. They don’t want to use your product for the shake of using a product. They want the results they’ll get from using your product, that’s where the focus should be. Let me repeat that again as it is quite important:<\/p>\n

Your users don’t want to use your product,
    they want the results they’ll get from using your product.<\/p><\/blockquote>\n

This means you have to identify what this end results are and focus your efforts in making it ever easier for your users to get there. This often means spending time refining areas of your tool instead of adding new features.<\/p>\n

Balancing scope and software quality<\/h2>\n

In the era of the Lean Startup<\/a>, the above ties nicely with the concept of minimum viable product<\/a>: in order to become sustainable, you need to identify several key pieces of functionality that when put together are going to allow your users to get the end results they are looking for. [Note that I’m talking about being sustainable (i.e. generating enough revenue to reinvest in the product to improve it), not just in order to sell or in order to find users for your product. You can sell almost any piece of broken software for a low enough price. But that’s a different discussion for a different time.]<\/p>\n

Throwing together those pieces and making sure that they can be made to work together as a coherent application is the very first stage in the lifecycle of the product. This means you’re solving a real problem, for real people, that will pay real money to get their problem solved. However, in the path to this first summit in your journey, you may have to release half-baked solutions or quirky code you are not proud of. You may even do this without being conscious about it (at the end of the day, you’re fighting an uphill battle, and getting results is the only think that counts on a daily basis).<\/p>\n

There is a tipping point where you realize that the strategy of knocking together functionality and releasing it is not going to work in the long run. You are accruing too much technical debt. If you are hoping to be developing and maintaining your tool for years to come, you better make sure that you are creating something that you will want to maintain, something that you are proud of.<\/p>\n

I saw the light while reading the Designing Web Applications<\/a> book by Nathan Barry<\/a> a few months ago. In particular a section discussing the ideas of Ryan Singer<\/a>, Software designer at 37signals, on product quality:<\/p>\n

\nI like to visualize software. Here\u2019s an intuition that works for me. Feature complexity is like surface area and quality of execution is like height.\n<\/p><\/blockquote>\n

\"A<\/a><\/p>\n

\nI want a base level of quality execution across all features. Whenever I commit to building or expanding a feature, I\u2019m committing to a baseline of effort on the user experience. That way feature complexity \u2014 scope \u2014 is always the cost multiplier, not user experience. There aren\u2019t debates about experience or how far to take it. The user experience simply has to be up to base standard in order to ship, no matter how trimmed down the feature is.\n<\/p><\/blockquote>\n

(Ryan has an article on his blog about the subject: What happens to user experience in a minimum viable product?<\/a>)<\/p>\n

Even though conceptually we’d all agree that it’s desirable to build good quality products, Ryan’s surface\/heigh metaphor makes it really easy to understand the end goal we’re striving for and the reasoning behind it. It is a great tool that you can keep on the back of your head and use to drive your development efforts on a daily basis.<\/p>\n

Keep your focus<\/h2>\n

It’s more important to ensure a consistent height across all areas of the product than it is to expand the surface. In fact, it is a trade off, there is no expanding the surface if the heigh isn’t going to be kept consistent.<\/p>\n

This helps in narrowing the focus of what you’re trying to build, less surface, more height, build something great. This isn’t new, and there are many ways to phrase this feeling, but I always remember Bill Crosby’s:<\/p>\n

\nI don’t know the key to success, but the key to failure is trying to please everybody.\n<\/p><\/blockquote>\n

You product can’t be all things to all people. This is why you’ve seen a multitude of minimalist text editors thrive by focussing on what is important and nothing else (iA Writer<\/a>, Writeroom<\/a>, Byword<\/a>…). Have the basics taken care of before thinking about adding new stuff. As Julie Zhuo, Director of Product Design at Facebook puts it, there is a tax associated with every new feature you introduce<\/a> that you better understand.<\/p>\n

Making this shift, this change of focus towards quality, clarity and purpose has benefits all around. It makes you proud of the work you do and it helps to ensure that you don’t have too many features that you can’t pay attention to.<\/p>\n

This is where we are going for the next few releases of Dradis Pro<\/a>: don’t expect a lot of growth in the surface, we’ll focus on pushing and levelling our height, always keeping an eye on the results our users want to realize.<\/p>\n

I’d like to wrap this post with another quote about quality and building a software product, this time by Jason Fried<\/a> also of 37 signals:<\/p>\n

\nIt better be good, because people are depending on it to be good\n<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"

When creating a software business there are a lot of things to consider and many decisions to be made. One of the most important ones, especially if you are by yourself, is: how high are you going to put the software quality bar? Giving the day-to-day pressures to build up the business (do you have […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":[]},"categories":[2,3],"tags":[],"jetpack_publicize_connections":[],"yoast_head":"\nSoftware quality: creating a product you can live with<\/title>\n<meta name=\"description\" content=\"How does software quality affect the long-term viability of your product and business? Scope vs. quality of execution. Surface \/ height intuition\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Software quality: creating a product you can live with\" \/>\n<meta property=\"og:description\" content=\"How does software quality affect the long-term viability of your product and business? Scope vs. quality of execution. Surface \/ height intuition\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/\" \/>\n<meta property=\"og:site_name\" content=\"Dradis Framework Blog\" \/>\n<meta property=\"article:published_time\" content=\"2013-08-20T13:17:24+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/securityroots.com\/blog\/wp-content\/uploads\/2013\/08\/06262011-features_as_surface_area.png\" \/>\n<meta name=\"author\" content=\"Daniel Martin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dradisfw\" \/>\n<meta name=\"twitter:site\" content=\"@dradisfw\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Daniel Martin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/\",\"url\":\"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/\",\"name\":\"Software quality: creating a product you can live with\",\"isPartOf\":{\"@id\":\"https:\/\/dradis.com\/blog\/#website\"},\"datePublished\":\"2013-08-20T13:17:24+00:00\",\"dateModified\":\"2013-08-20T13:17:24+00:00\",\"author\":{\"@id\":\"https:\/\/dradis.com\/blog\/#\/schema\/person\/0d7332083eed49c91ddf883f46f0dc52\"},\"description\":\"How does software quality affect the long-term viability of your product and business? Scope vs. quality of execution. Surface \/ height intuition\",\"breadcrumb\":{\"@id\":\"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/dradis.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Software quality: creating a software product you can live with\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/dradis.com\/blog\/#website\",\"url\":\"https:\/\/dradis.com\/blog\/\",\"name\":\"Dradis Framework Blog\",\"description\":\"Information management for security teams\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/dradis.com\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/dradis.com\/blog\/#\/schema\/person\/0d7332083eed49c91ddf883f46f0dc52\",\"name\":\"Daniel Martin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dradis.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/b0810040b4df4564381531b4d4a79a05?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/b0810040b4df4564381531b4d4a79a05?s=96&d=mm&r=g\",\"caption\":\"Daniel Martin\"},\"sameAs\":[\"http:\/\/securityroots.com\/story.html\"],\"url\":\"https:\/\/dradis.com\/blog\/author\/etd\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Software quality: creating a product you can live with","description":"How does software quality affect the long-term viability of your product and business? Scope vs. quality of execution. Surface \/ height intuition","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/","og_locale":"en_US","og_type":"article","og_title":"Software quality: creating a product you can live with","og_description":"How does software quality affect the long-term viability of your product and business? Scope vs. quality of execution. Surface \/ height intuition","og_url":"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/","og_site_name":"Dradis Framework Blog","article_published_time":"2013-08-20T13:17:24+00:00","og_image":[{"url":"http:\/\/securityroots.com\/blog\/wp-content\/uploads\/2013\/08\/06262011-features_as_surface_area.png"}],"author":"Daniel Martin","twitter_card":"summary_large_image","twitter_creator":"@dradisfw","twitter_site":"@dradisfw","twitter_misc":{"Written by":"Daniel Martin","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/","url":"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/","name":"Software quality: creating a product you can live with","isPartOf":{"@id":"https:\/\/dradis.com\/blog\/#website"},"datePublished":"2013-08-20T13:17:24+00:00","dateModified":"2013-08-20T13:17:24+00:00","author":{"@id":"https:\/\/dradis.com\/blog\/#\/schema\/person\/0d7332083eed49c91ddf883f46f0dc52"},"description":"How does software quality affect the long-term viability of your product and business? Scope vs. quality of execution. Surface \/ height intuition","breadcrumb":{"@id":"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/dradis.com\/blog\/2013\/08\/software-quality-creating-a-product-you-can-live-with\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dradis.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Software quality: creating a software product you can live with"}]},{"@type":"WebSite","@id":"https:\/\/dradis.com\/blog\/#website","url":"https:\/\/dradis.com\/blog\/","name":"Dradis Framework Blog","description":"Information management for security teams","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/dradis.com\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/dradis.com\/blog\/#\/schema\/person\/0d7332083eed49c91ddf883f46f0dc52","name":"Daniel Martin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dradis.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/b0810040b4df4564381531b4d4a79a05?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/b0810040b4df4564381531b4d4a79a05?s=96&d=mm&r=g","caption":"Daniel Martin"},"sameAs":["http:\/\/securityroots.com\/story.html"],"url":"https:\/\/dradis.com\/blog\/author\/etd\/"}]}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p3ijVs-5z","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":172,"url":"https:\/\/dradis.com\/blog\/2013\/04\/collaboration-tool-is-creating-your-own-worth-it\/","url_meta":{"origin":345,"position":0},"title":"Should you create your own back-office\/collaboration tools?","date":"April 17, 2013","format":false,"excerpt":"When an organisation tries to tackle the \"collaboration and automated reporting problem\", one of the early decisions to make is whether they should try to build a solution in-house or use an off-the-shelf collaboration tool. Of course, this is not an easy decision to make and there are a lot\u2026","rel":"","context":"In "Security Practice"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":766,"url":"https:\/\/dradis.com\/blog\/2017\/01\/dradis-framework-founders-letter-2017\/","url_meta":{"origin":345,"position":1},"title":"Dradis Framework Founder’s Letter – 2017","date":"January 9, 2017","format":false,"excerpt":"Good Software Takes Ten Years. I didn't know that when we started back in 2007, but I've come to terms with that rule since then. A lot can change in 9 years. You can go from the first commit of an internal project released as open-source to a small, independent,\u2026","rel":"","context":"In "Business of Software"","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/dradis.com\/blog\/wp-content\/uploads\/2016\/12\/downloads.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":642,"url":"https:\/\/dradis.com\/blog\/2020\/03\/the-problem-a-security-assessment-process-that-was-good-enough\/","url_meta":{"origin":345,"position":2},"title":"Security Assessment Process: The Problem With “Good Enough”","date":"March 4, 2020","format":false,"excerpt":"The Current Process As a freelance security consultant, researcher, and software developer, you could say Robin Wood is someone who knows their way around the security assessment process. On his site DigiNinja, you can find more than 50 security-related projects he\u2019s released to the community. Several years ago, Robin\u2019s workflow\u2026","rel":"","context":"In "User Stories"","img":{"alt_text":"Security assessment process quote about Dradis Pro ","src":"https:\/\/i0.wp.com\/dradisframework.com\/blog\/wp-content\/uploads\/2020\/03\/Dradisquote.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":1281,"url":"https:\/\/dradis.com\/blog\/2010\/11\/do-you-want-to-contribute-to-dradis\/","url_meta":{"origin":345,"position":3},"title":"Do you want to contribute to Dradis?","date":"November 30, 2010","format":false,"excerpt":"We have updated the\u00a0How to become a comitter\u00a0page with the guidelines for commit access approval. If you want to contribute with a plugin or a new feature, now it is easier than ever. 0 comments:","rel":"","context":"In "Business of Software"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2583,"url":"https:\/\/dradis.com\/blog\/2025\/12\/icymi-what-we-shipped-in-2025-%f0%9f%9a%80\/","url_meta":{"origin":345,"position":4},"title":"ICYMI: What we shipped in 2025 \ud83d\ude80","date":"December 17, 2025","format":false,"excerpt":"2025 has been a busy and productive year for the entire Dradis team. While we shipped a lot of cool stuff, there are some features that really stand out as we look back over the year. We hope you\u2019ve been making as much use of these as we have. Our\u2026","rel":"","context":"In "Design"","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/dradis.com\/blog\/wp-content\/uploads\/2025\/12\/Services-1.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":1458,"url":"https:\/\/dradis.com\/blog\/2020\/09\/hands-on-hacking\/","url_meta":{"origin":345,"position":5},"title":"Hands on Hacking","date":"September 30, 2020","format":false,"excerpt":"The team over at Hacker House has recently released their first book,\u00a0Hands on Hacking. The book is an incredibly accessible guide for learning pentesting and purple teaming and includes often-overlooked subjects like building a business case for hacking, ethical guidelines, and report writing.\u00a0 Report writing, you say? Needless to say,\u2026","rel":"","context":"In "Business of Software"","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/dradis.com\/blog\/wp-content\/uploads\/2020\/09\/hoh_dradis.jpg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/dradis.com\/blog\/wp-json\/wp\/v2\/posts\/345"}],"collection":[{"href":"https:\/\/dradis.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dradis.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dradis.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/dradis.com\/blog\/wp-json\/wp\/v2\/comments?post=345"}],"version-history":[{"count":0,"href":"https:\/\/dradis.com\/blog\/wp-json\/wp\/v2\/posts\/345\/revisions"}],"wp:attachment":[{"href":"https:\/\/dradis.com\/blog\/wp-json\/wp\/v2\/media?parent=345"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dradis.com\/blog\/wp-json\/wp\/v2\/categories?post=345"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dradis.com\/blog\/wp-json\/wp\/v2\/tags?post=345"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}