When scope shifted I made deliberate cuts early instead of trying to preserve everything. Prioritizing strong core flows over partial coverage across all features ensured the product remained cohesive. A focused experience is always more valuable than an incomplete one. When feedback cycles slowed I introduced more structure by documenting decisions and building buffer into internal deadlines. Establishing clarity earlier reduced pressure later, and I applied this approach progressively throughout the project. When escalation was necessary There were moments where involving the professor as a stakeholder was the right decision. Recognizing when to escalate — and doing so without hesitation — is part of effective leadership. The priority is always the success of the product, not personal ownership. What I would implement from the start I would establish regular, lightweight check-ins with each team member — not to micromanage, but to surface blockers early. Small investments in structure at the beginning prevent larger issues later in the process.