This applies to internal emails, especially requests to management chain. Whenever possible, aim to keep emails to two lines/sentences max, and put the request always first.
This depends on your management. If they trust you, and typically give you what you need, sure.. request first. But if they are more the kind where it is like pulling teeth to make changes or get more resources, then no - first you need to establish the reasons behind your need, explain the negative impact to the team, propose a solution, and explain how it will benefit the broader organization. You still need to do that all concisely, which is a challenge.
I've used that pattern in emails quite a bit since our company was bought a few years ago, and it works far more reliably than when I just send off a short request.
Sure, context matters. But an important lesson I learned only after 10+ years in the industry is that senior execs slice their time and mind-share very thinly. As a very junior engineer I would send out paragraphs explaining the background of an issue, discussions so far, proposals, etc, and sometimes I wouldn't even have an actual request. And then wonder why I got no reply.
