Development – How much functionality is too much?

Home / Blog / Development – How much functionality is too much?

Well, if you’ve been paying attention, I’m working on adding new functionality to Rapier.  While much of what I’m adding is a “no brainer”, I do start to question, how much is too much?  Right now, I’m working (mostly) full steam ahead on Rapier 2.0.  That means new functionality, new screens and new options based on things I’ve heard from potential customers.  Now, the problem comes when I start to over think things myself.  For example, I was working on enhancing the “My Notifications” portion of Rapier.  My original version just showed the notifications, but there was a request to show all of the follow-on documents as well.

Here’s where the analysis paralysis can quickly set in.  I see this functionality and think, cool…  But…  what new columns should I add, just in case a customer wants them?  Should I allow the functionality to be turned on or off?  Should I allow it be turned off for just end users, or for existing customers?  Do I allow the customer to configure the columns?  the sort order?

See where I’m going?  I could think this thing to death.  It’s one thing if I have a specific customer request, but when I’m thinking of everything a customer might want…  well, where does it end?

So I’m trying to reign myself in.  I’m going to continue providing any functionality I’ve provided for other screens, with the realization that customers may ask for more, and I can always add it later.

I’d love to hear your thoughts…  how do you determine where to stop?  do you purely go with what a customer asks for?  do you put it all in there?

Thanks for reading and I look forward to your thoughts.

As always, thanks for reading and don't forget to check out our SAP Service Management Products at my other company JaveLLin Solutions,
Mike

Leave a Reply

Your email address will not be published. Required fields are marked *