Yeah, I don't think there is any meaningful distinction there. I think Pierre is just framing things in terms of solving for teams that work with product + design + engineering to ship something to users that involves all of those parties, whereas GitHub has primarily catered to engineering.
Today in software companies there is basically a gap where each discipline kinda prefers to work in it's own software silo (eg. Asana / Figma / GitHub), but that doesn't really make a lot of sense from a fundamental standpoint where all of those aspects of a team want to work very closely together. You end up kinda syncing a lot of info/state across the silos, or via meetingss/slack etc, so I think Pierre is trying to bring all that into one tool with some opinionated workflow. Makes a lot of sense from my perspective, curious how it ends up working out.
