Neil Hopcroft

A digital misfit

The meeting went very well

Today we had a meeting. A meeting with a customer. It was one of the worst meetings I’ve been to in a long time[0]. Not because there was a lot of anger or problems or anything. It was just very unstructured.

Theres six of us in the meeting, two techies from the customer, two business guys from my company and us two techies. We’ve all been in the industry for a number of years. Theres a need they need addressing, they don’t really understand it but they know they want dealt with. We don’t think what they’re describing will be able to do the job that we think they want it to do.

We end up arguing over syntax when we should be figuring out the semantics. Noone is in control. It shouldn’t be my place to do that, I don’t want to wrestle control away from my companies directors. Not unless they want to give me control. And I don’t think they know me well enough to trust me to do that yet.

And now its my job to write up the requirements document.

Do you know how to hold a meeting? Do you find that people drift off topic? What can you do about that? Do you need to do anything about it?

[0] Notable career lowlights so far being the Racal Mug Incident, and the Yokoyama Torture.


7 comments

  1. Thats what I thought. But five other people, all with more experience in the industry than me, didn’t seem at all interested in any of that.

    We had a room and were all there on time.

  2. hsb

    I used to minute weekly meetings. After watching them discuss the same things over and over, I changed the format of the minutes so that there was one column for the actual issue, one for what action was due next, one of who was in charge of doing it and one for the date/timeline.

    This was an amazing tool for embarrassing people into actually doing what they said they would. I recommend it for all project managers. If it gets really bad, start putting ‘Postponed from xx/xx to xx/xx’ on all slipping deadlines, so that it’s clear just how long people have been saying they will do whatever it is for.

    When I left, they quietly abandoned being minuted, as requiring too much actual delivery on promises.

    H

  3. We’re essentially contractors for them, either they should be driving it or our business people should if the customer can’t.

    It didn’t help that my fellow techie, while good at the technical stuff, is something of a loose cannon. He tends to assume that everyone is stupid, which is a bit true, but he also lets them know it. Except he’s not a very good communicator so nobody understands anything he says….

  4. Thats an interesting idea, but seems there might be some problems with continuity, they won’t know if things are outside the scope of the project unless they’ve got some history with the project, at which point they become a part of the project.

    Do you find it works? Is there anything you think I could introduce into my company to make it work there? (we’re a much smaller company, about 25 people)

  5. Things don’t seem to be getting considerably better, its going to go horribly wrong, its just a question of how long before it happens.

  6. Just gotta play the game and make sure nothing sticks to me…which reminds me I’ve got to send a mail to all project members tomorrow explaining my concerns about relationship management.

Leave a Reply

Your email address will not be published.