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?

It doesn’t belong to you

The first thing to do is to promote ownership of the project within your team. Let them in on the solution. It can be tempting at times to solve (or try at least) all the problems yourself. It is much better to get your production team (designers and developers) in on the act as early as possible in the project. Do not present your designers with a list of things to do. Instead, give them a collection of problems that their design needs to solve. Do not dictate the technology that your developers must use. Instead give them the information that they need to choose the most suitable tools for the task.

Allow your team to shape the solution and they will take pride in the result. Let the project be their project. Not your project.

Express yourselves

The second thing to do is to allow your team the time and space to express themselves. Allow them to be creative; to try a new technique in a real project situation. Even if it is something very small in the grand scheme of the project it can act as the signature of your production team. This mark of ownership will inspire them to make sure that even the most mundane of projects can be the best that it can be.

Allow your techies to experiment with the new features of the latest programming language release. Allow your designers to put in that extra fun element that will only work in in the latest cool browsers. Give them the space play with a real project in a real life situation.

Using a new technique or a new technology can be enough to provoke the interest of your team. This means that the website for the brown paper bag manufacturers can be the most exciting project that you team has ever been a part of.

Slaves to the time line

Alarm bells are ringing. What about the time line! We have a deadline to meet.

And quite right too. These extra bells and whistles cannot get in the way of real targets and delivery milestones. However, if you build some time into your schedules to allow for this kind of experimentation you will have a happier, more enthusiastic and, ultimately, more productive team.

This will also encourage your team to keep developing their skill set knowing that they will get a chance to use their new found talents in real projects leading to a higher quality of work over all.

Is this something that you have tried? Or as a designer or developer have you tried to sneak little Easter Eggs into your work just to make sure that you still have a pulse at the end of the day? Let me know.

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?

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?

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.

1. 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.
2. 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.
3. 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?

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

“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.

We’ve all been there. There is a hole in your team, a job that needs to be done. Maybe somebody has moved on leaving a vacancy or your activities have expanded to such an extent that new skills or more resource is needed. And what’s more, you need it now!

The temptation is to fill the vacancy as quickly as possible. The first person who is willing and able is given the job. The nearest warm body is plucked out of the air and put in place as soon as possible. You just succumbed to ‘warm body syndrome’.

Ok, so you might get lucky. Somebody was in the right place at the right time and they are perfect for the role. They have all the skills, they have the temperament, you get on well, everything is a roaring success and all live happily ever after. However, sadly, this isn’t the norm. A simple rule to remember is; “just because they can, doesn’t mean they should.”

A few things to bear in mind:

1. You are not doing anybody a favour by asking somebody to do a job they can’t do. 
2. You are not helping anybody out by agreeing to a request from somebody to do a job that they are not able to do.
3. Making a wrong decision is expensive!
4. Making a wrong decision is waste of time!
5. Making a wrong decision just upsets all involved.
6. Making a wrong decision will mean you just have to go through the whole process again.

It’s best to take your time over such things. Don’t appoint somebody just because there is nobody else. If they are not right for the role then that’s it. End of story. Remember that undoing this decision is going to be a drawn out and painful process. It’s worth taking your time and getting it right first time.

This can be difficult. There is a temptation to either put somebody in post because they really want the role. Or to appoint because you really need the position filled.  But it is best to not appoint at all then to make the wrong decision. Taking your time and waiting for the right person may mean that the existing team need to work harder for a while. It may me somebody in the team doesn’t get the promotion that they have been after. It may mean the new initiative that you want to kick off will need to wait. But all these things are better than the alternative.

Resist the quick fix. Take your time. Get it right.

It’s very easy to indentify when something is wrong. It doesn’t matter if it’s a small one person task or a large project being undertaken by a whole team of people, finding issues is normally…  no, I would say, always possible; even easy to do. By spotting a problem you are nothing new. You are not doing anything different you do not stand out in any way. Solutions on the other hand are a rare commodity.

During my spell as the technical team lead at Headscape I tried to install something of a motto into the team. “Everything is possible, there is always a way.” And a few variations on that theme. When a project manager, or a client would approach me with a new piece of functionality or a new project or even just the beginnings of a new idea I tried to always approach it from the point of view that whatever they were asking for was possible to achieve. It was my job / my teams job to find the solution.

