We encourage our clients to provide feedback with suggestions for improvements to our software. However, we don't always act upon these as they have to fit with the aim of our software and follow the process mapping methodology. A suggestion that doesn't follow the aim or methodology can often be solved in a different way.
While mass configuration options seem to becoming more and more widespread we try and focus on it just working. The Isoma configuration is kept to a minimum and ideally undertaken at the start of the project. We find this improves consistency of the work produced and lowers the risk of re-work as all users understand and follow the same methodology.
No one wants friction in their products. Everyone works to reduce it. Yet it sneaks in everywhere. We collectively praise a service, app, or design that masterfully reduces friction. We also appreciate minimalism. We love when products are artfully distilled down to their essence. How do we achieve these broadly appreciated design goals? Frictionless and minimalism are related but not necessarily the same. Often they are conflated which can lead to design debates that are difficult to resolve.