3di Information Solutions Ltd.

In this week’s #TCFilmFriday, the Doctor faces some harsh criticism in ‘Doctor Who’ when the TARDIS, his loyal time-travelling companion, takes on human form and scolds him for ignoring instructions. To make matters worse, we learn that even the most straightforward instructions, such as pulling instead of pushing the TARDIS doors, have been blatantly disregarded for 700 years, despite being clearly marked. Although the instructions are perfectly clear, the Doctor’s disregard for technical writing is evident. We attribute this to user error, awarding the TARDIS instructions a 9/10 and the Doctor a 0/10. https://hubs.la/Q02Tp_Nb0

Creating software can be a long, resource-intensive process. So why, after all this hard work, would you ruin your work with a poor localization effort? In this article, we take a look at some famous examples of bad software localization hampering the success of a software product, and what lessons you can learn from these examples. Read the articles at https://hubs.ly/Q02Wjy2p0

Ever wondered what life as a Technical Writer would be like? Some video games let you experience it first-hand. In this article, we explore video games where you step into the shoes of a Technical Writer, crafting documentation and perhaps even saving the world. Discover how accurately these games portray the role and what real-life Technical Writers can learn from them. Read more at https://hubs.ly/Q02W6hks0 #TechnicalWriting #TechComm #TechnicalWriters

This week on #TCFilmFriday, we’re diving into ‘Fallout’ – a post-apocalyptic TV drama where Maximus tries his best to protect Lucy MacLean from The Ghoul, a ruthless bounty hunter with a sharp tongue. Maximus, ever the hero, suits up in his power armour to buy time for Lucy and Wilzig to escape. But, as you might expect, things don’t exactly go according to plan. The Ghoul, a master of both survival and sarcasm, easily outmanoeuvres Maximus, throwing in a bit of mockery for good measure – ‘Well, I guess basic training ain’t what it used to be. ‘Cause you drive that thing like a bloody shopping trolley. Rule number one - read the manual'.’ The distraction may have worked, but it seems Maximus could do with a refresher on power armour piloting. Some things never change – even after the end of the world. https://hubs.la/Q02Tp_2B0

Markdown, like many authoring tools, excels in specific scenarios but isn’t ideal for every project. How can you determine if it’s the right choice for you? In this article, we’ll explore when and where to use Markdown, its pros and cons, and offer tips to help you make the most of it. Read more at https://hubs.ly/Q02W6fhx0 #TechComm #TechnicalWriting #TechDoc

One of our Senior Technical Authors, Denise Marshall, delves into using Agile retrospectives to promote continuous improvement and cultivate a more collaborative work environment. Discover practical tips on conducting effective retrospectives, identifying obstacles, and transforming friction into opportunities for growth. Read more at https://hubs.la/Q02WgQZm0 #Agile #tipsandtricks #TechnicalWriters

Today is #ILoveToWriteDay, a perfect occasion to emphasize the importance of crafting documents that people actually want to read. Producing high-quality and accurate documents is essential, but their effectiveness hinges on one critical factor: usability. If your users aren’t reading your documentation, it’s falling short. Matt Rus, one of our Technical Authors, has put together a concise guide to assist you in planning your documentation effectively. He provides valuable tips on making your documentation easily accessible and user-friendly for those who need it most, and also examines ways to measure its success. Read more at https://bit.ly/4f9jWuG #TechComm #ContentStrategy #TechDoc

Proofreading your own work is a tedious and thankless task, and it’s made even more complicated because it is challenging to spot your own errors. However, it is a vital skill that Authors need to master to prevent errors from creeping into their work. That is why we’ve put together five practical steps you can take to improve how you proofread your own work, and help you eliminate any errors that you would have missed before. Read more at https://bit.ly/3Cpv5ZH #ProofReading #TechComm #TechnicalWriting #ILoveToWriteDay

Information architecture involves organising information so that users can quickly grasp complex topics, minimise frustration, and easily locate essential details when necessary. In this article, one of our Senior Technical Authors discusses fundamental information architecture principles, including breaking down information into manageable chunks and structuring it effectively. Read more at https://hubs.ly/Q02W6n7B0 #informationdesign #userexperience #uxwriting

In this week’s #TCFilmFriday, we explore the improper use of an aeroplane operator’s manual in ‘Madagascar 2’. After commandeering an aeroplane, penguins Skipper, Kowalski, and Rico notice a warning light blinking on the instrument panel. Skipper requests the operator’s manual, but instead of reading it, he uses it to smash the warning light. ‘Problem solved’, Skipper declares confidently. Unsurprisingly, this doesn’t fix the issue, and the plane ends up crash-landing. Although this is clearly a case of user error, we can’t help but think the operator’s manual is overly complicated, given it’s hefty enough to damage an instrument panel. Therefore, we can only rate this documentation a 5/10. https://hubs.la/Q02Tp-kn0