From the course: Career Clinic: Developer Insights
Raising concerns
From the course: Career Clinic: Developer Insights
Raising concerns
(gentle music) - So I'm not always good at this. I do suffer from anxiety and sometimes I'm probably not in the best frame of mind to raise concerns. I think everybody just, you know, you need to know yourself, you need to know your limitations and, you know, things can get really emotional, and you know, if everybody's keyed up, then, you know, nothing productive is happening. What I have learned is, you know, you have to stop, and get some space before you raise concerns, and then, you know, once you're ready to raise concerns, do it in the, you know, I have a tendency to want to come up with solutions, and this how it should be, you know, try and making it a little bit more of an open discussion is always key. - So when it comes to raising concerns, there's a topic about psychological safety. Google has done actually some fairly extensive research on this, and there should always be space to raise concern. So if you're in a situation where someone else is raising a concern, the best you can do is listen. You give them the space to express that concern. When you want to raise a concern yourself, my recommendation, my personal protocol is don't just say this isn't going to work. Or I don't like that. That is a dead-end comment that is not very productive. If you see a problem, propose a solution, or at least an approach. Say I'm worried that this direction might cause an issue for us, here's why and here's some things that I think we can try to mitigate that issue. That's what we do as software developers and architects, is we look at all the different trade-offs that, you know, there's many, many different ways to skin a cat in this industry. It's about trade-offs and understanding what those trade-offs can lead to, and in many cases, it's just about raising that up, and collaboratively deciding what the best combination of solutions might be. - You never know who's gonna find the problem that brings down the computers. Who finds the problem that causes you to have to recall something, you know, your, the phone that you just worked on because it had a bug in it, and it can't be fixed, they all gotta go back to the shop. You know, the thing that I would always say is that any time you have a concern about something, make sure that one, that it doesn't sound like an attack on that person who built the thing. Instead that it's a concern about hey, this piece of software I'm concerned about it, because, you know, we've had a lot of trouble getting it through QA, we've barely got it through, don't we want to sit on it some more? Make the concern about the thing, and not the people, and people will tend to listen to you better. And the other thing is that it does help sometimes if you have some mentors at the company that you work at, because maybe the older person, the person that's been around, they don't necessarily need to be older than you in age, but just older than you at being at the company, can either give you advice on how to get your concerns heard, or take you to the person who will listen more. - Everywhere we have problems. And everywhere we see and we do not want to talk about them. So the first thing that you do when you wanna raise a concern is stand up and build up the courage to speak about it. That's the first thing that you ever do. Because most of the people look at the problems around themselves, and they know that it is a problem, but they do not even want to talk about it. Second is when you're in an organization or when you're working in a team, the correct way to raise a concern is to first approach a hierarchy. The way you tell about the problem, you have to tell how it's affecting people. How it is becoming a concern and talk in such a manner that the person is going to realize that it's not a complaint, it's a serious problem, that's affecting the entire work environment possibly, and it has to be resolved as soon as possible. And you'll have to present facts, you'll have to present proofs, that this is what is, this is what has happened in the the past, which is now hampering everything around us. So we need to resolve this ASAP. But I'm absolutely sure that the person sitting across the table is definitely going to understand and help you resolve the problem. (gentle music)
Contents
-
-
Kirsten Hunter4m 55s
-
Mary Ellen Bowman3m 40s
-
Ray Villalobos4m 51s
-
Rae Hoyt4m 25s
-
Steven Lipton4m 26s
-
Diversity in tech5m 23s
-
Mohammad Azam4m 49s
-
Chiu-Ki Chan4m 56s
-
Maximiliano Firtman3m 27s
-
Carrie Dils2m 40s
-
Ted Neward5m 13s
-
Shonna Smith3m 1s
-
Janan Siam4m 3s
-
Emmanuel Henri3m 28s
-
Albert Lo3m 9s
-
Christina Truong3m 1s
-
Sasha Vodnik3m 47s
-
Jen Kramer4m 25s
-
Freelancing5m 14s
-
Upcoming in tech3m 39s
-
David Okun3m 57s
-
Learning and obtaining new skills3m 43s
-
Perseverance3m 59s
-
Clarissa Peterson4m 27s
-
Starting a business3m 27s
-
Mind of a developer4m 7s
-
Derek Peruo5m 26s
-
Clean code practice5m
-
Mentorship3m 33s
-
Bear Cahill3m 4s
-
Networking5m 15s
-
Ketkee Aryamane3m 28s
-
Conferences4m 19s
-
Meetups4m 19s
-
Leigh Lawhon2m 48s
-
Star Wars or Star Trek1m 43s
-
Unexpected opportunities4m 58s
-
Acting on your ideas3m 30s
-
Matt Boyd2m 31s
-
Career changes3m 53s
-
Business tips4m 57s
-
Bonnie Brennan2m 8s
-
Collaboration and open source5m 44s
-
Communication skills3m 49s
-
Upcoming in tech3m 46s
-
Diversity in tech5m 15s
-
Mind of a developer3m 48s
-
Working across generations5m 35s
-
Mentorship5m 33s
-
Conferences4m 59s
-
Collaboration on projects4m 26s
-
Networking3m 30s
-
Introversion5m 22s
-
Raising concerns4m 19s
-
Dealing with conflict5m 20s
-
Work-life balance5m 25s
-
Impostor syndrome5m 24s
-
Learning and obtaining new skills1m 42s
-
New tools learned4m 16s
-
Favorite gadgets/tech3m 46s
-
Communication skills5m 3s
-
Diversity3m 23s
-
Mentorship4m 29s
-
Motivate kids/development3m 31s
-
Work/life balance2m 14s
-
Perseverance4m 49s
-
Introversion3m 40s
-
Imposter syndrome3m 39s
-
(Locked)
Self-promotion3m 36s
-
Favorite projects4m 59s
-