Blogs

Intelligent Design

Hsld/Ind 2.0 - Comm's and Addresses

The project known simply as "Household/Individual 2.0" is a key building block in the overall re-design of Fellowship One.  We are excited to share our design ideas based wholly on your feedback of our product over the last several years.  We can’t afford to simply build this stuff in the dark and then spring it on you, so we are sharing this design step with you to help foster a better design/workflow/experience; your feedback is very important!  Please take the opportunity to shape this project by reviewing each of the following videos and commenting as you can.  In addition, please ask others who have an expertise in the area to review it and comment.

Thanks.

Forward: Household/Individual 2.0 Overview
Chapter 1: Household Members
Chapter 2: Involvement
Chapter 3: Giving
Chapter 4: Contacts and Notes
Chapter 5: Comm's and Addresses
Chapter 6: Basic Info
Chapter 7: Attributes
Chapter 8: Requirements
Chapter 9: Forms
Chapter 10: Gears, Groups and Dupes


Comm's and Addresses from Fellowship Technologies on Vimeo.
Published Wednesday, August 06, 2008 7:26 PM by CurtisHarris

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

sGilliam said:

We have instances where the parents are divorced and the kids are in two different households.  I'd like to see a function where the kids can have a primary and secondary household address.  That way if mom brings them one weekend and dad the other, we won't have to have the kids in two seperate entries.  Hopefully that makes sense.

August 6, 2008 3:19 PM
 

CurtisHarris said:

@sGilliam obviously the best scenario would be to create one person and associate the person to two different households; this is on our radar but not part of this project (talk about a ripple through our software, not a small project). So, anything besides that is a bit of a hack... could you instead use "alternate address"?

August 6, 2008 4:13 PM
 

jschneider said:

Curtis - I think it would be helpful to have some very small graphic to identify whether a communication item is inherited from the household rather than always having to hover order the icons you have. Something like a "small graphic with a white letter H in a blue circle" for a household comm item and a "small graphic with a white letter I in a green circle" for an individual comm item.

August 6, 2008 7:13 PM
 

jschneider said:

Curtis - Okay, this may be more an "Idea" than a answer to your question...but here it goes. With regards to the priority order, I know that we have some people that say - call me on my wireless first always.  Others say - call me at home and then work, then wireless. It would be great if we could priorize the contact order for each individual. Then the system displays it in what ever order specified for that individual.

August 6, 2008 7:24 PM
 

CurtisHarris said:

@jschneider why? Why is it important to know that the home phone shown is associated with the household vs. the individual?

August 7, 2008 9:34 AM
 

CurtisHarris said:

@jschneider you hit the nail on the head when you are referring to contact order for each individual.  We have identified that project (it is on the IDEAS tab) and certainly see it as a valuable one, but... to keep this replacement in scope we need to keep "feature creep" to a minimum and that project is not a small one; we would need to touch everything from reporting to check-in to email.

August 7, 2008 9:37 AM
 

jschneider said:

Curtis, to answer the "why" question, let me give you an example. Let's take a family where the a teenage child in the family has a personal "home" telephone number (less common now than in the past) and a wireless telephone number (very common now). I think being able to bring up that teenager's record in F1 and being able to quickly identify the telephone numbers identified with that individual (separate from the household) would be helpful. And in the case of email, my families household record has two email addresses - one mine and one my wife's. It would be helpful for someone to easily identify that those email addresses are from the household level and that that third one listed is for the individual in the family (like one of my children). To me a little icon identifying household or individual is easier and more time saving than having to hover the mouse over the entry.

August 7, 2008 7:09 PM
 

gstarnes said:

Divorced parents become irate if their name is not associated with their child. It would be most helpful to have dad's address, mom's address, and designate who each child lives with.

August 13, 2008 3:02 PM
 

gstarnes said:

Today's household frequently does not have a home phone number. When posting a cell phone number, the best contact us usually (but not always) mom's cell phone.  To create a phone tree list, a home number must be posted. So that means we must post a cell number designated as home phone number, then post it again under individual as a cell phone.  There's got to be a better way!  

August 13, 2008 3:04 PM
 

CurtisHarris said:

@gstarnes I agree with both of your posts, but both are enhancements outside the scope of this project.  The best thing you can do is use the IDEAS tab and vote. Since January of 2008, we have been able to address 31 of the top 100 ideas and have another 20 we are working on; it does work.

August 13, 2008 4:07 PM
 

Dan Lott said:

Don’t separate them into two sections.  Show all comm’s and addresses in same area for household or individual (1.0 shows it this way).

August 18, 2008 2:17 PM
 

Dan Lott said:

Clearly show an H or I without requiring a hover.  Both in contacting people and working with changes knowing which value you are seeing speeds the decision or action

August 18, 2008 2:17 PM
 

Dan Lott said:

Show date beside the value on the summary list.  The date is a trigger for seeing how recent the entry/change occurred.

August 18, 2008 2:18 PM
 

Dan Lott said:

Previous address should show with household or individual.  This gets used a lot particularly in splitting households and in new marriages.

August 18, 2008 2:18 PM
 

Dan Lott said:

We prefer an address order of Primary, Previous, Business, …

August 18, 2008 2:20 PM
 

Dan Lott said:

Add gender, Former Name, Goes By Name, and Tag Comment as priority elements.  These are the first things that are the most critical for viewing individuals and determining changes that may need to made. Former Name is important because of marriages, divorces, and blended families.  These are always changing.  Tag Comment is important as we work with check-in.

August 18, 2008 2:20 PM
 

kdorado said:

This is looking good.  I'd like to vote that you use Google Maps. Also, the highlighting for returned/incorrect address is great.  Any way to add that option for a communication?

August 18, 2008 5:36 PM
 

awhitworth said:

I like the map link that will be very helpful.  I also like highlighting or flagging of possible errors.  We are new to F1, but at this point I would say primary contact info would be displayed first.

August 19, 2008 2:49 PM
 

Gail Andersen said:

A little off the topic--but is there a way to add basic info (say like new registrants for an activity like the former Add household page. I really like that quick add better than the Add new household where you have to scroll down through so much info. That info can be added later, but I need the availability of the quick 1-page add to put in the members.

August 29, 2008 2:24 PM
 

srunte said:

Absolutely, love the google earth map option!!!!

November 19, 2008 11:43 AM
 

srunte said:

Curtis - It would be great if we could have the default option, as home, cell, Email.  Then have the opportunity to choose on each individual to priorize how they tell us how they want us to contact them.  And put button number 1, 2, 3 by each communication.  So, when each staff looks on the screen, we can easily contact in the order the person wants.

Thanks!  Have a great week!

November 19, 2008 11:55 AM

Leave a Comment

(required) 
(optional)
(required) 
Submit