From the early stages of my product's development (eg, the product I work on, but my employer owns it) we already had decades of experience in this market and understood our customers' business. We had already been through two green-screen text versions (eg, first and then major rewrite), one desktop GUI version (major rewrite), and then to the web. We pay attention to customer feedback. I am interested in feedback, especially negative feedback. In short, we've been doing this for a long time (decades). It's not some johnny-come-lately web application.
The more customizable you make software, the more complex it is to design, maintain, then configure for a customer, and then use by the user. Definitely have necessary customizability. Avoid that which is unnecessary. Understand the customer's business and workflow. Design workflows around that.
-- The lower I set my standards the more accomplishments I have.
(Score: 2) by DannyB on Friday April 03 2020, @03:20PM
That is true.
From the early stages of my product's development (eg, the product I work on, but my employer owns it) we already had decades of experience in this market and understood our customers' business. We had already been through two green-screen text versions (eg, first and then major rewrite), one desktop GUI version (major rewrite), and then to the web. We pay attention to customer feedback. I am interested in feedback, especially negative feedback. In short, we've been doing this for a long time (decades). It's not some johnny-come-lately web application.
The more customizable you make software, the more complex it is to design, maintain, then configure for a customer, and then use by the user. Definitely have necessary customizability. Avoid that which is unnecessary. Understand the customer's business and workflow. Design workflows around that.
The lower I set my standards the more accomplishments I have.