I was thinking about a hypothetical bucket overhaul on SP and how annoying it would be to, for example, make a new bucket for coworkers that has access to every person but only a few fields...
I finally realised that buckets can and should be separated between people, groups, and fields, not just the friends in the bucket.
We have over 350+ people, so the plain friends bucket can be the basic bucket that everyone gets. Most people would also get groups and all fields [though we already have a bucket for the nsfw fields that is an add on to the friends bucket] but in the case of coworkers, they don't need to see the groups and they only need a few basic info fields, so instead of making a coworker bucket and assigning it to the few fields and every person, I can just remove the friends field from all the groups and fields and make separate buckets for groups and various levels of field access. Three cheers for efficiency.
This may be obvious to other people but it wasn't to us ¯\_(ツ)_/¯