Getting from the strategy to the tests

Our test team have had a bit of feedback, which was nice, but it's left me struggling to think of solutions.

The feedback: "I'd like to see how the test team go from the test strategy, to the test cases, and I'd like that process to be more visible to a wider audience".

This sounds like a request for a test design walk-through, which we don't do, and never have. It's usually just in tester's head this part isn't it? We write a strategy which says what we're going to test, how long it'll take, how many testers we need, what environments we'll test on and how much it'll cost and then we get some testers, or scripters, and we write the tests before we get the product and start testing. If we're lucky, a developer might review some of our tests / planned coverage and highlight some inaccuracies but that's usually as good as it get's. And now someone wants us to make that whole thought process more visible; a reasonable request I guess.

Reality is, I haven't a clue how we'd do this and I haven't heard of people doing this elsewhere. Are people familiar with this kind of process? Do people need to do this? If so, how have you done this?

There's no reason why we couldn't write another document which details how we get from the strategy to the tests, maybe discussing risks and types of testing along the way but when we feel we don't get much input in to the strategy it's going to be difficult to think of reasons to justify yet another document...