Non-native English speakers often face significant hurdles when communicating when they move to English speaking countries, such as the US or UK. These challenges can include navigating language nuances, cultural expectations in written communication, and industry-specific jargon.
If you work in an IT company, you know that communicating both internally and externally to customers is always a challenge.
Creating a communications plan especially in IT is difficult as due to the dynamic nature of the industry, multiple stakeholders, and the technical complexity of the products.
If I were to identify some of the main challenges I see, it would include the following:
If you run a small business, you’re forever alert to a better way to juggle the thousand and one tasks that make up your work week. And there’s no shortcut here. As every scenario is unique, you need to investigate which tools, hacks, or frameworks work best for you.
So, with this in mind, I decided to re-examine how I run my business. Right down to the nitty gritty.
Last week, we went to IKEA to get some new equipment for our home office. In this Klariti tutorial, we look at how to write an installation guide that makes the assembly experience as smooth as possible, and include a series of checklists you can follow to ensure you’ve covered all points.
Remember, consistent practice is key to improving your proofreading skills. In addition to the above suggestions, I’d suggest that you look at proofreading as a separate task in the document development process.
For example, if you use software like Jira/Trello to manage your writing projects, add a specific ticket for proofreading. This ensures you carve out enough time to perform this task before you send the documents out to customers.
I’m increasingly using ChatGPT for different writing related tasks. To be clear, I’m not asking it to write original text for me, rather to help with the support tasks, such as research, analysis, proofing, and validation.
This is the first in a series of articles on how to use ChatGPT – Google Gemini and Claude are just as effective – to refine your response to RFPs.
This article presents a framework to write compelling case studies using ChatGPT. Since the initial draft of this document, ChatGPT and other LLMs have arrived. These offer a sophisticated toolkit to improve different aspects of your writing. If you’re interested in learning more about this, I’d encourage you read the following ChatGPT and Google Gemini tutorials on Klariti.
Why write a white paper for the renewable energy?
Right now, government bodies are looking at alternatives to traditional energy sources, such as oil. For this reason, companies with products and services related to renewable energy are increasingly in demand.
However, there’s a lot of competition in this space. One way to gain attention is to write a white paper which addresses a specific pain point. This will raise your profile and give you an edge over your competitors.
Interested?
Here’s five reasons to publish a white paper for renewable energy:
One of the most practical applications of AI is its ability to create ‘bespoke’ training plans. The limitation of most training courses is that they are too generic, cover material you already know, and fail to provide the level of detail you want.
In this tutorial, I’m going to walk you through how to create a tailored training plan. To give it some context, I’ll develop a plan to upskill a remote IT team. I’m using this as an example as increasingly we’re working as part of remote teams, and I suspect that coordinating the onboarding, upskilling, and development for remote workers can be quite challenging. While there are a lot of generic training materials out there, how do you find a way to carve out a bespoke plan for your team?
For Product Managers, using AI to write user stories offers several benefits, namely, Efficiency, Consistency, and Scalability.
Whether Google Gemini, ChatGPT or Claude, you can quickly produce multiple user stories, saving time compared to manual writing. If you provide with strict writing guidelines, it will follow a consistent structure and format, ensuring uniformity across all your user stories.
In this Klariti tutorial, we look at how to write, review, design and improve your datasheets.
A few weeks ago I wrote that I didn’t like business writing when I started out. Why? Well, it took me several centuries to write very long white papers, data sheets, and other sales collateral. Strange word ‘collateral’ isn’t it? The main reason we did this was the ‘assumption’ that customers preferred lengthy documents. These doorstoppers covered all aspects of the product/service. Sure, it had its place. But not all documents have to land with a thud. It’s the same with writing Business Plans. It doesn’t have to be fifty pages if you can get it under twenty and keep the material focused.
When writing technical documents, especially those that have gone through multiple revisions, what you initially set out to write and what appears in the review document may differ. In addition, you’re probably fatigued from wordsmithing the text and want to move on to something else. Nonetheless, as your name is on the document, it’s critical that you can stand by what you’ve written.
So, let’s look at how to review a technical document. Before I start, it’s assumed you’ve spellchecked the text, checked your sources, and so forth.
AI tools can be very helpful in drafting and reviewing executive summaries. Writing executive summaries plays to AI’s strengths in that it summarizes material you’ve provided and structures it accordingly. It has no reasoning or creative elements involved, which is where AI struggles.
So, with that said, let’s look at how to start writing executive summaries using Google Gemini, my personal go-to AI tool. You can follow the same steps with Claude and Microsoft Bing if you prefer.
Last week, I was teaching a group of business analysts how to rethink their approach to business case writing. It was a shortish course, so we zeroed on a few details. The aim was to give them enough guidance to feel confident when writing the next set documents, without being too prescriptive.
During the sessions, we identified three main problems when structuring the business case:
