How to structure your system design answer in 45 minutes?

i consistently run out of time in 45-minute system design interviews. i feel like i have a good grasp of the concepts, but my time management during the actual interview is poor. i usually spend too much time on requirements gathering or a specific deep dive. i'm looking for an ideal time allocation strategy. for example, how much time should be spent on clarifying requirements, high-level design, diving into a specific component (e.g., database or scaling), and then wrapping up with trade-offs or future improvements? what's a typical breakdown that allows you to cover enough ground without rushing the ending?