Earlier today, I replied to @johncutlefish on this. I want to add a few more thoughts in a thread. Because to me, fixing little things is a Big Thing. 1/6
I've heard some advocate that fixing something is worthwhile only if the effort to fix is less than the effort to work around it. This ignores hidden costs. 2/6
There's eroding user trust. For example, a typo is almost never the most critical thing to fix. But when your users see it repeatedly and all the other little things, are you giving them confidence that you can solve their bigger needs? 3/6
There's the energy spent by the team in working around the issues. I can't count the times that mental gymnastics and kludges were needed because what was once a small thing became a major roadblock to a new important thing. 4/6
There's a growing acceptance for bugs that I mentioned in my original reply. If the one small thing isn't fixed, then we're more apt to let two small things go unfixed. And so on... 5/6
"Quality is a bar, not a tradeoff." This is one of the first things I bring up when discussing quality. Your users notice your bar. Your team and others inside the company notice your bar. And they will act accordingly. Don't lower your bar. 6/6
medium.com/the-year-of-th…
medium.com/the-year-of-th…
