[rgoulter]

Hmm. "poor software design" suggests a high risk that something might go wrong; "poor development practice" suggests that mistakes won't get caught/remedied.

By focusing on particular errors, there's the possibility you'll think "problem solved".

By focusing on process, you hope to catch mistakes as early as possible.

[DamonHD]

When trying to make better systems in moderately-critical roles (investment banking, not medicine though) my approach was both try to understand and fix the immediate fault, but also find out if (and fix if so) any systemic issue that would make other related errors likely.