views:

476

answers:

10

I am always misunderstood by my non-technical boss.

Its frustrating that they would think that a programmer isn't working when he's not in front of the computer typing code.... or even when in front of the computer and has his browser on, reading about new programming stuff. It got to the point where I was told I was unproductive even though I solved the challenging and unconventional problems.

I think I'm not the only one who has to deal with this problem and I think its common amongst programmers with non-technical bosses.

How would you deal with this problem?

Possibly related question: Should I just shrug off that I'm misuderstood and accept that programmers have prickly personalities (if so, how would I explain that)?

+1  A: 

I find that the best way to be understood is to make sure you understand him. By repeating what he says and what you think it imples for you.

And then deliver what you both have agreed he wants, in little tiny chunks, so you can discuss something real instead of what you're both imagining.

le dorfier
+4  A: 

One, don't be prickly.

Two, produce.

Your justification is in your work product. In my experience, if you produce as expected then no one looks over your shoulder to see what you're actually doing. I've had bosses without programming/software experience, and if you do what is expected they care the least. For me it's the bosses with technical experience that cost me more time. Since they want to know every detail of my implementation. Not that it's a bad thing, since I've been lucky to, for the most part, have smart bosses, and my work product has improved for it.

The bosses with less technical knowledge only bother me if they see a problem, and if they see a problem, then its a an expression of the quiet desperation of our customers. Listen to it.

If you have to spend a lot of time keeping up on the latest technologies in order to do your job, express that specifically with our boss. If you want to keep up on the latest technologies in order to improve your experience, either make time at work while keeping up with what's expected, or do it on your own time. Your bosses job is to make sure you get done what you're assigned to, not to improve your skill set.

While you may have solved the "challenging and unconventional problems", if you don't solve the day-to-day "staying in business" problems, it may be satisfying to you, but your job satisfaction doesn't always translate to company success.

Darren Clark
I upmoded you although it didn't apply to me. I actually produce good products that our customer enjoys. It just that they think that I didn't do anything special. Example, the "challenging and unconventional problems" includes deep math code which had solve their "staying in business" problems.
MrValdez
I actually got the impression that it didn't apply in your particular case, at least most of what I said didn't. I just on a rant/roll. ;)
Darren Clark
+9  A: 

I think that it is a communication problem, programmers and non-programmers live in two different worlds. A non-technical boss needs to measure your performance but since he doesn't really understand what you are doing he needs get more information

So what I did (when I was in that situation) was to write regular reports to my boss written in a non-technical language once every week summarizing what I have been working on, what I will work on the next week and other things I've been doing. That way he was much more understanding when I was reading Dr Dobbs or surfing the net. ;)

Anders K.
+1  A: 

Agile programming practices would be a good start. Don't have programming conversations with non-programming people. Focus on their needs, not the techniques. If your boss comes to you and says this other consultant recommends you use cookies in your websites, you reply that the real focus should be "what does the customer really want to do?" You end up talking about how the customer really wants to save their content on the page for future visits.. and that is what is really important, not the dam cookies...

Dr. Zim
+3  A: 

1800 INFORMATION
Doesn't work. They don't understand what's compiling means. ....also, I tried that excuse before. xP
MrValdez
+2  A: 

Tell you what - the best thing to do would be to start your own technology company and be your own boss :-)

Raj
That would be great! But would I get anything done, that is the question ;-)
Subtwo
A: 

The best thing you can do is to adapt your language to the non-technical person.

Assuming you succeeded to do that, you have to convince your boss on the impact of so called "non-productive" activities: what happens if you do it, what happens if you don't. Insist on the negative impact of not doing various activities (e.g. testing, design, analysis).

