So, you say you have developed a new cutting-edge app, and now you want it to rock the tech world? Don’t want to dash your hopes, but it takes more than that to succeed. Let’s take a closer look at one of the TechCom trends–user adoption. Once you finish this article, you will understand what user adoption is, why it is so important, and how it can boost your production.
The phases of project initiation and project closure are substantially covered in blog posts, talks, and other resources across the TechComm society. Today, I would like to address a less frequently discussed phase – replacing a technical communicator in a project team.
Have you ever been assigned a task to write API documentation, and then you got lost in tools for creating it?
If yes, I would like to share with you amazing research by Diána Lakatos who analyzed loads of info to provide us with a magnificent overview of open-source tools for documenting APIs.
Complex System of Information Security (CSIS) comprises a set of organizational and technical measures aimed to ensure the protection of information circulating in the system from disclosure, leakage, and unauthorized access (c).
If your company is implementing the CSIS, it’s in for reinforced credibility and boosted sales. And you as a Technical Communicator are in for a bumpy ride. 😊
Let’s take a look at a grueling journey of meticulously described processes, roadmaps, and guidelines that need to accompany every stage of the System development.
People tend to create stereotypes about things they don’t have much insight into. I broke into information development from a different industry, and I’d like to share my own experience of mythbusting.
Before starting my career as an Information Developer, I was a translator and had little awareness of the role and its responsibilities. As a philosopher once said, “Theory without practice is empty”, and I’m glad I got a chance to fill the void and break my stereotypes during the first month of practical experience. Let me share some of them with you. Continue reading
Nowadays, artificial intelligence is a central subject in the constantly evolving world of technologies. It is believed that in the long run, it will define the next generation of software solutions. Simultaneously, there is a lot of anxiety that Artificial Intelligence (AI) is going to lead to significant labor displacement.
So, in the context of Technical Communication, does the advance of AI mean that our trade is doomed to extinction as well?
One of the typical ways for agreeing to have project documentation in place is this:
- Customer voices the need for documentation (on a side note, product-based software companies are not considered in this discussion).
- Documentation team provides the estimates.
- Estimates are adjusted and approved.
This works well for new projects and new features in existing projects. On a side note, this also assumes that the people who give the final approval for documentation do understand why documentation is needed.
But what about legacy projects, the ones that are poorly documented or not documented at all? How do you convince the company (or the customer) that documentation is needed?