copyright @ Salesforce.org

                                                                                                                                                                                                             copyright @ Salesforce.org

Company: Salesforce.org

Role: Lead Product Designer

Team: Scrum teams

Responsibilities: End-to-end design, User research, Design strategies, Sketches, User flows, Early Conceptual Mock Ups, Prototyping.

Salesforce Nonprofit Success Pack (NPSP)

I was the very first UX designer at Salesforce.org back in 2015. Company's culture and philanthropy mission really motivate me to use my skillset to work hard so I can deliver great products to make our nonprofit organizations success. I work hand-in-hand with our product managers, developers and business partners to bring impact to the industry. 

Over the past three years, I have been working as a lead designer on Salesforce Nonprofit Success Pack (NPSP) - the world #1 CRM for nonprofits that helps nonprofits from fundraising to operations to programs and more. There are a lot of awesome features in the pack that empower our non profit customers grow their business, connect their non profit partners, manage their company data and most importantly reach out to and foster the relationship with their donors. 

Salesforce.org Customers report growth shows the percentage improvements in performance metrics for nonprofits and higher education customers. We help them raise more funds faster

+23% Faster Close of Fundraising Deals

+30% Increase in Funds Raised

My responsibilities include:

  • User Research
  • Information Architect
  • UX Strategy
  • Design System
  • Persona
  • User flow
  • Wirefram
  • Prototype
  • Hi-fi mockups 
  • User testing

Non-design role:

  • Evangelizing UX value, process and methods to stakeholders
  • Hiring more designers  

 

Here are some sample projects that I have been working on. 


Project 1: Data Management

Some non-profits generate large volume of opportunity records. Large data volume requires large storage space and adversely affects performance. Data management is likely to help non-profits that have >1M opportunity records in navigating these issues. 

 

Design Mocks

Design Alts 

old design.png
 

Project 2: Batch Gift Entry

 

Batch Gift Entry is a new feature for NPSP, we are still under construction.

Goal:

Optimizing non-profit organizations streamlines the process of entering gift records into Salesforce. 

Use case:

Nonprofit receives check payments from its donors, and these payments need to be manually entered into a "holding area" until they are ready to be committed into real donation and payment records. 

 

Key Features  

  • Batch Gift Entry provides a single screen to enter all the gift data you wish to capture. Within this screen you can look up related contacts, donations and payments, or add new contacts if needed. So you never need to leave the screen when entering batch items
  • CVS entry
  • Keyboard-friendly interface to make the entire data entry process as quick and painless as possible. 
  • Entered data is stored in a Batch. Each Batch consists of one or more Batch Items. Each Batch Item contains information about a single Payment.
  • Batches are not committed until user explicitly initiate a commit. 
  • When you commit a batch, all the items in the batch are copied into the appropriate fields in the Payment and Donation records.

Freehand sketches (process)

Screen Shot 2018-06-25 at 10.57.50 PM.png
Screen Shot 2018-06-25 at 10.58.44 PM.png
Screen Shot 2018-06-25 at 10.59.08 PM.png
Screen Shot 2018-06-25 at 10.59.33 PM.png
 

Design Mocks


Project 3: Engagement Plan & Level Management

An Engagement Plan is a set of tasks (literally a “plan”) that helps nonprofits engage with their donors, especially for the case of tracking engagement activities for Major Gifts. Major donors typically require a deeper level of engagement than other average donors. Engagement plans can help nonprofits from calling donor to schedule a lunch, then having the lunch with the donor, then sending a follow-up email to the donor, and so on.

 

Create an Engagement Plan Template

The Engagement Plan Template simply defines the set of tasks for the process.  

 

Sketch 

engagement plan.jpg

Design mocks with annotations

 1. Click the  Engagement Plan Templates  tab.    2. Click  New  to create a new Engagement Plan Template.  3. Give the Template a meaningful name, such as "Major Gift Follow Up".  4. You can configure additional options as shown 

1. Click the Engagement Plan Templates tab.  

2. Click New to create a new Engagement Plan Template.

3. Give the Template a meaningful name, such as "Major Gift Follow Up".

