How to structure your system design answer in 45 minutes?

I often find candidates, and even myself sometimes, running out of time during a 45-minute system design interview. It feels like there's so much to cover: understanding requirements, high-level design, deep dives into specific components, and then discussing trade-offs and future scaling. What's your ideal time allocation for each phase? For example, 5 minutes for requirements, 10 for high-level, 15 for a deep dive, 10 for trade-offs/scaling, and 5 for questions? Or is it more fluid? I'm trying to find a balance where we cover enough depth without rushing through important discussions or cutting off the interviewer's questions.