It sounds quite obvious really. We are a “solutions” business. Our job is essentially to solve our clients problems (even if they don’t see it that way). But this is not a concept that everyone has grasped. I’ve been involved in a number of teams who almost seemed to pride themselves on indentifying why a particular request wasn’t possible or was a silly idea.  Often talking themselves out of work in the process. In fact, thinking about it now, I wonder if that was the aim of the exercise. *smile*

Now I’m involved in project management I don’t want to hear about problems. Problems don’t help me. I want to hear about solutions.  Obviously there are often many issues with a particular request or piece of work. I’m not suggesting we just run along like a collection of blind robots and try to implement any idea that comes our way. But rather than just listing all the reasons why a given piece of functionality is a silly idea, think it through and offer an alternative solution.

If you approach every situation “knowing” that everything is possible and that there is always a solution then, in my experience, you will find it. And in a room full of people who are very capable of, and often very eager to, point out the issues you will stand out as the person who offers solutions.

It is very easy to find problems. The key is to find the solutions.

It’s good to get things off your chest. Inevitably, during the course of a project things will annoy you. A customer will insist on something stupid, a college will make a hash of something which will add to your work load, a member of your team will do something daft and you will have to pick up the pieces, you will release that you had not thought something through or that you have cut a corner to save time and it’s made everything take three times as long as it should.

It happens. But how you deal with these situations will have a big impact on, not only your project, but your general state of mind too.

A wise man once said

There is an old proverb that goes something like this; “don’t let the sun go down on an argument”. This is good advice; not only for the sake of the relationship involve but also because we all know that you generally feel better when the air is cleared. The same principle needs to be applied here.

There may not have been an actual argument or disagreement but somehow somebody has gotten under your skin and you can feel the tension and frustration building. Of course, it is not always appropriate to ‘have it out’ with the person involved. After all, an offended client is likely to only make your situation worse. A disgruntled team member is not really very likely to up their game either. And after all, your boss may just fire you *smile*.

Get it all out

However, you need to do something. If you are getting increasingly frustrated and don’t have a vent then your productivity, creativity, and general happiness will very quickly hit a downward curve.

At Headscape; amongst the Project Managers at least, we have the concept of the rant line. Essentially, when  something has ‘gotten our goat’ we can call one of the other PM’s and rant.  It’s great! It makes you feel so much better.

This is an informal, and somewhat tongue in cheek, arrangement but it is a concept that is worth considering.

Some organisations have a more formal system. The idea of ‘buddies’, or some sort of mentoring or accountability. The system is tweaked to the situation but the idea is the same. A safe place to unload, without fear of reprisals. To be open and honest. To clear the air when there is no other sensible outlet.

If you let such frustrations build up; your project suffers, your team suffers, and ultimately, you suffer. So don’t let things get you down. Call the rant line! *smile*

It’s amazing what we will say to get people to do what we want. Whether it be to win a sale from a new client, convince our boss that our latest bright idea is worth everybody’s time, or to just convince members of your team that this new project or methodology is really exciting, we have a tendency to exaggerate. But this can cause more of a headache than simply an interesting moral dilemma.

Don’t promise the Earth

Promising the Earth, in under six days, is easy. With the right people skills and experience it’s possible to sell any product or idea to just about anybody. The short term gains are obvious; you win the sale, your great idea goes into production, your team get really excited and motivated. But your exaggeration, or slight stretch of the truth, will become obvious pretty quickly.

The damage this causes can be long lasting or even irreversible. If you company gains a reputation for under estimating time scales on projects it will soon start to count against you. If you have exaggerated the potential benefits of your new structure or methodology, your next idea will not be so easily received. If you have told your team that this next project is earth shatteringly exciting and it turns out to be the same old dirge, you will have a problem motivating them in future.

The element of suprise

The positives of doing the reverse are massive. To surprise your new client by delivering a little early or providing an extra little feature can make the difference between them giving you those all important repeat sales. To be known as an individual who takes the extra care to double, triple check everything before it goes higher up the food chain can be the difference when that coveted promotion comes up. You get the idea.

It’s a very simple lesson really, but one which we so often ignore. If we over sell something; a product or our own skill set, we are digging ourselves a big hole. You create disappointment and negativity that had no reason to be there. What you provide might be just what’s needed but because it’s less that you promised it will not be as well received. Whereas if we under sell what we are providing, the positive impact of the delivery far outweigh what was delivered on its merits alone.

It’s a difficult balance to get. If you under sell too much, then nobody will want you. But that said; under sell, over deliver, is a good little motto to live by.