4. You can configure additional options as shown 

 5. Click "Add Task" to fill in the detail for first task. Now the tasks will be scheduled when an Engagement Plan is deployed.  Check "Send Email" enables the standard task notification email that is sent the moment the task is created.  Check "Reminder" enables the standard task reminder setting, which shows a pop-up reminder to the assigned user on the due date of the task.   6. Click  Add Task  to add another top-level task. Click  Add Dependent Task  to add a task that is dependent on the previously added task.  When finished, click  Save  at the top of the page.   

5. Click "Add Task" to fill in the detail for first task. Now the tasks will be scheduled when an Engagement Plan is deployed.

Check "Send Email" enables the standard task notification email that is sent the moment the task is created.

Check "Reminder" enables the standard task reminder setting, which shows a pop-up reminder to the assigned user on the due date of the task. 

6. Click Add Task to add another top-level task. Click Add Dependent Task to add a task that is dependent on the previously added task.

When finished, click Save at the top of the page.

 

Assign an Engagement Plan to a Record

Engagemt_Plans_Create.png
 

Project 4: Create and Manage Levels

NPSP Levels give customer a way to track a donor's level of commitment and engagement based on criteria such as total gifts or number of hours volunteered. Levels for donors based on the total gifts they've donated over time.

For example;

  • Bronze Level: A donor who's donated $0 to $100 dollars
  • Silver Level: $101 - $1000
  • Gold Level: $1001 - $10,000 

This overtime donation information is important for helping to recognize milestones and determine how to continue building on and fostering the relationship with the donors. 

In addition, Levels work with Engagement Plans so nonprofits are able to outline what, who, how, and how often to communicate with the constituent and keep them moving up the ladder of engagement.

 

Create Levels

Users only need to set up their levels once and thereafter NPSP will monitor the fields they've selected and automatically update related Level fields on a nightly basis.

Design mocks with annotations

  1. Level Name  —The Name that will appear in the Level field on the Account, Contact, or other object you've chosen. You must type in a name before you can enter any other fields.   2. Target  —The object that this level applies to. Select either Account, Contact, or other object you've chosen.     3. Source Field  —The field that will be totaled across all records to determine what Level the Contact or Account is in. For our example, we selected Total Gifts (a currency field) however you can select any currency or number field.   4. Level Field  —Remember that custom field you created earlier? Here's where you select it. If you don't have a Level field, you'll need to create one.    5. Previous Level Field  —This field is optional. It stores the previous Level value if the Level changes. Select the custom Previous Level field you created earlier.   6. Minimum and Maximum Amount  —This defines the range of this Level. You can leave Minimum blank to cover all up to (but not including) the Maximum Amount. Likewise, you can leave Maximum Amount blank to cover all amounts over (and including) the Minimum Amount (such as your very top level). Remember, Amount is not necessarily currency.   7. Engagement Plan Template  —If you want to have a series of Task Activities that are automatically generated when a Contact or Account reach a certain Level, this is where you would select that Engagement Plan. See  Create and Manage Engagement Plans  for information on configuring and using Engagement Plans.  8. Check " Active"  which will give your Level an appropriate Description

1. Level Name —The Name that will appear in the Level field on the Account, Contact, or other object you've chosen. You must type in a name before you can enter any other fields.

2. Target —The object that this level applies to. Select either Account, Contact, or other object you've chosen.  

3. Source Field —The field that will be totaled across all records to determine what Level the Contact or Account is in. For our example, we selected Total Gifts (a currency field) however you can select any currency or number field.

4. Level Field —Remember that custom field you created earlier? Here's where you select it. If you don't have a Level field, you'll need to create one. 

5. Previous Level Field —This field is optional. It stores the previous Level value if the Level changes. Select the custom Previous Level field you created earlier.

6. Minimum and Maximum Amount —This defines the range of this Level. You can leave Minimum blank to cover all up to (but not including) the Maximum Amount. Likewise, you can leave Maximum Amount blank to cover all amounts over (and including) the Minimum Amount (such as your very top level). Remember, Amount is not necessarily currency.

7. Engagement Plan Template —If you want to have a series of Task Activities that are automatically generated when a Contact or Account reach a certain Level, this is where you would select that Engagement Plan. See Create and Manage Engagement Plans for information on configuring and using Engagement Plans.

8. Check "Active" which will give your Level an appropriate Description

 

OTHER Projects