Wait, this is just a train of thought... and it's got almost nothing in it. I'll save you the read: "Good software is produced by teams who represent the peopl

Wait, this is just a train of thought... and it's got almost nothing in it. I'll save you the read: "Good software is produced by teams who represent the people they’re building software for." I feel like this has to be backed up by something. I don't feel it's necessarily true, or even correlated with good software. Some good software tends to come from teams which have domain knowledge, but good software also comes from teams where not everyone on the team necessarily does. Sometimes just the UX team has the domain knowledge, and the programming team knows how to program really well. Sometimes they're one and the same. The author hasn't landed on anything here except perhaps "UX process is a relatively important part of creating good software." I'll offer a deeper answer. Good software is created by good process executed by people who understand both the importance of that process, as well as how to create. Knowing how to create is step one. You must master the craft of software first, and find people who also have, or want to. Good. Now you must understand process. As your software grows, it will cease to fit inside your head. You have to build systems surrounding your software that guarantee its quality, and bypass your feeble human limitations. Good. Now, as your company grows, you must understand people. The relationships and complex interactions and psychology will cease to fit inside your head. You have to understand the motivations and limitations of people in general, and your specific people, and make sure your company aligns them all in the direction of quality. You must build a company that values quality, and values the quality process, above all else. Build an organization which is aligned toward quality, and it will produce quality software. I didn't go into enough depth, but this guy did: https://en.wikipedia.org/wiki/W._Edwards_Deming https://en.wikipedia.org/wiki/W._Edwards_Deming But yes, for a team of one, it is probably closely aligned with how well you understand your users.