How to make retrospective review
Retrospective is a look into the past. The story of how this or that program, a line of devices, a company, and even the whole field of knowledge or industry has been developing. Retrospectives entertain the reader, but at the same time they help to make a picture of the world more complete and more accurate.
Try to find everything you can on the Internet. If you find any paper sources, great! — they're less likely to be read by anyone than articles on the Web. If you can find eyewitnesses of the events, that's fantastic.
From what you found, highlight the most significant events and put them on a timeline.
How to write
For those who prepare a retrospective review, we can give the same recommendations as for any other format: write simply and clearly — as if you were telling this story to your friends.
It is good when clear milestones are passed through the text, which will help the readers to relate what was happening to the history known to them. The most obvious thing is to specify years or exact dates, if they are important. But there is also a more textual way — to point out the significant events that took place at the same time.
In 1983, Microsoft expands its influence beyond the United States by creating new products (Microsoft Mouse) and Microsoft Press publishing house.
In 1983, Microsoft expands its influence beyond the United States by creating new products (Microsoft Mouse) and Microsoft Press publishing house. The same year, Apple launches the Lisa computer.
What to tell about
The main advice is to write about what's interesting to you. If you while preparing said "Wow!" to yourself, most likely it will be interesting to others. To test it, tell a couple of facts to your friends or colleagues and look at their reactions.
Iconic programs, gadgets, companies, services, trials — you can write retrospectives about any of this.
How much to write
Write as long as it takes to tell a story. But if you feel that there is a monster article 100 thousand characters long on the horizon take a break and think: shouldn't you divide the text into several parts and release them once a week? The main thing, do not forget to give clear navigation between the parts.