Skip to main content

UCD Process

Over the last couple of years UCD (User Centered Design) has become a buzz word just like RWD (Responsive Web Design). 5 years ago when I wrote my SharePoint Branding book I use to call it the 4D’s of User experience. It included Discovery, Definition, Design, and Development. I had a nice little picture and everything to depict the different phases.

Now the picture is much nicer and clean however, I really don’t think it matters what you call each phase it matters more what you do within them. I have seen so many different variations sliced and diced in different ways. To me it is about adjusting your approach based on the needs of your users and your client. In a more traditional waterfall project you have a tendency to over burden yourself with documentation because there is no chance of going back. Also those types of project are usually the ones where you scope out in the begging a full solution without ever fully knowing what the real need actually is. I would much rather only scope the first couple of phases to really truly understand what you are dealing with before you can even imagine what the technical effort would be.

The biggest shift that I have seen though a more refined UCD approach is really focusing on the first phase which is understanding who the users are, and what are their needs. This is a shift in getting away from just focusing on Functional Requirements but diving deeper and truly understanding individual user needs. In the past I used to focus on how to customize and configure a tool like SharePoint to give the users a somewhat tailored experience. This did not always provide the users what they needed but it was better than nothing. I do have to say it is really refreshing being able to go into a project technology agnostic. To me it sometimes feels like you are trying to put a square peg in a round hole if a technology has already been defined by IT and there is no clear use case or need from the users on how they will use it. This is a clear case where user adoption will become an issue and it will be a big waste of time and money.

One other shift I have noticed over the last few years is that personas have really changed their meaning and purpose. We use to define different personas based on their organizational structure (HR, IT, Sales) or by their permission roles (Admin, Contributor, Reader). We also use to focus more on their demographical information such as (Age, Location, Device Types) which really did not provide much value.

I think due to the fact that I spend more time diving deep through user interviews to gather as much as I can about their day to day activities. Learning more about what their pain points are and identifying commonalities with all that we have met with. This helps drive better insights into who those core personas will be and not just based on a title or a role. These types of personas will help us during the definition phase when we start to translate their user needs on to paper.

Not every project needs to have a full set of polished personas, but at least some level of understanding who you are designing the application for. For the most part the 4D’s still hold up pretty well but like I said before it really does not matter what you call each phase so long as you are providing value in each one of them.

Popular posts from this blog

SharePoint 2010 Base CSS Classes

This will be the first of many SharePoint 2010 posts. I will be focusing on a few of the main CSS classes used for SharePoint 2010 Public Beta. As the product becomes more final there might be some changes to the class names but I will be sure to create a new post if that happens. This will be quite a lengthy but it should be helpful. The default CSS given below are just highlights of the full CSS attributes for that class.I will be using a basic team site as my base for the screenshots. Here is a basic structure of the main areas that I will cover.Ribbon RowTable Row Left Site Actions Navigate Up Edit Tab List Browse Page Table Row Right Give Feedback Welcome Menu WorkspaceBody Container Title Row Title Title Logo Title Text / BreadcrumbPage DescriptionSocial Data SeparatorI like It Tags/Notes Top Header 2/Top Links li Static-Selected li Static SearchHelpStatus Bar Container Main A…

How To: Hide Left Side Navigation on Home Page

I was recently asked: "How can I hide the side nav bar on the main homepage layout ?? I want to be able to use the side NAV with in the team site etc etc, but I don't want it on the front page.. " There are a couple of ways to do this in SharePoint 2010. If you are using a non-publishing site you can add a Content Editor Web Part to the page and add the following to the HTML Source.
<Style>
body #s4-leftpanel
{
display: none;
}
.s4-ca
{
margin-left: 0px;
}
</style>
Basically the CSS above hides the left navigation Div, and then sets the content area to not have a left margin. Once you are done, simply modify the web part and hide it on the page. If you are using a publishing site for your homepage simply add the same styles specified above to a custom page layout. That way if you have a need for other pages that do not need the left side navigation you can re-use the page layout.

Small Calendar for SharePoint 2010 & 2013

First off I would like to apologize for the lack of posts. I have been really busy with my new role as the UX Design lead within Slalom Consulting Boston. I will share more about that in another post. In a previous post Create Really Small Calendar I showcased how to do this for SharePoint 2007. However the 2010 and 2013 calendar views have changed and therefore we cannot use the same method or CSS as 2007.SharePoint 2010 Small Calendar:
SharePoint 2013 Small Calendar:
See video below for a video walk through on how to create a small calendar for SharePoint 2010 and & SharePoint 2013 with just CSS.Per the video above here is the code that I referenced:2010 CSS link reference in Master Page:
<SharePoint:CssRegistration name="<% $SPUrl:~sitecollection/Style Library/smallcalendar.css %>" After="corev4.css" runat="server"/>2010 CSS:
/**** Small Calendar ***/
.ms-acal-item{height: 10px !important;}
.ms-acal-sdiv,
.ms-acal-mdiv,
.ms-…