It's interesting that you mention it's important for as many people as possible in the organization to read and remember your test strategy. I infer that by default, people will not read or remember your test strategy. That tells me you want a document that is both instructive and persuasive. If you want someone to read all the way to the end, you ought to start by telling them why they need read and remember it, i.e. why they should care. If you're a powerful writer, it is possible that you can take something as -- let's be honest -- dry and uninspiring as a test strategy document and convince people it's important. On the other hand, if you write on par with the rest of us, perhaps a leader in your organization needs to impress upon the team why the test strategy matters.
Persuasion aside, I think you should cover the goals that the test strategy seeks to reach, the technology you intend to use, and the schedule you need to follow.