326- Thomas Dewar on IT Leadership, Building Trust, Communication, and Problem-Solving Part-1

Dissecting Popular IT Nerds

Technology

5 • 49 Ratings

🗓️ 23 September 2024

⏱️ 47 minutes

🔗️ Recording | iTunes | RSS

🧾️ Download transcript

Summary

Thomas Dewar Thomas Dewar has been working in IT since the late 1970s, starting with programming on early home computers. With a background in psychology, Thomas brings a unique perspective to IT leadership, focusing on communication, problem-solving, and understanding business needs. His experience spans various industries and roles, giving him valuable insights into the challenges and opportunities in modern IT management. Thomas Dewar on IT Leadership, Building Trust, Communication, and Problem-Solving How can IT leaders improve communication, build trust, and solve business problems? In this episode, Thomas Dewar shares insights from his long career in IT, starting with his early days of programming in the 1970s. Thomas discusses the importance of understanding business needs, communicating effectively with executives, and applying concepts like “Love It or List It” to IT decision-making. He also explores the psychological aspects of IT work and offers advice on building trust in a skeptical environment.

Transcript

Click on a timestamp to play from that location

0:00.0	Everyone out there listening to Dissecting Popular IT Nerds today covering the Scotty method with Tom
0:07.9	Dewar. He's a doer and I've been doing things for a long time. And I don't mean any offense
0:15.1	by that. I don't mean any offense by that. But the fact that you were in IT back in November of
0:20.7	2000 coding things is, I don't tell us a story. Let's go back in time. Let's go back in the, you know, the, I don't know, Star Trek probably had some back in time episode, right? Didn't they have time warp? Yeah, they had time travel episodes for sure, yeah.
0:35.5	For some reason, the first thing that always pops into my head with Star Trek is either
0:39.0	Klingon and the dictionary or the wrath of Kahn.
0:43.9	That's just the first thing that pops into my head all the time with Star Trek.
0:47.5	So let's go back in time to 2000.
0:49.4	Coding in 2000.
0:51.3	None of my children were born yet.
0:54.1	I had not graduated college yet because I uh, I transferred and did like a five and a half year degree, little, um, revealing myself, truth be told. Uh, as an English major, you were, uh, you were from talking earlier, you're a psychology major. You were, you did or you took psychology or something like that, which is going to be very good.
1:10.6	A psychology major, yep. Yeah, we need to get back to that because the IT people have a lot of psychology issues,
1:15.8	psychological problems and issues that we need to. The second, the other possible name for this
1:21.3	podcast would be, yeah, like the IT shrink. We should, we should shrink some people. We should do
1:26.7	that. That should be like a, that should be like
1:28.0	another side show. Like, come on and we'll, we'll deal with your IT, where your IT psychological
1:33.3	problems. And what's interesting is a term quite highly caffeinated at the moment. You can tell
1:39.1	because my ADD is coming out. We're jumping around from all kinds of subjects. The psychological protection of our people underneath us is something that's coming up.
1:48.3	The psychological safety of the people on our IT team, creating a psychological, safe environment.
1:56.4	This topic has been coming up a lot, and I'm wondering why it does not get covered that
2:05.1	often.
2:05.6	So we need to talk, we need to talk about one on this episode, psychological safety.
	...

Please login to see the full transcript.

Previous episode | Next episode

Disclaimer: The podcast and artwork embedded on this page are from Dissecting Popular IT Nerds, and are the property of its owner and not affiliated with or endorsed by Tapesearch.

Generated transcripts are the property of Dissecting Popular IT Nerds and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.