I know a lot of SharePoint consultants that implement solutions that are more or less “standard” SharePoint. They are afraid to (think out of the box) change SharePoint according to the end user’s needs, because it will result in tough maintenance in the long run.
The problem is: SharePoint is a generic tool for generic problems. But if I have a specific need which can not be satisfied with standard SharePoint functionality, then why should I use it? After all, you hire a tool to get a job done…right?
Here is my advice to most SharePoint consultants:
Don’t rush into (SharePoint) solutions . First try to understand the user and its needs, this will make you understand what real problem you need to solve.
Try a methodology called: Design Thinking