How to create a dropdown user control?

The user is always right

  • I get really frustrated with the process at my workplace, particularly meetings. After many details, I have a couple of questions about work (specifically software development and project management decisions) and how to deal with meeting-related frustration. I work for a small research department of a larger business. Myself and a second person were hired to create a software application to assist in the research this department does. Neither of us has had a software development position before. We are under the guidance of a Project Manager (PM) who has worked in marketing and is knowledgeable in this specific realm of research but not in software. There are a few other "advisory" team members: A couple of researchers familiar with the research process, a programmer 'consultant', and the lead researcher, the visionary behind this software application. The second programmer and my roles are pretty much the same - we both work on all aspects of the project. We started with nothing except a vague goal that has changed tremendously over time. When we started, I decided on the programming language to use (this fact is important and overwhelming and embarrassing to me, because it makes me feel like a) I should be an expert in all things related to the language [I'm not], and b) that any limitations of the application are my fault because I picked the language). At this point we have more or less finished the basic application and we have a well established "to-do" list of features. In addition to creating this application, we are occasionally given writing tasks to do, mock-ups to make, presentations to make for researchers to show elsewhere, and documentation tasks. Part of our role has also been to help design this application, which I've found to be difficult given the complexity of this research and my lack of depth of knowledge in it. However, I'm having a problem with the processes here. I cannot tell if these are personal issues that I have and need to get over (such as being a control freak, or not understanding how "work" works), or if these are issues anyone would have in this situation. This is my first job after college and I really do not know what is "normal." Many times during the week we have meetings that are just the three of us - two programmers and PM. When PM is around these meetings can happen one to three times a day. Full project-team meetings happen weekly. Lately I am finding that I have to suppress a huge amount of annoyance and frustration before and during these meetings, particularly the PM-only ones. To hide it, I try not to volunteer input, and I say as little as possible to get the meeting over with. Other tactics (providing and defending my opinion, suggesting an idea) have proven unsuccessful. A PM meeting is usually something like the following: - "Can you come into my office and look at something? Look at [X feature on some commercial program]. Can we do something like that for [Y feature on our program]? Is it hard to do?" - "Let's go through this list of comments from users. User A thinks the label on this button should be different, let's change that. User B thinks [Z feature on our application] should be more like [Q feature on commercial application]. [Head researcher] would like that. How long would it take to do that?" - "Let's look at your mockups for the next to-do feature. Can we make it look more like [existing application] I showed you? What if a user wants to [do more complex thing we didn't discuss before]?" In our last full team meeting, PM had my co-programmer demo the progress of a feature. The resulting team conversation was about rearranging stuff on screen, and eventually went backwards to discussing changing an existing feature. (Co-Programmer and I do not have the authority to say "No, we aren't going to change that.") After this I presented some mock-ups PM asked me to do. I only got to slide 3 of 20. The team discussion was about user privileges (something that has been discussed greatly but not decided on), and the conclusion from Head Researcher was "let's come up with more general concepts for the feature." Another point of frustration for me was that it had previously been agreed that my mock-ups would apply to a clearly defined scope of the project, but much team discussion was about having the feature in a larger scope that would be more complex (and confusing to users) and take more time to create. I will probably end up having to implement both. Re-reading these things, they do not seem that bad and I should be able to suck it up and deal with it. However, for some reason I have become conditioned to feel overwhelmingly ANNOYED by meetings. I dread them. I am starting to dread hearing PM's voice. I am struggling to articulate why I feel this way. I think it is because nothing is ever decided. We never get a chance to perfect and fix problems in what we have because we are always adding new bells and whistles and changing things to make the team happy. If I volunteer what I think is valid input, it's not used or it's modified until it's complicated. I feel kind of bad for the users of this application and I don't have much pride in the result - but I am not a researcher/user so maybe it is completely fine! Another short story: When Head Researcher thought we might want to get input from a user interface consultant, I quickly jumped on it and found one. I was hoping that some things might get finalized faster if we had an authority on software design and development giving us advice. Nobody really knew 'how to use' the UI consultant. We do not get input from them any more because "the research process is too complex" and they can't help us with designing features without us taking lots of time to teach them about the process. Yesterday when talking to PM, they said "No, you really seem more angry when things don't go your way" and I internally said oh no everyone here thinks I'm selfish and bitchy and angry all the time, better apply for jobs on the other side of the country so I can never see any of them again. I wasn't able to express that I'm trying really hard not to be a jerk, it's not because things don't go my way, I really don't care if someone likes my input or not, it is this inexplicable frustration I feel at the process of things here. PM's comment to me from yesterday and my internal reaction to it are leading me to seek advice here. What I need help on is: - Are these normal processes for software development? Are these meeting situations par for the course, or is it just my particular workplace? Do I just not understand something here? - Is my inner meeting rage completely unjustified? Do I have anger problems? - How can I get rid of my meeting frustration and just be a normal worker who works? If I can't get rid of it, how can I better hide it? - Does this mean I will be frustrated as a software developer anywhere? Thanks for taking the time to read this mess. I can attempt to clarify anything as needed. But feel free to tear me apart. I think I need it.

  • Answer:

    You selected the programming language, presumably others agreed, so don't feel like everything bad that happens is somehow your fault because of that initial decision. Nobody else spoke up, so think of it as a group decision. Own it and move on. Workplace culture can be hard to change, and it sounds like you have one where there are lots of meetings that don't accomplish much. As a result, it sounds like you feel you're banging your head against a wall. A few things here: First, others probably feel this way too. Maybe you can informally talk to others and enlist them in making meetings more productive. Second, read up on ways to make meetings more productive (entire books have been written on this subject -- here's one of many http://www.techrepublic.com/blog/10things/10-ways-to-make-meetings-more-effective/263, you will find more with some quick Googling) and think about what you can implement in your workplace. Third, talk to the PM and try to explain that you're not concerned about things not going your way, it's that [you would like more input] [you would like to spend less time in meetings] [you would like meetings to be more focused] [or whatever -- it's not clear from your post]. One easy tip about meetings -- start with an agenda and end with a list of action items. You don't need to be in charge of the meeting for this. At the beginning, you can speak up and say, "I think we're here to accomplish X and Y, is that right?" and at the end you can say, "Okay, so I will do ___, Second Programmer will do ___, and PM will look into issue ___ and we'll meet about this again next week to discuss that issue." This prevents meeting sprawl and makes sure you're focused on actually getting something done. You may want to check about a book about negotiation -- Getting to Yes and Crucial Conversations are good ones. They will help you communicate clearly and effectively about what you want. These books, or generally learning about negotiation and workplace communication, will also help you talk to PM about some of your frustrations without sounding angry or defensive.

sarahj at Ask.Metafilter.Com Visit the source

Was this solution helpful to you?

Other answers

Oh my goodness, I was not expecting such constructive comments from this. Thank you so much for the wonderful info and advice, everyone. I've definitely got some good reading ahead of me. For the record, I really don't think my PM is as horrible as it came off in the question. I guess I thought I wouldn't be consulted every time there is an idea and that the requirements-deciding and the dev process would be more... concrete. And I think 'rage' was the wrong word choice regarding my feelings towards these meetings. "annoyed" is probably more accurate. I've realized that I fully enjoy everything about my job except this Process and I was expecting that being a software developer would involve more Creating and Doing and less Process. It doesn't ruin my life, but The Process is what makes me groan about going to work because I know a significant fraction of my day will be Process. I'm glad to know now that this is pretty standard so I can get my butt on an alternative career path ASAP. I probably won't be speaking up again or asking anything about changing the process any time soon. I just sound angry and annoyed when I do so, I guess. Last time I tried to do that I asked PM to send me requests in emails so i could prioritize things that way, and then just ONE time I forget to open my Outlook... sigh. So now, meetings. and someone mentioned SSRI's which I find funny because I just went off them. they made me give too few fucks and I got nothing done. I will consider reconsidering. Seriously, thanks a million, everyone. I'm off to get some of those books.

sarahj

If you have a sympathetic manager (that is not the PM), I would talk to him/her about it. You tried to work it out with the PM, the PM is not working with you, and now you need to do something else about the obstructive PM. Time to get somebody else to have a talk with her.

crazycanuck

On the flip side, working alongside competent colleagues on a project with a competent PM can be extremely enjoyable. Don't write off professional software development just because your present boss is pointy-haired. In general, you're more likely to find competent teams working for smaller businesses. Or perhaps you could try to land a job as the sole developer in a really small business whose proprietor you have reason to respect - there's a lot of fun and freedom there as well.

flabdablet

I'm a pretty terrible employee to begin with I guess, so I really have no business pushing my own desires in this place. That doesn't follow. If you're incompetent, you won't keep a job whether or not you push your own desires (unless, obviously, you're at least in middle management; incompetence is apparently no barrier to career advancement in a management role). If you're competent and you know it, negotiating whatever working arrangement suit you best is perfectly appropriate. Software project managers without software development experience are usually not the least bit good at managing software development teams. They tend to prefer managing the kind of useless drone who just puts their head down and shuts up and pretends to do what they're told, and they're almost always totally insensitive to whether or not the people they're managing can actually write code. This makes them insanely frustrating for any competent developer to work with; hence my http://ask.metafilter.com/201725/The-user-is-always-right#2906100

flabdablet

Sigh, a late follow up, for my own sanity... I had another sort of falling out with my PM today, as in we were previously back on at least somewhat-good terms and now it has become very clear that I'm the child with the bad attitude who needs correction. She emailed me to talk about something unrelated to my current project, I replied asking if we could discuss it tomorrow so I wouldn't get off track, she insisted, I went over and then she asked me to close her office door and gave me a talking-to. In the previous month I had started doing a lot of asking about "where will this fit into the schedule" and "is this priority?" whenever a new Random Thing 2.0 popped into conversation and she called me out on my "stress" about the schedule, mainly, although I can tell it was also against my (poorly hidden) resentment/bad attitude towards her constant distractions. (I know. I suck at this sort of social graces thing, I guess.) The funny thing is, rereading this response from crazycanuck:Have a meta conversation in private about how you have conversations with your PM. Tell your PM that you just want to do your shit in a timely manner, and not be randomized with requests out of the blue all of the time. You understand that PM wants to make the product better, however this PM's requests are simply annoying you and distracting you from getting important work done. Ask for PM's input on how you can communicate better to solve this problem. Brainstorm for a while. Set some boundaries - perhaps sandbox the feature creep discussions to once a week, not once a day. Enforce the boundaries. I said all of these things and was overruled because I'm not PM. I tried to describe that my work style is to take things one step at a time and asked if we could implement scrum-style daily morning meetings and have those be the ONLY daily pm-programmer meetings, and she said "that's not going to happen." She also brought up the fact that I come in at 9:30 instead of 9 and work through lunch to make up for it and have weekly doctor's appointments, so shouldn't you stay late today to make up for it? so it also turned out to be mostly that I'm not following office protocol (and not being there when she needs me for whatever) although I'm still getting the important things done when they need to be done. I'm a pretty terrible employee to begin with I guess, so I really have no business pushing my own desires in this place. After today I think I've pretty much sufficiently trashed whatever positive reference I thought I might get out of this job so I'm looking for other positions, although I'm pretty disenchanted with software/web development if this is what it's going to be like generally. So it goes.

sarahj

To directly address the issue of being interrupted multiple times per day - ask the PM to gather those items onto an "issue log" and have regularly scheduled meetings to go over the items and make decisions on them all at one time. Try to get them to be weekly meetings, but be prepared to meet somewhere in the middle between 3 times a day and weekly.

CathyG

I work in a very different sector and am relieved to see this isn't unique to us. I started out four years ago very angry and loathing meetings. In some ways I hate how I've become so resigned and passive in just letting it wash over me now. But in other ways I realise that being less angry is part of growing up and working in a team. It made me angry that I'm right and they can't see how wrong they are but then I realise (1) I may not know everything (that came as a shock) (2) maybe they know something or they're bringing something to the table that balances my outlook (3) it's a human process and these are opportunities to study people. As far as I can see, being able to deal with people will do more for career prospects than technical knowledge. Can you treat this job as an opportunity to hone your people skills/study peopledynamics/acquire a toolkit for conflict disposal (frame it how you like)? Sorry to ramble, but to offer inexpert advice (after Dale Carnegie) on you question of how to how to repair office relations, I think the first principle of peopledynamics is seeing the issue from the other's point of view reduces friction. If you can work out what kind of personality your PM has, what pressures he's under and what his brief is, you'll find it much easier to be nice to him, and you'll get along better.

Gomoryhu

We are under the guidance of a Project Manager (PM) who has worked in marketing I stopped there. RUN AWAY

flabdablet

I struggled with the same feelings in my first post-college job, and I also had a manager call me on it, even though I thought I was hiding it. It was super embarassing, but it actually forced me to deal with my feelings, which helped. During meetings, I would focus on keeping my voice even and a little bit softer than normal. That gave me something besides my emotions to focus on and prevented me from talking through clenched teeth. Also, if I was the one currently presenting, I made myself be assertive about controlling the discussion. The phrase "let's take this offline" is your friend (delivered with a polite smile, of course). I left that job six months later for unrelated reasons, but in that time I didn't receive any more criticism for being angry. And somehow I found that at my second job, those feelings were just gone, even though the workplace was even more disorganized and frustrating. I think it can be a trial-by-fire thing for new grads.

neushoorn

Find solution

For every problem there is a solution! Proved by Solucija.

  • Got an issue and looking for advice?

  • Ask Solucija to search every corner of the Web for help.

  • Get workable solutions and helpful tips in a moment.

Just ask Solucija about an issue you face and immediately get a list of ready solutions, answers and tips from other Internet users. We always provide the most suitable and complete answer to your question at the top, along with a few good alternatives below.