• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Ben Barden

Products - Projects - Process

  • Ben Barden
  • Home
  • Music
  • Weekly blogging in 2021
  • About
You are here: Home / Product management / Software quality: why you shouldn’t ignore the small things

11th August 2018 by Ben Barden

Software quality: why you shouldn’t ignore the small things

When your product to-do list (aka the product backlog) is very long, with “urgent” items or requests from your biggest or most demanding users, the natural path is to focus on the high value work.

New features that could bring in new users or retain existing ones. Major bugs. Quick wins.

Everywhere I’ve worked, and in fact in most software projects I’ve heard of, there’s always more to do than you can actually get through. You can’t do everything, so you have to prioritise what to work on next.

As part of gathering feedback from users, QAs, or your own product review cycles, you’ll sometimes identify issues or potential tweaks which, in the grand scheme of things, seem very minor. Perhaps there’s a small layout bug on iOS. A little-used setting doesn’t work for a small number of users. An old page that hardly anybody goes to doesn’t look right with a recent design overhaul. Or a page is retired and removed from the navigation links – but it’s still accessible if you visit it directly.

I’ve heard numerous excuses for not dealing with minor changes such as the above. It’s not important. We’ve got bigger fish to fry. We’re too busy. Etc. However, if you ignore all of these small issues, they can build up and collectively give users the impression that the product is being neglected.

It’s a broken window situation.

In The Pragmatic Programmer, there’s a section called Software Entropy that mentions broken windows. I’d like to highlight this quote:

Don’t leave “broken windows” (bad designs, wrong decisions, or poor code) unrepaired. Fix each one as soon as it is discovered. If there is insufficient time to fix it properly, then board it up. Perhaps you can comment out the offending code, or display a “Not Implemented” message, or substitute dummy data instead. Take some action to prevent further damage and to show that you’re on top of the situation.

If something’s broken, fix it. If it’s not used anymore, remove it. To help with this, gather feedback to see if users are finding pain points that you’re not aware of. Use analytics to see which parts of the product are being used.

Don’t ignore the minor things. While one small UX quirk might not make much difference if you fix it, lots of UX issues in the same area of the product can really annoy your users. Leaving this unresolved can make software feel awkward and frustrating to use, or just plain broken.

Is that the kind of product you want?

Filed Under: Product management Tagged With: product strategy, software, software development, tech, technology improvement

About the author

Web dev, bug finder, writer of niche music
Founder/coder at switchscores.com
Product Manager at Octopus Energy / Kraken Technologies Read More…

Primary Sidebar

benbarden

I have some new music coming soon. 😁🕺🥳💥🦆 It's almost ready to submit to Spotify... once I've finished tweaking one of the tracks. In the meantime, here's the artwork.
Soft and comfy. #catsofinstagram Soft and comfy. #catsofinstagram
Winding path on a cloudy day. Winding path on a cloudy day.
Found this on a walk in #guildford . Found this on a walk in #guildford .
Check it out- brand new electric radiator! Just ar Check it out- brand new electric radiator! Just arrived. I have 2 in this size and a bigger one for the lounge. On feet for now but will be fixed to the wall at a later date. Once set up, no more ancient storage heaters to contend with!
It was a very nice day! I went for a walk at lunch It was a very nice day! I went for a walk at lunchtime.
One of my favourites. #pokemongo One of my favourites. #pokemongo
Out for a walk on my lunch break. Out for a walk on my lunch break.
An imposter in the fruit bowl! An imposter in the fruit bowl!
Rainbow! Rainbow!
The tea station in my new flat. The tea station in my new flat.
There's space for drinks in the window seat. There's space for drinks in the window seat.
View from the windows. View from the windows.
Setting up the new study. That's a wardrobe on the Setting up the new study. That's a wardrobe on the left. It is bigger than the pic shows but the rest of the room is a bit of a mess, as I still have some sorting to do.
Setting up the Switch is an important part of movi Setting up the Switch is an important part of moving.
It's been a long week, as I've been moving to a ne It's been a long week, as I've been moving to a new place. This was my final pic of the old flat, all boxed up and ready to go.
New music now on Spotify! It's a disco EP - well, New music now on Spotify! It's a disco EP - well, some of it. Search for GFD and look for this pic. Or use this link, but you'll have to copy it: https://open.spotify.com/album/04eiQOEeJZiOThpRyjm60w?si=gsRT8JHwQHeQFXIPqTyw_g&utm_source=copy-link
New disco/dance album, coming to Spotify etc in a New disco/dance album, coming to Spotify etc in a couple of weeks 😁🕺💥❤
I love this game. Very happy to have it on the #Ni I love this game. Very happy to have it on the #NintendoSwitch !
So much food, but it was good! So much food, but it was good!
Load More… Follow on Instagram

Recent Posts

  • How many projects should a team work on at a time?
  • Practical tips for organising your backlog, from my home improvement project
  • New music: Night Sessions
  • Getting things done
  • A few things I’ve learned about software testing

Archives

Categories

Handcrafted with on the Genesis Framework