Scheduling larger, non-user-facing features

We had a long chat in our #scheduling Slack channel about how we do things currently. This is my perspective:

1. Major features, or things that are linked to our overall product direction, go through product.
2. If sales have a specific request, IMO that should also go through product to ensure it's lined up with our goals.
3. The majority of support and production issues are bugs, or smaller enhancements that make our lives less painful - like adding spam checking to snippets. a PM doesn't need to waste their time with that, because if we need to do it, we need to do it.
4. Those bugs and smaller issues, including support and production priorities, should go through the lead.

For the fourth item, support and production leads can ping the relevant team lead on the issue, and use the Slack channel for follow-up if something's missed / slipped / etc.

However, this is missing a category of issues, which @pcarranza explained:

from production there is a but regarding the kind of things we ask for: we may be requesting an architectural change to cope with scale, those are not small things to do. How do we deal with those?

I don't think we have a good solution for that written down to me. For Geo DR, we have an ad-hoc team with @stanhu as lead, and @dbalexandre, @rspeicher, and @brodock working on it. This seems like a reasonable model to me, and I wonder if we could extend it.

@pcarranza wdyt? Can you link to some issues in this category?