Give your team room to express themselves
Paul Boag, one of the founders and directors of Headscape, once said; “We specialise in sh*t projects.”
If, like me, you run projects for a normal, every day web agency. If you do not always get the opportunity to be working with the latest cool technology or utilize the next whizz bang idea. If you don’t build sites for rock bands or the latest cool technology start-ups. How do you keep you team excited and enthusiastic about their day jobs? After all, if your team is not interested in the work that they are doing then they will not produce the high standards that you need and that they are capable of. This in turn is demotivating and you end up in a downward spiral.
How do you get your team excited about a project for brown paper bag manufacturers?
Read MoreWarm Body Syndrome – reprise
Back in March, when I first had an attempt at launching this blog, I published an article called “Warm Body Syndrome“. Despite nobody actually reading it at the time (except Sam Barnes; thanks Sam) it is my most popular post via google searches.
As Headscape are back on the recruitment merry-go-round (product marketing or something(?) | tech guy/gal), and some people actually  read this blog now, it seemed like a good time to float this post back to the top again.
Found any warm bodies?
Have a read of  ”Warm Body Syndrome“. Google stats can’t be wrong! It must be good. *smile*
Let me know what you think. Have you ever recruited a “warm body”? Maybe you have been a “warm body”. What was your experience?
Read MoreProject managers: the great ambassadors of our time
A big, if not the biggest, part of my job as a web project manager is dealing with clients. This is actually the part of the job I enjoy the most and see the client as, very much, a part of the project team. I have found that an honest and transparent approach is best when dealing with query’s and problems and involving clients in the general processes of the project (as much as they are able) leads to a smoother road for all concerned.
I have said this before but I see a PM’s role as one of facilitation. I need to enable people to do what they are good at and I need to, wherever possible, stay out of the way. To some extent, this includes client communication.
The ambassador
I recently read a good post by John Reeve; Project Managers: Why every creative agency needs one. In this article he talks about the PM’s role of ambassador. A go-between between the client and the production team. While I agree that this can be necessary at times I see this as only a temporary role.
As PM I need to be aware of all communications. I need to have  a complete overview of the project and understand what is going on when and who needs to do what next. This doesn’t mean that I need to be a middle man. While I still hold on to my technical routes, the chances are, when a client has a question or a problem of a technical nature I will not know the answer.  I will need to go and ask the tech team. Similarly, with a design based question, I generally have no hope without first consulting the design team. So why should I get in way?
Expose your team
We have found it useful to introduce the client to the team at the earliest possible stage in the process. Wherever possible the lead designer and lead tech on a project will be at the project kick-off meeting.  The team will take a lead in conference calls where questions or discussions are to be had about their area of expertise. As long as I am kept in the loop then there is no reason for me as PM act as messenger boy.
When this process works well the client feels more connected with the process and, as they get to know the team, have a greater level of confidence in the the time-scales, quality control and ultimately, the deliverable.
Obviously, some relationships are difficult. This is where the role of “ambassador” goes on for longer than is ideal. As PM it is important to spot and manage these situations so as to still produce the required results and get the job done. I have found this to be a rare scenario.
Openness and transparency as an approach needs to stretch throughout the structure of the project. This includes exposing your team to your clients.
What is your experience?
As a designer or a developer, what is your experience of  dealing directly with a client? As a client, what is your experience of talking directly to production team members or maybe your experience of not being able to? PM’s, do you have experience of this approach going horrible wrong?
Read MoreConfidence is king
Confidence plays an important role in many areas of our lives. You will often here it said of footballer, for example, that they are a confidence player. I know from my own inability to play golf that I become marginally less rubbish if I have confidence in my next shot. Leaders who lead directly and with confidence are people that we want to follow. If you offer somebody direction, with confidence, they will, most likely, blindly follow. And the opposite is also true. Even if you know what you are talking about, if you do not present a confident argument, you will generally be ignored.
The same is true of your team. A team, full of confidence, will be more efficient at finding solutions to your problems. Â If confidence is low, time will be wasted while they decide even if they can solve the issue. The idea that; there is no such thing as a problem without a solution, goes out of the window.
When a team questions their ability to solve a problem. The problem is in danger of not being solved.
Building Confidence.
It is important to be active in building the confidence of your team. This includes being on the look out for things which will damage the confidence of individuals.
- Public praise.
Be vocal about the successes of your team and the individuals within it. Publicise the good activity that is going on all the time. This is especially important if an individual  has been struggling for confidence. Inform other areas in the organisation of your successes. When a project is completed or an important milestone is reached, spread the word. Send an email highlighting the work and the individuals involved. Twitter is also a great tool for this and especially useful in the web world where what you are working on is often in the public domain. When your team does something well, hold it up for all to see. - Do not allow individuals to dominate a team.
A certain way to knock the confidence of an individual is if they are in a team with one or two unapproachable ‘experts’ . When one member of a team is perceived to always have the best solution others will be less willing offer suggestions.  Remember, a quite individual does not equate to an incompetent individual.  It is important to build the confidence of such individuals otherwise you will lose their valuable input. If you identify this situation your can try to build their confidence and their standing within the team.  Ask them specifically for their opinion. Take them aside and seek their assessment of an issue. Public praise can also be a useful tool for individuals as well as teams. If somebody doesn’t have the confidence to contribute then you will lose their contribution. - Do not set people up to fail.
Be realistic with the challenges that you set for your team. If you consistently set an unrealistic target which ends with your team not achieving their goals, then their confidence and eventually their effectiveness will suffer. Break larger tasks into achievable chunks. Give people the opportunity to achieve something small along the way to a larger success. Failure is a demotivating experience. If it happens too often it can become habitual. Make sure that your team has a fighting chance of success. Do not set them up to fail.
A confident team is more productive. They are also more innovative in their solutions because they expect to not only achieve their goals but to excel at what they are doing.  It is important to not go too far and breed arrogance and complacency but a team of confident individuals will make your job a lot easier.
Have you had the experience of being in a team that has lacked confidence? What other ways of building the confidence of the team, or an individual, have you come across?
Read MoreReduced to stereotypes
I’m often asked questions about the differences between working with designers and developers. Today an article I wrote for boagworld.com was published which takes a brief look at this question.
Donât Reduce Your Designers And Developers To Stereotypes
Read MoreIt’s OK to not know.
“I don’t know” is actually a valid answer to a problem.
“Let me think about that” is not an excuse to waste time.
“I think I should discuss this problem with my peers” doesn’t present you as incapable.
No need to be infallible
We all want to be seen in the best light. We don’t want to be seen to make mistakes. We want to be appreciated for what do. We want acknowledgement for all we put in and what we can achieve. We definitely don’t want to be seen as the weak link. We want to give an impression that we are in control and that we are ready for whatever challenge may come our way. We want people to know that they can trust us; that they can rely on us. We want to inspire confidence that we know what we are doing.
To achieve this we do not need to be infallible.  We need to be honest; with other people and ourselves.
It can be too easy to try and have an answer for everything.  If you are presented with a problem you want to solve it quickly. Most problems that come up in my world as a web project manager do not have instant answers and I’m typically very suspicious of off the cuff solutions.  When I pose a problem to my team I would expect an answer that is something along the lines of; “Give me some time to consider that” or “I’m not sure, there could be several solutions, let me do some thinking and research”.
Similarly, in an environment of peers, if you don’t know how something works, ask your team mates. Share the knowledge around. It’s sounds obvious but many people are too afraid of what people my think of them if they ask a seemingly obvious question.
Honesty is just fine
Acknowledging areas of weakness or gaps in understanding, far from creating a negative picture you, will actually increase your standing with people around you. Understanding who you are and what you can (and can’t) do is a sign of strength. It will produce self confidence which others will feed off. And if you can pin point the areas where you need to improve then you are in a much stronger position to do something about them. People around you will recognise this and therefore have more confidence in you.
A quick answer that,  further down the road, proves to not the be the best solution, causes problems. It might make you appear to be on top of your game at that moment in time but it will leave people with less confidence in you in future. However, a more considered approach, which yields good results, leaves everybody with greater confidence in your ability. It will breed trust.
Fear can be a big issue; both for team members and team leaders. We are afraid to appear weak, or slow, or unreliable. We are concerned that our boss or our peers will think we do not know what we are doing.
It’s worth remembering that asking questions and saying, “I don’t know”, are not a sign of weakness. In fact, they are a sign of strength.
Read More