Designing a light weight UX process for small teams

-



Designing User Experience (UX) is a crucial step in the new product development process.  The process shall help the product develop a personality and deliver the value proposition. UX design process needs substantial investment from development team and business users. Small teams may not have the time and resources to go through the full process of User Research, Modeling, Requirements Definition, Design Framework, Detailed Dev Sprints and Ensure Success (Metrics). 

The following points shall help us keep the process on target. 

1. Always have a mother ship - Latching on to a well established UXD horizontal in internal/external organisation will take burden off the team. By doing so you automatically subscribe to it's principles, policy, patterns, design guides, standards and tooling. 

2. Pick the top 3-4 principles - Don't try to boil the ocean. Understand the top 3-4 important principles and their order of priority. 

3. Reduce tooling overhead - You don't need to use highly sophisticated prototyping and mockup tool to make it work. Paper, pencil and ruler can do wonders. 

4. Drive business ownership  - Most important part is to keep the business involved and engaged through out process. At the end of funnel, core team shall feel emotionally invested in the product and out come. Use Design Thinking methodology to identify and solve the core business problem. 

5. Stick to UI basics - Get the fundamentals of UI design right. 

6. Don't try to please everyone - My favourite. Trying to please everyone, pleases no one. 

  • Alignment – Be purposeful not ambiguous  & visually connect elements 
  • Proximity – Group relevant times 
  • Consistency & repetition – Show relationships. Signify special elements. All headings/subheadings related items should have same style (color, font, weight) 
  • Contrast – elements should be contrasted for better readability and content arrangement. Use color shape, size, position & orientation  
  • Color – Be purposeful not ambiguous. Use JDA colors for content. Use gray shades for contrast, labels.  
  • Typography – Open Sans, Skopex Gothic. Use all caps sparingly. Use size > 10 
  • Visibility – Be wary of fold of the webpage (resolution changes fold), scrolling. Don’t make your content look like an Ad or banner, people will ignore it.  
  • Understandability –  Users don't need a help guide to understand the product
  • Simplicity – make things easier  
  • “Space is like AIR, let your design breath”  

 

In my experience, I got an opportunity to drive a sales engagement platform end to end with a team of 3 web developers.  

  • Our Mothership - Internal UX Team & Salesforce UX Team for principles https://medium.com/salesforce-ux/building-an-enterprise-framework-is-hard-1e8d8b33e082#.8yvulggjm for more details.
  • Principles
    • Clarity - Users shouldn't require a help guide/video to use the product
    • Efficiency - Less number of clicks/effort from user
    • Consistency  - All form factors should look and feel the same. 
    • Beauty - It's should look good. 
  • Process 
    • Proto-Persona - Don't get bogged down by interviews and user research to define Personas. Describe target users based on stakeholder assumptions. 
    • MindMap - Conduct 2-3 focussed design thinking sessions and MindMap the findings all the way. 
    • Sketch - Pencil and Paper worked for us.  
    • Iterate - until business sees value 


Image credit IDEO http://bit.ly/2a9RrNK​

Comments

Post a Comment

Feedback - positive or negative is welcome.

Popular posts from this blog

Updating SourceData/ Data Source of the Pivot Table

-
Image
Errors:  1. Run time error '1004' Cannot Open PivotTable source file https://....[servlet.FileDownload?]... 2. Data source reference is not valid 3. Can not use web data source as pivot data 4.  Run-time error '-2147024809 (80070057)' Item with specified name wasn't found 5.  Error: Cannot open PivotTable source file ‘[filename[x].xls]SourceData’ 6.  Exception from HRESULT: 0x800A03EC   at System.Dynamic.ComRuntimeHelpers.CheckThrowException(Int32 hresult, ExcepInfo& excepInfo, UInt32 argErr, String message)    at CallSite.Target(Closure , CallSite , ComObject , String )    at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)    at CallSite.Target(Closure , CallSite , Object , String )    at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1) Solution: We have spend a day searching around for the solution. We ...
Read more

Salesforce.com migration tool - Deploying Weblink and migrating files with special characters

-
Image
Recently, I noticed the followed issues in SFDC Ant deployment. Issue 1: Typo in XML <name> metadata data for Web Link Just to reiterate, all the buttons and links created under "Buttons and Links" section of the Object are treated as Web Links . Screenshot from Force.com Migration Tool Guide It should be WebLink, not Weblink. Otherwise, the following error occurs while extracting the package :  package.xml - Entity type: 'Weblink' is unknown. Correct XML is:  <types> <members>Opportunity.Cancel_CheckOut</members> <members>Opportunity.Generate_Deal_Sheet</members> <name>WebLink</name> </types> Issue 2: Unable to deploy entities with special characters Example: <types> <members> User w/Export  </members> <name>Profile</name> </types> I tried to deploy Profile entities with special characters like '-' and '/...
Read more

Information Architecture - Setup your term store to scale

-
In this post I am going to put together a list of best practices to consider when setting up a term store in Sharepoint Online. As you may already know term store is collection of term groups. And each term group consists of number term sets. Each term set contains a list/hierarchy of terms. Team group gives the flexibility in terms of access. You can assign permissions to users on their term group, rather than giving them access to the entire store.  Always maintain a corporate/general term group which contains common term sets across organization.  Every group/business unit should have a term group. Pin the terms from corporate term group as required into Business unit term groups.  For example, you plan to maintain list of document types in common term group. Thus, there is a term set created. Marketing department want to use this term set. But, they want to add a few more terms. In this case, you should create another term set in Marketing department term g...
Read more