Convincing non-technical staff (boss) on the usefulness of these activities is very hard. I would try to do one (or all of the following things):

  • On concrete case, on your project, before starting such activity, provide your boss the cost of doing that activity, and what is the "Return of Investment" for that activity (estimated cost saved by doing it, compared to the situation when not doing it).

  • If it is the case, provide those two alternatives to him, state your preference, and ask his oppinion. But in this case, it is important to have some documented, realistic estimations.

  • Never say no to his oppinions. Just explain the impact (good or bad) of
    his ideas/constraints.

  • At the end of a project/phase, try to make some measurements, present them as "Lessons learned". Again, objective figures are the key.

  • (Maybe not possible) Support your oppinions/proposals of
    "non-producing" activities with documented sources where the software development principles/mistakes are stated by people well known to software community.

Cătălin Pitiș
+13  A: 

Although you're asking for communications advice, what you're really talking about is a hidden agenda in your specific situation. Bosses with hidden agendas are a tricky and sometimes dangerous thing. Sometimes that agenda can be you, sometimes it can be something else. Your task is to get them to admit what the agenda is, while keeping their feathers unruffled.

You'll need to prepare, both physically (with supporting paperwork and - God Forbid - visual aides) and mentally. If you're lucky, just getting some mental preparation will suffice. If you're not, you may be faced with generating performance charts, etc. Still, failing to prepare is preparing to fail.

In your preparations, target specific things, and keep the list small and manageable. If you have more than 5 things, you're asking for trouble, the average person handles only 3-5 simultaneous events/concepts at a time, and you don't want to vex them with overload.

You need to set aside time. At least 15 minutes; if you get done sooner, it will be seen as a positive thing (we completed the meeting early and went on to other things, good job!). Warning Sign: you can't get more than 5 minutes, or worse, they think that the 5 minute manager means everything is answered in 5 minutes or less. This is a Bad Sign(tm), really bad, and you will not be able to break through your work issues because your boss has more or less erected a permanent barrier. I know this sucks, but if you can't get a time slot with them alone, take your lunch with them.

You need to get your boss to agree to stop moving around at this time. I mean, literally get him/her to sit still and listen, and not be distracted by telephones, other subordinates, paperwork, deadlines, etc. Close the office door and keep it shut. Distractions are the unintended ADHD syndrome of bosses everywhere, and even a missed cell phone call can break a train of thought, leading to "aw heck I don't care, just get back to work" as an excuse to get out of the meeting. The whole point of getting time with them is to get their attention, their focus, on what you are trying to convey.

Once you are ready to communicate effectively, keep one rule in mind: only speak when it's absolutely necessary. Unless it's absolutely needed to confer the information your boss needs, or if it's needed to keep the communication flowing, don't even bother openning your mouth. Samuel Clemens was remarkably spot-on in this estimation: "It is better to keep your mouth closed and let people think you are a fool than to open it and remove all doubt."

During this time, you need to (politely!) approach him/her and breach the topic. You will want to do so in a non-accusatory fashion, i.e. you want to do so without generating the feeling that anyone - you or your boss - is at fault for the situation. Rather, you'll be presenting the issue in a manner that encourages teamwork. You want this to be a positive impression and you will want to keep this upbeat. Even the slightest hint of negative can (and often will) turn against you. I cannot give this enough emphasis. Negative verbage, and even negative emotions, are weapons in the hands of a bad boss with a bad agenda that targets you. Do not give them this, it will devolve into an opportunity to use any of this against you. Yeah, you'll wanna puke with the constant "sunshine and pony" crap, but trust me on this, it's nigh-impossible to put the thumbscrews to you if everything they try to use against you is a positive. Hopefully that isn't the case and it's just a situation where there's a misunderstanding; and this meeting will set you both on the right track.

Avoid technical jargon, unless it's something they're going to hear over the long term. Think of this: remember when "cyberspace" was Hollywood's trendy buzzword? How would you like it if your boss latched on to this term and used it for the next 3 years? Wouldn't you cringe less and feel better when they speak, if they used the correct term(s)? This is the corollary to the "Speak when needed" maxim above - everything you say will be under a brilliant spotlight for a few moments, and verbal gaffs will stick around long after...

