WEBVTT
00:00:02.240 --> 00:00:06.878
Hello friends and welcome to season eight of Inside Tech Comm with Zohra Mutabanna.
00:00:06.878 --> 00:00:16.160
This season features a collection of conversations that explore the ideas, challenges, and opportunities shaping technical communication today.
00:00:16.160 --> 00:00:21.838
From AI and content strategy to leadership, product thinking, and the future of our profession.
00:00:21.838 --> 00:00:26.160
Each episode offers a fresh perspective from people doing the work.
00:00:26.160 --> 00:00:27.120
Let's get started.
00:00:30.460 --> 00:00:34.719
Season eight is proudly sponsored by LavaCon.
00:00:34.920 --> 00:00:41.380
Use discount code ITC26 to save $200 on registration for this year's conference.
00:00:41.859 --> 00:00:44.719
I'll share more about LavaCon later in this episode.
00:00:45.600 --> 00:00:46.240
Hello listeners.
00:00:46.799 --> 00:00:48.560
Welcome to a new episode.
00:00:48.619 --> 00:01:09.760
Today we have Ramesh Aiyyangar, and we are going to be talking about how with the field, the way it is evolving currently and where things are with not just because of AI and new technologies, but because the roles and career paths and expectations in the community are that the practitioners, the technical writers that support, is shifting.
00:01:09.760 --> 00:01:20.480
So we'll explore what these changes mean for the community and draw on Ramesh's experience across industry, leadership, training, mentoring, and community building.
00:01:20.480 --> 00:01:22.560
This is going to be more of a human conversation.
00:01:22.560 --> 00:01:24.959
With that, Ramesh, welcome to my show.
00:01:25.680 --> 00:01:30.319
Thank you so much, Zohra, for giving me this opportunity to be on your show.
00:01:30.319 --> 00:01:33.040
I'm really looking forward to this conversation.
00:01:33.040 --> 00:01:46.000
And I must add, Zohra, that you're doing a great service to the technical communication profession by doing these podcasts and getting specialists and others to share their insights.
00:01:46.000 --> 00:01:50.480
And we learn a lot from these podcasts and there are a lot of takeaways.
00:01:50.480 --> 00:02:00.799
So I really appreciate that you spare your valuable time to talk to experts, and it's a huge learning for all of us from the tech comm community.
00:02:00.799 --> 00:02:01.438
Thank you.
00:02:01.840 --> 00:02:02.078
Thank you, Ramesh.
00:02:02.078 --> 00:02:03.358
Thank you.
00:02:03.358 --> 00:02:09.680
It's a pleasure doing this, and it's thank you to people like you who are willing to come and talk to me.
00:02:09.680 --> 00:02:12.000
So it's a community effort, and I appreciate that.
00:02:12.000 --> 00:02:13.438
Appreciate your time as well.
00:02:13.438 --> 00:02:18.800
Ramesh, introduce yourself and tell us about the different roles you've played in your long career.
00:02:19.598 --> 00:02:20.240
Absolutely, Zohra.
00:02:20.240 --> 00:02:28.158
So to tell you very briefly, I enjoy simplifying the complex, enriching it, and that's what I've been doing.
00:02:28.158 --> 00:02:32.318
And I know it's been a long journey, nearly four decades so far.
00:02:32.318 --> 00:02:37.280
So the way it happens for me is I would divide into two phases.
00:02:37.280 --> 00:02:42.960
The first phase is before tech comm and after I joined tech comm.
00:02:42.960 --> 00:02:47.438
The reason why I would like to do that is the common thread is communication.
00:02:47.438 --> 00:03:09.919
So before I entered tech writing, I'm primarily a journalist and I worked as a reporter, editor, and I also had short stints in terms of advertising and public relations and other areas of communication, which tend to be more on the creative side, or as we call as a MarCom in today's parlance.
00:03:09.919 --> 00:03:19.038
And around early 90s is when we got computers and we started acquiring computer skills, software knowledge, and so on.
00:03:19.038 --> 00:03:25.520
And that's precisely around that time, around 93-94, I entered the software industry.
00:03:25.520 --> 00:03:35.360
And my first job as a tech writer was with a software company in Pune called Kale Consultants, and it was more of ISO documentation.
00:03:35.360 --> 00:03:43.120
And of course, I had no clue about technical writing then, and it's been a totally hands-on approach.
00:03:43.120 --> 00:03:46.400
I don't have any formal degrees in tech writing.
00:03:46.400 --> 00:03:56.318
Thanks to my peers in US and Europe and other areas who helped me acquire the primary core skills and, of course, the community.
00:03:56.318 --> 00:04:21.680
I owe a lot of my skills, my accomplishments to the STC community, where I've spent a substantial time of my professional career is around two decades, and I enjoyed every moment of it, not only in terms of learning and development, but also the community aspect in terms of networking, connect, and so on.
00:04:21.680 --> 00:04:31.278
And I'm very thankful to STC for having given me this opportunity to be associated so closely with some of the best in the industry.
00:04:31.278 --> 00:04:37.439
And of course, a lot of them whom I work very closely are pretty seniors right now.
00:04:37.439 --> 00:04:44.879
In fact, I would like to call out a lot of names, but I would avoid that, who had a major influence and who have helped me through.
00:04:44.879 --> 00:04:48.319
But it's been a really satisfying and long journey.
00:04:48.319 --> 00:04:52.560
But at the same time, it brings a lot of disappointment to me.
00:04:52.560 --> 00:05:00.240
The news that STC, uh, had to close its operations a few years back.
00:05:00.240 --> 00:05:09.360
And of course, I feel uh that you know we still do not have a global community like STC, which really enabled a lot of things.
00:05:09.360 --> 00:05:23.838
In fact, they were critical in terms of defining our profession, creating awareness, promoting things, and listing everything that we really needed, especially for folks like me who were in India and didn't have a clue about it.
00:05:23.838 --> 00:05:25.519
It helped me a lot.
00:05:25.519 --> 00:05:28.720
And of course, I wanted to do my little bit.
00:05:28.720 --> 00:05:45.278
And since I had this experience with STC, I started my own group in India called as Institute for Technical Communicators of India, which is primarily a free platform to enable people to come together, connect, and learn.
00:05:45.278 --> 00:05:56.000
And eventually this platform kind of you know uh translated into what I see right now as a company, which is TechWritePro.
00:05:56.000 --> 00:06:21.680
Of course, I do not have any major commercial ambition, but my mission is primarily to create awareness and promote the profession in whatever limited way I can, and to empower technical writers uh to a great extent and provide opportunities, enable them, recognize them, and do whatever I can as an individual through this company.
00:06:21.680 --> 00:06:23.360
That's roughly my background.
00:06:24.160 --> 00:06:26.800
So that is a very impressive background.
00:06:26.800 --> 00:06:29.439
Four decades, congratulations on that, Ramesh.
00:06:29.439 --> 00:06:31.439
Thank you for doing that.
00:06:31.439 --> 00:06:35.838
I think we need more such anchors today than we realize.
00:06:36.720 --> 00:06:38.399
Thank you so much, Zohra, for your kind words.
00:06:39.199 --> 00:06:42.079
You've seen technical communication with such a long spanning career.
00:06:42.079 --> 00:06:45.278
You've seen technical communication evolve through significant changes.
00:06:45.278 --> 00:06:49.600
When you look at the profession today, what concerns you most?
00:06:49.600 --> 00:06:52.879
Not in terms of the technology, but about the people.
00:06:53.680 --> 00:06:55.838
Absolutely. And you're absolutely right.
00:06:55.838 --> 00:07:01.360
I mean, especially in this long journey, I have seen tech comm really evolve.
00:07:01.360 --> 00:07:05.680
In fact, I would extend it further to publishing as such, you know.
00:07:05.680 --> 00:07:11.680
Uh way back when I started my journalism and was working with newspapers and periodicals.
00:07:11.680 --> 00:07:27.600
I uh have literally seen the manual uh printing press where they used to assemble those fonts and then kind of print it to uh AI agents today and all about skills.
00:07:27.600 --> 00:07:32.720
So uh it's like really an evolutionary thing that I've really seen.
00:07:32.720 --> 00:07:51.439
But the most distinctive and important thing is the human element is always there, and I don't think so, irrespective of the technology changes and other things, the human aspect will go away, especially in terms of tech writing, because it's a very niche skill.
00:07:51.439 --> 00:08:03.519
Even if it is AI, it's all about documentation, it's all about automation, and it's only going to be about the mechanical or repetitive or iterative task.
00:08:03.519 --> 00:08:11.600
A lot of things related to documentation cannot be automated, so the human element will always be there.
00:08:11.600 --> 00:08:22.959
And the most critical aspect, I think, is the critical thinking or the thinking aspect, which is something very specific to humans, and I don't think so.
00:08:22.959 --> 00:08:41.840
Automation or agents can really do that because even with AI, I think the foundational stuff or the overarching content, or you know, the judgment aspect, the discernment, even after the drafts are created, is primarily with humans.
00:08:41.840 --> 00:08:44.000
So who's driving all of this?
00:08:44.000 --> 00:08:46.000
It's the human in the loop, right?
00:08:46.000 --> 00:08:50.879
So I think that's a very, very important element, and it will not go away.
00:08:50.879 --> 00:09:07.918
And the core skills of thinking, articulating, explaining, simplifying, giving better examples, understanding the user needs is so important that we understand the psychological aspect, the behaviors, and so on.
00:09:07.918 --> 00:09:19.200
And we do say that we have agents, the traffic to doc sites are more of agents and stuff like that, but we still do not know how they consume content, right?
00:09:19.200 --> 00:09:28.798
And it's so important to understand how end users, and definitely it's going to be a human at the end of the chain who is kind of looking at the content.
00:09:28.798 --> 00:09:40.720
So these things are very important, and I think we really need to uh understand these aspects, especially in the current era of AI, while we talk a lot about automation.
00:09:40.720 --> 00:09:42.960
I hope that answers your question.
00:09:43.600 --> 00:09:43.840
It does.
00:09:43.840 --> 00:09:55.918
I think you're right about the human element, the core human characteristics that we have, that we possess, that cannot ever be well, can be replicated by a machine.
00:09:55.918 --> 00:09:58.240
I'm gonna take a chance and say that.
00:09:58.240 --> 00:10:01.278
And technical writing is a niche field.
00:10:01.278 --> 00:10:06.080
And do you have any concerns since you run an institute?
00:10:06.080 --> 00:10:12.000
What kind of concerns are you seeing surface when you talk to technical writers?
00:10:12.960 --> 00:10:18.158
I don't see uh quite a few issues when it comes to learning, upskilling.
00:10:18.158 --> 00:10:29.840
There are a lot of anxiety and there are a lot of worry, and people still are not clear as to what is the path because it's like seeking the unknown.
00:10:29.840 --> 00:10:39.918
Uh, people are not sure about what careers they will have or what are the things that they need to do, because not all companies are investing in AI.
00:10:39.918 --> 00:10:44.158
They are not very clear as to what skills they need to build.
00:10:44.158 --> 00:11:03.038
A lot of it also has to do with self-reflection, because very few individuals really spend a substantial time in understanding or maybe introspecting, realizing their own strengths, weaknesses, or even for that matter, what they really want to do going ahead.
00:11:03.038 --> 00:11:08.798
In some cases, people take an approach of let's take it as it comes, right?
00:11:08.798 --> 00:11:12.080
So the kind of clarity is not there.
00:11:12.080 --> 00:11:28.960
So, what really happens in a situation like this when we are going through a mini-revolution right now, and we are trying to tread unknown territories or explore new areas or new frontiers, how do you really go about it, right?
00:11:28.960 --> 00:11:31.918
So I think the first thing is optimism.
00:11:31.918 --> 00:11:42.158
I mean, we have to have a lot of optimism because it's not something that is very easily available or it's there around the corner.
00:11:42.158 --> 00:11:43.519
It's within you.
00:11:43.519 --> 00:11:46.000
You have to keep that hope each day.
00:11:46.000 --> 00:11:48.798
It is something that you build every day, right?
00:11:48.798 --> 00:11:56.240
So being very hopeful, that's very important because anxiety, worry, stress is not going to help you in any way.
00:11:56.240 --> 00:12:02.000
It kind of paralyzes or things become stagnant, and then you're not able to act.
00:12:02.000 --> 00:12:08.320
And that's the worst thing that you can do to your career when you're just kind of you know thinking and not acting.
00:12:08.320 --> 00:12:11.120
So optimism is one thing definitely.
00:12:11.120 --> 00:12:16.000
But the second thing is um it's not only about technical skills.
00:12:16.000 --> 00:12:25.600
People are so obsessed with only the technical skills or maybe just the tools or you know, software and stuff.
00:12:25.600 --> 00:12:32.798
While it is good to learn these skills, it is good to learn about AI and tools and so on.
00:12:32.798 --> 00:12:38.000
But as I said sometime back, automation is only to a limited extent.
00:12:38.000 --> 00:12:52.240
The kind of value that you add is going to be from your core skills, because at the end of the day, it is the experience for the user or the consumer of content, and there's a human at the end of the chain.
00:12:52.240 --> 00:12:54.080
So that's very important.
00:12:54.080 --> 00:13:13.918
So while technology skills are important, you also need to focus on the other aspects which are less uh known right now, because we really need to understand the user behavior, how they are really kind of you know consuming the content right now, because it's just not about agents, uh right.
00:13:13.918 --> 00:13:16.798
So, do we really have data about that?
00:13:16.798 --> 00:13:31.278
It's not about just some analytics, uh, like how many hits are there on the pages, or how many agents are visiting the page, or so on, but you really need to see the behavior, like what typically we had UX folks doing it, right?
00:13:31.278 --> 00:13:43.840
The user behavior, trying to see how people are using it because even the customers you uh will be kind of exploring all of this, they will be implementing software, they'll be investing their time in this.
00:13:43.840 --> 00:13:46.480
So, doc is just a small aspect of it.
00:13:46.480 --> 00:14:07.759
So we have to understand that, and I think it is still pretty gray, or people do not have enough access to all that data, to all that analytics, or to all those interactions and so on, because not all tech writers are really cleared for that, and that is the area where you can really add value.
00:14:07.759 --> 00:14:14.960
So, what I would say is the ultimate goal of documentation is to exceed customer expectations.
00:14:14.960 --> 00:14:32.639
So, irrespective of the technology and the advancement, while it is good to learn all of that, we should not miss the core aspect in terms of why you're writing those docs, for whom you're writing those docs, and how the experience is.
00:14:32.639 --> 00:14:36.000
It's like uh I can give a simple analogy, right?
00:14:36.000 --> 00:14:37.360
Like cooking, right?
00:14:37.360 --> 00:14:45.519
We can have all the ingredients in place, very uh neatly placed, the right quantity, the right volume, and so on.
00:14:45.519 --> 00:14:48.960
But ultimately, uh the person who's cooking it.
00:14:48.960 --> 00:14:51.278
I mean, you need to get that taste, right?
00:14:51.278 --> 00:14:53.519
And taste is something which is an experience.
00:14:53.519 --> 00:14:59.519
Not everybody can create the right dish with the right taste, something which can be relished.
00:14:59.519 --> 00:15:10.798
Now that comes with your skills, that comes with your experience, that comes with the knowledge of people who are going to have that dish, and so on.
00:15:10.798 --> 00:15:14.240
So that's where the differentiator will happen, right?
00:15:14.240 --> 00:15:16.879
So we have to focus on the taste aspect.
00:15:16.879 --> 00:15:25.440
You may have the best ingredient, you may have the best chunks of content, but if you don't know how to orchestrate the whole thing, what's the point?
00:15:25.440 --> 00:15:40.639
I might have the best violinist, I might have the best vocalist, I might have the best guitarist, but if I don't know how to compose or how to create that symphony, that music is not going to be so soothing for me, right?
00:15:40.639 --> 00:15:42.960
So, or enjoyable, correct?
00:15:42.960 --> 00:15:57.278
So somewhere we miss that aspect or that overarching the vision, the foresight, the ownership, because doc is not about deliverables anymore, right?
00:15:57.278 --> 00:16:01.278
It's about uh a service, it's a product by itself.
00:16:01.278 --> 00:16:06.639
So, do all tech writers really understand that doc is a product by itself?
00:16:06.639 --> 00:16:22.000
We need to take ownership, we need to have that vision, and that's where other aspects like content strategy is very important, and then we have content design, then we have the other aspect of system design, all right?
00:16:22.000 --> 00:16:27.200
And then we have the delivery aspect where all the operational aspects are concerned.
00:16:27.200 --> 00:16:32.320
So these are four major things which are very important as we go ahead.
00:16:32.320 --> 00:16:48.080
Now, you might polarize to some aspects or you may have proximity to some of these things, but you cannot restrict yourself, you cannot say I do not know the other things, or I will not do this, or I will not do that.
00:16:48.080 --> 00:16:50.798
You'll have to be extremely flexible, right?
00:16:50.798 --> 00:16:52.798
And that's where you have to keep moving.
00:16:52.798 --> 00:17:02.480
If you say no, I am a DITA expert, or I just want to do information architecture, but I don't know about the product, doc as a product.
00:17:02.480 --> 00:17:10.960
I don't understand content strategy, or I really don't understand the engineering aspect or the engineering depth or the product in detail.
00:17:10.960 --> 00:17:18.720
You cannot afford to say those things going forward because a lot of things will matter on the value add.
00:17:18.720 --> 00:17:40.558
Now it's the same product, but there is novelty in there because you have to look at it at different angles, not the same way that, for example, typically in the olden days, when you used to work with products, we always used to focus our time on finding bugs, be it UI, be it the functionality, be it the error, it could be anything.
00:17:40.558 --> 00:17:50.798
But the way we would look at the product is the effort would be to break it down, you know, and try to do as many things to add value to it from various aspects.
00:17:50.798 --> 00:17:55.759
So the depth from an engineering perspective is very important.
00:17:55.759 --> 00:18:15.759
You have to be able to look at a product in depth, not the same way as others, possibly different ways of how users will look at it, or even from your own experience and skills and apply it to some of the things that I mentioned, that is what is going to be the differentiator.
00:18:15.759 --> 00:18:23.038
Of course, we have other aspects like delivery and all of that, the system aspect and so on.
00:18:23.038 --> 00:18:29.358
But this is how uh I look at it, or this is what I think will be important going forward.
00:18:29.358 --> 00:18:31.358
Yeah, I hope that makes sense.
00:18:31.680 --> 00:18:32.640
I mean, you can ask me.
00:18:32.640 --> 00:18:34.078
Definitely makes sense.
00:18:34.078 --> 00:18:42.400
How is this message landing with the youngsters that are entering the field versus somebody who's been in the field for somebody who's experienced?
00:18:42.400 --> 00:18:52.160
Because I'm I'm just thinking right now, the message in general that I'm hearing around me is youngsters that are finding it hard to break into any profession.
00:18:52.160 --> 00:18:57.920
So, this conversation, as much as it is about technical communication, other roles are equally being challenged.
00:18:57.920 --> 00:19:08.960
Have you noticed any marked difference in how the two generations, the different generations receive your message that you've talked about from your experience specifically?
00:19:10.160 --> 00:19:10.480
Yeah, definitely.
00:19:10.480 --> 00:19:28.078
Because uh, see, in terms of experience, we have to understand there's a lot of unlearning also required because when it comes to learning, unlearning is equally important because when you're going through a revolution, you cannot afford to learn the traditional way, right?
00:19:28.078 --> 00:19:37.440
Now I cannot learn AI through books or through uh Udemy or doing some certification or you know other things.
00:19:37.440 --> 00:19:39.759
That's not really going to take me very far.
00:19:39.759 --> 00:19:44.318
But I can do that, or it can help me understand some conceptual stuff.
00:19:44.318 --> 00:19:48.880
You have to do things for yourself to get a good grasp of it.
00:19:48.880 --> 00:20:03.358
Like as I tell them, it's not about formatting your resume anymore, it's not about how good your resume looks, but like as Fabrizio Ferri Benedetti has said in one of his articles, it's about the beauty of the doc itself, right?
00:20:03.358 --> 00:20:16.318
And when I say beauty of the doc, it has a different connotation or an interpretation, which indirectly reflects on the principles of what good tech writing is all about, right?
00:20:16.318 --> 00:20:26.720
I mean, for example, if I'm trying to simplify something complex, it should be so simple for the user that he doesn't have to carry the load of the complexity.
00:20:26.720 --> 00:20:29.920
That is where your value add is.
00:20:29.920 --> 00:20:33.278
The transformation is the value add, right?
00:20:33.278 --> 00:20:41.838
And so the difference between the youngsters and the experienced is how you really adapt, how flexible you are.
00:20:41.838 --> 00:20:59.838
And definitely we all know that with age, with experience, we try to erect walls, we try to create fences, we try to get deeper into something, and you know, you don't want to experiment or you know, try out new stuff and all of that.
00:20:59.838 --> 00:21:02.480
I would definitely not recommend something like that.
00:21:02.480 --> 00:21:07.680
But the younger folks, they're totally new, they are open, they don't have any such blocks.
00:21:07.680 --> 00:21:14.000
So probably for them it would not be so difficult to adapt or to learn and all of that.
00:21:14.000 --> 00:21:21.920
But nonetheless, irrespective of whether you're young or senior or whatever, we are treading something totally unknown.
00:21:21.920 --> 00:21:24.720
Nobody knows where you're heading, right?
00:21:24.720 --> 00:21:29.759
So you have to explore, you have to discover, you have to learn.
00:21:29.759 --> 00:21:34.720
There's nothing like a ready map which is already there, right?
00:21:34.720 --> 00:21:41.519
Uh which you can navigate, or the typical linear kind of career ladders that we had earlier.
00:21:41.519 --> 00:21:42.960
It's not going to make sense.
00:21:42.960 --> 00:21:50.000
In fact, I doubt even if we'll have the same titles as technical writers or technical communicators, right?
00:21:50.000 --> 00:21:53.838
Now, people are talking about context engineers, content curators.
00:21:53.838 --> 00:21:59.358
There are as many titles, and this may uh vary as much as possible because.
00:21:59.358 --> 00:22:04.720
It depends upon the company, it depends upon the scale, it depends upon the size and so on.
00:22:04.720 --> 00:22:11.838
So if we try to typically expect things in the future based on the past, it's not going to work anymore.
00:22:11.838 --> 00:22:16.400
So the flexibility is one thing which is very, very important.
00:22:16.400 --> 00:22:23.278
But definitely one thing that one should definitely do and should have an excellent skill.
00:22:23.278 --> 00:22:25.680
And that's where I really appreciate your podcast.
00:22:25.680 --> 00:22:30.798
Like I said in my earlier conversation, the kind of questions that you ask, you know.
00:22:30.798 --> 00:22:32.558
That's a skill by itself.
00:22:32.558 --> 00:22:39.759
Because asking the right questions is going to really add a lot of value, and that's going to be a differentiator.
00:22:39.759 --> 00:22:51.440
Because now we take on roles as reviewers and editors, and we have to keep reviewing stuff endlessly through the entire day, right?
00:22:51.440 --> 00:22:53.838
And you have to ask a lot of questions.
00:22:53.838 --> 00:23:01.358
You'll have to call out what is trash, what is bullshit, what is right, what's wrong, what's not good, and all of that.
00:23:01.358 --> 00:23:03.200
And how are you going to do that, right?
00:23:03.200 --> 00:23:07.598
So you have to keep asking a lot of questions, challenge the status quo.
00:23:07.598 --> 00:23:11.680
You have to go back and tell them this is right, not right, and so on.
00:23:11.680 --> 00:23:22.160
So asking the right questions is one of the most like in the earlier days we used to say the interviewing skills where we used to connect with SME and ask a lot of questions.
00:23:22.160 --> 00:23:26.318
Unless you ask the right questions, you will not get the right content, right?
00:23:26.318 --> 00:23:29.118
So it's very important, I would say, going ahead.
00:23:29.118 --> 00:23:30.318
That's one skill.
00:23:30.318 --> 00:23:33.038
I would say thinking is critical.
00:23:33.038 --> 00:23:56.558
Asking questions is equally important to understand the why aspect because, like I said earlier, irrespective of all the automation, the explaining aspect, the fundamental aspect of what this product is, what the feature is all about, or all the conceptual related stuff is going to be done by writers, and you need to know to do that very well.
00:23:56.558 --> 00:23:57.278
Right.
00:23:57.519 --> 00:24:03.598
And that it doesn't matter which way you are on your career journey, how your experience.
00:24:03.598 --> 00:24:12.558
But when I asked you this, yeah, when I asked you this question, Ramesh, I came with a very different expectation from you in terms of the answer.
00:24:12.558 --> 00:24:14.720
But the and it's actually good.
00:24:14.720 --> 00:24:31.358
You broke, I suppose, you challenged me in a way to think differently because here I am experienced, and I thought you might say, Oh yeah, the youngsters and probably speak about them, but you actually started with the the experienced professionals have to unlearn.
00:24:31.358 --> 00:24:37.838
And that was a very, I think, a good way for me to challenge myself.
00:24:37.838 --> 00:24:39.519
I didn't expect that.
00:24:39.519 --> 00:24:40.880
I didn't expect that answer.
00:24:40.880 --> 00:24:42.240
So that's so important.
00:24:42.240 --> 00:24:43.519
I didn't even think about it.
00:24:43.519 --> 00:24:59.838
That what the experienced have to do, because I thought, oh, maybe the experienced are more advantaged, but you actually challenge that with your response, which was uh that fixed thinking, no experimentation, generally as we grow in our careers, that tends to happen.
00:25:00.880 --> 00:25:17.838
Right, uh Zohra, because we also have to move from hyper uh specialization to a generalization right now, because we have to move with the flow, we have to be extremely flexible, we have to connect, we have to have discourses, we have to connect with stakeholders, a lot of aspects, you know.
00:25:17.838 --> 00:25:23.440
So we cannot go with a rigid mind because see ultimate differentiator is the mindset, right?
00:25:23.440 --> 00:25:29.838
So and it's so important that you have need to have the right attitude to be able to survive and thrive.
00:25:29.838 --> 00:25:35.278
It's like when you're seeking storms, we cannot say this is the way I will do it, right?
00:25:35.278 --> 00:25:39.598
I mean, you never know how the storm is coming, what's the speed, how to handle it, right?
00:25:39.598 --> 00:25:48.160
So you'll have to uh do what is best at that particular moment and see how you uh kind of you know react to the whole thing.
00:25:48.160 --> 00:25:50.400
And merely reaction will not help.
00:25:50.400 --> 00:25:55.838
You need to respond to it in the right way, and that is only possible when you have an open mind.
00:25:57.038 --> 00:26:10.480
Yeah, and I think the earlier point that you made about self-reflecting is equally important because when you're in the storm in the thick of it, you're reacting, but then it's also important to pause and reflect is this where I'm headed?
00:26:10.480 --> 00:26:13.278
The what my response is, is that the right response?
00:26:13.278 --> 00:26:19.118
Because you still want to respond in an informed way.
00:26:19.118 --> 00:26:21.038
Would you agree with that?
00:26:21.358 --> 00:26:35.038
Absolutely. I give a lot of importance to, uh, self-introspection because I do a lot of mentoring and I see that uh people at times want to do things very, very mechanical.
00:26:35.038 --> 00:26:45.118
Uh, we are so used to the rat race, or we just want to compare ourselves with others and try to do things that have already been done.
00:26:45.118 --> 00:26:48.078
Uh, do only a few things because they are easy.
00:26:48.078 --> 00:26:54.720
Uh, we don't challenge us and say now you need to be prodded, you need to be nudged, and all of that.
00:26:54.720 --> 00:27:06.880
But if you really introspect, if you really understand yourself better, the way you would relate to the outside world will be far better, be it your professional life or other things.
00:27:06.880 --> 00:27:10.558
And when we say introspect, you really understand yourself.
00:27:10.558 --> 00:27:11.358
What is that?
00:27:11.358 --> 00:27:19.118
Because all said and done, we need to understand what is the purpose, how do we really create meaning in what we are doing, right?
00:27:19.118 --> 00:27:30.400
Because even the professional life, when you're spending a substantial amount of time of the day and the life, you definitely want it to be meaningful, satisfying, and fulfilling.
00:27:30.400 --> 00:27:37.920
It should not be like at the end of the day, you're so frustrated and you feel like, why am I doing this day in and day out?
00:27:37.920 --> 00:27:38.880
What's the point?
00:27:38.880 --> 00:27:48.240
You're not enjoying the process, and naturally, if some you're doing something that you're not enjoying, it doesn't give you joy, nor will it give others, right?
00:27:48.240 --> 00:27:50.798
So, and when will you realize that?
00:27:50.798 --> 00:27:59.759
You can realize that only when you introspect, when you pause, as you rightly said, stop, pause, and think, why am I doing this?
00:27:59.759 --> 00:28:01.838
What is the potential that I have?
00:28:01.838 --> 00:28:03.118
What am I good at?
00:28:03.118 --> 00:28:04.558
What would I like to do?
00:28:04.558 --> 00:28:11.598
No, the more you think, you will get some of these answers because, as we all know, all answers are within us only, right?
00:28:11.598 --> 00:28:23.358
And then it's just that we don't seek it, we don't spend time, we don't spend quality time with us because we are so busy hustling and doing things, you know.
00:28:23.358 --> 00:28:24.720
We don't get that time.
00:28:24.720 --> 00:28:34.318
So once you do that, and when you actually start putting things down and you get that clarity, the growth happens very fast.
00:28:34.318 --> 00:28:42.318
And uh the growth sometimes is so good that you yourself will not expect because there is nothing like can't, right?
00:28:42.318 --> 00:28:42.960
In that.
00:28:42.960 --> 00:28:46.160
Because that is something that you really understand very well.
00:28:46.160 --> 00:28:48.318
You know you want to do it, you love it.
00:28:48.318 --> 00:29:06.480
Then growth is like 10x times or maybe 100x times, but that exercise is extremely important because self-realization, as we say, is the goal, and the endeavors always to learn more about ourselves, which never really happens in the real world.
00:29:06.480 --> 00:29:13.598
It takes a lot of time to do that, and we are always figuring out what is the purpose, what is the meaning, and so on.
00:29:13.598 --> 00:29:35.440
So, of course, it may sound a bit spiritual or philosophical, but I would say in the age of AI world, it is very important that we need to uh kind of get back to the roots of the human thought process or action, and definitely all that is based on philosophy and all this kind of thinking, which will make you a better individual.
00:29:35.440 --> 00:29:42.400
Because if all that thinking didn't happen earlier, we wouldn't be here doing some of the things that we do today.
00:29:42.720 --> 00:29:49.059
The episode is sponsored by LavaCon, the content strategy conference taking place this October in Charlotte, North Carolina.
00:29:49.660 --> 00:30:03.358
With more than 70 sessions and workshops featuring speakers from companies like Salesforce, TikTok, T-Mobile, and Amazon, LavaCon brings together content strategists, documentation leaders, and content professionals to share practical ideas you can apply right away.
00:30:03.358 --> 00:30:10.400
And yes, it's known as the Fun Conference, too, with networking events, therapy dogs, comfort llamas, storytelling, and karaoke.
00:30:10.400 --> 00:30:14.640
Use discount code ITC26 to save $200 on registration.
00:30:14.640 --> 00:30:23.118
Even though we are taking a bit of a philosophical and a spiritual approach to this discussion, that's exactly I think what I'm looking for.
00:30:23.118 --> 00:30:29.920
Because in this time of hustling and the rat race, as you mentioned, we've become so mechanical.
00:30:29.920 --> 00:30:33.118
We are responding on the go.
00:30:33.118 --> 00:30:37.920
And from a human perspective, it's not sustainable, right?
00:30:37.920 --> 00:30:40.078
Each day you cannot be treating it as a transaction.
00:30:40.078 --> 00:30:41.920
You've got to live it.
00:30:41.920 --> 00:30:44.720
And if you're going to live it, you need that self-realization.
00:30:44.720 --> 00:30:50.078
I would also add self-awareness to guide where you want to go.
00:30:50.078 --> 00:30:52.160
That answer only can come from within.
00:30:52.160 --> 00:30:55.598
So I'm not going to shy away from that conversation, uh Ramesh.
00:30:55.598 --> 00:31:00.960
I'm happy that you're bringing these things to the fore because we don't talk about them.
00:31:00.960 --> 00:31:02.798
We are on the go, go, go.
00:31:02.798 --> 00:31:09.200
And it's very important to pause and to reflect so that you can move forward in a better way.
00:31:09.200 --> 00:31:11.920
And with that, that this question comes to mind.
00:31:11.920 --> 00:31:14.160
You talked about the new titles that are emerging.
00:31:14.160 --> 00:31:18.400
In fact, my company also rolled out new titles for us.
00:31:18.400 --> 00:31:20.558
Personally, I feel awesome about it.
00:31:20.558 --> 00:31:29.680
And I do feel that from where I see there is a career evolution that is happening, and those titles are appropriate to what we are doing.
00:31:29.680 --> 00:31:32.240
Because titles do carry some weight.
00:31:32.240 --> 00:31:34.960
That said, what is your take?
00:31:34.960 --> 00:31:39.038
Seeing these new titles, is there a genuine career evolution happening?
00:31:39.038 --> 00:31:40.400
Because what I'm saying is anecdotal.
00:31:40.400 --> 00:31:42.960
What are you seeing in the field?
00:31:43.838 --> 00:31:47.358
I would not necessarily say it's an evolution.
00:31:47.358 --> 00:32:11.118
I would say getting back to some of the core uh skills that we have or foundational and kind of getting into depth with that, you know, because sometimes we are just so caught up in the technical skills or you know, uh, or tools and other things, we forget that we are communicators first.
00:32:11.118 --> 00:32:17.519
And irrespective of your knowledge, you know, uh communication is what really enriches it.
00:32:17.519 --> 00:32:24.558
And that's our job because we say we simplify the complex and what can do it better than communication.
00:32:24.558 --> 00:32:28.240
And it's just not about communicating again, right?
00:32:28.240 --> 00:32:32.160
Communication is also about enriching lives, right?
00:32:32.160 --> 00:32:38.400
Or elevating uh lives, in this case, particularly about your customers, right?
00:32:38.400 --> 00:32:39.038
Or users.
00:32:39.038 --> 00:32:41.519
And that's what our goal is, right?
00:32:41.519 --> 00:32:45.358
The goal of a documentation team is to exceed customer expectations.
00:32:45.358 --> 00:32:48.078
So are we really doing justice to that?
00:32:48.078 --> 00:32:49.838
Is what we really need to see.
00:32:49.838 --> 00:32:55.440
I mean, if we are writing some conceptual content to write from scratch, are we doing our best?
00:32:55.440 --> 00:33:00.480
Are we investing our time in such a way that we are telling the best stories?
00:33:00.480 --> 00:33:02.880
Or is there are there any alternatives?
00:33:02.880 --> 00:33:04.160
Can we do it better?
00:33:04.160 --> 00:33:06.000
Can we do it in a different way?
00:33:06.000 --> 00:33:09.038
How much of experimentation do we really do that?
00:33:09.038 --> 00:33:12.160
How much of that do we really share socially?
00:33:12.160 --> 00:33:14.000
Do we talk about those experiments?
00:33:14.000 --> 00:33:15.598
Do we share those experiments?
00:33:15.598 --> 00:33:17.598
Do we connect with people?
00:33:17.598 --> 00:33:18.720
Do we connect with customers?
00:33:18.720 --> 00:33:20.720
Do we really understand their behaviors?
00:33:20.720 --> 00:33:24.078
I doubt we do a lot of that, right?
00:33:24.078 --> 00:33:35.118
Because we don't have the time to do that, because we are so caught up in the mechanics that we don't spend time in some of these things which are critical to our goal itself.
00:33:35.118 --> 00:33:38.400
And that's always been a challenge all the time.
00:33:38.400 --> 00:33:54.078
We talk about understanding our audience, we talk about understanding our user needs, but sometimes the users themselves are so vague about everything, starting from requirements to using the product, to adopting the product, to being able to use the document and so on.
00:33:54.078 --> 00:34:11.360
And if you see the conversations they have with the bots and other things, when they visit the site, you'll realize there are so many errors and bugs, and there are so many issues that they are grappling with, which sometimes are so straightforward, or a lot of that can be prevented.
00:34:11.360 --> 00:34:15.920
I would say, why do so many issues happen in the first place?
00:34:15.920 --> 00:34:26.960
If you understand your audience and user needs so well, we take pride in saying that we reduce support tickets and adding to the bottom line or adding to the revenue.
00:34:26.960 --> 00:34:30.400
But why have those support tickets in the first place?
00:34:30.400 --> 00:34:32.079
That should be your value add.
00:34:32.079 --> 00:34:33.920
You have to we talk about innovation.
00:34:33.920 --> 00:34:37.199
What innovation are we really doing from that perspective?
00:34:37.199 --> 00:34:42.320
How well we understand the product or the behaviors that we can avoid such things.
00:34:42.320 --> 00:34:50.159
We have to take a preventive approach than a reactive approach to documents because it's all about the experience, as I said.
00:34:50.159 --> 00:34:55.039
It's all about the taste that I mentioned when I gave an analogy of that dish.
00:34:55.039 --> 00:34:58.559
Now that is something which is cultivated over a period of time.
00:34:58.559 --> 00:35:00.400
We really need to understand that well.
00:35:00.400 --> 00:35:07.599
A person who has cooked and tasted multiple times will only understand the subtle things of that.
00:35:07.599 --> 00:35:14.960
Only he will be able to distinguish which ingredient is more, why is the flavor such, or why is the aroma such.
00:35:14.960 --> 00:35:22.800
Only they will be in a better position, or only they will have that discernment and judgment to do those things.
00:35:22.800 --> 00:35:30.400
That is where we should be focusing on the subtle aspects, not the gross or the raw stuff.
00:35:30.400 --> 00:35:33.518
You know, I would say that is where the value add will happen.
00:35:33.518 --> 00:35:41.440
I hope again, like I said, I tend to go on.
00:35:33.518 --> 00:35:42.000
I don't know whether this one was an interesting answer.
00:35:42.639 --> 00:35:47.360
But I want to again go back to you said that the career really isn't evolving.
00:35:47.360 --> 00:35:52.159
Because in my question, I asked you the career evolution that's happening with the titles.
00:35:52.159 --> 00:36:04.719
And again, I came here with a certain expectation, and you challenged me in a good way, where you said that it's the core skills that are kind of reflected with the new titles.
00:36:04.719 --> 00:36:13.679
We are going back to what the different aspects of our profession that are now surfacing, the specialization even within what we do as a technical writer.
00:36:13.679 --> 00:36:23.440
And you prompted me to think that maybe technical writing became a title that was looked down upon lately was because it it sounded very mechanical.
00:36:23.440 --> 00:36:26.079
It sounded very monotonous.
00:36:26.079 --> 00:36:38.719
And all the other attributes of the profession are now AI is probably giving us a chance to dig into those and really specialize content engineering, content strategy.
00:36:38.719 --> 00:36:41.599
Just think about it in a creative way.
00:36:41.599 --> 00:36:46.800
Again, as a communicator, how can you get creative with those aspects of your profession?
00:36:46.800 --> 00:36:48.079
Thank you for that.
00:36:48.639 --> 00:36:57.039
Absolutely, because I think something that doesn't go away from uh writing is writing is primary thinking, and writing is all about articulation.
00:36:57.039 --> 00:37:03.039
Writing is about research, writing is about creativity, writing is about structure.
00:37:03.039 --> 00:37:07.119
What we talk about information architecture, design, and all that.
00:37:07.119 --> 00:37:16.880
But AI can vomit a lot of content, but if it cannot tell you what is the right structure, and that comes inherently with good writing skills, right?
00:37:16.880 --> 00:37:23.679
Because writing is all about the structure, the flow, the context, the examples, the visuals, and so on.
00:37:23.679 --> 00:37:27.840
So these are some very inherent and core skills, I would say.
00:37:27.840 --> 00:37:34.079
I mean, of course, you can specialize in this, but if we were to say what is good tech writing, it's all of this.
00:37:34.079 --> 00:37:36.719
Like I said, it's multiple skills, right?
00:37:36.719 --> 00:37:46.239
So we have to excel in these to be able to add value, or that is what is good tech writing all about, is what I would say.
00:37:46.239 --> 00:37:48.400
And that is where we need to get to.
00:37:48.400 --> 00:38:00.880
And I think AI is giving us an opportunity to do that because we need to be more of thinkers right now and see how we can really handle this and do better in such a situation.
00:38:00.880 --> 00:38:21.518
So, I mean, I in a way I would say AI is doing uh good stuff to us because it's taking us back to the core skills, making us think, get to the depth of things, you know, look at the product or software or technology in different ways, try to seek user needs in a different way, provide better experiences.
00:38:21.518 --> 00:38:27.840
Because unlike the earlier days, uh things have radically changed, even for the software engineers.
00:38:27.840 --> 00:38:32.880
And for them, at least they have the QAs who can test their code.
00:38:32.880 --> 00:38:36.159
But for documentation, we don't have anybody who will test that.
00:38:36.159 --> 00:38:38.079
It is the writer who has to do it, right?
00:38:38.079 --> 00:38:39.760
He has to take ownership for that.
00:38:40.239 --> 00:38:46.719
Yeah, and it's a beautiful irony that AI is allowing us to really dig deep, actually.
00:38:46.719 --> 00:38:54.079
And this was again when I switched and I started pivoting and experimenting with AI, I did not expect that outcome.
00:38:54.079 --> 00:39:02.159
And where I am today, those for me again, this is personally, has definitely been the experience.
00:39:02.159 --> 00:39:07.119
And you kind of are validating that anecdotal experience of mine.
00:39:07.119 --> 00:39:15.760
Uh Ramesh, you you mentioned you have this global experience with through the mentoring and the work that you've done.
00:39:15.760 --> 00:39:28.400
Does globalization create greater opportunity for us technical communicators, or does it also risk making documentation work something organizations increasingly evaluate primarily through cost?
00:39:29.440 --> 00:39:30.719
I think it increases opportunity.
00:39:30.719 --> 00:39:32.559
Definitely there's a cost aspect.
00:39:32.559 --> 00:39:38.480
I mean, hiring or investment in people has always had the cost aspect.
00:39:38.480 --> 00:39:42.400
But again, getting the right talent is equally important.
00:39:42.400 --> 00:39:50.960
As a good leader, you would always ensure that you get the right talent to avoid a lot of other things which may cost you in a different way.
00:39:50.960 --> 00:39:59.199
So, in that sense, if you have to get the right hire, you cannot restrict yourself to certain regions or certain areas or whatever.
00:39:59.199 --> 00:40:14.480
So, in that sense, globalization definitely makes a lot of sense because you get access to good talent pool, and as far as your business needs are concerned, they will be met, and definitely it will create more opportunities.
00:40:14.480 --> 00:40:20.639
And of course, uh it's not going to be similar across regions or whatever.
00:40:20.639 --> 00:40:27.280
It's all dictated by the needs and the talent and the skills and the requirements and so on.
00:40:27.280 --> 00:40:33.039
So, but if you ask me, I would definitely recommend globalization as far as our profession.
00:40:33.039 --> 00:40:48.239
One, of course, in terms of opportunities, uh, but in terms of learning, or I work a lot with communities, and for me, in this age, all the learning will happen only socially, not traditional ways.
00:40:48.239 --> 00:40:56.239
So I would rate that you need to be part of a global network or global communities to be able to learn more.
00:40:56.239 --> 00:41:02.400
You need to experiment more, share more, invite views, learn from others, and so on.
00:41:02.400 --> 00:41:07.760
So, in that particular context, yes, globalization makes a lot of sense.
00:41:07.760 --> 00:41:16.320
In fact, I would say even three, four decades back, a lot of my learning uh did happen through my peers who are based across the globe.
00:41:16.320 --> 00:41:24.880
I mean, because even the cultural uh nuances are equally important because each uh peer brings a different aspect.
00:41:24.880 --> 00:41:33.119
And as we go ahead, I would say that even linguistics, cultural nuances are very important from an end-user perspective.
00:41:33.119 --> 00:41:37.920
The more you understand that, the value that you will add will be far better.
00:41:37.920 --> 00:41:48.480
And in that case, definitely understanding globalization, global cultures, different regions, different individuals is more important, is what I would say.
00:41:49.199 --> 00:41:57.360
Yeah, in that same way, Ramesh, where do you see career expectations differing between one country?
00:41:57.360 --> 00:42:01.440
I don't want to say India versus the US, but just across the world.
00:42:01.440 --> 00:42:04.239
How do you see career expectations differing?
00:42:05.280 --> 00:42:18.320
I I think more than career, I would say access to resources, be it in terms of learning, be in terms of knowledge, or other things which enable learning and thereby the career, right?
00:42:18.320 --> 00:42:20.480
And I would give a quick example.
00:42:20.480 --> 00:42:22.800
Like I will give my own example.
00:42:22.800 --> 00:42:28.320
Uh when I started off uh tech writing, I was clueless about tech writing, right?
00:42:28.320 --> 00:42:30.400
I had started with ISO documentation.
00:42:30.400 --> 00:42:37.920
Now, if if I were to learn tech writing, I would always recommend that you learn tech writing from the right tech writer.
00:42:37.920 --> 00:42:45.039
That's very important because unless you learn tech writing the right way, it's not going to make a huge difference, right?
00:42:45.039 --> 00:42:51.679
Because if I learn the wrong stuff, I'll be doing uh totally unaware the things which I should not be doing.
00:42:51.679 --> 00:42:56.000
Now, you need a right person to be able to guide you.
00:42:56.000 --> 00:43:06.800
All right, and in that case, I would say I was extremely fortunate to have peers who are very seasoned tech writers back then itself who guided me uh through this process.
00:43:06.800 --> 00:43:10.880
And that is where mentoring plays a very important role.
00:43:10.880 --> 00:43:20.000
It's just not about skills, but there is somebody overseeing you, guiding you on that path, helping you deal with every challenge.
00:43:20.000 --> 00:43:26.719
Not that they are practically doing it, but they are there to kind of you know enable your growth, right?
00:43:26.719 --> 00:43:31.199
And that's is very important, is what I would say.
00:43:31.199 --> 00:43:36.960
And uh mentoring is more than the theoretical stuff that we talk about.
00:43:36.960 --> 00:44:10.079
Mentoring is never about theoretical stuff, or it is not coaching, or it is not spoon feeding, it's about you do your own stuff, but if there is some major eventuality or something, something very serious, some something seriously going wrong, either with what you're doing, your career or something, there is somebody to help you to avoid those pitfalls or somebody to correct that, somebody to bring you on the right path with your experience, with your knowledge, with your examples.
00:44:10.079 --> 00:44:18.320
And that is where I think we are lacking right now somewhere, because one, of course, uh, we are seeking new horizons.
00:44:18.320 --> 00:44:27.039
There's there is no clarity, and definitely there are going to be no clear-cut roles, clear-cut demarcation, and all of that.
00:44:27.039 --> 00:44:34.159
But at the same time, culturally, not everybody is willing to share, mentor, and all of that.
00:44:34.159 --> 00:44:46.000
Like, unlike what I've seen in the past, people were so forthcoming and they were so willing because it requires a lot of energy and time to help somebody grow, right?
00:44:46.000 --> 00:44:53.760
I mean, while you have your own professional and personal commitments, imagine that you are investing in mentoring others, right?
00:44:53.760 --> 00:45:04.239
And I really appreciate all those who have done that for me and who have been doing that as part of various communities in the last few decades, you know.
00:45:04.239 --> 00:45:07.199
And I think that trend should continue.
00:45:07.199 --> 00:45:20.159
But unfortunately, with a lot of devices, with a lot of technology advancement, and now with AI, slowly that people connect is missing.
00:45:20.159 --> 00:45:23.840
I mean, the communities are slowly dying down.
00:45:23.840 --> 00:45:27.280
People are not building, they are not nurturing that.
00:45:27.280 --> 00:45:31.920
And I and the irony is now all the learning has to happen socially.
00:45:31.920 --> 00:45:33.760
It's all about experiments.
00:45:33.760 --> 00:45:41.199
Now, if I do an experiment and if I don't connect with others, or if I don't know whom I should talk to, how am I going to learn?
00:45:41.199 --> 00:45:47.679
That's where I think the social aspect or the community aspect plays a very critical role.
00:45:47.679 --> 00:45:54.960
And I think we as a profession need to do a lot to nurture these communities, right?
00:45:54.960 --> 00:46:03.679
And unfortunately, there are not many global communities right now or communities of repute that are there or exist.
00:46:03.679 --> 00:46:11.518
There could be a lot of communities in pockets doing great work, but I think the synergy aspect would be missing, right?
00:46:11.518 --> 00:46:20.400
And that's what is really required the unifying aspect or bringing in all that knowledge, bringing in all the insights, you know.
00:46:20.400 --> 00:46:24.159
And that's going to be one of the most important things as we go forward.
00:46:24.960 --> 00:46:28.880
You're making me ask a lot of questions, but I'm going to go with this one question.
00:46:28.880 --> 00:46:33.280
You rightly mentioned that you have to have the right mentoring.
00:46:33.280 --> 00:46:37.920
Now, somebody who is getting mentored, what do you think they should be looking for?
00:46:37.920 --> 00:46:40.079
What kind of red flag should they be looking for?
00:46:40.079 --> 00:46:48.400
If they are getting mentored, if they're fortunate, but things that they should not be learning, or rather unlearning, or even maybe teaching the mentor.
00:46:48.400 --> 00:46:50.639
I would love to get a take on that.
00:46:51.360 --> 00:46:59.119
Like I said, you know, first thing is, of course, even before you take any mentoring, I think that self-introspection is very important.
00:46:59.119 --> 00:47:03.119
Unless you have that, even a mentor will not be able to help you.
00:47:03.119 --> 00:47:05.679
So at least you should have a clear idea.
00:47:05.679 --> 00:47:14.079
Or if you don't have one, of course you can see because innate qualities, inherent strengths differ from individual to individual.
00:47:14.079 --> 00:47:18.960
It's like a mentor will not have a universal solution for everyone.
00:47:18.960 --> 00:47:22.559
It's like you have to really go into depth for each individual.
00:47:22.559 --> 00:47:29.840
It's all about customization, personalization, it's all about your aspirations, it's about your dreams and wishes.
00:47:29.840 --> 00:47:40.000
And of course, the gap between it, like I might aspire for a lot of things, but if my strengths are not aligned with that, I may not be able to achieve that.
00:47:40.000 --> 00:47:51.920
So it's it requires a lot of courage also to tell you the truth up front, like what you have, what you don't have, what you can do well, like typically the writer and the editor, right?
00:47:51.920 --> 00:48:03.039
If the editor shies away from telling you that you know the content is great or not, or whatever, then you're really not doing a service uh to the writer in that sense.
00:48:03.039 --> 00:48:12.159
Because you're not really helping that person, because trying to please somebody is not going to really help you, or giving temporary solutions is not going to work for the individual.
00:48:12.159 --> 00:48:20.159
Advice as important as "You should not be working in this field" is equally important if they don't have the skills, right?
00:48:20.159 --> 00:48:24.880
But I think very few people uh would speak up like that or would be upfront.
00:48:24.880 --> 00:48:39.679
But I think that's important because you really need to work at that level with a mentee to be able to really understand all aspects holistically, even before you suggest anything.
00:48:39.679 --> 00:48:46.320
And the mentoring happens much later, I would say, only when you understand all of this.
00:48:46.320 --> 00:48:52.159
It's not like you directly dive in, like somebody says, I want to learn this, and you start mentoring.
00:48:52.159 --> 00:48:54.239
I never do that, in fact.
00:48:54.239 --> 00:48:57.119
I never coach, also, I never train people.
00:48:57.119 --> 00:49:04.239
I just try to be in the background and try to enable their growth with what is available and whatnot.
00:49:04.239 --> 00:49:07.599
So that's the approach I would take from a mentoring perspective.
00:49:07.599 --> 00:49:10.400
And it's been pretty successful at that.
00:49:10.400 --> 00:49:16.400
And of course, I have also told a lot of people why they should not take up tech writing also as a profession.
00:49:16.400 --> 00:49:31.679
So, but I think truth and honesty is equally important no matter what profession you are, or what professional, the most important aspect of that is professional ethics, and you also owe it to the profession.
00:49:31.679 --> 00:49:34.719
You also owe it to the professions, right?
00:49:34.719 --> 00:49:37.760
So you have to do the right things all the time.
00:49:37.760 --> 00:49:42.320
You should not hesitate or restrain yourself from doing that.
00:49:42.320 --> 00:49:46.639
So be it mentoring or be it creating deliverables or serving the customers.
00:49:46.639 --> 00:49:48.559
Um it's all the same.
00:49:48.559 --> 00:49:50.880
I think it's all about servant leadership.
00:49:50.880 --> 00:49:57.679
You've consciously made a choice to serve or give back or do things that you wish to, right?
00:49:57.679 --> 00:49:59.920
That's the way I look at it, including mentoring.
00:49:59.920 --> 00:50:03.599
So the point is to enable and empower the individual.
00:50:03.599 --> 00:50:06.800
You can only do that when you understand the individual better.
00:50:06.800 --> 00:50:14.320
And if you don't, you need to enable them to do that, and as a result of the outcome, enable them with whatever is required.
00:50:14.320 --> 00:50:18.320
And that requires the individual themselves to do a lot of effort.
00:50:18.320 --> 00:50:24.960
It could be very difficult, it could be complex, it may take time, it may not yield results as you expect.
00:50:24.960 --> 00:50:31.840
But nonetheless, it will happen because once you're set up on the right path, you're set up for success.
00:50:31.840 --> 00:50:37.760
It's the path that is important because without that foresight, you know, it will not help.
00:50:37.760 --> 00:50:44.000
You may have the best uh vehicle, but if you don't have a map, you may not land at your destination.
00:50:44.000 --> 00:50:49.360
You have to have the map, you have to have the GPS to be able to reach your destination.
00:50:49.360 --> 00:50:51.039
But who gives the GPS?
00:50:51.039 --> 00:50:52.719
Mentoring could be that.
00:50:53.199 --> 00:50:54.800
It's been a great discussion, Ramesh.
00:50:54.800 --> 00:50:56.000
I invite you.
00:50:56.000 --> 00:50:59.119
Do you have any last thoughts that you would like to add?
00:50:59.840 --> 00:51:06.159
I would say that we often say that our work should speak, but I disagree on that.
00:51:06.159 --> 00:51:10.480
I feel as technical communicators, we should speak about our work.
00:51:10.480 --> 00:51:15.599
We should be very vocal advocates and we should be ambassadors of our profession.
00:51:15.599 --> 00:51:20.159
My mission is to create awareness and promote our profession.
00:51:20.159 --> 00:51:35.199
And I would request, I mean, through this podcast, I would like to say unless we invest our time in being vocal or being an advocate for our own profession, we'll not be able to survive and thrive.
00:51:35.199 --> 00:51:39.920
So it's very important to nurture our own profession.
00:51:39.920 --> 00:51:43.760
It's very important to connect with fellow communicators.
00:51:43.760 --> 00:51:47.440
It is very important to be part of a community.
00:51:47.440 --> 00:51:50.000
It's important to give back.
00:51:50.000 --> 00:51:58.719
It's not just being consuming, it's not about just taking or it's also about giving, giving back whatever you can.
00:51:58.719 --> 00:52:04.000
So it's good to be part of a community and give back apart from your professional commitments.
00:52:04.000 --> 00:52:09.199
And I think that will really keep uh the profession really thriving.
00:52:09.199 --> 00:52:11.039
And I don't think so.
00:52:11.039 --> 00:52:23.760
Any technology can really replace or take away tech comm because tech comm or communication by itself can only enrich and elevate the way we go ahead.
00:52:23.760 --> 00:52:25.518
That's my message to all.
00:52:26.079 --> 00:52:26.480
Thank you, Ramesh.
00:52:26.480 --> 00:52:31.360
And I want to give a big shout out to Nibu for introducing us.
00:52:31.360 --> 00:52:34.320
Without that introduction, we wouldn't have had this conversation.
00:52:34.320 --> 00:52:35.440
So thank you, Ramesh.
00:52:36.079 --> 00:52:42.239
And definitely, I would also like to thank Nibu for introducing me to you.
00:52:42.239 --> 00:52:45.119
And I enjoyed every bit of this conversation.
00:52:45.119 --> 00:52:46.400
Thanks to Nibu.
00:52:46.400 --> 00:52:49.599
And it was great talking to you, Zohra, today.
00:52:49.599 --> 00:52:53.119
And uh I hope it was useful and uh helpful.
00:52:53.119 --> 00:52:57.599
If not, definitely I can look forward to sharing more stuff if required.
00:52:58.480 --> 00:53:02.400
This was very helpful, and I would love to have you again on my show in the next season.
00:53:02.400 --> 00:53:03.760
So, with that, thanks, Ramesh.
00:53:03.760 --> 00:53:05.119
Have a great evening.
00:53:05.119 --> 00:53:06.480
I know you're calling from India.
00:53:06.480 --> 00:53:09.119
It's pretty late in the evening for you there.
00:53:09.119 --> 00:53:11.518
I appreciate your time and have a good one.
00:53:11.920 --> 00:53:12.239
Thank you, Zohra.
00:53:12.239 --> 00:53:13.679
You do have a great day.
00:53:13.679 --> 00:53:19.518
Thanks for talking to me today, and all the best, and you're doing a great job uh through these podcasts.
00:53:19.518 --> 00:53:27.920
I only hope and wish you all the best that you continue and invite as many experts, and this is the best way to give back to the community, too.
00:53:28.639 --> 00:53:29.199
Thank you.
00:53:29.199 --> 00:53:32.559
Thank you for listening to Inside Tech Comm.
00:53:32.559 --> 00:53:37.199
If there's a guest you would love to hear on the show, please let me know.
00:53:37.199 --> 00:53:42.400
And don't forget to follow and catch every episode on your favorite podcast app.
00:53:42.400 --> 00:53:43.760
See you next time.
00:00:02.240 --> 00:00:06.878
Hello friends and welcome to season eight of Inside Tech Comm with Zohra Mutabanna.
00:00:06.878 --> 00:00:16.160
This season features a collection of conversations that explore the ideas, challenges, and opportunities shaping technical communication today.
00:00:16.160 --> 00:00:21.838
From AI and content strategy to leadership, product thinking, and the future of our profession.
00:00:21.838 --> 00:00:26.160
Each episode offers a fresh perspective from people doing the work.
00:00:26.160 --> 00:00:27.120
Let's get started.
00:00:30.460 --> 00:00:34.719
Season eight is proudly sponsored by LavaCon.
00:00:34.920 --> 00:00:41.380
Use discount code ITC26 to save $200 on registration for this year's conference.
00:00:41.859 --> 00:00:44.719
I'll share more about LavaCon later in this episode.
00:00:45.600 --> 00:00:46.240
Hello listeners.
00:00:46.799 --> 00:00:48.560
Welcome to a new episode.
00:00:48.619 --> 00:01:09.760
Today we have Ramesh Aiyyangar, and we are going to be talking about how with the field, the way it is evolving currently and where things are with not just because of AI and new technologies, but because the roles and career paths and expectations in the community are that the practitioners, the technical writers that support, is shifting.
00:01:09.760 --> 00:01:20.480
So we'll explore what these changes mean for the community and draw on Ramesh's experience across industry, leadership, training, mentoring, and community building.
00:01:20.480 --> 00:01:22.560
This is going to be more of a human conversation.
00:01:22.560 --> 00:01:24.959
With that, Ramesh, welcome to my show.
00:01:25.680 --> 00:01:30.319
Thank you so much, Zohra, for giving me this opportunity to be on your show.
00:01:30.319 --> 00:01:33.040
I'm really looking forward to this conversation.
00:01:33.040 --> 00:01:46.000
And I must add, Zohra, that you're doing a great service to the technical communication profession by doing these podcasts and getting specialists and others to share their insights.
00:01:46.000 --> 00:01:50.480
And we learn a lot from these podcasts and there are a lot of takeaways.
00:01:50.480 --> 00:02:00.799
So I really appreciate that you spare your valuable time to talk to experts, and it's a huge learning for all of us from the tech comm community.
00:02:00.799 --> 00:02:01.438
Thank you.
00:02:01.840 --> 00:02:02.078
Thank you, Ramesh.
00:02:02.078 --> 00:02:03.358
Thank you.
00:02:03.358 --> 00:02:09.680
It's a pleasure doing this, and it's thank you to people like you who are willing to come and talk to me.
00:02:09.680 --> 00:02:12.000
So it's a community effort, and I appreciate that.
00:02:12.000 --> 00:02:13.438
Appreciate your time as well.
00:02:13.438 --> 00:02:18.800
Ramesh, introduce yourself and tell us about the different roles you've played in your long career.
00:02:19.598 --> 00:02:20.240
Absolutely, Zohra.
00:02:20.240 --> 00:02:28.158
So to tell you very briefly, I enjoy simplifying the complex, enriching it, and that's what I've been doing.
00:02:28.158 --> 00:02:32.318
And I know it's been a long journey, nearly four decades so far.
00:02:32.318 --> 00:02:37.280
So the way it happens for me is I would divide into two phases.
00:02:37.280 --> 00:02:42.960
The first phase is before tech comm and after I joined tech comm.
00:02:42.960 --> 00:02:47.438
The reason why I would like to do that is the common thread is communication.
00:02:47.438 --> 00:03:09.919
So before I entered tech writing, I'm primarily a journalist and I worked as a reporter, editor, and I also had short stints in terms of advertising and public relations and other areas of communication, which tend to be more on the creative side, or as we call as a MarCom in today's parlance.
00:03:09.919 --> 00:03:19.038
And around early 90s is when we got computers and we started acquiring computer skills, software knowledge, and so on.
00:03:19.038 --> 00:03:25.520
And that's precisely around that time, around 93-94, I entered the software industry.
00:03:25.520 --> 00:03:35.360
And my first job as a tech writer was with a software company in Pune called Kale Consultants, and it was more of ISO documentation.
00:03:35.360 --> 00:03:43.120
And of course, I had no clue about technical writing then, and it's been a totally hands-on approach.
00:03:43.120 --> 00:03:46.400
I don't have any formal degrees in tech writing.
00:03:46.400 --> 00:03:56.318
Thanks to my peers in US and Europe and other areas who helped me acquire the primary core skills and, of course, the community.
00:03:56.318 --> 00:04:21.680
I owe a lot of my skills, my accomplishments to the STC community, where I've spent a substantial time of my professional career is around two decades, and I enjoyed every moment of it, not only in terms of learning and development, but also the community aspect in terms of networking, connect, and so on.
00:04:21.680 --> 00:04:31.278
And I'm very thankful to STC for having given me this opportunity to be associated so closely with some of the best in the industry.
00:04:31.278 --> 00:04:37.439
And of course, a lot of them whom I work very closely are pretty seniors right now.
00:04:37.439 --> 00:04:44.879
In fact, I would like to call out a lot of names, but I would avoid that, who had a major influence and who have helped me through.
00:04:44.879 --> 00:04:48.319
But it's been a really satisfying and long journey.
00:04:48.319 --> 00:04:52.560
But at the same time, it brings a lot of disappointment to me.
00:04:52.560 --> 00:05:00.240
The news that STC, uh, had to close its operations a few years back.
00:05:00.240 --> 00:05:09.360
And of course, I feel uh that you know we still do not have a global community like STC, which really enabled a lot of things.
00:05:09.360 --> 00:05:23.838
In fact, they were critical in terms of defining our profession, creating awareness, promoting things, and listing everything that we really needed, especially for folks like me who were in India and didn't have a clue about it.
00:05:23.838 --> 00:05:25.519
It helped me a lot.
00:05:25.519 --> 00:05:28.720
And of course, I wanted to do my little bit.
00:05:28.720 --> 00:05:45.278
And since I had this experience with STC, I started my own group in India called as Institute for Technical Communicators of India, which is primarily a free platform to enable people to come together, connect, and learn.
00:05:45.278 --> 00:05:56.000
And eventually this platform kind of you know uh translated into what I see right now as a company, which is TechWritePro.
00:05:56.000 --> 00:06:21.680
Of course, I do not have any major commercial ambition, but my mission is primarily to create awareness and promote the profession in whatever limited way I can, and to empower technical writers uh to a great extent and provide opportunities, enable them, recognize them, and do whatever I can as an individual through this company.
00:06:21.680 --> 00:06:23.360
That's roughly my background.
00:06:24.160 --> 00:06:26.800
So that is a very impressive background.
00:06:26.800 --> 00:06:29.439
Four decades, congratulations on that, Ramesh.
00:06:29.439 --> 00:06:31.439
Thank you for doing that.
00:06:31.439 --> 00:06:35.838
I think we need more such anchors today than we realize.
00:06:36.720 --> 00:06:38.399
Thank you so much, Zohra, for your kind words.
00:06:39.199 --> 00:06:42.079
You've seen technical communication with such a long spanning career.
00:06:42.079 --> 00:06:45.278
You've seen technical communication evolve through significant changes.
00:06:45.278 --> 00:06:49.600
When you look at the profession today, what concerns you most?
00:06:49.600 --> 00:06:52.879
Not in terms of the technology, but about the people.
00:06:53.680 --> 00:06:55.838
Absolutely. And you're absolutely right.
00:06:55.838 --> 00:07:01.360
I mean, especially in this long journey, I have seen tech comm really evolve.
00:07:01.360 --> 00:07:05.680
In fact, I would extend it further to publishing as such, you know.
00:07:05.680 --> 00:07:11.680
Uh way back when I started my journalism and was working with newspapers and periodicals.
00:07:11.680 --> 00:07:27.600
I uh have literally seen the manual uh printing press where they used to assemble those fonts and then kind of print it to uh AI agents today and all about skills.
00:07:27.600 --> 00:07:32.720
So uh it's like really an evolutionary thing that I've really seen.
00:07:32.720 --> 00:07:51.439
But the most distinctive and important thing is the human element is always there, and I don't think so, irrespective of the technology changes and other things, the human aspect will go away, especially in terms of tech writing, because it's a very niche skill.
00:07:51.439 --> 00:08:03.519
Even if it is AI, it's all about documentation, it's all about automation, and it's only going to be about the mechanical or repetitive or iterative task.
00:08:03.519 --> 00:08:11.600
A lot of things related to documentation cannot be automated, so the human element will always be there.
00:08:11.600 --> 00:08:22.959
And the most critical aspect, I think, is the critical thinking or the thinking aspect, which is something very specific to humans, and I don't think so.
00:08:22.959 --> 00:08:41.840
Automation or agents can really do that because even with AI, I think the foundational stuff or the overarching content, or you know, the judgment aspect, the discernment, even after the drafts are created, is primarily with humans.
00:08:41.840 --> 00:08:44.000
So who's driving all of this?
00:08:44.000 --> 00:08:46.000
It's the human in the loop, right?
00:08:46.000 --> 00:08:50.879
So I think that's a very, very important element, and it will not go away.
00:08:50.879 --> 00:09:07.918
And the core skills of thinking, articulating, explaining, simplifying, giving better examples, understanding the user needs is so important that we understand the psychological aspect, the behaviors, and so on.
00:09:07.918 --> 00:09:19.200
And we do say that we have agents, the traffic to doc sites are more of agents and stuff like that, but we still do not know how they consume content, right?
00:09:19.200 --> 00:09:28.798
And it's so important to understand how end users, and definitely it's going to be a human at the end of the chain who is kind of looking at the content.
00:09:28.798 --> 00:09:40.720
So these things are very important, and I think we really need to uh understand these aspects, especially in the current era of AI, while we talk a lot about automation.
00:09:40.720 --> 00:09:42.960
I hope that answers your question.
00:09:43.600 --> 00:09:43.840
It does.
00:09:43.840 --> 00:09:55.918
I think you're right about the human element, the core human characteristics that we have, that we possess, that cannot ever be well, can be replicated by a machine.
00:09:55.918 --> 00:09:58.240
I'm gonna take a chance and say that.
00:09:58.240 --> 00:10:01.278
And technical writing is a niche field.
00:10:01.278 --> 00:10:06.080
And do you have any concerns since you run an institute?
00:10:06.080 --> 00:10:12.000
What kind of concerns are you seeing surface when you talk to technical writers?
00:10:12.960 --> 00:10:18.158
I don't see uh quite a few issues when it comes to learning, upskilling.
00:10:18.158 --> 00:10:29.840
There are a lot of anxiety and there are a lot of worry, and people still are not clear as to what is the path because it's like seeking the unknown.
00:10:29.840 --> 00:10:39.918
Uh, people are not sure about what careers they will have or what are the things that they need to do, because not all companies are investing in AI.
00:10:39.918 --> 00:10:44.158
They are not very clear as to what skills they need to build.
00:10:44.158 --> 00:11:03.038
A lot of it also has to do with self-reflection, because very few individuals really spend a substantial time in understanding or maybe introspecting, realizing their own strengths, weaknesses, or even for that matter, what they really want to do going ahead.
00:11:03.038 --> 00:11:08.798
In some cases, people take an approach of let's take it as it comes, right?
00:11:08.798 --> 00:11:12.080
So the kind of clarity is not there.
00:11:12.080 --> 00:11:28.960
So, what really happens in a situation like this when we are going through a mini-revolution right now, and we are trying to tread unknown territories or explore new areas or new frontiers, how do you really go about it, right?
00:11:28.960 --> 00:11:31.918
So I think the first thing is optimism.
00:11:31.918 --> 00:11:42.158
I mean, we have to have a lot of optimism because it's not something that is very easily available or it's there around the corner.
00:11:42.158 --> 00:11:43.519
It's within you.
00:11:43.519 --> 00:11:46.000
You have to keep that hope each day.
00:11:46.000 --> 00:11:48.798
It is something that you build every day, right?
00:11:48.798 --> 00:11:56.240
So being very hopeful, that's very important because anxiety, worry, stress is not going to help you in any way.
00:11:56.240 --> 00:12:02.000
It kind of paralyzes or things become stagnant, and then you're not able to act.
00:12:02.000 --> 00:12:08.320
And that's the worst thing that you can do to your career when you're just kind of you know thinking and not acting.
00:12:08.320 --> 00:12:11.120
So optimism is one thing definitely.
00:12:11.120 --> 00:12:16.000
But the second thing is um it's not only about technical skills.
00:12:16.000 --> 00:12:25.600
People are so obsessed with only the technical skills or maybe just the tools or you know, software and stuff.
00:12:25.600 --> 00:12:32.798
While it is good to learn these skills, it is good to learn about AI and tools and so on.
00:12:32.798 --> 00:12:38.000
But as I said sometime back, automation is only to a limited extent.
00:12:38.000 --> 00:12:52.240
The kind of value that you add is going to be from your core skills, because at the end of the day, it is the experience for the user or the consumer of content, and there's a human at the end of the chain.
00:12:52.240 --> 00:12:54.080
So that's very important.
00:12:54.080 --> 00:13:13.918
So while technology skills are important, you also need to focus on the other aspects which are less uh known right now, because we really need to understand the user behavior, how they are really kind of you know consuming the content right now, because it's just not about agents, uh right.
00:13:13.918 --> 00:13:16.798
So, do we really have data about that?
00:13:16.798 --> 00:13:31.278
It's not about just some analytics, uh, like how many hits are there on the pages, or how many agents are visiting the page, or so on, but you really need to see the behavior, like what typically we had UX folks doing it, right?
00:13:31.278 --> 00:13:43.840
The user behavior, trying to see how people are using it because even the customers you uh will be kind of exploring all of this, they will be implementing software, they'll be investing their time in this.
00:13:43.840 --> 00:13:46.480
So, doc is just a small aspect of it.
00:13:46.480 --> 00:14:07.759
So we have to understand that, and I think it is still pretty gray, or people do not have enough access to all that data, to all that analytics, or to all those interactions and so on, because not all tech writers are really cleared for that, and that is the area where you can really add value.
00:14:07.759 --> 00:14:14.960
So, what I would say is the ultimate goal of documentation is to exceed customer expectations.
00:14:14.960 --> 00:14:32.639
So, irrespective of the technology and the advancement, while it is good to learn all of that, we should not miss the core aspect in terms of why you're writing those docs, for whom you're writing those docs, and how the experience is.
00:14:32.639 --> 00:14:36.000
It's like uh I can give a simple analogy, right?
00:14:36.000 --> 00:14:37.360
Like cooking, right?
00:14:37.360 --> 00:14:45.519
We can have all the ingredients in place, very uh neatly placed, the right quantity, the right volume, and so on.
00:14:45.519 --> 00:14:48.960
But ultimately, uh the person who's cooking it.
00:14:48.960 --> 00:14:51.278
I mean, you need to get that taste, right?
00:14:51.278 --> 00:14:53.519
And taste is something which is an experience.
00:14:53.519 --> 00:14:59.519
Not everybody can create the right dish with the right taste, something which can be relished.
00:14:59.519 --> 00:15:10.798
Now that comes with your skills, that comes with your experience, that comes with the knowledge of people who are going to have that dish, and so on.
00:15:10.798 --> 00:15:14.240
So that's where the differentiator will happen, right?
00:15:14.240 --> 00:15:16.879
So we have to focus on the taste aspect.
00:15:16.879 --> 00:15:25.440
You may have the best ingredient, you may have the best chunks of content, but if you don't know how to orchestrate the whole thing, what's the point?
00:15:25.440 --> 00:15:40.639
I might have the best violinist, I might have the best vocalist, I might have the best guitarist, but if I don't know how to compose or how to create that symphony, that music is not going to be so soothing for me, right?
00:15:40.639 --> 00:15:42.960
So, or enjoyable, correct?
00:15:42.960 --> 00:15:57.278
So somewhere we miss that aspect or that overarching the vision, the foresight, the ownership, because doc is not about deliverables anymore, right?
00:15:57.278 --> 00:16:01.278
It's about uh a service, it's a product by itself.
00:16:01.278 --> 00:16:06.639
So, do all tech writers really understand that doc is a product by itself?
00:16:06.639 --> 00:16:22.000
We need to take ownership, we need to have that vision, and that's where other aspects like content strategy is very important, and then we have content design, then we have the other aspect of system design, all right?
00:16:22.000 --> 00:16:27.200
And then we have the delivery aspect where all the operational aspects are concerned.
00:16:27.200 --> 00:16:32.320
So these are four major things which are very important as we go ahead.
00:16:32.320 --> 00:16:48.080
Now, you might polarize to some aspects or you may have proximity to some of these things, but you cannot restrict yourself, you cannot say I do not know the other things, or I will not do this, or I will not do that.
00:16:48.080 --> 00:16:50.798
You'll have to be extremely flexible, right?
00:16:50.798 --> 00:16:52.798
And that's where you have to keep moving.
00:16:52.798 --> 00:17:02.480
If you say no, I am a DITA expert, or I just want to do information architecture, but I don't know about the product, doc as a product.
00:17:02.480 --> 00:17:10.960
I don't understand content strategy, or I really don't understand the engineering aspect or the engineering depth or the product in detail.
00:17:10.960 --> 00:17:18.720
You cannot afford to say those things going forward because a lot of things will matter on the value add.
00:17:18.720 --> 00:17:40.558
Now it's the same product, but there is novelty in there because you have to look at it at different angles, not the same way that, for example, typically in the olden days, when you used to work with products, we always used to focus our time on finding bugs, be it UI, be it the functionality, be it the error, it could be anything.
00:17:40.558 --> 00:17:50.798
But the way we would look at the product is the effort would be to break it down, you know, and try to do as many things to add value to it from various aspects.
00:17:50.798 --> 00:17:55.759
So the depth from an engineering perspective is very important.
00:17:55.759 --> 00:18:15.759
You have to be able to look at a product in depth, not the same way as others, possibly different ways of how users will look at it, or even from your own experience and skills and apply it to some of the things that I mentioned, that is what is going to be the differentiator.
00:18:15.759 --> 00:18:23.038
Of course, we have other aspects like delivery and all of that, the system aspect and so on.
00:18:23.038 --> 00:18:29.358
But this is how uh I look at it, or this is what I think will be important going forward.
00:18:29.358 --> 00:18:31.358
Yeah, I hope that makes sense.
00:18:31.680 --> 00:18:32.640
I mean, you can ask me.
00:18:32.640 --> 00:18:34.078
Definitely makes sense.
00:18:34.078 --> 00:18:42.400
How is this message landing with the youngsters that are entering the field versus somebody who's been in the field for somebody who's experienced?
00:18:42.400 --> 00:18:52.160
Because I'm I'm just thinking right now, the message in general that I'm hearing around me is youngsters that are finding it hard to break into any profession.
00:18:52.160 --> 00:18:57.920
So, this conversation, as much as it is about technical communication, other roles are equally being challenged.
00:18:57.920 --> 00:19:08.960
Have you noticed any marked difference in how the two generations, the different generations receive your message that you've talked about from your experience specifically?
00:19:10.160 --> 00:19:10.480
Yeah, definitely.
00:19:10.480 --> 00:19:28.078
Because uh, see, in terms of experience, we have to understand there's a lot of unlearning also required because when it comes to learning, unlearning is equally important because when you're going through a revolution, you cannot afford to learn the traditional way, right?
00:19:28.078 --> 00:19:37.440
Now I cannot learn AI through books or through uh Udemy or doing some certification or you know other things.
00:19:37.440 --> 00:19:39.759
That's not really going to take me very far.
00:19:39.759 --> 00:19:44.318
But I can do that, or it can help me understand some conceptual stuff.
00:19:44.318 --> 00:19:48.880
You have to do things for yourself to get a good grasp of it.
00:19:48.880 --> 00:20:03.358
Like as I tell them, it's not about formatting your resume anymore, it's not about how good your resume looks, but like as Fabrizio Ferri Benedetti has said in one of his articles, it's about the beauty of the doc itself, right?
00:20:03.358 --> 00:20:16.318
And when I say beauty of the doc, it has a different connotation or an interpretation, which indirectly reflects on the principles of what good tech writing is all about, right?
00:20:16.318 --> 00:20:26.720
I mean, for example, if I'm trying to simplify something complex, it should be so simple for the user that he doesn't have to carry the load of the complexity.
00:20:26.720 --> 00:20:29.920
That is where your value add is.
00:20:29.920 --> 00:20:33.278
The transformation is the value add, right?
00:20:33.278 --> 00:20:41.838
And so the difference between the youngsters and the experienced is how you really adapt, how flexible you are.
00:20:41.838 --> 00:20:59.838
And definitely we all know that with age, with experience, we try to erect walls, we try to create fences, we try to get deeper into something, and you know, you don't want to experiment or you know, try out new stuff and all of that.
00:20:59.838 --> 00:21:02.480
I would definitely not recommend something like that.
00:21:02.480 --> 00:21:07.680
But the younger folks, they're totally new, they are open, they don't have any such blocks.
00:21:07.680 --> 00:21:14.000
So probably for them it would not be so difficult to adapt or to learn and all of that.
00:21:14.000 --> 00:21:21.920
But nonetheless, irrespective of whether you're young or senior or whatever, we are treading something totally unknown.
00:21:21.920 --> 00:21:24.720
Nobody knows where you're heading, right?
00:21:24.720 --> 00:21:29.759
So you have to explore, you have to discover, you have to learn.
00:21:29.759 --> 00:21:34.720
There's nothing like a ready map which is already there, right?
00:21:34.720 --> 00:21:41.519
Uh which you can navigate, or the typical linear kind of career ladders that we had earlier.
00:21:41.519 --> 00:21:42.960
It's not going to make sense.
00:21:42.960 --> 00:21:50.000
In fact, I doubt even if we'll have the same titles as technical writers or technical communicators, right?
00:21:50.000 --> 00:21:53.838
Now, people are talking about context engineers, content curators.
00:21:53.838 --> 00:21:59.358
There are as many titles, and this may uh vary as much as possible because.
00:21:59.358 --> 00:22:04.720
It depends upon the company, it depends upon the scale, it depends upon the size and so on.
00:22:04.720 --> 00:22:11.838
So if we try to typically expect things in the future based on the past, it's not going to work anymore.
00:22:11.838 --> 00:22:16.400
So the flexibility is one thing which is very, very important.
00:22:16.400 --> 00:22:23.278
But definitely one thing that one should definitely do and should have an excellent skill.
00:22:23.278 --> 00:22:25.680
And that's where I really appreciate your podcast.
00:22:25.680 --> 00:22:30.798
Like I said in my earlier conversation, the kind of questions that you ask, you know.
00:22:30.798 --> 00:22:32.558
That's a skill by itself.
00:22:32.558 --> 00:22:39.759
Because asking the right questions is going to really add a lot of value, and that's going to be a differentiator.
00:22:39.759 --> 00:22:51.440
Because now we take on roles as reviewers and editors, and we have to keep reviewing stuff endlessly through the entire day, right?
00:22:51.440 --> 00:22:53.838
And you have to ask a lot of questions.
00:22:53.838 --> 00:23:01.358
You'll have to call out what is trash, what is bullshit, what is right, what's wrong, what's not good, and all of that.
00:23:01.358 --> 00:23:03.200
And how are you going to do that, right?
00:23:03.200 --> 00:23:07.598
So you have to keep asking a lot of questions, challenge the status quo.
00:23:07.598 --> 00:23:11.680
You have to go back and tell them this is right, not right, and so on.
00:23:11.680 --> 00:23:22.160
So asking the right questions is one of the most like in the earlier days we used to say the interviewing skills where we used to connect with SME and ask a lot of questions.
00:23:22.160 --> 00:23:26.318
Unless you ask the right questions, you will not get the right content, right?
00:23:26.318 --> 00:23:29.118
So it's very important, I would say, going ahead.
00:23:29.118 --> 00:23:30.318
That's one skill.
00:23:30.318 --> 00:23:33.038
I would say thinking is critical.
00:23:33.038 --> 00:23:56.558
Asking questions is equally important to understand the why aspect because, like I said earlier, irrespective of all the automation, the explaining aspect, the fundamental aspect of what this product is, what the feature is all about, or all the conceptual related stuff is going to be done by writers, and you need to know to do that very well.
00:23:56.558 --> 00:23:57.278
Right.
00:23:57.519 --> 00:24:03.598
And that it doesn't matter which way you are on your career journey, how your experience.
00:24:03.598 --> 00:24:12.558
But when I asked you this, yeah, when I asked you this question, Ramesh, I came with a very different expectation from you in terms of the answer.
00:24:12.558 --> 00:24:14.720
But the and it's actually good.
00:24:14.720 --> 00:24:31.358
You broke, I suppose, you challenged me in a way to think differently because here I am experienced, and I thought you might say, Oh yeah, the youngsters and probably speak about them, but you actually started with the the experienced professionals have to unlearn.
00:24:31.358 --> 00:24:37.838
And that was a very, I think, a good way for me to challenge myself.
00:24:37.838 --> 00:24:39.519
I didn't expect that.
00:24:39.519 --> 00:24:40.880
I didn't expect that answer.
00:24:40.880 --> 00:24:42.240
So that's so important.
00:24:42.240 --> 00:24:43.519
I didn't even think about it.
00:24:43.519 --> 00:24:59.838
That what the experienced have to do, because I thought, oh, maybe the experienced are more advantaged, but you actually challenge that with your response, which was uh that fixed thinking, no experimentation, generally as we grow in our careers, that tends to happen.
00:25:00.880 --> 00:25:17.838
Right, uh Zohra, because we also have to move from hyper uh specialization to a generalization right now, because we have to move with the flow, we have to be extremely flexible, we have to connect, we have to have discourses, we have to connect with stakeholders, a lot of aspects, you know.
00:25:17.838 --> 00:25:23.440
So we cannot go with a rigid mind because see ultimate differentiator is the mindset, right?
00:25:23.440 --> 00:25:29.838
So and it's so important that you have need to have the right attitude to be able to survive and thrive.
00:25:29.838 --> 00:25:35.278
It's like when you're seeking storms, we cannot say this is the way I will do it, right?
00:25:35.278 --> 00:25:39.598
I mean, you never know how the storm is coming, what's the speed, how to handle it, right?
00:25:39.598 --> 00:25:48.160
So you'll have to uh do what is best at that particular moment and see how you uh kind of you know react to the whole thing.
00:25:48.160 --> 00:25:50.400
And merely reaction will not help.
00:25:50.400 --> 00:25:55.838
You need to respond to it in the right way, and that is only possible when you have an open mind.
00:25:57.038 --> 00:26:10.480
Yeah, and I think the earlier point that you made about self-reflecting is equally important because when you're in the storm in the thick of it, you're reacting, but then it's also important to pause and reflect is this where I'm headed?
00:26:10.480 --> 00:26:13.278
The what my response is, is that the right response?
00:26:13.278 --> 00:26:19.118
Because you still want to respond in an informed way.
00:26:19.118 --> 00:26:21.038
Would you agree with that?
00:26:21.358 --> 00:26:35.038
Absolutely. I give a lot of importance to, uh, self-introspection because I do a lot of mentoring and I see that uh people at times want to do things very, very mechanical.
00:26:35.038 --> 00:26:45.118
Uh, we are so used to the rat race, or we just want to compare ourselves with others and try to do things that have already been done.
00:26:45.118 --> 00:26:48.078
Uh, do only a few things because they are easy.
00:26:48.078 --> 00:26:54.720
Uh, we don't challenge us and say now you need to be prodded, you need to be nudged, and all of that.
00:26:54.720 --> 00:27:06.880
But if you really introspect, if you really understand yourself better, the way you would relate to the outside world will be far better, be it your professional life or other things.
00:27:06.880 --> 00:27:10.558
And when we say introspect, you really understand yourself.
00:27:10.558 --> 00:27:11.358
What is that?
00:27:11.358 --> 00:27:19.118
Because all said and done, we need to understand what is the purpose, how do we really create meaning in what we are doing, right?
00:27:19.118 --> 00:27:30.400
Because even the professional life, when you're spending a substantial amount of time of the day and the life, you definitely want it to be meaningful, satisfying, and fulfilling.
00:27:30.400 --> 00:27:37.920
It should not be like at the end of the day, you're so frustrated and you feel like, why am I doing this day in and day out?
00:27:37.920 --> 00:27:38.880
What's the point?
00:27:38.880 --> 00:27:48.240
You're not enjoying the process, and naturally, if some you're doing something that you're not enjoying, it doesn't give you joy, nor will it give others, right?
00:27:48.240 --> 00:27:50.798
So, and when will you realize that?
00:27:50.798 --> 00:27:59.759
You can realize that only when you introspect, when you pause, as you rightly said, stop, pause, and think, why am I doing this?
00:27:59.759 --> 00:28:01.838
What is the potential that I have?
00:28:01.838 --> 00:28:03.118
What am I good at?
00:28:03.118 --> 00:28:04.558
What would I like to do?
00:28:04.558 --> 00:28:11.598
No, the more you think, you will get some of these answers because, as we all know, all answers are within us only, right?
00:28:11.598 --> 00:28:23.358
And then it's just that we don't seek it, we don't spend time, we don't spend quality time with us because we are so busy hustling and doing things, you know.
00:28:23.358 --> 00:28:24.720
We don't get that time.
00:28:24.720 --> 00:28:34.318
So once you do that, and when you actually start putting things down and you get that clarity, the growth happens very fast.
00:28:34.318 --> 00:28:42.318
And uh the growth sometimes is so good that you yourself will not expect because there is nothing like can't, right?
00:28:42.318 --> 00:28:42.960
In that.
00:28:42.960 --> 00:28:46.160
Because that is something that you really understand very well.
00:28:46.160 --> 00:28:48.318
You know you want to do it, you love it.
00:28:48.318 --> 00:29:06.480
Then growth is like 10x times or maybe 100x times, but that exercise is extremely important because self-realization, as we say, is the goal, and the endeavors always to learn more about ourselves, which never really happens in the real world.
00:29:06.480 --> 00:29:13.598
It takes a lot of time to do that, and we are always figuring out what is the purpose, what is the meaning, and so on.
00:29:13.598 --> 00:29:35.440
So, of course, it may sound a bit spiritual or philosophical, but I would say in the age of AI world, it is very important that we need to uh kind of get back to the roots of the human thought process or action, and definitely all that is based on philosophy and all this kind of thinking, which will make you a better individual.
00:29:35.440 --> 00:29:42.400
Because if all that thinking didn't happen earlier, we wouldn't be here doing some of the things that we do today.
00:29:42.720 --> 00:29:49.059
The episode is sponsored by LavaCon, the content strategy conference taking place this October in Charlotte, North Carolina.
00:29:49.660 --> 00:30:03.358
With more than 70 sessions and workshops featuring speakers from companies like Salesforce, TikTok, T-Mobile, and Amazon, LavaCon brings together content strategists, documentation leaders, and content professionals to share practical ideas you can apply right away.
00:30:03.358 --> 00:30:10.400
And yes, it's known as the Fun Conference, too, with networking events, therapy dogs, comfort llamas, storytelling, and karaoke.
00:30:10.400 --> 00:30:14.640
Use discount code ITC26 to save $200 on registration.
00:30:14.640 --> 00:30:23.118
Even though we are taking a bit of a philosophical and a spiritual approach to this discussion, that's exactly I think what I'm looking for.
00:30:23.118 --> 00:30:29.920
Because in this time of hustling and the rat race, as you mentioned, we've become so mechanical.
00:30:29.920 --> 00:30:33.118
We are responding on the go.
00:30:33.118 --> 00:30:37.920
And from a human perspective, it's not sustainable, right?
00:30:37.920 --> 00:30:40.078
Each day you cannot be treating it as a transaction.
00:30:40.078 --> 00:30:41.920
You've got to live it.
00:30:41.920 --> 00:30:44.720
And if you're going to live it, you need that self-realization.
00:30:44.720 --> 00:30:50.078
I would also add self-awareness to guide where you want to go.
00:30:50.078 --> 00:30:52.160
That answer only can come from within.
00:30:52.160 --> 00:30:55.598
So I'm not going to shy away from that conversation, uh Ramesh.
00:30:55.598 --> 00:31:00.960
I'm happy that you're bringing these things to the fore because we don't talk about them.
00:31:00.960 --> 00:31:02.798
We are on the go, go, go.
00:31:02.798 --> 00:31:09.200
And it's very important to pause and to reflect so that you can move forward in a better way.
00:31:09.200 --> 00:31:11.920
And with that, that this question comes to mind.
00:31:11.920 --> 00:31:14.160
You talked about the new titles that are emerging.
00:31:14.160 --> 00:31:18.400
In fact, my company also rolled out new titles for us.
00:31:18.400 --> 00:31:20.558
Personally, I feel awesome about it.
00:31:20.558 --> 00:31:29.680
And I do feel that from where I see there is a career evolution that is happening, and those titles are appropriate to what we are doing.
00:31:29.680 --> 00:31:32.240
Because titles do carry some weight.
00:31:32.240 --> 00:31:34.960
That said, what is your take?
00:31:34.960 --> 00:31:39.038
Seeing these new titles, is there a genuine career evolution happening?
00:31:39.038 --> 00:31:40.400
Because what I'm saying is anecdotal.
00:31:40.400 --> 00:31:42.960
What are you seeing in the field?
00:31:43.838 --> 00:31:47.358
I would not necessarily say it's an evolution.
00:31:47.358 --> 00:32:11.118
I would say getting back to some of the core uh skills that we have or foundational and kind of getting into depth with that, you know, because sometimes we are just so caught up in the technical skills or you know, uh, or tools and other things, we forget that we are communicators first.
00:32:11.118 --> 00:32:17.519
And irrespective of your knowledge, you know, uh communication is what really enriches it.
00:32:17.519 --> 00:32:24.558
And that's our job because we say we simplify the complex and what can do it better than communication.
00:32:24.558 --> 00:32:28.240
And it's just not about communicating again, right?
00:32:28.240 --> 00:32:32.160
Communication is also about enriching lives, right?
00:32:32.160 --> 00:32:38.400
Or elevating uh lives, in this case, particularly about your customers, right?
00:32:38.400 --> 00:32:39.038
Or users.
00:32:39.038 --> 00:32:41.519
And that's what our goal is, right?
00:32:41.519 --> 00:32:45.358
The goal of a documentation team is to exceed customer expectations.
00:32:45.358 --> 00:32:48.078
So are we really doing justice to that?
00:32:48.078 --> 00:32:49.838
Is what we really need to see.
00:32:49.838 --> 00:32:55.440
I mean, if we are writing some conceptual content to write from scratch, are we doing our best?
00:32:55.440 --> 00:33:00.480
Are we investing our time in such a way that we are telling the best stories?
00:33:00.480 --> 00:33:02.880
Or is there are there any alternatives?
00:33:02.880 --> 00:33:04.160
Can we do it better?
00:33:04.160 --> 00:33:06.000
Can we do it in a different way?
00:33:06.000 --> 00:33:09.038
How much of experimentation do we really do that?
00:33:09.038 --> 00:33:12.160
How much of that do we really share socially?
00:33:12.160 --> 00:33:14.000
Do we talk about those experiments?
00:33:14.000 --> 00:33:15.598
Do we share those experiments?
00:33:15.598 --> 00:33:17.598
Do we connect with people?
00:33:17.598 --> 00:33:18.720
Do we connect with customers?
00:33:18.720 --> 00:33:20.720
Do we really understand their behaviors?
00:33:20.720 --> 00:33:24.078
I doubt we do a lot of that, right?
00:33:24.078 --> 00:33:35.118
Because we don't have the time to do that, because we are so caught up in the mechanics that we don't spend time in some of these things which are critical to our goal itself.
00:33:35.118 --> 00:33:38.400
And that's always been a challenge all the time.
00:33:38.400 --> 00:33:54.078
We talk about understanding our audience, we talk about understanding our user needs, but sometimes the users themselves are so vague about everything, starting from requirements to using the product, to adopting the product, to being able to use the document and so on.
00:33:54.078 --> 00:34:11.360
And if you see the conversations they have with the bots and other things, when they visit the site, you'll realize there are so many errors and bugs, and there are so many issues that they are grappling with, which sometimes are so straightforward, or a lot of that can be prevented.
00:34:11.360 --> 00:34:15.920
I would say, why do so many issues happen in the first place?
00:34:15.920 --> 00:34:26.960
If you understand your audience and user needs so well, we take pride in saying that we reduce support tickets and adding to the bottom line or adding to the revenue.
00:34:26.960 --> 00:34:30.400
But why have those support tickets in the first place?
00:34:30.400 --> 00:34:32.079
That should be your value add.
00:34:32.079 --> 00:34:33.920
You have to we talk about innovation.
00:34:33.920 --> 00:34:37.199
What innovation are we really doing from that perspective?
00:34:37.199 --> 00:34:42.320
How well we understand the product or the behaviors that we can avoid such things.
00:34:42.320 --> 00:34:50.159
We have to take a preventive approach than a reactive approach to documents because it's all about the experience, as I said.
00:34:50.159 --> 00:34:55.039
It's all about the taste that I mentioned when I gave an analogy of that dish.
00:34:55.039 --> 00:34:58.559
Now that is something which is cultivated over a period of time.
00:34:58.559 --> 00:35:00.400
We really need to understand that well.
00:35:00.400 --> 00:35:07.599
A person who has cooked and tasted multiple times will only understand the subtle things of that.
00:35:07.599 --> 00:35:14.960
Only he will be able to distinguish which ingredient is more, why is the flavor such, or why is the aroma such.
00:35:14.960 --> 00:35:22.800
Only they will be in a better position, or only they will have that discernment and judgment to do those things.
00:35:22.800 --> 00:35:30.400
That is where we should be focusing on the subtle aspects, not the gross or the raw stuff.
00:35:30.400 --> 00:35:33.518
You know, I would say that is where the value add will happen.
00:35:33.518 --> 00:35:41.440
I hope again, like I said, I tend to go on.
00:35:33.518 --> 00:35:42.000
I don't know whether this one was an interesting answer.
00:35:42.639 --> 00:35:47.360
But I want to again go back to you said that the career really isn't evolving.
00:35:47.360 --> 00:35:52.159
Because in my question, I asked you the career evolution that's happening with the titles.
00:35:52.159 --> 00:36:04.719
And again, I came here with a certain expectation, and you challenged me in a good way, where you said that it's the core skills that are kind of reflected with the new titles.
00:36:04.719 --> 00:36:13.679
We are going back to what the different aspects of our profession that are now surfacing, the specialization even within what we do as a technical writer.
00:36:13.679 --> 00:36:23.440
And you prompted me to think that maybe technical writing became a title that was looked down upon lately was because it it sounded very mechanical.
00:36:23.440 --> 00:36:26.079
It sounded very monotonous.
00:36:26.079 --> 00:36:38.719
And all the other attributes of the profession are now AI is probably giving us a chance to dig into those and really specialize content engineering, content strategy.
00:36:38.719 --> 00:36:41.599
Just think about it in a creative way.
00:36:41.599 --> 00:36:46.800
Again, as a communicator, how can you get creative with those aspects of your profession?
00:36:46.800 --> 00:36:48.079
Thank you for that.
00:36:48.639 --> 00:36:57.039
Absolutely, because I think something that doesn't go away from uh writing is writing is primary thinking, and writing is all about articulation.
00:36:57.039 --> 00:37:03.039
Writing is about research, writing is about creativity, writing is about structure.
00:37:03.039 --> 00:37:07.119
What we talk about information architecture, design, and all that.
00:37:07.119 --> 00:37:16.880
But AI can vomit a lot of content, but if it cannot tell you what is the right structure, and that comes inherently with good writing skills, right?
00:37:16.880 --> 00:37:23.679
Because writing is all about the structure, the flow, the context, the examples, the visuals, and so on.
00:37:23.679 --> 00:37:27.840
So these are some very inherent and core skills, I would say.
00:37:27.840 --> 00:37:34.079
I mean, of course, you can specialize in this, but if we were to say what is good tech writing, it's all of this.
00:37:34.079 --> 00:37:36.719
Like I said, it's multiple skills, right?
00:37:36.719 --> 00:37:46.239
So we have to excel in these to be able to add value, or that is what is good tech writing all about, is what I would say.
00:37:46.239 --> 00:37:48.400
And that is where we need to get to.
00:37:48.400 --> 00:38:00.880
And I think AI is giving us an opportunity to do that because we need to be more of thinkers right now and see how we can really handle this and do better in such a situation.
00:38:00.880 --> 00:38:21.518
So, I mean, I in a way I would say AI is doing uh good stuff to us because it's taking us back to the core skills, making us think, get to the depth of things, you know, look at the product or software or technology in different ways, try to seek user needs in a different way, provide better experiences.
00:38:21.518 --> 00:38:27.840
Because unlike the earlier days, uh things have radically changed, even for the software engineers.
00:38:27.840 --> 00:38:32.880
And for them, at least they have the QAs who can test their code.
00:38:32.880 --> 00:38:36.159
But for documentation, we don't have anybody who will test that.
00:38:36.159 --> 00:38:38.079
It is the writer who has to do it, right?
00:38:38.079 --> 00:38:39.760
He has to take ownership for that.
00:38:40.239 --> 00:38:46.719
Yeah, and it's a beautiful irony that AI is allowing us to really dig deep, actually.
00:38:46.719 --> 00:38:54.079
And this was again when I switched and I started pivoting and experimenting with AI, I did not expect that outcome.
00:38:54.079 --> 00:39:02.159
And where I am today, those for me again, this is personally, has definitely been the experience.
00:39:02.159 --> 00:39:07.119
And you kind of are validating that anecdotal experience of mine.
00:39:07.119 --> 00:39:15.760
Uh Ramesh, you you mentioned you have this global experience with through the mentoring and the work that you've done.
00:39:15.760 --> 00:39:28.400
Does globalization create greater opportunity for us technical communicators, or does it also risk making documentation work something organizations increasingly evaluate primarily through cost?
00:39:29.440 --> 00:39:30.719
I think it increases opportunity.
00:39:30.719 --> 00:39:32.559
Definitely there's a cost aspect.
00:39:32.559 --> 00:39:38.480
I mean, hiring or investment in people has always had the cost aspect.
00:39:38.480 --> 00:39:42.400
But again, getting the right talent is equally important.
00:39:42.400 --> 00:39:50.960
As a good leader, you would always ensure that you get the right talent to avoid a lot of other things which may cost you in a different way.
00:39:50.960 --> 00:39:59.199
So, in that sense, if you have to get the right hire, you cannot restrict yourself to certain regions or certain areas or whatever.
00:39:59.199 --> 00:40:14.480
So, in that sense, globalization definitely makes a lot of sense because you get access to good talent pool, and as far as your business needs are concerned, they will be met, and definitely it will create more opportunities.
00:40:14.480 --> 00:40:20.639
And of course, uh it's not going to be similar across regions or whatever.
00:40:20.639 --> 00:40:27.280
It's all dictated by the needs and the talent and the skills and the requirements and so on.
00:40:27.280 --> 00:40:33.039
So, but if you ask me, I would definitely recommend globalization as far as our profession.
00:40:33.039 --> 00:40:48.239
One, of course, in terms of opportunities, uh, but in terms of learning, or I work a lot with communities, and for me, in this age, all the learning will happen only socially, not traditional ways.
00:40:48.239 --> 00:40:56.239
So I would rate that you need to be part of a global network or global communities to be able to learn more.
00:40:56.239 --> 00:41:02.400
You need to experiment more, share more, invite views, learn from others, and so on.
00:41:02.400 --> 00:41:07.760
So, in that particular context, yes, globalization makes a lot of sense.
00:41:07.760 --> 00:41:16.320
In fact, I would say even three, four decades back, a lot of my learning uh did happen through my peers who are based across the globe.
00:41:16.320 --> 00:41:24.880
I mean, because even the cultural uh nuances are equally important because each uh peer brings a different aspect.
00:41:24.880 --> 00:41:33.119
And as we go ahead, I would say that even linguistics, cultural nuances are very important from an end-user perspective.
00:41:33.119 --> 00:41:37.920
The more you understand that, the value that you will add will be far better.
00:41:37.920 --> 00:41:48.480
And in that case, definitely understanding globalization, global cultures, different regions, different individuals is more important, is what I would say.
00:41:49.199 --> 00:41:57.360
Yeah, in that same way, Ramesh, where do you see career expectations differing between one country?
00:41:57.360 --> 00:42:01.440
I don't want to say India versus the US, but just across the world.
00:42:01.440 --> 00:42:04.239
How do you see career expectations differing?
00:42:05.280 --> 00:42:18.320
I I think more than career, I would say access to resources, be it in terms of learning, be in terms of knowledge, or other things which enable learning and thereby the career, right?
00:42:18.320 --> 00:42:20.480
And I would give a quick example.
00:42:20.480 --> 00:42:22.800
Like I will give my own example.
00:42:22.800 --> 00:42:28.320
Uh when I started off uh tech writing, I was clueless about tech writing, right?
00:42:28.320 --> 00:42:30.400
I had started with ISO documentation.
00:42:30.400 --> 00:42:37.920
Now, if if I were to learn tech writing, I would always recommend that you learn tech writing from the right tech writer.
00:42:37.920 --> 00:42:45.039
That's very important because unless you learn tech writing the right way, it's not going to make a huge difference, right?
00:42:45.039 --> 00:42:51.679
Because if I learn the wrong stuff, I'll be doing uh totally unaware the things which I should not be doing.
00:42:51.679 --> 00:42:56.000
Now, you need a right person to be able to guide you.
00:42:56.000 --> 00:43:06.800
All right, and in that case, I would say I was extremely fortunate to have peers who are very seasoned tech writers back then itself who guided me uh through this process.
00:43:06.800 --> 00:43:10.880
And that is where mentoring plays a very important role.
00:43:10.880 --> 00:43:20.000
It's just not about skills, but there is somebody overseeing you, guiding you on that path, helping you deal with every challenge.
00:43:20.000 --> 00:43:26.719
Not that they are practically doing it, but they are there to kind of you know enable your growth, right?
00:43:26.719 --> 00:43:31.199
And that's is very important, is what I would say.
00:43:31.199 --> 00:43:36.960
And uh mentoring is more than the theoretical stuff that we talk about.
00:43:36.960 --> 00:44:10.079
Mentoring is never about theoretical stuff, or it is not coaching, or it is not spoon feeding, it's about you do your own stuff, but if there is some major eventuality or something, something very serious, some something seriously going wrong, either with what you're doing, your career or something, there is somebody to help you to avoid those pitfalls or somebody to correct that, somebody to bring you on the right path with your experience, with your knowledge, with your examples.
00:44:10.079 --> 00:44:18.320
And that is where I think we are lacking right now somewhere, because one, of course, uh, we are seeking new horizons.
00:44:18.320 --> 00:44:27.039
There's there is no clarity, and definitely there are going to be no clear-cut roles, clear-cut demarcation, and all of that.
00:44:27.039 --> 00:44:34.159
But at the same time, culturally, not everybody is willing to share, mentor, and all of that.
00:44:34.159 --> 00:44:46.000
Like, unlike what I've seen in the past, people were so forthcoming and they were so willing because it requires a lot of energy and time to help somebody grow, right?
00:44:46.000 --> 00:44:53.760
I mean, while you have your own professional and personal commitments, imagine that you are investing in mentoring others, right?
00:44:53.760 --> 00:45:04.239
And I really appreciate all those who have done that for me and who have been doing that as part of various communities in the last few decades, you know.
00:45:04.239 --> 00:45:07.199
And I think that trend should continue.
00:45:07.199 --> 00:45:20.159
But unfortunately, with a lot of devices, with a lot of technology advancement, and now with AI, slowly that people connect is missing.
00:45:20.159 --> 00:45:23.840
I mean, the communities are slowly dying down.
00:45:23.840 --> 00:45:27.280
People are not building, they are not nurturing that.
00:45:27.280 --> 00:45:31.920
And I and the irony is now all the learning has to happen socially.
00:45:31.920 --> 00:45:33.760
It's all about experiments.
00:45:33.760 --> 00:45:41.199
Now, if I do an experiment and if I don't connect with others, or if I don't know whom I should talk to, how am I going to learn?
00:45:41.199 --> 00:45:47.679
That's where I think the social aspect or the community aspect plays a very critical role.
00:45:47.679 --> 00:45:54.960
And I think we as a profession need to do a lot to nurture these communities, right?
00:45:54.960 --> 00:46:03.679
And unfortunately, there are not many global communities right now or communities of repute that are there or exist.
00:46:03.679 --> 00:46:11.518
There could be a lot of communities in pockets doing great work, but I think the synergy aspect would be missing, right?
00:46:11.518 --> 00:46:20.400
And that's what is really required the unifying aspect or bringing in all that knowledge, bringing in all the insights, you know.
00:46:20.400 --> 00:46:24.159
And that's going to be one of the most important things as we go forward.
00:46:24.960 --> 00:46:28.880
You're making me ask a lot of questions, but I'm going to go with this one question.
00:46:28.880 --> 00:46:33.280
You rightly mentioned that you have to have the right mentoring.
00:46:33.280 --> 00:46:37.920
Now, somebody who is getting mentored, what do you think they should be looking for?
00:46:37.920 --> 00:46:40.079
What kind of red flag should they be looking for?
00:46:40.079 --> 00:46:48.400
If they are getting mentored, if they're fortunate, but things that they should not be learning, or rather unlearning, or even maybe teaching the mentor.
00:46:48.400 --> 00:46:50.639
I would love to get a take on that.
00:46:51.360 --> 00:46:59.119
Like I said, you know, first thing is, of course, even before you take any mentoring, I think that self-introspection is very important.
00:46:59.119 --> 00:47:03.119
Unless you have that, even a mentor will not be able to help you.
00:47:03.119 --> 00:47:05.679
So at least you should have a clear idea.
00:47:05.679 --> 00:47:14.079
Or if you don't have one, of course you can see because innate qualities, inherent strengths differ from individual to individual.
00:47:14.079 --> 00:47:18.960
It's like a mentor will not have a universal solution for everyone.
00:47:18.960 --> 00:47:22.559
It's like you have to really go into depth for each individual.
00:47:22.559 --> 00:47:29.840
It's all about customization, personalization, it's all about your aspirations, it's about your dreams and wishes.
00:47:29.840 --> 00:47:40.000
And of course, the gap between it, like I might aspire for a lot of things, but if my strengths are not aligned with that, I may not be able to achieve that.
00:47:40.000 --> 00:47:51.920
So it's it requires a lot of courage also to tell you the truth up front, like what you have, what you don't have, what you can do well, like typically the writer and the editor, right?
00:47:51.920 --> 00:48:03.039
If the editor shies away from telling you that you know the content is great or not, or whatever, then you're really not doing a service uh to the writer in that sense.
00:48:03.039 --> 00:48:12.159
Because you're not really helping that person, because trying to please somebody is not going to really help you, or giving temporary solutions is not going to work for the individual.
00:48:12.159 --> 00:48:20.159
Advice as important as "You should not be working in this field" is equally important if they don't have the skills, right?
00:48:20.159 --> 00:48:24.880
But I think very few people uh would speak up like that or would be upfront.
00:48:24.880 --> 00:48:39.679
But I think that's important because you really need to work at that level with a mentee to be able to really understand all aspects holistically, even before you suggest anything.
00:48:39.679 --> 00:48:46.320
And the mentoring happens much later, I would say, only when you understand all of this.
00:48:46.320 --> 00:48:52.159
It's not like you directly dive in, like somebody says, I want to learn this, and you start mentoring.
00:48:52.159 --> 00:48:54.239
I never do that, in fact.
00:48:54.239 --> 00:48:57.119
I never coach, also, I never train people.
00:48:57.119 --> 00:49:04.239
I just try to be in the background and try to enable their growth with what is available and whatnot.
00:49:04.239 --> 00:49:07.599
So that's the approach I would take from a mentoring perspective.
00:49:07.599 --> 00:49:10.400
And it's been pretty successful at that.
00:49:10.400 --> 00:49:16.400
And of course, I have also told a lot of people why they should not take up tech writing also as a profession.
00:49:16.400 --> 00:49:31.679
So, but I think truth and honesty is equally important no matter what profession you are, or what professional, the most important aspect of that is professional ethics, and you also owe it to the profession.
00:49:31.679 --> 00:49:34.719
You also owe it to the professions, right?
00:49:34.719 --> 00:49:37.760
So you have to do the right things all the time.
00:49:37.760 --> 00:49:42.320
You should not hesitate or restrain yourself from doing that.
00:49:42.320 --> 00:49:46.639
So be it mentoring or be it creating deliverables or serving the customers.
00:49:46.639 --> 00:49:48.559
Um it's all the same.
00:49:48.559 --> 00:49:50.880
I think it's all about servant leadership.
00:49:50.880 --> 00:49:57.679
You've consciously made a choice to serve or give back or do things that you wish to, right?
00:49:57.679 --> 00:49:59.920
That's the way I look at it, including mentoring.
00:49:59.920 --> 00:50:03.599
So the point is to enable and empower the individual.
00:50:03.599 --> 00:50:06.800
You can only do that when you understand the individual better.
00:50:06.800 --> 00:50:14.320
And if you don't, you need to enable them to do that, and as a result of the outcome, enable them with whatever is required.
00:50:14.320 --> 00:50:18.320
And that requires the individual themselves to do a lot of effort.
00:50:18.320 --> 00:50:24.960
It could be very difficult, it could be complex, it may take time, it may not yield results as you expect.
00:50:24.960 --> 00:50:31.840
But nonetheless, it will happen because once you're set up on the right path, you're set up for success.
00:50:31.840 --> 00:50:37.760
It's the path that is important because without that foresight, you know, it will not help.
00:50:37.760 --> 00:50:44.000
You may have the best uh vehicle, but if you don't have a map, you may not land at your destination.
00:50:44.000 --> 00:50:49.360
You have to have the map, you have to have the GPS to be able to reach your destination.
00:50:49.360 --> 00:50:51.039
But who gives the GPS?
00:50:51.039 --> 00:50:52.719
Mentoring could be that.
00:50:53.199 --> 00:50:54.800
It's been a great discussion, Ramesh.
00:50:54.800 --> 00:50:56.000
I invite you.
00:50:56.000 --> 00:50:59.119
Do you have any last thoughts that you would like to add?
00:50:59.840 --> 00:51:06.159
I would say that we often say that our work should speak, but I disagree on that.
00:51:06.159 --> 00:51:10.480
I feel as technical communicators, we should speak about our work.
00:51:10.480 --> 00:51:15.599
We should be very vocal advocates and we should be ambassadors of our profession.
00:51:15.599 --> 00:51:20.159
My mission is to create awareness and promote our profession.
00:51:20.159 --> 00:51:35.199
And I would request, I mean, through this podcast, I would like to say unless we invest our time in being vocal or being an advocate for our own profession, we'll not be able to survive and thrive.
00:51:35.199 --> 00:51:39.920
So it's very important to nurture our own profession.
00:51:39.920 --> 00:51:43.760
It's very important to connect with fellow communicators.
00:51:43.760 --> 00:51:47.440
It is very important to be part of a community.
00:51:47.440 --> 00:51:50.000
It's important to give back.
00:51:50.000 --> 00:51:58.719
It's not just being consuming, it's not about just taking or it's also about giving, giving back whatever you can.
00:51:58.719 --> 00:52:04.000
So it's good to be part of a community and give back apart from your professional commitments.
00:52:04.000 --> 00:52:09.199
And I think that will really keep uh the profession really thriving.
00:52:09.199 --> 00:52:11.039
And I don't think so.
00:52:11.039 --> 00:52:23.760
Any technology can really replace or take away tech comm because tech comm or communication by itself can only enrich and elevate the way we go ahead.
00:52:23.760 --> 00:52:25.518
That's my message to all.
00:52:26.079 --> 00:52:26.480
Thank you, Ramesh.
00:52:26.480 --> 00:52:31.360
And I want to give a big shout out to Nibu for introducing us.
00:52:31.360 --> 00:52:34.320
Without that introduction, we wouldn't have had this conversation.
00:52:34.320 --> 00:52:35.440
So thank you, Ramesh.
00:52:36.079 --> 00:52:42.239
And definitely, I would also like to thank Nibu for introducing me to you.
00:52:42.239 --> 00:52:45.119
And I enjoyed every bit of this conversation.
00:52:45.119 --> 00:52:46.400
Thanks to Nibu.
00:52:46.400 --> 00:52:49.599
And it was great talking to you, Zohra, today.
00:52:49.599 --> 00:52:53.119
And uh I hope it was useful and uh helpful.
00:52:53.119 --> 00:52:57.599
If not, definitely I can look forward to sharing more stuff if required.
00:52:58.480 --> 00:53:02.400
This was very helpful, and I would love to have you again on my show in the next season.
00:53:02.400 --> 00:53:03.760
So, with that, thanks, Ramesh.
00:53:03.760 --> 00:53:05.119
Have a great evening.
00:53:05.119 --> 00:53:06.480
I know you're calling from India.
00:53:06.480 --> 00:53:09.119
It's pretty late in the evening for you there.
00:53:09.119 --> 00:53:11.518
I appreciate your time and have a good one.
00:53:11.920 --> 00:53:12.239
Thank you, Zohra.
00:53:12.239 --> 00:53:13.679
You do have a great day.
00:53:13.679 --> 00:53:19.518
Thanks for talking to me today, and all the best, and you're doing a great job uh through these podcasts.
00:53:19.518 --> 00:53:27.920
I only hope and wish you all the best that you continue and invite as many experts, and this is the best way to give back to the community, too.
00:53:28.639 --> 00:53:29.199
Thank you.
00:53:29.199 --> 00:53:32.559
Thank you for listening to Inside Tech Comm.
00:53:32.559 --> 00:53:37.199
If there's a guest you would love to hear on the show, please let me know.
00:53:37.199 --> 00:53:42.400
And don't forget to follow and catch every episode on your favorite podcast app.
00:53:42.400 --> 00:53:43.760
See you next time.
