Another workflow I use, which again is using Studio as an authoring memory system, is one I call "Monolingual Track Changes in PowerPoint" which is useful as I get a lot of PowerPoint presentations to review, frequently written in English by non-native authors (second language authoring ("2LA") also being increasingly prevalent, who have presentations in working groups that they ask me to check. One of the weaknesses of PowerPoint is the fact that there is not the same track changes feature as in Word (track changes in PowerPoint from the 2013 uses the Review > Compare feature. SDL Studio's bilingual preview mode (Ctrl + P in Editor mode) is particularly useful as I often have to go through slides with colleagues and can then see what has been changed.
In addition I also have a Monolingual Termbase that I use in conjunction with this workflow that I use in conjunction with a QA terminology check, as a way of trapping frequent errors and also AutoCorrect entries to correct numbers (e.g. where the English presentations continues to use German abbreviated forms for millions and billions). As I have a lot of regular customers who tend to be consistent in usages (ie. the same changes are often required between one presentation and the next where they write from scratch on each occasion). One colleague has asked me before now if I am aware of mistakes he regularly makes - and by using a job number in each project which includes the customer's in-house abbreviation (we all have three letter abbreviations eg. ABC or BAI etc.) coupled with a "user" field in the Termbase, it has helped some improve their authoring by being aware of what frequently gets changed.
When the target language version presentation is generated, it can of course also be compared and reviewed in PowerPoint if required. The only downside is that sometimes the formatting needs checking in PowerPoint afterwards.