Assume that they don't know what it is you know. Assume that they also may harbor fear, resentment, indifference, or any one of thousands of other personal or political agendas. Also consider that they may be filtering what you say through those agendas.

Try and get them to clearly define what they consider to be progress. It might be something entirely different from what is called for in reality, and that will touch back on the personal/political agenda just mentioned. If their definition sounds even slightly vague, do not let it slide, politely ask them to clarify or provide additional details, what you want to accomplish is to get them to admit what their hidden agenda is in a polite manner that doesn't threaten them.

After it is sparkling crystal-clear what their agenda is, be sure to (politely) repeat it back to them, i.e. "...so just to make sure I have it down pat, you said you want such-and-such accomplished by means of xyz within a given timeframe that you specify, correct?" Repetition back to them will give them a sense that their communcation was effective and provide a positive feedback. Bosses like this because they feel their intentions are conveyed effectively, so this is a good thing(tm).

This should give you the critical insight you're after. You'll have a better understanding of their expectations - and like it or not, part of your job is to set expectations. If their expectations are unrealistic, or completely disconnected from the reality of the situation, it falls to you to provide realistic, clear, informative feedback that focuses on what they need to accomplish their tasks, not yours. If that feedback shows that their expectation is unrealistic, they'll quickly re-adjust it on their own. Sometimes, all that's needed is exactly that - a re-assessment on their part of what is really needed and what's really going on. The goal here is to start and establish an unbroken chain of communication between you and them, and that communication will only help everyone out over the long run.

If by this point you can't get a sense of what it is that they are after, then the situation is truly dire and you're not in a good working situation at all; either the boss is incompetent (either by lack of effective communication to their subordinates, or they are not even close to competent in the field they are working in), or they have a hidden agenda that is adverse to you. Either way you're on your way out in the long term. Thank them for their time, assure them that the meeting was well-received and informative, and drop the whole thing. In the meantime, stick it out and do the best you can, but start looking (discretely, on your personal time) for work elsewhere. I truly hope this isn't the case, but I have been in this situation at least once, and while uncomfortable, it's pretty clear you're better off just getting out while you can...

After this point, you're on your own. Good luck.

Avery Payne
Thanks for that great response. I really appreciated it.
MrValdez
Sorry for the constant edits. It's late where I'm at and I'm sure I'm a little too rummy for some of these, but I think I have it in a final form. Good luck!
Avery Payne
*breach the topic: broach the topic. Also, thanks for the Mark Twain quote!
Anton Tykhyy
Great response. I especially liked "failing to prepare is preparing to fail"
ya23
+1  A: 

One of my clients thinks he is technical but really isn't all that up to speed. He likes to maintain control on things he has not much idea about.

When I have been in the situation of over the shoulder observation, or if they start to offer ideas which are outside of their league but they are just mentioning them to appear like they know what is what, I say "oh great, you know about this? because I'm actually busy and it would help me out if you could do that for me". You just might find they learn their position. While you are there to generate cash, I would never put myself under a person like that again and would rather work at a cafe earning money to generate savings to start my own business than be in a position of being ruled by non-technical bosses while working in a high tech arena. It can be very frustrating.

My experience has shown me as well that if you are the smartest technological person in your business, then its a sort of suicide to let people try and control the show. They are bringing in you, the professional coder to come and create the new stuff. You are the fella with the wisdom in this field... don't be fooled into thinking you are the subservient.

Man up. Take over your career. Don't take criticism from people who don't know what they are talking about but if you do, take it with a smile and delete it from memory soon after because most of the time what the critiques think is herd like fear masked as leadership.

All the best.

cosmicbdog
+1  A: 

Talk to your boss am together clearly specify what being "productive" means. Then all you have to do is try to meet his expectations (or look somewhere else for work).

Sergio