Agree -- 1:n is the safest approach if you don't know, but 1:1 has its place. I think the core thing I've learned over time (in a startup) is that I rarely act

Agree -- 1:n is the safest approach if you don't know, but 1:1 has its place. I think the core thing I've learned over time (in a startup) is that I rarely actually know for sure if there should be more of something, and 1:1 tends to create more "permanent" or "hard to reverse" changes to the way you design your system.