This though has come up for me several times and I never feel like I get it quite right so I will be very interested to hear how others are doing this. I am just really happy in the new JOs you can rename programs where that was not previously the case. 

Since the names can get cut off depending on screen size or the width of a field in reporting I try and keep that in mind with the naming. We also use JO a lot for internal emails as part of automations where CTAs are not a good fit or we need to update someone who is not a user of GS. 

Ours usually look like: 

Internal/External | Segment Product Outreach Description Geo

For one time sends, I typically do:
YYYY MMDD Outreach Name

For monthly recurring (ex: monthly check-ins, etc.), I do:
YYYY Month Outreach Name

Recurring sends are a bit of a different beast. Not sure where the post is, but there’s an idea that mentions adding a “tag” column for JOs and Email Templates, which would be a fantastic way to remove the dreaded “v2, v3” versioning issues we’re plagued with.

So you don’t distinguish between audience type? We typically use HT (High Touch) when a CSM is assigned to the account and TT (Tech Touch) when no CSM is assigned. 

Our segmentation usually determines the high vs low touch or level of CSM engagement. We have 4 different segments or what we are currently calling service levels Foundation, Standard, Standard Plus, and Premium but we have not done a lot of JOs that differentiate by service level. We typically include all then in the email template we will have versions if we need to have a tech touch default where there is no CSM assigned. 

We do, but a lot of it depends on the program. And we usually distinguish between private (commercial) vs public sector, and/or email communication type (HTML vs defanged).