I was looking in the questions but couldn't find anything about it. There is a ton of info in the internet about bottom-top approach but still can't understand how it works in reallity. Any actual example projects would be great. I read many times that you as Senior/Staff should convince team/teams in an idea/project, and this is one of the ways to get promoted. An example - Staff Engineer created scope for 20+ people and worked on feature X. So my questions there:
I've always worked for top-bottom companies and even if we have an idea for a feature/improvement, eventually the management decides if we should go for it or not. After all, the management is the one "holding" the budget.
I highly recommend checking out this playlist (it's full of examples and tactics): [Taro Top 10] How To Create Scope As An Engineer
How does it happen?
It's generally through these steps (oversimplified):
These steps are oversimplified because:
Is there any management involved here?
In order to get full credit, you generally should involve management, at least in terms of making them aware of what you're doing (visibility is very important for growth).
How much you need management will vary from company to company as you alluded too. Some companies are slow, bureaucratic messes where you need permission to breathe (I recommend not working for those) and others give much more power to ICs (e.g. Meta and hyper-growth startups).
Lastly - For future reference, the terms are "bottom up" and "top down" culture from my experience. But I feel like your inverted terms are more intuitive.
I went 2/2 for projects that better defined the direction my team and made it onto my org's 2024 roadmap. Both projects are E5+ scope (imo) and require a significant time investment. The process was really simple:
While the process is simple, getting to that point was not.