list best practice

Here's the consultant answer: it depends!

If the list is used across your instance (i.e. internal seed list), put it in the lead database.

If it is related to a certain program, keep it there.

Lists cannot be created in Design Studio. Perhaps you meant Lead Database?

My rules:

Global lists, regional, things that will be used often --> Lead Database in a clear folder structure
Imported Lists- -> Lead Database with dates in the name.
Any sort of automated static list --> Lead Database


Local Lists, reports, scratch pads: best at the Program Level.

Yes and thanks

You both gave great answer - so i cant click best answer ... pssh ~

Hi Josh, Can you elaborate on your answer? Jason made a point for program lists at the program level.

Yours is more detailed; however, I dont completely follow. You mention usage as a determination; however, being that we want to send emails to all our lists commonly, that would mean to use no program level lists. 

Also, you can use a list from program A within program B with the correct name spacing (correct?), so what is the best practice if this is the case anyway?

As always.thanks ~