Well, Thanksgiving weekend is here.  I signed up for my first ever half-marathon this Sunday… I’ve been training but let’s face it - its gonna clobber me.

A recurring theme kept coming up with my customers this week – the importance of paring down complexity for users by hiding or removing unused pmPoint elements.  Its not hard to do, yet so often this mundane step is overlooked.  The result is that team members, and project managers are puzzled by fields and webpart elements that haven’t been given meaning so everyone ignores them.

At BrightWork, we take pride in all the fields and options that are available in pmPoint.  Some of them look impressive.  But if your organization is not using a certain field, its best to hide it.  If a webpart is not relevant to your process, remove it.

This may seem obvious, yet we see this all the time, where the UI and captions have not been customized enough to fit the process.  In fact, we believe this is a leading cause of user discouragement and poor adoption during pmPoint deployments.

You can clean up New Item and Edit Item forms on pmPoint lists in the Column Visibility settings (Settings | List Settings).  If you are concerned that you may forget something that you may want to use later, take advantage of the sample templates and reports on www.brightworkdemo.com.    Then go ahead and hide it in your environment.