To find common grounds for success while scaling a cloud based system, the key is to align all stakeholders with common goal. - Understand the extreme boundaries of impacted attributes that each stakeholder might have a concern - Understand the relation between them. (Eg, directly/ inversly propostional to other attributes, etc) - Capture assumptions & tradeoff considered to decide the scaling goal - Arrive at the range for each attributes that is technically & practically feasible as per each stakeholders expectations (Might require several iteration to arrive at final expectation) - Post agreement with each stakeholder, finally execute the plan towards successful execution

When scaling a cloud-based system, collect a list of problem statement/pain areas from the team related to the existing system. These would (and should?) overlap with many aspects of the problem statement that drove the decision to scaling the cloud-based system. - The solution to these items become the objectives. Now drive the discussion around solutions and present the option that is chosen and compare with other solutions if anyone had. - This creates a common ground and buy-in. Then document the missing areas as per discussion - These become spikes to explore and technical debts. Chart out execution goals/ phases of iterations that might be needed. - This becomes the vision of scaling process.

When debating scaling a cloud-based system, I focus on fostering open communication and a shared understanding of goals. I encourage the team to outline their perspectives, ensuring every voice is heard. By framing discussions around data, system metrics, and user impact, we ground decisions in facts rather than opinions. Aligning on priorities, whether it's performance, cost, or future-proofing, creates a clear roadmap. Collaboration, coupled with a commitment to the system's success, helps us find common ground and move forward with confidence.

Scaling a cloud system? Team alignment is key! Here's how I roll: Shared goals: Make sure everyone’s clear on the why behind scaling. Open discussions: Hear out all perspectives—risks, rewards, and everything in between. Compromise & commit: Find the sweet spot and get everyone on board.

Always started with understanding the business case for the change. Identify functional (business) and non-functional requirements (operational costs, security) requirements that will inform the design. Identify stakeholders. Not only decision makers and "C-suite" members but also influencers and those impacted by the changes. Make sure their needs are appropriately factored. It's almost a given today, but rely on automation in scaling to reduce operational overhead. Infrastructure as code is helpful here, regardless of your preferred solution in achieving it. Last, if the workload needs to be elastic, don't forget to account for scaling back down in your design. Keeping costs down will win support from business folks.