What’s more annoying, the crap cliché or font style and position?

Image source

While I’m not going to dispute this, I do feel this life lesson is often misunderstood and even abused in the workplace with the result being failure in the short-term, and in the long-term a very damaging self-perpetuating culture that actually hinders businesses everywhere by scaring employees into silence and creating a delusional mindset – or as described in the fascinating article by Jason Yip…

…a systemic inability to confront brutal reality.
Jason Yip, Why does problem-hiding occur?

To bring it back to a web project management level, I’m talking about a situation where a client or your colleagues give you what looks like an impossible web project-based mountain to climb and when you begin to raise anything other than positive sugar coated comments you’re labelled as being negative.

I’ll say it now – I think this is utter BULLSHIT.

But hang on a minute, how do you know you’re not being negative? How do you know what’s being asked of you and your team is not feasible? How do you know by immediately taking this approach isn’t dooming the challenge to failure before you’ve even tried?

Negativity Explored

The dictionary describes ‘negativity’ as:

Expressing, containing, or consisting of a negation, refusal, or denial – indicating opposition or resistance. Lacking positive or constructive features, unpleasant, disagreeable, gloomy, pessimistic.
The Free Dictionary

Pretty depressing huh, kind of makes you feel like the below made me feel as a child, FIGHT AGAINST THE SADNESS!

Horrific! If you want to take a few minutes to recover at this point I completely understand.

However when it comes to web project management I sincerely believe it is a Web Project Manager’s job to execute most of the actions listed in the first sentence of the dictionary’s definition when necessary, and absolutely at all costs never any of those in the second – thus throwing the very essence of ‘what is negativity’ in web projects into a spin.

It’s my belief that there are two types of people labelled as negative in digital agencies:

1. A person who’s never positive about any web project or agency strategies
2. A person who’s realistic and isn’t afraid to speak up while others are afraid

A feline representation of a Type 1

Image source

For the purposes of this article I’m going to ignore the Type 1 people and leave them with their dehumanised droid-esque title but want to emphasis just how different these two types are.

The Dangers of Blind Positive Thinking

Before I get into why negativity isn’t always bad, let’s look at the benefits of blind positive thinking. I use this term to refer to the mentality adopted by some whereby no matter what the challenge they believe simply by being positive means they will prevail – an attitude commonly associated with entrepreneurs.

There is absolutely no doubt in my mind that adopting this mindset will see both you and teams working for you through tough times. It is infinitely nicer to work in an environment where everyone is positive rather than negative, it motivates people, it encourages people to excel beyond their previously self-imposed limits and, just like negativity it’s highly infectious.

But, and it’s a big but, at what point does positivity drift into the delusional? I’ll tell you when, it’s at the point where no amount of positive thinking in the whole wide world will revert a doomed situation into a successful one.

To focus 100% on positivity, to try to trick your brain into thinking everything is great, is to prevent yourself from making an impact in your life and in the world. When you turn a blind eye to what’s wrong in the world and what’s wrong in your life, you’ll never be able to do anything to fix it.
Joey Weber, The Case for Being Negative

Positive thinking will not fill your tank with gas when you’ve run out, nor will it get your £100k web project complete for £10k – in steps the realist – or in the context of this article, the Web Project Manager.

Weeeeeee… donk!

Image source

There will be points in a Web Project Manager’s career where they have to be the ones to put a total shitter on everyone’s ‘positive’ plans by getting annoying logical on their ass, some will call this being negative, but it isn’t, it’s just fact.

Sometimes you have to ram home the dangers of blind positive thinking and stop people making huge mistakes on web projects, but the method you choose to do this can seriously make or break your reputation as a Web Project Manager – play it wrong and you’ll be labelled as negative and future sceptical stands will be ignored, play it right and over time your judgment will be trusted.

The Confession

As with any lesson in web project management I’ve ever learnt, I learnt it the hard way, by making mistake after mistake. For example, when being given completely unrealistic budgets or deadlines I’ve made a ‘you must be mental‘ face and pretty much said that.

I was told to stop being so negative and to get on running the web project. I ran it to the best of my ability and of course it ran massively over schedule and budget. Was I right 99% of the time? You bet your sweet ass I was, but had I played this situation well? Hell no.

What I had done was de-motivate my boss, my team, myself and spent the whole project uttering bad things and occasionally getting accused of actually causing the overrun due to my negativity – total nonsense but also a total fail on my part.

Naughty Web Project Manager

Image source

So what exactly did these painful lessons teach me… they taught me how to communicate realism.

How to Be Negative (Realistic)

Below are the lessons I’ve learnt when it comes to expressing huge concerns about web projects. If only one or two Web Project Managers out there can put these into practice and save themselves from some pain, I’ll be a happy little Englishman.

It’s Not Obvious to Everyone

First of all, when I was pulling my ‘you must be mental’ face I was making the mistake of assuming that the ‘mission impossible demand’ was so obviously unachievable only a fool could think otherwise.

Later I realised this is not the case and that was actually my experience managing web projects that meant I could see it immediately from a proposal, an estimate or proposed timeline, where others could not.

Think Before You Speak

Before you pull your version of ‘the face’ take a few minutes to consider the very real possibility that it’s not common sense but actually your skill, your expertise and the very reason they hired you that make it so clear to see – even if you’re completely right, holding back from reacting quickly will save you oodles of pain.

Her Twitter profile says “CEO of my vagina” – genius

Image source

Ignore Your Instinct, Maybe It’s Possible

Instead of immediately going toe-to-toe with a positive smiley person and ruin their mood and your reputation, start by being humble and consider the fact that your instincts may be wrong.

Approach the problem logically i.e. take all of the requirements, break them down into smaller chunks and assign money, time or people to it on the absolute happy path where there is zero resistance and see if in fact you’re right.

Try your damndest to make it work on paper, and only when you’ve sincerely tried every trick in the web project management book and still you find gaping holes can you start to take the next steps.

Don’t Use Your Opinion, Use Cold Hard Numbers

Once you’ve done all the calculations for the happy path, save it and format it in such a way that it cannot be disputed by anyone regardless of their sunny disposition. Although taking longer, this is the maths equivalent of the ‘are you mental’ face and is much more powerful, unless you’re Chuck Norris.

Chuck Norris can use Comic Sans

Image source

Offer a Real Solution, and Get Positive!

This is one of the most important lessons in web project management, if not life… if you flat out disagree with something, don’t waste the limited time you have on this planet whining about it unless you’re willing to try and fix it.

As a Web Project Manager it’s your job to solve problems just as much as it is a designer’s or developer’s job.

Always follow the unveiling of your dream crushing numbers with either a proposed solution or a forum where a solution can be derived. Be it by adding more resource to a web project, using clever workarounds to achieve the same goals, getting more money or phasing the solution.

But don’t stop there, do the numbers on this too. Get the web project into a position where, even if it’s still going to be a mission, everyone, including you is able to get genuinely positive about it again!

The Crux of the Matter

Anyone who hides behind the mask of eternal and permanent positivity claiming that anyone who protests are all negative, aside from getting right on my tits, need a swift kick up the behind.

There is a very real difference between being negative and being realistic.

A negative person is rarely positive, a realistic person is sometimes positive and sometimes not, but when not, always tries to get things into a state where they can feel positive about it as opposed to constantly ‘thinking positive’ and screwing up time and time again.

Being realistic does not mean limiting your dreams; it simply means you make sensible steps to reaching them.

To be realistic is to think about things that you feel are really possible to achieve.
Difference Between Negative and Realism

My role as a Web Project Manager is to make the web developer’s jobs stress free.

At the time I thought this was just a fancy little trick to make the guy give me an interview gold star from his point of view, however, in my subsequent years as a Web Project Manager I’ve come to realise this wasn’t just a nice line to use – it’s actually one of the core principles of being a good Web Project Manager and actually extends further than web developers.

I now believe that one underlying line in any Web Project Manager Job description should be:

My role as Web Project Manager is to make everyone’s job as productive and stress free as possible.

With focus on web designers and developers, but true for the whole project team, let me explain…

Web Team Expertise Focus

Over the years I’ve seen digital agencies making big mistakes when it comes to effective web project management. One of the most common mistakes was having production team members e.g. web designers and developers performing web project management tasks rather than keeping them focussed on what they do best, designing and developing.

Web designers and web developers are highly skilled people and nothing will destroy their passion, productivity and morale quicker than having them involved in areas of a web project that stop them from doing what they love and do best, designing and developing.

The range of tasks that can stop these experts from doing what they’re hired to do are endless, but what is finite is that when it comes to web project team management, one primary goal of a Web Project Manager is to do everything within their power to ensure these guys and gals don’t get sidetracked or bogged down in things that will reduce the quality of their work.

The minute this happens the effectiveness of the team is diluted, momentum is reduced and Web Project Managers need to understand this.

Whether you used to be a web designer or developer or not, you have to appreciate that when these guys are in the zone and working hard to meet deadlines you probably set out for them, stopping to answer the phone, an e-mail or an ad hoc question can seriously break their flow and it takes time to get back into it.

Web Project Managers Are Stress Sponges

Another key aspect to being a good Web Project Manager is keep the production teams as stress free as possible by absorbing as much stress for them as you can.

This should be included in Web Project Manager induction packs

Image source

Although never on any Web Project Manager Job description, it should be assumed that part of the role is to basically take crap on behalf of your team in such a way that they don’t even get a whiff of it, even if they’re the cause of it.

During a web project there are a zillion things that will happen that will cause stress, but a test of your team management leadership skills is to see how much of this stress you can personally absorb in such a way that your production team don’t feel the heat, why?

Simply because a stressed web designer or developer will not work as well as a happy one.

Why Should I Take All The Crap!?

Many Web Project Managers out there have asked this question and it’s a valid one, but the answer is because it’s your job.

Think about it, your boss right now, do you think he or she is completely open with all members of their company about all the issues that exist right now? Of course not. While they may be transparent with many about certain workflow or revenue concerns they don’t bother the design or development teams with tax or buildings insurance issues.

Web Project Managers must shield their teams

Image source

There is a reason for this, it’s because it would serve no purpose other than to make everyone worry, and what happens when people are worried? They start to feel negative and this will only result in negative impact across the entire company.

Although a rather elaborate example, the theory is the same as to why you as a Web Project Manager should take all the crap you can and shield your web project team from it – because your job is to keep your team positive, motivated and focussed on their job – and if this means taking some crap you know you don’t deserve then so be it.

If you don’t like the sound of this then you have no business being a Web Project Manager, or a manager of any kind for that matter.

Web Project Managers Play Rhythm Guitar

If you want to be a good Web Project Manager you should try to aim to be a rhythm guitarist rather than play lead guitar or sing lead vocals.

By this I mean you should understand that your job is to sit behind the boys and girls that get all the attention for finished products and make sure everything runs smoothly without expecting any glory – for example, in the video below I’m not the pretty boy on lead, but his much wiser looking band mate on the left… cool eh!

Or as my Dad once told me, a good rhythm guitarist keeps the song going in such a way that when they’re playing you tend not to notice, but if they were taken away you immediately notice and the song falls flat on its face.

I’ve worked on many web projects in the past where the final website or application was delivered and all the praise was focussed around how beautiful the end product looked or how amazing this or that piece of functionality was – and the point here is that despite no one saying how great the web project management was, I didn’t mind one bit – I took an enormous amount of silent pleasure at the smiles on the faces of the designers and developers as they were patted on the back.

In many cases only I knew what stresses there was along the way and how much crap I’d taken on behalf of the team, and on occasion how I’d opted to make myself look at fault rather than make sure blame was assigned to who it should’ve been, but I kept it quiet and sat there smiling to myself because I had done my job.

And while this may all sound like some kind of self-proclaimed nobility and humility, it really isn’t. I just adamantly believe that a Web Project Manager’s greatest success should come in the form of being able to sit back and watch others be praised knowing that behind it all was you – I get more pleasure and satisfaction from that then receiving praise myself and have noticed this is a common trait among Web Project Managers the more I meet.

But I deserve some credit surely!?

People Aren’t Stupid, Respect Will Come

Of course Web Project Managers deserve credit for successful web projects, but I personally find that this comes over time, but if you’re like me it’s not so much credit that you want, it’s respect, and respect from not only management by the production team too.

Respect lil man!

Image source

In the heat of the moment when you’re taking the crap from someone or for someone it can often make you question why you’re bothering, after all Web Project Managers are just human too. Every part of you wants to shout out that actually it’s not your fault and it’s his or hers, and why should you be suffering all the stress when you’re not at fault.

But if you continually stay strong and show strength of character your manager and production teams will start to notice just what part you play in the success and appreciate it.

This not only means you can look yourself in the mirror at night knowing you’ve retained your dignity when others would’ve play the blame game, but you also gain an awful lot of respect that in the long term will actually reduce your own stress levels as people want to work for you more and more.

It’s kind of a strange philosophy but it seems to work – make your mission to make everyone else look good without ever expecting reward or credit, and somehow you end up looking good and receiving reward and credit.

Anyone who sets out on a mission to make themselves look good and receive reward or credit above their team – always seem to end up looking like dickheads.

Web Project Managers – don’t be a dickhead

Image source

So what can you do to minimise getting a ‘dickhead’ label?

Web Project Manager Anti-Dickhead Tips

Below are my top ten tips of how to make web designer’s and developer’s jobs as easy and stress free as possible by keeping them focussed on what they do best, which of course makes your web projects run smoother – if you get some respect along the way then consider it a bonus, not a birth right.

1. Try to pick the right moments to disturb them with questions e.g. be observant enough to realise when they’re in ‘the zone’
2. Don’t just forward website or application issues to them, try to identify the problem yourself so they can easily replicate the issue and get to work on the solution rather than investigation
3. Don’t drag them into meetings they don’t need to be in. If questions come up that they’re best to answer, take a note and get back to whoever once you have the answer
4. Be willing to push back clients or other teams if they need more time
5. Never say something is urgent when the truth is it’s easier for you to pressure them than to have an awkward conversation with someone else
6. Don’t let them work too much overtime to hit a target, if burn out is looking possible, send them home and take crap from the boss yourself
7. Have the balls to defend your team to management when it would be easier to blame them
8. Don’t gossip with them about web project politics, keep that to yourself
9. Put yourself in their shoes and make sure they get the files and documents they need in an organised manner
10. Never ever see yourself as above them

Have you got any anti-dickhead tips for keeping web production teams focussed and stress free? Let me know in the comments.

Is it about how to manage clients? Or maybe how to spot bad clients? Or what about how to handle client meetings? You could do an article that was more client-focussed.
@ioptics, Every single bloody night, 2010 – 2011

I then let him beat me at FIFA so he doesn’t go to bed crying. However, as much as it pains me to say it, he does make a good point.

The Game Genie is the only way @ioptics can win

There are an awful lot of web project management articles out there that are focussed on client management, as well as estimating, scope creep and budgets etc. but one area that is often overlooked is what part a Web Project Manager can play in team management.

My next series of articles will focus more on the internal aspects of web project management.

This article focuses on why and how a Web Project Manager should resolve common issues that cause internal team conflicts that ultimately stall web projects and lower team morale.

Dysfunctional Digital Families

Web designers hate developers, developers whine about designers and both bitch about the Web Project Managers – this is the stereotypical view of the relationship between these three parts of a web project team that resembles what social workers would undoubtedly call a dysfunctional digital family.

Why can’t we just all get along like this?

Image source

The reasons for these notoriously frosty relationships have been well documented over time in articles such as:

• Two Cats in a Sack: Designer-Developer Discord
• Why Project Managers are a Barrier for Designers

However, as my comments in the latter article suggests, I believe the reasons for issues all boil down to four things:

1. Conflicting priorities
2. Arrogance
3. Lack of competence
4. Low awareness of the bigger picture

Guess what, these four things are here to stay and as well as having to manage multiple web projects, several clients, a handful of suppliers and even your boss to some extent – I sincerely believe it’s down to the Web Project Manager to also manage these aspects of a digital team dynamics.

As some of you may be thinking right now “Why me!?”, well here’s why…

Web Project Managers: It’s Your Job

The simple answer to why it should be you, is because as a Web Project Manager you are responsible for the successful delivery of the web project and failure to manage the four issues will almost certainly result in either web project failure or a lower quality result than it could’ve been.

Not only are you responsible, but you’re often the only person with the full overview of the situation and thus are best placed to start resolution and below are some approaches to each.

Conflicting Priorities

As a Web Project Manager you are smack bang in the middle of web projects. Your boss just wants the project to go well, the client wants what they paid for, designers want to produce something they can be proud of and developers want to create elegant efficient code that solves the problem.

You have to manage bitches like this and their priorities

Image source

Unfortunately these priorities often clash and this is where the problems start, but the resolution approach is generally the same…

First you must understand the priorities of each party, then empathise completely, and finally educate all on everyone else’s priorities and feelings – and you have to do so in a way that leaves each party empathetic to all sides of the equation and willing to compromise.

To effectively achieve this you have to believe and champion the notion that no one is looking to screw anyone else over and all parties are just looking to produce the best thing they can – and you know what, this isn’t fantasy land, this is pretty much always the case but for some reason it’s rarely communicated.

Arrogance

We’ve all met them, the arrogant designer, developer and even the occasional arrogant Web Project Manager :)

They think they know it all and when challenged they see it as almost an insult, dig their heels in and seemingly set out on a mission to be as obstructive as possible to a smooth web project process.

Look at him, he so thinks he’s it!

Image source

However the truth is, pride and a high level of skill mixed with confidence is often mistaken for just arrogance. But whether these people are good or not is irrelevant really when it comes to eliminating this as a cause of web project problems.

Your mission is to remove barriers to momentum and get things going again and so, when faced with an arrogant team member just take them to one side and talk to them with respect about what their issues are – and when I say talk to them, really talk and more importantly listen first, and then once you’ve fully understood their issues make sure they know you’ve understood and then proceed to explain how all you want to do is move things forward.

Try offering up parallel issues that another team has with the project, try to make them appreciate it’s not just them in a bit of a situation and then finally make sure to leave the room with a deal that removes the barrier.

Lack of Competence

Sometimes a designer will hate a developer for putting the brakes on a design element that would require certain rocket science functionality, or a developer will get annoyed with a designer because a PSD has been poorly organised – while these situations can arise due to poor communication or squeezed time, it can also be a simple case of a lack of competence.

“Seriously guys, I swear I did it right this time, ya feel me?”

Image source

In either case there is one sure fire way to make matters worse and that’s to bitch and whine with either party about the other. Instead of enflaming the issue look at positive ways to solve it.

Immediately quell any slating of anyone and start to guide the conversation to a vibe of “Ok, how are we going to fix this now and make sure it doesn’t happen again”. Again, by default take the position that the person who has caused issues with low competence probably meant well and what’s needed is education not crucifixion.

Get the two parties together and facilitate a little informal session on why this element causes issues and what approach can be taken in the future to reduce them.

You’d be surprised how quickly the tone turns from spiteful and toxic to something a little more positive and constructive when a Web Project Manager gets two people together and facilitates a little education session, that leaves both parties feeling a little bit more empathetic towards the other.

Low Awareness of the Bigger Picture

Aside from conflicting priorities this is probably the most common reason for internal squabbling on digital teams and having been on the production side myself I can think back to when I was the biggest culprit.

I would build a site in superbly clean front-end code and then get annoyed when I was told there was no time to ensure the site passed a heap of accessibility checkpoints, be it through testers or by human testing – outrageous!!

“Oh no you didn’t just ask me to use inline CSS!!!”

Image source

Despite meaning well and knowing what best practice was I just didn’t understand that from a commercial standpoint that there just wasn’t the budget to allow me to do this. The mistake my manager at the time made was not to explain this to me in a way I could understand – I was totally peed off and thought he didn’t care about best practice.

From experiences like this I learnt that in similar design or development situations where a Web Project Manager will make a decision that makes production teams vomit, it’s important that you communicate that you’re fully aware it’s not best practice and then move onto explain why you’ve made the decision.

It really annoys me when any management person talks about production teams as if they don’t care about the commercial side of business, or even worse, wouldn’t understand it – bullshit.

Web designers and developers are very smart people and if they’re talked to as such I’ve yet to find one that doesn’t end up appreciating why they have to ‘code it dirty’ from time to time. No, it doesn’t make them happy to do so, nor will it stop the same frustrations next time as these people have passion and pride, but it does get the job done and compliance should always be rewarded on a future web project with some breathing space to do the right thing.

I genuinely believe if a production team member seems to not care about the bigger picture, his manager or Web Project Manager has simply not found the right way to communicate it and they should keep trying before assuming the worst of the person.

Summary

While there are many more common issues experienced within digital teams, the main points I wanted to get across are that as a Web Project Manager you should see it as your responsibility to try and resolve any issues that are causing problems with your web projects.

Please do not immediately go bleating to your manager or colleagues about these issues, first try and resolve them yourself.

Running to your manager each time not only puts more on their already busy plates, but it also loses you massive respect points from your team, the very people you’re meant to be leading and keeping motivated to work for you – the manager route should be your last point of call, not first.

Web Project Managers should never run to Lumbergh

Image source

Always start by being empathetic to Jedi levels when any issues arise. So often I see in-house fighting between two parties that turns nasty when all along both just wanted to do what they saw as the right thing – stop it before it turns nasty by genuinely (not falsely) listening and understanding the reasons for the feelings – a powerful weapon in the Web Project Manager’s arsenal is the ability to empathise where others cannot.

Make sure to resolve each conflict with education. This education could take many forms, be it on the skills front or business angle, but make sure that by the end of it all parties involved have a heightened awareness to the feelings of others and increased knowledge on how to avoid it next time.

Do you have any golden tips on managing internal issues in production teams?

What I especially loved about Rafael’s article was that as well as being funny, it actually was a pretty accurate list that I bet so many web developers can relate to, and he was using this approach to raise awareness among visual designers about what makes web projects go tits up from his perspective.

Rafael Mumme: My kinda man (no not like that!)

Although a different tactic, the desired result is similar to that which I will discuss in a new article I’m currently drafting, on resolving issues in web project management teams – one major point being to always educate colleagues about why certain things they do cause issues on web projects for others.

Of course, I just couldn’t help but jump on the bandwagon and immediately start drafting a list of the things that production teams do that really gets up Web Project Manager’s noses.

So, before I finish off some articles that defend you… Visual designers, Front-end Specialists, UX teams and Web Developers – please make sure you follow these guidelines if you want to get on the wrong side of your Web Project Manager :)

1. Make sure to only fill in your timesheets at the end of the week, it adds excitement to a web project when on Friday morning we think we have 20% budget left but by the end of Friday we’re 5% over.
2. When we chase you to make sure you’ve filled out your timesheet, remember to make the insightful point that while you’re doing this you’re not working. For bonus points ask how long you should add into your timesheets for the task of filling out your timesheets. As Web Project Managers we sometimes forget that the only reason we find the time is because we’re not as busy as you.
3. When we ask you to complete a task, please don’t let us know when you’ve completed it – let us chase you, we love being kept on our toes.
4. Keep drumming it into us that no one uses Windows or Internet Explorer anymore. Despite the analytics saying different, if you keep saying it, preferably with a sneer, then one day we’ll realise we’re wrong and thank you.
5. Don’t waste time reading our detailed functional specifications, scan read it and get the general idea of the features, then just get coding as soon as possible – neither the client nor us will mind.
6. Try not to open your work e-mail client more than once a day. Our e-mails to you are rarely important. But so you can stay on top of your industry, please keep your personal e-mail , Tweetdeck and IM client open at all times – you never know when that game changing Tweet will be published.
7. Please do not spend twenty minutes setting up any rules in your work e-mail client. Having an Inbox with 3000 auto-generated messages from 40 applications has efficiency value that we just don’t want to admit.
8. When finishing off a feature don’t waste time testing it thoroughly, that’s what we’re here for and we rely on to fill our days.
9. When it comes to the boring part of a web project like content entry or browser testing, make sure to lower the quality level of your work – it highlights to us that you’re above it and that we should hire a junior to do this kind of work.
10. No matter what, never ever test a website or web application on staging or production servers after deploying – if it worked on your local development environment it will definitely work on staging and production with no issues.
11. If asked to make a change halfway through development of a template or feature, always assume this is due to Web Project Manager incompetence rather than client-lead.
12. Keep pushing to go ‘lean’ and ‘agile’. Web Project Managers are old fashioned and always want to plan in detail despite the fact it’s incredibly boring and has no value. The real secret is to just start coding and see how it goes from there.
13. If you find yourself with nothing to do, don’t come and tell us. Instead make use of the time by watching a few videos on YouTube or reading that blog you like so much.
14. To help us keep our feet on the floor, please look at us with disgust and complain to someone on your table that we are useless because we don’t know web development like you – we know we really should be experts in all digital fields and are simply too lazy to learn.
15. When we give you more work please take the time to look horrified. Web Project Managers often get so far up the senior management’s asses they start to believe it’s more work that keeps us all in jobs.
16. When at lunch in the office and you’re sitting on a beanbag playing Xbox, don’t forget to mention how much better it probably is to work at another place where you don’t have to put up with the hardships you do at your current place.
17. Never give up stating how constant interruptions break your flow. The trouble with Web Project Managers is they just don’t realise that it depends on what kind of interruption it is. Work-based interruptions from managers are disruptive, Twitter disruptions are not – it’s obvious when you think about it.
18. When replying to e-mails that a Web Project Manager has CCd two other people on, don’t hit Reply All. This is tantamount to you being in a meeting and is a waste of your time.
19. Absolutely never agree to “just code it dirty”. You know as well as I do that all Web Project Managers care about is their precious schedule and budget, and if they’re asking you to bypass best practice it’s probably for no other reason than because they don’t care about standards and isn’t a commercial decision.
20. When anything goes wrong on a project, always blame the Web Project Manager just like Sir Alan does – this earns you big respect points amongst your peers.

As I said, my next few articles are all about defending you guys, so go easy on me :) actually don’t, blast me to hell and back in the comments, it’ll be fun.

You sign contracts and NDAs, and it’s time to actually get to work kicking off the project… the first question comes “When can I see some designs?”

To which many a Web Project Manager out there will reply “In a week” – I believe this is a big mistake.

I’ve experienced this approach, and taken my own enough times to back this belief up, let me explain…

The Speculative Work Trend

Before we get onto why I think providing mock-ups too early is a mistake we’ll deal with something some of you may object to right from the off – speculative web design work at the pitch stage.

There is a strong feeling amongst the web elite that providing visual mock-ups as part of the sales process is wrong for many reasons. Back in 2009 Ryan Taylor wrote a very concise article called Why Speculative Design is Wrong listing reasons like:

• It costs everybody money
• It’s about selling not delivering
• It’s wasteful
• It’s uninformed
• It ignores the collaborative nature of design

I happen to agree with every single word of this post and there have been focussed attempts to champion this approach in the industry, by the likes of NO!!SPEC, in the hope it slowly but surely changes our industry’s attitudes about providing this ‘free’ and misguided work and ultimately eradicates it from the prospective client’s expected sales process.

However, back then, as much as now, I couldn’t help feeling that this would be a hard nut to crack for the very fact that it relies on three things:

1. Enough web agencies and freelancers get on-board and refuse to do speculative work
2. Those same agencies and people have a solid enough portfolio that they can rely on as sales aid
3. They’re skilled enough in sales and client management to sell the ‘no spec’ position and still win the work

I would love this shift to take place and never have to do any speculative design work again, but my gut feeling is this just will never happen on a permanent basis.

Unfortunately some things will never go away

Image source

The fact of the matter is I believe it really is only established web agencies and freelancers who can pull this off and the majority of lesser known people out there will always submit to the request for mock-ups and see it, as do most clients, as an integral part of the web sales process.

But while I don’t believe this tradition will change anytime soon, I do believe many agencies then make their first crucial mistake – and it isn’t producing speculative designs, but beginning the web project based on the speculative designs that helped them win the work in the first place.

The First Mistake

I understand it because I learnt the hard way, but some people don’t seem to learn. Three of the reasons Ryan Taylor states as a reason to not do speculative work are actually the exact same reasons why using a pitch design is precisely the wrong thing to base the final design solution off – in fact the “It’s wasteful” reason IS often the result of following this path.

What was the point of producing a piece of design only to discard it? Because ultimately you (the client) are paying for the design it is absurd that you would then choose not to use it.
Ryan Taylor, Why Speculative Design is Wrong

However this statement was made on the assumption that all those who produce speculative designs throw them away upon commencement of the web project, well unfortunately they don’t.

Many out there seem to think it’s best to keep the designs in place for one main reason – if the client loved the designs; it must be what they want. Well maybe yes, but it’s important to identify what the client liked about it before proceeding to base the rest of the web project on it.

All too often it will transpire that the functionality implied by those very early designs, based on probably only 3-4 hours of communication with the client, will actually be built without nearly enough thought given to if they really need it.

What you’ll usually find is the client actually loved the style and colours used in the speculative designs – the final design and functionality should not be set in concrete at this stage.

The Second Mistake

The second mistake often made is to start a won web project by briefing your designer to create a homepage and perhaps some sub-page designs for client approval – no no no!

Yes, this is me, and yes I’m designing far to early

Why not? Well because at this early stage of the project you still have an awful lot of research to do in order to clarify exactly what the best solution is, from a design and functional perspective, so how can you really expect to produce designs that satisfy the user requirements and ensure that the business goals are aligned with the agreed functionality when they haven’t all been completely agreed yet? Quite simply, you can’t.

Good design comes from being well informed. The designer needs to understand business objectives, success criteria, brand personality, competition and numerous other factors in order to provide the right solution.
Ryan Taylor, Why Speculative Design is Wrong

What invariably happens next when adopting this approach is what I believe to be one of the biggest causes of budget overrun in web projects – the designs will be ‘signed-off’, the functionality will then be agreed and defined, and then come the budget and time sapping design revisions that bring those early homepage and sub-pages in-line with what will actually be built.

Don’t rush straight into solution design and build before you’ve done the groundwork. Take time to create a good plan, gather customer requirements, and create solid functional and technical specifications.
Duncan Haughey, PMP: Six Cliches That Make You a Better Project Manager

Why not just skip these unnecessary revisions altogether with some confident web project and client management skills!

The Alternative Approach Bombshell

My approach is to win the web project and then definitely not agree to produce a single design for quite a while.

Web PMs often have to be stubborn for a project’s sake

Image source

Now I know what you’re thinking “Haha you naive fool Mr. Barnes, none of my clients would accept your ridiculous approach, they will insist on designs early and throw a complete hissy fit if I don’t do this for them!”

Well yes, in my experience most clients will not expect this approach easily but that’s when the confidence in the approach must show itself in the form of articulate explanation as to why you follow this approach.

The Alternative Approach

It’s at this point, usually in a kick-off meeting, I will explain to the client how the web project will be managed, what phases are involved, in what order they’ll occur and why, and it goes something like this:

1. I will take the budget and deadline and cast them in concrete (for now)
2. We’ll then talk, and talk for quite a bit and as we’re no longer in sales mode our conversation will almost certainly be more valuable. In these talks I will discuss your business goals and then cross match them against the functionality laid out in the proposal, crossing some off (with your complete approval and buy in) that actually don’t align with any of your goals and keeping those that do
3. We’ll then explore those that do in more depth and also discuss other functionality that may not have been in the proposal that would help you achieve your goals, to the point where I can visualise what your requirements are from a design and functional perspective, and have a pretty good idea of how the functionality will work, both in front of and behind the scenes
4. I’ll then vanish into my web project management Batcave and create an initial project breakdown that lists all the things we’ll need to complete and my estimated hours and hope and pray the total matches the agreed budget
5. If the numbers match, I’ll walk you through this list and explain that this is the first step to confirming what exactly we’re going to build and deliver and eventually you’ll approve this initial list
6. Then we produce a sitemap and functional specification for sign-off

I truly love your project approach Mr. Web Project Manager m’kay

Image source

At this point the client may protest and insist on designs much earlier as they “need to know what it will look like” or the “board of Directors want designs” – this is when you start the explanation for wanting to take this ‘crazy’ approach.

Convincing Clients on the Approach

Now this is a debate you may win or lose. Losing means the client listens to your point of view and then says they don’t care, they must have designs first – but winning means you have not only almost certainly and immediately stopped precious web project hours being spent on design revisions, but you’ve also gained the client’s trust and respect – both the most valuable digital account and web project management commodities.

The actual explanation itself is nothing short of a crash course for the client in web design and functional separation. During the crash course you need to communicate five key points:

1. Achieving the business goals are the primary aim of the web project
2. The pages that need to be included to meet these goals can be decided independently of what they look like
3. The functionality (what the website or application must be able to do) is completely irrelevant to any design that will essentially be overlaid on top of the moving parts
4. By the mere fact the client has hired you means they’ve seen, and liked, the agency’s creative and UX capabilities and need to trust that the same quality level will be applied at the right time
5. When designs are eventually produced and presented they will be perfectly aligned with the required functionality, sitemap and business goals and thus reduce web project hours required and minimise budget overrun and thus more money needed

I won’t lie to you, most of the time this conversation is not easy and the client will challenge you at certain points, but the real secret lies in your ability to convey absolute conviction in your approach and if possible back it up with examples of previous web projects where the process was, and was not followed.

Web Project Managers must be able to control clients

Image source

For example you could show the client some previous speculative design work, followed by the first set of post-sale designs produced too early, then all subsequent revisions right up until the final version – and then show the amount of hours spent, and duration in work days / weeks, to reach the solution.

This can be followed up quickly by an example where the unorthodox approach was taken and, having used it many times before, I can assure you both the total hours and duration will be comparatively less.

When you start talking in a client’s language about best use of their money and quicker time to market they’ll invariably take a keen interest.

Of course with any web project management approach come challenges and so here are a few tips to help you with this one.

Don’t Be Afraid To Rip Up the Proposal

One thing I’ve learnt over the years is that the sale is the sale, and the project is the project – and both are very different beasts.

A successful sale can spell for project disaster if badly sold

Image source

By this I mean in my early days as a Web Project Manager I used to take a sold web project proposal, with included speculative designs, and pretty much attempt to use those as a statement of work.

As the web project progressed it transpired that some requirements had been misunderstood, were no longer in the same priority and other requirements would emerge – and by the end of the web project, the final solution was often quite far from the outlined solution set out all those months ago – bad times.

Over time I began to view all of the sales documentation as a guide more than a blueprint.

Nowadays, upon receiving all of the sales ‘stuff’ I’ll open talks with the client and define their business goals, target audience, marketing plan and required functionality again. As described earlier in this post, I’ll then create a web project task list with time estimations and see if they match the numbers in the proposal – often they don’t and this is the point at which I’ll start talking to the client about what it would be best to deliver to them for their budget they have.

This may all sound a little odd, and perhaps if the people selling your web projects are amazingly accurate in requirement gathering then you’ll rarely have to go through this step, but in my experience sales documents are pretty high-level and numbers are ‘ball-park’ estimates.

Project budgets in proposals are rarely this detailed

Image source

At the end of the day, when I’m given a web project to manage I consider that it has an initial scope, rough budget and ideal timeline, but that none are final and all are negotiable – and ultimately if I can deliver a solution that the client is happy with, produces commercial return, and my agency can be proud of, then I’ve done my job well and my boss will be happy no matter what he originally sold.

Don’t forget, a happy client is not always one that you delivered a web project for as per the budget and timeline set out in the proposal, but one that is happy with how much they spent on the project and when it was delivered – these numbers and dates are in your control as a Web Project Manager, as is the relationship you form with the client.

I’ve delivered many a web project where it was delivered for twice the cost and weeks or even months later than the original proposal stated, but the client was a very happy person as the process was managed and communicated clearly and the eventual solution was the right one – food for thought.

Ultimately you’re looking for the following client reaction at the end of the web project… is this too much to ask for? I don’t think so.

Collaboration is Key

Moving ahead on a web project without any designs is not easy for some people, but it can also come across as a very waterfall-based approach where the Web Project Manager works in a silo with the client until such times as he or she are ready to hand over to the web designers and developers – but this is most definitely not the correct path.

At all times a Web Project Manager should be working very closely with everyone in their team, in fact failure to do this will always have a negative impact on the web project – no matter what your approach is.

With regards to my own approach, although I will not produce designs for a client until a sitemap and functional specification have been approved, this doesn’t mean I haven’t been talking to the web designers, UX and development teams while producing both – far from it.

Web project collaboration also has unseen benefits

Image source

For example, when writing a functional specification you have to, to some extent, be able to visualise and define certain parts of the website or application that will influence or perhaps even dictate an eventual design or UX factor – but that’s fine – talk though these aspects with the teams, and talk through functionality with developers.

Not only is this collaborative approach getting the key people involved early, which always help to gain buy in and motivate teams, but in most cases a Web Project Manager is not the best person to define any of these things – this is not their expertise.

Part of a Web Project Manager’s expertise however is to get the right people involved at the right time, to utilise the experts in their field and to gently ensure the solutions provided by the experts are within the web project boundaries such as budget, scope and timeline.

This Works For Me, What Works For You?

So this approach works for me, and works well, but as always in web project management different people have different approaches – so tell me

How do you manage the design phase to be as streamlined as possible?

So here’s a little (well, a lot) more on why they work, what should be in them and a few tips on producing them.

Why a Weekly Web Project Report?

Well first of all it should be said that a web project report does not necessarily have to be compiled and sent to the client on a weekly basis, however I believe this only applies to large projects with big budgets that are spanning over more than six months, but even then the web project report should be sent out once every other week at least!

But let’s assume we’re all talking about your bog standard website or web application project (if there is such a thing), isn’t sending a weekly web project a little too over the top?

Well quite frankly, no.

I’ve lost count of the number of times this approach has made certain conversations with clients infinitely easier, which I’ll explain below, but there are other beneficial reasons too.

Conveys Professionalism

When it comes to web industry (or any industry for that matter) there are varying quality levels amongst us suppliers, some great and some absolute cowboys – a key part of maturing as a business is to make clients feel looked after to the point where they give you repeat business and referrals to others.

I’ll build you a website pilgrim

Image source

Achieving these key points come from a multitude of factors but consistently coming across as professional when it comes to web project management is one of the most important.

You can deliver the most amazing looking or functionally cutting edge product to your client, but if the road to that delivery leaves the client feeling anything less than 100% confident in your approach to business in general, they could very well think twice before giving you more work or staking their reputation with peers by recommending you.

You’d be surprised how organised ‘paperwork’ (or lack thereof) can influence a client’s impression of you – weekly web project reports contribute to that professional approach that is not only beneficial for you but also your agency.

Internal Web Project Status Communication

As you’re going to all that trouble of compiling this ‘easy to digest’ web project report, why not send it to your boss and project team also. By all rights it will contain exactly the information both of them should be interested in and you need to keep them regularly updated on.

Use your red stapler for multi-paged web project reports

Image source

Highlights Issues

For anyone involved in running web projects you know that on a daily basis any number of issues can rear their ugly head no matter how well it was planned. The weekly web project report can highlight these issues and instigate the conversations that need to happen in order to find a solution.

One benefit of this approach is that all issues are collected and communicated at one time rather than via several conversations at different times and by different means. This is often a more efficient way of dealing with issues and has the added bonus of acting as a high-level ‘in writing’ web project issue log that both you and the client can be held accountable for.

Web Project Schedule Visibility

It should go without saying why everyone involved in a web project would want a regularly updated understanding of if it’s ahead, on or behind schedule and why. But all too often I see one or two project schedules created (as I described in Part 3 of my Pragmatic Web Project Planning series), in the proposal and for the kick-off meeting, and that’s it for a while – this is a mistake.

What often happens next is milestones are dated, the work begins and the schedule is not communicated again to the client until the first milestone is approaching, which could be weeks from the start of the project – and as we all know, a lot can happen in web projects on a daily basis, let alone weeks.

Selling a project is only the first part of a successful project

Image source

There are clear benefits to providing a weekly schedule update for agency and client alike.

For both parties it provides the obvious view into the status of the project’s progress and allows decisions to be made on a regular basis that allows for the smoothest path to completion, including needing to secure more resource or de-prioritise requirements to stay on track.

But crucially for the agency and client, a weekly update will aid any conversations that need to be had with regards to schedule revisions, as opposed to ringing the client weeks after starting and trying to explain why you need an extension to a particular phase or task.

As with web project budgets discussed below, if a client is updated on a weekly basis, any changes to the initial project schedule are far easier to sell if they’ve been fully aware of the road that led to this request.

Web Project Budget Visibility

The web project budget update again is pretty self-explanatory and project management 101, but the real benefit of providing regular budget updates is best seen when, like with schedule, budget revisions are needed.

Again, you’ll find it far easier to negotiate additional funding if the client has received a weekly update on budget and was always kept informed of any phases or tasks that were potentially running over, and why – as opposed to if you get to 90% of your design budget after allowing more changes than you wanted and then suddenly drop the “we need more money” line.

Clients have a subtle way of showing their anger

Image source

With web project schedules and budgets, the key thing to understand is at the start of a project they should both be thought of as ‘initial’ and that only at the end of the project will you know the actual!

Its how you navigate to those ‘actual’ numbers, how happy the client is at the end and how effective your solution has been that really are the true measures of a successful web project.

I’ve witnessed web projects where the solution was delivered a week or two late and only a little over budget, but where the client was left feeling thoroughly in the dark and unloved and thus it felt like a failed project.

However I’ve also seen instances where timelines overran by months and budgets doubled, but because the client had been kept well in the loop and understood along the way why these situations had happened, they were happy bunnies by the end and this was a successful project.

Actions Encourage Momentum and Accountability

Part of the weekly web project report should be actions. This part will list actions for both agency and client, at a high-level, which were completed in the previous week, and actions for both parties to be completed in the following week.

The reason for including actions is simply for web project momentum and accountability.

By this I mean that although a web project schedule may have been produced that has a zillion tasks on it, many clients will be busy with other work and a short list of ‘things they need to do this week’ can be a handy tool for them.

As well as a makeshift to do list, these action lists can also serve as conversations linked to the web project schedule, for example, if in one weekly report a client has an action to deliver content to you and fails to do so and you know this affects the schedule, you can point to specific un-completed actions as causes for slips – again, this transparency and communication helps you out too!

Forces Good Web Project Management Practice

As busy chainsaw juggling Web Project Managers, one of our constant challenges is sticking to processes when time is short. At times like this it’s all too easy to cut corners and the weekly report is understandably one of the first things deemed as not critical.

Some Web Project Managers like to exaggerate

Image source

However discipline is something that separates average web project managers from great ones.

Not only will the weekly report prove its weight in gold when things don’t go to plan, it also forces the web project manager to keep an eye on every project they’re running and trust me, to effectively stay on top of the multitude of projects you’re likely to have on at any one time you really have to be aware of the most minute detail on a regular basis.

The weekly report forces you to catch up with everyone and analyse the numbers when without you may take the “I’ll review it next week” approach and then one week becomes two – and then the earth falls in on itself and suddenly you’ve lost control of the project.

…and if you don’t believe it’s possible to lose control of a web project a little bit by taking your eye off the ball just for a week or two, you’re sorely mistaken!

Weekly Web Project Status Report Contents

From the previous section it should be somewhat clear as to what should be included in a weekly web project report, but below is an example list of contents.

• Client, web project name, date range the report covers
• Actions completed last week
• Actions to be completed this week
• Web project schedule update
• Web project budget update
  • Complete budget and broken budget down by phase
• Questions, comments

Remember, these reports can be delivered in any format you feel is appropriate – some like to use a slide deck or PDF template, but you may find a message template on Basecamp or e-mail template work just as well.

Dilbert would make a great Web Project Manager

Image source

As long as the format remains consistent and clear you’re all good to go!

Producing Weekly Web Project Reports

There are many reasons why keeping disciplined enough to produce weekly web project status reports can be a complete ball ache and so below are a few tips that may help you.

You Don’t Have to Create the Report Yourself

Many Web Project Managers have executives or support staff, use them. You setup the template, you create and send the first three or four, but after that there is no reason why a competent executive couldn’t be the ones to dig out the data for you leaving you to adjust schedules, polish up and send on.

Adapt Per Client

All clients are different and as with web project management approaches, they’ll all react differently to methods of communication and you have to adapt accordingly.

While the fundamentals of the weekly report shouldn’t be changed too much, the way it’s written and delivered should match what you feel the client will be most responsive too. For example, if your client isn’t a ‘details person’ avoid lengthy reports, or if they’re not technical at all, make sure to not include technical web jargon as much as possible.

Sexual PM tips from Dan

Dan Storbaek on Twitter

Adaptation also extends to how you deliver the report, some clients will be happy to just receive it in an e-mail with a short summary, whereas others respond better to the report and quick call to go through it.

Personally I’ll call the client for the first few and then just send through thereafter, unless there are specific elements I’d like to talk to them about.

The important thing is that the client doesn’t see the e-mail arrive in their Inbox, or meeting request reminder pop-up and groan, but instead feel like they’re receiving a professional service and the information included is important.

Don’t Drop Bombshells in Reports

Although weekly web project reports are the place to capture vital things such as project and budget updates, make sure you don’t let the client find out these facts from the report alone. If any time I feel the total, or phase budget is at risk of overrun, or the schedule is slipping and needs revision, I’ll speak to the client when I realise and not surprise them in the report.

Summary

Producing and sending weekly web project status reports to clients seems like an obvious one, and something many of us start out doing at the beginning of a web project, but as the workload builds up and other projects on your plate are starting or ending, it can often fall by the wayside. This might not seem to be a problem in the short term, but it will become one the minute something doesn’t go according to plan.

From the very beginning it’s important to remain disciplined and send your client a report every week. In this report you should highlight key information such as actions completed, actions to do, schedule and budget updates.

Web project management, discipline is the name of the game

Image source

It may seem over the top to do this the week after the web project starts, as very little has changed from the initial plan; but as the web project progresses and things inevitably slip, because there has been an on-going weekly summary it’s in no way a surprise to the client and makes negotiating additional time or budget a lot less painful.

Too often I see people running web projects that don’t send weekly reports with it invariably ending up the same way – the project slipping in various places, small places, but building into significant schedule and budget problems over time. Then, after a few months, the client suddenly asks “Are we on track for go-live?” or “Are we on budget?”

This is when the shit hits the web project fan as the client, quite rightly, says “I assumed all was OK as you hadn’t mentioned anything before!”

Not only do you have to fumble your way through an awkward phone call or meeting but you’ve put yourself in a weak position and damage has been done to your relationship with the client and their level of trust in you – bad times, and all because you weren’t disciplined and clear from day one.

Send those weekly reports from week one, to the end…

Awwwwww, look at cuddly lil Jabba

Image source

Ok now that confession is out of the way, I’d also like to let you know how using a digital voice recorder in web project management meetings has proved invaluable time and time again for me when compared to old skool method of note taking with pen and paper.

The Problem with Note Taking

Don’t get me wrong, when it comes to being a Web Project Manager I never go anywhere without my notepad and pen, despite it being a cheap notepad and having never actually owned a pen like a proper grown up.

However there are just some web project management meetings where I get back to the office, look at my notes and realise they no longer make sense as they did in the meeting, but look like a cross between that guy’s tattoos in Prison Break and the scribbles on the wall of a mental case who didn’t leave his room for twenty years before being separated from society.

The web project management meetings I’m talking about are the long ones where you’re required to understand your client’s entire business model, current technical and business workflows and rules, design brief and the oodles of new requirements they have – and all in the space of one or two hours.

Now perhaps I’m just useless at note taking, but the fact is I just can’t remember all that information word for word and got a little scared when I had that inevitable moment we all have from time to time where your eyes glaze over, you see people talking, you nod profusely, but you’re literally hearing nothing.

It was moments like this that resulted in me buying a digital voice recorder – ladies and gentleman, I present to you Excalibur!

Behold Excalibur – she’s beautiful… innit

The Digital Voice Recorder Solution

Due to my note taking being not great, the primary reason I use a digital voice recorder in detailed web project management meetings is because I want to focus 100% on the meeting and I’m not senior enough to have a PA.

In all seriousness, when I’m talking to a client about their business, project and requirements I genuinely want to immerse myself into the process and really get down and dirty in the details, for two main reasons:

1. I know off the back of the meeting I will have to probably create a sitemap, functional specification and creative brief and I will need to get the details right
2. I want the meeting to flow smoothly and be an organic conversation. I find this type of meeting to be brilliantly productive and invariably ends up with both parties getting excited about the web project

Once the meeting is over, I press ‘Stop’ and head on back to the office. I know all that detailed goodness is captured and will be there for me when I need to sit down and write some documents or brief the team – in fact, the team can also listen to the meeting themselves – double efficiency bonus points!

I won’t drone on much more about the why, needless to say the number of times I’ve sat with headphones writing a big functional specification and literally enjoyed capturing a complex piece of functionality perfectly, first time – high bloody five!

Alternative Recording Solutions

Of course nowadays digital voice recorders look a little archaic and alternative solutions are available for all you smartphone and tablet people.

Clever iOS note taking apps are

Translated using the Yoda Speak Generator

These range from simple voice recorders to awesome apps that let you record a meeting, type notes, draw diagrams, and even highlight the notes and drawings you made in sync with the playback. A few decent ones for the iPad are:

• Audionote
• Noteability

However, I did try using these and personally found it a little more cumbersome than pen and paper and also made me come across slightly detached from the client, like typing away on a laptop does – but maybe this type of solution will work for you.

Navigating the Excalibur Unveiling

Although the theory and practice of recording web project meetings is solid, it’s still a little bit of a taboo when you mention the idea to a client, and to be honest I’m not surprised – it’s not exactly standard practice and there are confidentiality concerns.

But I find, as always with clients, honesty is the best policy and by simply explaining that you want to concentrate 100% on the meeting itself and not note taking, and that it will ensure you capture all the fine detail and enable more efficient briefing and web project documents, you’ll generally get agreement.

In fact clients tend to fall into three camps when they see Excalibur, the:

1. Happy and understanding type who say “Ooo good idea!”
2. Tentative but accommodating type who say something along the lines of “Ok, but I won’t see this posted on YouTube will I?” while laughing nervously
3. Very freaked out type who simply say they do not want to be recorded

The first two types of clients end up not thinking about the recorder 30 seconds into the meeting, and the third type, if you’re smart, you’ll identify before even being silly enough to get the recorder out.

Sometimes, recording is just a bad idea

Image source

But in case you’re not too smart (like me, trust me I learnt the hard way) here’s a few handy tips on when to suggest recording and when not too.

The Dos and Don’ts of Recording

Do

• Be completely honest about the fact you’d like to record the meeting, even if it’s a conference call
• Make the point to mention you will be discreet with the recording
• Name your recordings semantically so you don’t have to trawl through “untitled.mp3″ only to find out it wasn’t the meeting you needed after all
• Use your instinct to determine if it would feel appropriate to get the recorder out

Don’t

• Try to record pre-sales meetings and conflict resolution meetings
• Record meetings where it isn’t necessary e.g. budget discussions
• Ever use recordings to try and settle web project disputes
• Send recordings to non-employees
• Covertly record, ever – it’s just plain wrong and illegal I think

But come on, I’m probably just a bit rubbish when it comes to note taking, and because it’s just not always appropriate to record web project management meetings…

…what are your tips for note taking in web project management meetings?

This article continues the series and talks about more things Web Project Managers want more than money; things that would keep our sensitive egocentric control freak selves happy :-)

Heed the Web Project Managers motto

Image source

4. Reliable support staff

As a Web Project Manager you simply do not have the time to perform every task yourself during the lifecycle of a web project, this is when support staff can seem like a gift from the Gods, but there is a massive difference between support staff and reliable support staff.

This kind of person is actually rare to find, but if you’re lucky enough to find one they can provide you with the vital breathing space you need in order to keep on top of all your web projects.

In short, a reliable web project management support member is one who you can delegate tasks too safe in the knowledge they will be completed, and to a quality level you are happy with – sounds simple, right?

Noooooo, how many times have you had to chase someone on a tasks several times, only to find that when it’s eventually finished it’s of poor quality and you mutter the immortal words under your breath “I should’ve done it my bloody self!”

“WTF, I asked you to gather content from the client an hour ago!”

Image source

Don’t just expect support, provide it too

Of course, finding reliable web project management support is gold dust and most Web Project Managers would take this over any financial bribe, but I believe it is crucial to not only use the support you have, but to also provide reliable support too!

Offering your support to other stressed and overworked Web Project Managers (and any team members for that matter) is vitally important because it:

1. Encourages others to support you, and each other
2. Shows humility in that you don’t think you’re ‘above’ web project management support tasks
3. Keeps you humble by reminding you what it’s like on the other side of things

Just remember one thing… the golden rule of delegating tasks to others, is to always be on hand to support them while they’re completing them. There’s nothing worse than dumping a load of work on someone and not being around to answer questions or provide encouragement.

Always fully appreciate a person that can provide reliable web project management support, they’re often are the unsung heroes of digital agencies!

Special thank you: This is an apt point to thank my bestest pal in the world, Deb, for all the support she gives me on this blog by way of superhuman proof reading skills, thank you!!! :-)

5. Understanding production teams

Effectively managing digital production teams of web designers and web developers is one of the black arts of web project management. If you get a great production team on a web project it will invariably be a resounding success, but if you encounter difficult production teams, then get ready for the pain!

But before I get into the kind of digital production team a Web Project Manager wants more than money, it’s important to understand things from their perspective, and never has it been summarised better than in the quote below… a short must read for any Web Project Manager.

“Developers often treat PM as The Source of All Evil. And to some point they’re right. It’s a project manager who brings more work. It’s a project manager who bugs everyone asking when they’re going to be done.”
Pawel Brodzinski, What Can Project Manager Do For Developers?

Having worked for a few years as a front-end developer, and been ‘affectionately’ referred to as a Code Monkey I can definitely remember and understand what it’s like on the production side of a web agency.

But it’s funny how life has a way of holding a mirror up to your past behaviour as time goes by…

As people who know me will testify to, when I hear digital production teams commenting about how web projects are being run, how standards are the most important thing and that more budget is needed for proper testing, I’ll often have a little ‘old wise man giggle’ to myself and think back to the time I was saying (shouting) exactly the same things to previous bosses when on the digital production team.

But of course, once you cross over to the dark side of web project management everything changes.

Web Project Management, a new reality

When you transfer from the digital production side of things and become a Web Project Manager your whole world is changed forever. Even if at some stage you decide to venture back into production, you will be doing so with new commercial knowledge about the realities of running web projects and in some cases businesses themselves.

Suddenly your priority balance shifts slightly away from code standards and is weighted more towards clients, budgets and schedules. Rather than having one or two things to work on at a time for solid periods, you have a million things to deal with and numerous key decisions to make on a daily, and sometimes even hourly, basis.

As a Web Project Manager you are constantly being pulled in three directions by the client, your boss and your production team, and each of them want different things from you at all times – somehow you have to find a way to keep everyone reasonably happy at all times – this is where a Web Project Manager would sacrifice any pay rise in the world to have an understanding production team ploughing through the work!

This means that when you’re pulling a developer off the work they’re on, breaking their flow, to fix a bug raised by a client, or you ask a designer to stick to a certain level of design so you can hit budget and schedule, the dream is to have production team members who fully appreciate the pressure you’re under and happily oblige.

In most cases Web Project Managers completely understand the production team’s point of view and try to accommodate it where possible. We’ll try and organise their work into solid blocks, create task lists and test their work, but all these things have to be combined with our new pressure filled priorities, and sometimes it’s a bad mix.

The devs didn’t react how the Web PM had hoped to the decision

Image source

More than anything, Web Project Managers out there would just like a certain amount of understanding of this fact from production teams. For them to appreciate that as well as having pressures like cash flow, budgets, schedules and clients on their mind, they’re also are the one person who has the complete overview of the web project at all times and are making decisions based on that overview knowledge that’s ultimately best for the business and project.

Sometimes these decisions can appear stupid, rash, akin to demanding low quality work, short sighted or naive, and in some cases they are! But as I’ve learnt over time, if a Web Project Manager seems to be a reasonably intelligent person who understands what the production teams are saying, the decision they make is probably the right one for the web project or agency overall, and if the production team continues to have a job and steady flow of web projects to work on, you can be sure the decisions made weren’t too bad at all.

To all digital production teams out there, I’m pretty confident if you could spend just six months as a Web Project Manager your perspective of things would change too. You would find that when you’re pulled in lots of different directions on lots of different web projects you’re sometimes just too busy to provide the perfect brief, create all tasks as nice lists, insist on world-class quality code every time and have time to create accurate detailed functional specifications that leave not a single detail in the land of un-scoped or ambiguity…

How do I know this? Because I really was once one of you, fighting for all things good and right in the world!!

All we ask is you trust us. Our hearts are in the right place, we want the same things as you, but our priorities are weighted differently to yours. Surely there’s some happy place in the middle we can meet, and over time get to that place together by keeping our business healthy, steadily growing and profitable through a utopian mix of design masterpieces, technical wizardry and commercial realities…

The real Web Project Manager reality

In the last two articles I’ve given just a few of the things Web Project Managers want more than money, but there are many more. However, the painful truth is getting all of these things is extremely unlikely and a little la la land given the real commercial world we live in.

But, by being able to identify what these things are is the first step on the path to improving how you run web projects, how to interact and conduct yourself with your team members and superiors, and if you can improve things even slightly in all those areas, you’ll be well on your way to being a happier Web Project Manager!

But enough from me… as someone managing digital accounts or projects, what things do YOU want more than money in your web project management job?

Related reading:

• Five Things Web Project Managers Want More Than Money: Part 1 »

Read on to find out what would go a long way to making Web Project Managers out there a little less Mr. Grumpy Gills…

Note: If you’ve never watched Finding Nemo please do so!

Note to bossman: If you’re reading this, it’s not a whinge, see #3 ;-)

1. A solid pre-sales process

So a brand new web project is heading your way, it sounds awesome; you’re excited and can’t wait to get your teeth into it. You begin to the review all of the pre-sales documentation with the intention of beginning to plan the web project.

As you start to break down the project into tasks and allocate time, your web project management instinct and experience kicks in as the horrid reality dawns on you that the deliverables are ambiguous and what’s been sold looks unrealistic for the time and budget, and at this finite moment in time, you’re the only one that realises it – you bow your head and weep like a little girl.

Web Project Managers are masters at subtle body language

Image source

Inheriting a web project with these kinds of issues puts the Web Project Manager in a very tricky situation from the start where one of the first actions is to start to push the client back on things and re-define project scope. This immediately affects how the client feels about you and makes trust that much harder to gain – trust from a client being one of the most important factors in web project success and is always formed most strongly at the beginning of a business relationship.

When I hear of this situation arising it reminds me of an article by Rob Borley called Under Sell and Over Deliver. The article title pretty much says it all and I’m sure it’s the dream of all the Web Project Managers out there, much more so than a pay rise.

Have a whinge, then try to fix the problem

However, if you’re finding yourself in this position more and more, rather than bitch and moan (well, at least after bitching and moaning) I would suggest you try doing something to help resolve the situation, for example:

1. Speak to the people selling web projects and explain what the problem is and the position it puts you and the agency in
2. Try to get involved in the pre-sales process so you can identify potential issues early on
3. Track all project actual vs. actual times so you can give average percentages for project phases (handy when sales people know the budget they have to work with)
4. Involve the sales people in parts of projects so they can understand what they’re selling a little more
5. Have a major hissy fit at whoever sold the project until they burst into tears

Too often do I hear of people complaining about elements of their job yet they consistently choose to do nothing constructive to try and resolve the situation – to me this is just gutless whining and I have no time for it.

If you have a problem, raise it with the relevant people in a professional manner and try to suggest solutions, in most cases the recipient will be understanding and take your comments on board for next time – and if they don’t, proceed to Step 5.

2. Adequate time to manage projects

Web project management takes time and there is nothing worse than being forced to manage web projects without enough time to perform even the basic project management necessities e.g. regular monitoring of budgets, schedules and tasks all the way through the lifecycle – but, how much time should a web project manager need per project? 10%, 15%, 20% of the project?

How much time a web project manager needs is very much a ‘how long is a piece of string’ question given how different web projects can be, some are simple and take little time, some are little but have a difficult client and thus take a long time, and others are tantamount to delivering the Death Star project before the Ewoks have a chance to help destroy it.

Wicket PMP dealt with people questioning his time in his own way

Image source

I read a blog post a while back (but typically can’t find it now) that stated because there is no way to determine how much time should be spent managing web projects, the only real way to know is to analyse your own time and if you’re finding you don’t have enough time to do the following on a daily basis then you are not being given enough time to effectively manage web projects:

• Review all budgets
• Review all progress against schedules
• Redefine all tasks completed and left outstanding
• Revise all budgets and schedules accordingly
• Update the client

A common cause for project management overload isn’t in fact that you have too many projects on the go, but you have too many at a similar phase at the same time. As Brad Egeland puts it…

Having your project life cycles staggered is definitely one key to sanity and greatly increases your chances of success. One cannot sanely go through life managing 5 projects that are at the same point in their project life cycles at the same time. The demands on the project manager vary by phase.
Brad Egeland, Managing Multiple Projects – Stagger the Lifecycles

However, it could be argued that you’re not finding the time to do these things because you’re working inefficiently, but if you know you’re a competent web project manager and have the trust of your boss, this workload analysis holds true and you should raise it with them and hope for understanding and support.

If you don’t raise it as soon as you feel you’re not getting enough time to manage a web project, the likelihood is that you will probably lose control of the project and the risk of it being over budget, late or of low quality is increased significantly. It will often also result in you getting a smacked bum when perhaps it isn’t fully deserved, and that sucks donkey balls.

A happy web project manager is one that feels they have enough time to manage all the projects on their list in the right way. As with web designers and developers, if we have enough time to do our jobs properly we feel more confident of delivering high quality projects and that’s what makes us happy much more than money.

3. Trust from your boss

Trust is important to every Web Project Manager out there and is a key component in web project management. Trust from your client and your production team, or lack of, can seriously affect the result of any web project.

I talked about how to gain trust from all of the above in a previous article called Web Project Management: Honesty, Trust & Integrity and it mainly revolves around conducting yourself at all time in a manner that is clearly seen as being full of honesty and integrity no matter what temptations arise.

But, to a Web Project Manager, more valuable than any salary is having the trust of your superiors, because as we all know, when managing a web project you are the person right on the front line at all times, making critical decisions on a daily basis and are ultimately responsible for success or failure, and when this depends on more internal and external factors than you can shake a stick at, well… this is a very precarious position to be in!

I mean let’s face it, when things go well you look like a superhero, a master of your trade and an example to everyone, but, when things don’t go so well, oh my, that is when any Web Project Manager needs, and needs to see, absolute trust from their boss and for him or her not to go all Alan Sugar on them.

Sometimes you wish you’d just stuck to coding

Image source

When your boss hears a web project is coming in over budget or late and you know for certain why, and that the reasons are mostly due to factors outside of your control, for them to listen to your reasons and say “I don’t think you did anything that wrong, web projects contain too many elements for you to be in full control of at all times.”, this, my Pedigree Chums, is music to our ears.

Web Project Manager Tip of the Day… Get your boss to read Good Project Management Doesn’t Guarantee Project Success

Of course this reaction is only possible if you have demonstrated in the past that you can effectively control web projects under the right circumstances and if it is a cast iron known fact that you always take full responsibility and admit fault if that happens to be the case, without that honesty and integrity you will never have trust from anyone.

For a Web Project Manager no amount of money in the world is a substitute for feeling trusted.

Related reading:

• Five Things Web Project Managers Want More Than Money: Part 2 »

Just keep swimming, just keep swimming!

I don’t, but how else can you start a Saw movie themed article?

So there I am watching the latest Saw movie (Saw 6), cringing at the gore levels and twisting plot lines when it hit me, the main character affectionately named “Jigsaw” (or John to his friends) is quite frankly an excellent project manager!

From that point on the movie took on a rather different perspective for me and was transformed into taking notes on how to run multiple projects with pin point precision (and kill people in imaginative ways).

In this article I want to discuss what an insane serial killer can teach all of us about managing projects, or has he calls them, games…

A one line synopsis of the Saw movies by a local film critic

Image source

Project kick-off meeting

When starting a new game, or project, Jigsaw always conducts an excellent project kick-off meeting. Although always by video or audio (due to certain legal reasons), he always:

1. Starts with introductions, explaining who he is and who everyone else in the room is
2. States the purpose of the meeting e.g. “I want to play a game”
3. Explains why the projects exists (usually because they’ve been a naughty boy or girl)
4. Communicates the aims and objectives of the project, or in other words, what the goals of the project are and how he intends to achieve the goals
5. Sets out clear timelines for project completion (usually around two minutes before someone’s head explodes, but at least they are fully aware of the timelines – every cloud…)
6. Explains all of the above in a language everyone involved can understand.

By following this set of pointers, a project manager should be able to conduct an effective project kick-off meeting that leaves everyone involved with a clear picture of the road ahead.

Jigsaw always conveys project timelines effectively

However, if you’re reading this John, I would recommend you allow for a little QnA session with people in this kick-off meeting to get other people’s input… just a thought.

Project planning

One of the critical success factors of any project is planning, planning and more planning.

As I’ve mentioned before in my Pragmatic Web Project Planning series, project planning allows the project manager to:

• Define and manage the project scope
• Identify and minimise risks to the project
• Break the allocated project time into manageable phases and tasks
• Determine realistic milestones and client-side deadlines
• Track progress and control the project
• Secure the necessary resource

There is little doubt that Jigsaw was a big project planning fan. His projects had to be so tightly run, without planning he would have definitely been arrested pretty early on, probably in Saw II.

But alas, due to his world-class talent at project planning, scheduling and excellent people skills, giving him the ability to pre-empt most mid-project surprises, he was able to avoid the law and keep his picture on the FBI’s Most Wanted page – hoorah for project planning!

A snippet of a project schedule John kindly sent me

Personally I think Jigsaw would’ve used a Gantt chart as his primary project scheduling tool, as with many projects, more modern project management methodologies such as Agile or Kanban just wouldn’t have been suitable.

Either way, careful inspection of the Saw projects illustrates just how important project planning really is for effective project management, and serial killing.

Project teams are crucial

During the Saw series Jigsaw enlists the help of three people for his project team; some ex-drug addict criminal, his wife and dodgy police officer called Hoffman – we shall refer to them as Team Psycho Nutbags.

Initially in Saw I, Jigsaw manages the project alone with good results, but as he moves onto managing larger projects he realises that he needs support and thus sets about creating his own project team. From this it is clear Jigsaw has learnt a vital lesson, you need a team to get the job done.

Task Delegation and team empowerment

Working as a project manager with a team, Jigsaw demonstrates how delegating key project tasks to team members are a crucial part of managing successful projects.

Many project managers find this a difficult thing to do and usually it’s solely down to trust issues, in that the project manager doesn’t fully trust a team member to complete the task to a good enough standard thus adding risk to the project.

A key lesson Jigsaw has learnt however, is that when you empower team members with a certain level of responsibility they will often exceed your expectations and perform above and beyond.

At first John’s team felt overwhelmed by his unique PM style

If as a project manager you have trust issues with team members and feel uneasy delegating key tasks to them, but at the same time clearly have a packed work schedule building death traps, you could start by delegating lower risk tasks to test the water.

These tasks would ideally be challenging but not soul destroying, or you run the risk of the team member thinking you’re just handing out the boring work you can’t be bothered to do.

When delegating any tasks it’s vitally important to always make it clear you are there for them if they need support.

In my experience, and I’m sure Jigsaw’s, what you tend to find is if you delegate the right tasks to the right people and are there to provide support, over time you will trust the team member more and more, they will feel and appreciate that trust and you will be able to hand over more project critical tasks thus freeing up valuable time for yourself to build those torture machines.

Project team development

Not only does Jigsaw demonstrate a supreme skill set when managing projects, but he also understands the advantages in developing his project team’s skills.

Although forceful, John’s development techniques are effective

Throughout the Saw series, while personally managing multiple projects, Jigsaw is constantly teaching his project team new skills – but why when he has so much killing to do and so little time?

A good project manager will make it part of their remit to teach their team new skills for a variety of reasons:

• It increases the skill set of the individuals and thus helps grow the company
• Team members with new skills can take on more key project tasks
• Team development increases team morale
• Willingness to share knowledge rather than protect it improves company culture

In my experience, those who are willing to take the time to develop their teams are the ones that ultimately have the most success simply because people are more willing to work for someone who is clearly not just looking after themselves.

Game over, project completion

As with all projects, it is important to clearly define the markers that define a project as complete.

All too often I hear of projects that have been run really smoothly, encountered few problems until right near the end when the project manager is beginning to talk about completion and the client suddenly pipes up about how they thought they were going to get more features or services before the end… uh oh.

This situation mostly only arises when a project manager has not clearly defined the deliverables, and scope of deliverables, that will constitute the project as complete.

Jigsaw, an experienced veteran project manager never makes this mistake. As previously mentioned, he always clearly states what the project consists of and the victim is never under any other impression, just perhaps under a slow body crushing device with blades.

What do you mean we only have 15 hours budget left!?

Of course real life project management isn’t as clear cut as Jigsaw’s games (no offence John mate), and often what is stated as the project completion deliverables at the start of a project have changed dramatically by the end, but this is ok, in fact, I would say for larger projects this is completely normal and to be expected.

Many times I’ve been running projects that had several huge shifts mid-lifecycle, for example:

• New functionality requested that is of higher priority than previously in-scope functionality
• One or several phases take far longer to implement than initial estimates allowed for
• Client’s budget or timeline is cut mid-project and an early completion is demanded

In each instance, it was required to re-state the project completion deliverables to the client and the project team so that it was clear to everyone involved where the finishing line was.

Constantly re-establishing the finishing line

Hearing of a project suffering from lack of a clear finishing line at any stage of a project is a subtle way to identify those true practitioners of project management amongst the sea of people just pretending to be project managers… why?

Simply because establishing and re-establishing the finishing line is very easy to do if a project has been run according to project management 101 guidelines.

You can always tell a real project manager from a wannabe

Image source 1
Image source 2

In order to determine project completion deliverables throughout the project you just need to:

1. List the completion deliverables last communicated
2. Gather updates on all deliverables progress
3. Analyse the current budget used and remaining
4. Estimate the remaining tasks in the project against the remaining budget
5. Look at the results, are you looking under budget, on budget or over budget
   1. If under budget, smile and tell the client you’re on track
   2. If on budget, smile and tell the client you’re on track
   3. If over budget, smile and try to explain to the client why, negotiate additional budget or provide them with the de-scoped features or features you proposed are moved to a later phase
6. Once understood, clearly re-state the project completion deliverables and scope in writing and get agreement
7. Wait a period of time and go back to Step 1

Generally, as with most project information, if you have been honest and consistent with the client from day one, they will understand that the initial estimations were a little off and a slight re-adjustment is needed that means neither side lose out.

It tends to only get ugly when the client has received few progress reports, been told everything is great for the whole project and then suddenly has a project manager pushing back on everything spouting “out of scope” and “over budget” phrases – phrases that must feel exactly the same as if the agency was cutting a jigsaw shape from their flesh!

Although don’t forget to always get your agency’s credentials in the website footer, always leave your mark – another great tip from John.

Despite all the bad feeling John’s players must have towards him and his games, if you could stitch all their limbs back together and re-animate them, I doubt a single one of them could whinge that they didn’t know where the finishing line was in their game.

Formal project completion documentation

Assuming you’re an awesome project manager like John Kramer, you will rarely come up against this problem of hazy project completion, and as well as the finishing line always being clear to everyone involved, you’ll also make sure you formally close the project with documentation and a client signature – ahhh, there is little sweeter than when you get the written confirmation that the project is complete and any extra work will require further funding.

Of course you could just try ringing or mailing the client and saying “Game Over”, but I just can’t see this going down to well, unless of course you have fostered a Saw movie theme with your client throughout the project, in which case you’re amazingly cool and so is the client and I want to be both of your friends forever and ever and ever.

Project management 3D glasses

Although this article hasn’t professed any remarkable project management revelations, hopefully you can see past the slightly odd dark association, don your 3D glasses, look past the initial visual layer and appreciate the links and inspiration you can make and take between project management, and general digital work, that you see in everyday life rather than just relying on project management books and blogs.

These everyday associations are brilliantly pointed out in articles and presentations like…

Phil Bennet’s Project Management is like Star Wars article, where he maps things like Han Solo being frozen in Carbonite and The Force to project management.

Adaptive Path’s SWSX 2008 presentation entitle 10 Tips for Managing Creative Environments where Bryan Mason and Sarah Nelson talk about how professional kitchens and orchestras are run as a tight knit team in relation to running a digital team.

Andy Budd’s presentation on UX where he presents analogies of website user experience based on when you first walk into a hotel lobby.

So the next time you watch a movie, order a coffee or arrive at a hotel, be a super nerd and try to recognise how the processes you see could help you in your current role.

ARTICLE OVER!

Related reading:

• Pragmatic Web Project Planning »
• Web Project Management: Honesty Trust and Integrity »

In my latest article published on Smashing Magazine I discuss a few approaches that can help when having to explain to a client they’re wrong.

Stop waffling and take me to the full article!
How to Explain to Clients They’re Wrong »

In the article I talk about first asking yourself if the client is in fact wrong, and if so, how you can talk to them in a language they understand so as to give yourself the best chance possible of making them understand your reasoning.

Voicing my opinions (big mouth) on Smashing Magazine

I also discuss the advantages of establishing yourself as the web expert and highlighting any high-profile clients you’ve worked with, so as to increase your reputation and credibility with the client and thus your recommendations.

Mentioned also is how backing up your recommendations with third-party evidence can sometimes be the edge you need when trying to convince a client to go with your suggestions.

However sometimes a client just simply won’t listen to you and pretty much order you to do what they want. In cases like this the article advises to admit defeat gracefully and professionally, but not to let it necessarily be the end of the debate as there’s always a way to turn to defeat into victory that results in a win / win for both you and the client!

Read the full article: How to Explain to Clients They’re Wrong »

Warning: Controversial post alert

This may make your blood boil, but if it does, please feel free to add a venomous comment or two after reading.

PCs suck! Microsoft suck! Windows sucks! IE sucks!

Oh my, how often do those of us working in the web industry hear this from the community and colleagues? I would take a guess at daily, and they’re all probably right.

Although not a Mac user myself (cool points totally lost I know), I know enough people, whose opinions I respect highly, that say Apple and Macs are far superior in every way to PCs and Windows – I believe them.

I was a front-end developer and have spent days and nights (mostly nights) pulling my hair out, shouting and swearing at bugs in IE from what I know to be solid clean code – from this perspective I know how this browser can at times seem like a demon sent straight from hell to torment us all and make us doubt all that we know to be good.

The post isn’t about IE6 alone, but this made me ‘gigglesnort’

Image source: John Martz

But, as a Web Project Manager your perspective of this whole topic has to shift dramatically because guess what – as much as most who manage, design and build websites loathe to say or admit it…

THE WHOLE WORLD USES WINDOWS AND IE!

Ok, maybe not the whole world, but a bloody lot of people.

The Evidence

Now while I imagine pretty much everyone reading this article will know this to be a fact, I still think it’s important to show the figures to really ram it home, because it seems to me, the more the web industry production teams out there move closer and closer to an all Mac environment, the attitudes to catering for anything Microsoft become more negative, to the point of being damaging to a business commercially through decreased bug fixing competencies / speed and lowering team low-morale.

OS Usage in 2009, with Windows at about 90%

Popular browser usage in 2009 – hmm no Netscape ;-)

Source: W3Schools Browser Information Statistics

This last table says about 40% of people use IE with Firefox now the market leader at 46.6%, huzzah!

But wait, I would hazard a guess that if you take a look at the Operating System and Browser combination analytics for your client’s sites, not your own (unless you only make sites for cool kids only) these aren’t the figures you’ll see.

I’d bet Windows and IE combinations are way ahead of any other – on average the combo splits on client sites tend to lean overwhelmingly towards Windows and IE combos, usually around 70% and upwards of all traffic.

Please, take a look at your client’s analytics and tell me I’m wrong. I’m basing this statement on only stats I can see, which is a lot, but this is one instance where in a way I’d love to be wrong and look like a complete Muppet…

10 Reality Check Facts

Of course I completely understand, and empathise, that by pampering to the makers of IE it can feel like we’re possibly postponing the evolution of the product to what most would consider acceptable standards, but I’d like to point a few things out to web production teams that I believe to be perhaps uncomfortable truths:

1. We primarily design and develop websites for non-web industry people, not cool kids
2. Most clients do not give two hoots about, or even understand, the IE vs. Firefox vs. Safari debate, they just want a site the majority of their users see as the designs they paid for indicated
3. Most clients do not accept progressive enhancement as an acceptable solution when confronted with stats that tell them two thirds of their traffic is from IE
4. Testing and bug fixing in IE is just as much of an important part of a developer’s job as is cracking that awesome innovative piece of new code
5. It’s commercially pointless to be able front-end develop at warp speed for Firefox and Safari if subsequent fixing for IE takes an age due to lack of knowledge, experience or enthusiasm
6. No matter how much you scream, you will still have to fix those IE bugs so why not accept it and see it as an important part of your job rather than a chore – to deliver a solid product for the client and their customers
7. Leaving IE testing right to the end, after creating some really complex CSS and JavaScript, is asking for trouble. Maybe don’t fix till the end, but just have a few quick peeks during development to see just how broken things are so you can adjust your strategy early if need be
8. Saying client’s and their customers “Should use a better browser” is just not an acceptable or constructive response or attitude, despite it being completely true
9. Quality developers want their work to be perfect in all browsers, and despite resenting it, will work tirelessly to accommodate IE out of sheer pride and determination
10. And most importantly of all… Please try to realise and appreciate how lucky we are to work in such a cool industry and in jobs we love!

I’ll take full-time IE bug fixing over a dead end job I hate any day! How many people do you know who live THAT life…

Seriously guys we are SO lucky!

In My Defence…

Now let’s get one thing straight here, I’m not defending IE here, I would love as much as anyone to see it go away never to be seen again. It causes me, and anyone in Web Project Management, endless amounts of headaches, but, being on the front-line with clients and their KPIs means I just can’t ignore the reality right now.

This article is not meant as a rant at designers and developers, but really a plea on behalf of all Web Project Managers to the web designers and developers out there to just take a step back from the in-house, ‘in-industry’ red mist that surrounds this topic for a moment and appreciate the bigger commercial picture – the one Web Project Managers and web agency owners have to live in on a daily basis.

Let’s all keep trying to spread the word about using more standards compliant browsers, continue to educate clients we meet on the benefits of using Firefox over IE, inform everyone about the Google Chrome Frame, Progressive Enhancement and Graceful Degradation, but…

Please try to realise the commercial reality and support us in getting web projects finished on budget, on time, with minimal in-house stress and making client’s, and the large majority of their users, really freakin happy – which the for the time means accommodating IE in all its dominant form.

To a Web Project Manager, while it has such a large market share, getting it right in IE is just as important a part of the project as getting the designs signed off on time or making sure as much JavaScript as possible is un-obtrusive – we have to set personal feelings aside, be tenacious and get the job done.

Trust me, we Web Project Managers understand that Microsoft, Windows and IE completely suck when developing websites and applications, but as we openly empathise with you, please try to empathise with us, accept the amount of people that still use them and the position that puts us in when managing the delivery of websites and web applications.

So come on, quit with the un-constructive negativity and stop dragging your heels when it comes to getting it right in IE, it adds nothing positive to the atmosphere or morale of a web agency team – set your personal feelings aside, be tenacious and get the job done.

Ok, time for me to put my riot gear on…

In this final part I will discuss what I think good Digital Account Management is, the skill set you need and what it takes to distinguish yourself as a great Digital Account Manager.

What is good Digital Account Management?

Simply put, good Digital Account Management is… the ability to keep clients consistently happy, by being able to constantly identify ways to increase their business’s revenue using digital solutions, solutions that your web agency can implement at a cost that results in profit.

Although a job with a hundred other roles and responsibilities, they all ultimately are geared towards:

1. Winning new business from new clients
2. Winning repeat business from existing clients
3. Extending their agency’s reach into the client’s business

If a Digital Account Manager can consistently meet the monthly revenue targets set by their superior while keeping all their clients happy and losing none to competitors, then they have a done a good job and shown what good Digital Account Management is.

Ok, we now know what good Digital Account Management is, but what skill set does a Digital Account Manager need today in order to get employed and stay employed?

The Digital Account Manager basic skill set

Rather than immediately launch into what I believe makes a great Digital Account Manager I thought I’d take a look around some job boards to see what the general consensus currently is among digital agencies looking to hire Digital Account Managers, or put another way, what is the basic skill set required to be a Digital Account Manager today.

Client management

• Build and maintain client relationships as the primary contact point
• Responsible for day-to-day management of clients, requests and accounts

Tactical and strategic sales

• Identify new sales opportunities within existing accounts
• Achieve personal monthly new business / revenue targets set by the CEO
• Spearhead client meetings, presentations and account winning client pitches
• Provide sales and project documentation including proposals, quoting, contracts and budgeting
• Lead, write and present client account strategy development documents

Analysis and reporting

• In-depth analysis of web analytics to produce monthly reports with key recommendations for client
• Monitoring and understanding your clients markets; be aware of market issues and competitive activity

Consultancy

• Information Architecture, SEO, PPC, and Social Media consultancy

Internal and personal

• Proven digital creative and technical experience
• Manage production teams to ensure delivery of projects is on time and on budget
• Reporting monthly to the agency management team on your activities

As you can imagine, I’ve omitted the usual “great communicator” and “must be pro-active” attributes, I even came across the requirement “Mastery of MS Word” – mastery? … wow.

So we can see the skill set that an average Digital Account Manager should have in their arsenal, but what makes the great ones stand out? What do they have, what can they do that the bog standard ones can’t?

What makes a great Digital Account Manager?

From my experience, the difference between an average Digital Account Manager and a great one is the same thing that separates an average designer or developer from a great one – a burning passion for all things web. They live and breathe it, during the day and when they go home – they absolutely love it and can’t get enough.

Great Digital Account Managers crave input like Johnny 5

Although this isn’t the only difference, the others tend to be born out of this one alone.

Ok, so other than the burning passion thing, here’s what else I believe are the tell tale signs of a great Digital Account Manager, they tend to have:

• The ability to provide quality solutions to the client that they love because it helps achieve their business aims, but also aligns with their web agency’s business strategy – clever
• An honest addiction to the web that enables them to be able to know about and suggest new solutions to clients that are cutting edge and no competitors have started to adopt yet
• Enough web design and development knowledge that earns the respect of both production teams because they rarely sell solutions to clients that are unrealistic in terms of time or complexity
• Enough knowledge to handle the whole selling process mostly alone, right up until the production phase needs to begin
• The willingness to personally research any digital topic they need to in order to be able to speak to the client with complete confidence without relying too much on creative or technical production resource

Great Digital Account Managers are rare, if you find one, hold onto them for dear life because the unfortunate reality is that far too many Digital Account Managers simply act as a web agency’s face and voice, making out to the client they know what they’re talking about when in reality they’re completely relying on the creative and technical teams to cover their lack of knowledge, in some cases even asking them to write whole e-mails that they can send to the client as if they wrote it.

I believe this reality is unlikely to change simply because few people who work as a great web designer or web developer (and thus have the burning passion needed) want to make the leap from production into Digital Account Management, or Web Project Management for that matter, so you tend to find the space full of people who have minimal web experience.

However, maybe there is hope… looking at the Digital Account Management job descriptions it seems that to be a Digital Account Manager today you are now required to know much more about web design, development and trends than ever before – could it be we are heading towards an era where most Digital Account Managers are really and genuinely web savvy? I really hope so…

In summary

As a Web Project Manager working in a small web agency you will almost certainly be called upon to perform Digital Account Management tasks on a regular basis and they will usually come with no warning and need your immediate attention, throwing your web project schedules into bedlam.

Unless your agency adopts the approach of larger companies, by employing a dedicated Digital Account Manager, you will just have to get used to it because the client will probably know you a million times more than anyone else in the company and always approach you with requests – see this for the compliment it is if nothing else.

Try to make sure you’re in a position where you can justify any delays to your web projects due to account management to your boss and then start to embrace and enjoy it, you’re being paid to develop your own skill set that will never go out of date, something you wouldn’t get an opportunity to do in a larger company and something that even benefits your own agency – everyone’s a winner.

If it all gets too much and you simply can’t cope with the additional workload, seek help, find out if you can deal with it when you know you’ll have the time or work a little overtime and take one for the team – there are always options that mean the client stays happy and you don’t go insane.

Once you find the time to put your Digital Account Management hat on, do the best job you can. Remember the point of it, it’s not only to generate new revenue for your agency, but to do so while providing genuinely useful solutions to the client that help them achieve specific business goals.

As a Web Project Manager you probably already have enough knowledge and passion to temporarily pass as an average Digital Account Manager. But why not try to be a great one by keeping up to date with the latest web trends and technologies and putting in the extra work to keep the Digital Account Management work away from your production team, and retaining the Web Project Management ethos of trying to keep them doing what they should be and making their job as easy as possible – you will reap all of the rewards in the end – fact.

Related reading:

• Account Management for the Web Project Manager: Part 1
• Account Management for the Web Project Manager: Part 2

In this next part I would like to give you my thoughts on why Web Project Managers, despite the grief it causes, should actually embrace the opportunities they have and a few different ways to manage the additional workload as and when it arises.

Embrace Account Management

So this may be an alien concept to some Web Project Managers out there, almost as much as the concept of enjoying web development is to most Account Managers, but I’d like to explain why I feel Web Project Managers should actually try to embrace those times when you get an unexpected client request, just when you don’t need it, rather than spit fire.

In short, it’s a free crash course (in fact you’re paid to learn) in several new skill sets that are invaluable to you and your company and that will never become out of date, unlike web development techniques – everyone’s a winner.

This really is the only point and it should be a no brainer to everyone. Yes it’s tiring, yes it’s scary, yes it can be a right royal ball ache at times, but, I absolutely guarantee you, if you somehow manage to get through a few months of insanely manic times where you were juggling more projects than you know you should be, plus dealing with incoming requests and new business opportunities, you will look back at some point and realise just how much you learnt and it will blow you away.

I totally understand that when you’re right in the depths of hell in terms of your schedule, it’s practically impossible to sit back, relax and fully appreciate the experience you’re gaining, but go through the cycle enough times and slowly but surely, when things are getting really tough, you’re able to see the bigger picture and press the reset switch just before giving someone else an actual physical ball ache and being escorted from the building.

Irrelevant to the post but found searching for “ball ache” on Flickr. Check out the cow stool with udders.

Account management is a whole career path for some, as Web Project Managers we tend to act as Account Managers at least once a week, I honestly believe the better Web Project Manager you are the better Account Manager you are, and vice versa. Embrace the opportunity to be paid to learn, you will retain the skills no matter where you go.

*Note: You have no idea how happy I am that I managed to get the term ‘ball ache’ into a post, must use more.

Dealing with additional Digital Account Management work load

Now, as with most articles published about web project management, the advice given is very ‘ideal world’ and is not always easy to put into practice, as are job descriptions in small web agencies. The reality is, if you work in a small web agency as a Web Project Manager, you will have to perform Account Management duties, amongst many other roles, and they will generally come without any warning and need your immediate attention, superseding what you had planned to work on.

So now you know this, how can you go about dealing with the requests out of nowhere when you least need them? Well, there are some short-term, tactical techniques and long-term strategic techniques:

Short-term

1. Strike a deal with your Account Manager, or someone else, to help each other out
2. Postpone dealing with the request
3. Delay another project
4. Work overtime

Long-term

1. Cultivate a change in internal operations where an Account Manager is involved in the web project from the start and not post-launch

Strike a deal

When working in any company, be it small web agency or large corporate within a digital department, try to build a rapport with an Account Manager you like to work with and strike a deal whereby they help you out, and you them, when work load becomes intolerable.

This relationship can not only be a sanity saver in times of chaos, but it can also be used as a knowledge sharing exercise that will benefit both of you and the company you work for:

1. The Account Manager gets to learn a little about how you run web projects and web technology (something many seem to be short on)
2. The Web Project Manager gets a little insight and experience at what a dedicated Account Manager does
3. The company has more employees at their disposal that are developing their own skill sets

A key skill for any Web Project Manager is to negotiate win / win situations – this is a win / win for everyone.

Postpone dealing with a request

Sometimes even when you look around you for help, it’s just not there due to everyone else being insanely busy. In situations like this you can always consider putting off dealing with the request.

Now some Account Managers would physically vomit at the thought of telling a client that they don’t have the time to deal with this new request that is probably new revenue.

But I’m not saying you should tell the client you are too busy and can’t deal with their request, but simply enquire as to the urgency of it. You’d be surprised how many times I’ve taken a call out of the blue that is a client wanting to talk about new work only to discover it’s not something they need an answer on immediately. I’m equally surprised at how often the Web Project Manager or Account Manager doesn’t ask the client when they need a response, instead choosing to scramble around trying to react immediately.

Looking back, this is something I rarely used to ask because I very much had a “OMG a client is on the phone and I must answer them immediately in order to keep them liking us” – only as I became more experienced and realised client’s are just people with busy schedules too did I start to ask when they needed a response if I knew my schedule was mental at the time.

If a client says they need a response that day and you’re busy, tough, you’ll just have to deal with it somehow, perhaps by using some of the techniques described in this article. However, if the client says they’re happy to wait for a day or a week, this can be a life saver! Always ask, you have nothing to lose and everything to gain.

Delay another project

Occasionally you’ll get a request from a client out of the blue that will be a real opportunity for your web agency, more than occasionally you will have a completely full schedule.

It’s at times like these you have to think commercially about the new request versus the current web projects you’re running, in other words, does the new request have massive potential benefits that are worth delaying another project for…

This is a question that only you and your web agency can answer at the time, and only then on a case by case basis, but the option should always be considered.

Work overtime

Of course, the infamous ‘work overtime’ option. In order to deal with new client requests when your schedule is full you always have the choice to work overtime so you can fit it in.

Again, your decision can only be based on a case by case basis and can have many influencing factors e.g. massive opportunity for you or the agency, agency is not doing so well financially, you get paid for overtime and could do with the cash injection or brownie points etc.

Although it’s your decision, in most cases, I would give you one word of warning about working overtime, especially when working in a small company – it’s habit forming.

I could probably write a whole new article on the pros and cons of working overtime, but in short, working overtime once or twice to deal with new client requests when you have a busy schedule is ok, but there is a fine line between once or twice and it becoming a routine for you that can actually result in people expecting it and being annoyed when you say no.

This can then slowly become the culture of the entire agency and ultimately cause people to feel like it’s a mandatory rather than a choice – a sure fire way to cause team morale problems and burn out.

But ultimately, working overtime is always an option and there are just as many reasons to use it as there are not too.

Account Manager involvement from the start

This is an approach that’s adopted by larger organisations but something I feel smaller web agencies would also benefit from and should think about implementing as a long-term strategy – it’s where each project / client has both a dedicated Account Manager and Web Project Manager.

This person needs to be someone who will take the responsibility of looking after the client in terms of:

• New business opportunities
• Non-project related requests during the project
• Invoice sending and cash collection
• Post-project day-to-day account management and small work requests

The most important thing is that they’re included from the start of the web project and maintain an involvement throughout by attending kick-off meetings, being present on teleconferences and receiving weekly briefings from the Web Project Manager on project status and relationship development, thus enabling them to:

1. Build rapport and trust with the client
2. Deal with any non-project related requests a client may send through
3. Act as an understudy for the Web Project Manager in case of illness or holiday
4. Pro-actively spot opportunities, suggest and sell genuinely useful solutions to the client
5. Take on the client as a new account after the web project has been completed

…the very things that destroy Web Project Manager’s schedules and ultimately make them shy away from Account Management tasks.

Now, while the amount of work for one project or account may not be able to justify the hiring of a dedicated Account Manager in a small web agency, I’m of the belief that with multiple web projects and clients, there almost certainly is a full time role there, and that the role can be justified further by adding the standard measurable target to it that all Account Managers have to satisfy – monthly revenue targets.

Too often I see smaller agencies employ two or three Web Project Managers and then assign them each a project that has a client and that’s it – that Web Project Manager will not only plan and deliver the solution, but retain sole ownership of the client and account from that day forth. This tends to create a silo-type environment where only one person has client and account knowledge which is never a good thing.

I also feel this isolated multi-role approach is one of the many reasons Web Project Managers find their schedules obliterated on a weekly basis (thus affecting project schedules and quality) and why many small agencies are always playing catch-up and never make the transition to medium size – the people essentially responsible for growing the account tend to see it as a low priority task that isn’t their core skill and rarely have the chance to dedicate the time Account Management really needs in order to bear fruit.

I believe the aim should be exactly the same as it is when we try to keep web designers designing and web developers developing – to keep Web Project Managers managing projects and Account Managers handling the day-to-day tasks and growth of accounts.

I don’t think it’s a coincidence that medium to large sized agencies tend to have one person per role. By definition, the fact they are now medium or large means they have grown significantly, and in a stable manner, while others haven’t and I like to think smaller web agencies, if they want to grow to medium size, should always try to look at how the bigger fish operate in order to identify how they achieved this.

In Part 3 I’ll talk about what good Digital Account Management is, the skill set you’d ideally have and what it takes to be a great Digital Account Manager rather than just an average one.

Related reading:

• Account Management for the Web Project Manager: Part 1
• Account Management for the Web Project Manager: Part 3

This is one of the best, and worst, things about working for a small web company. You get to gain tonnes of experience in a variety of areas and develop a plethora of business skills, but, invariably it’s just these kinds of sub-roles that can crop up right when you don’t need them to, and often are responsible for wiping out an entire day that you had carefully planned out in order to stay on schedule.

At this point it should be noted that when I talk about Account Management in this article I mean Digital Account Management, and I’m talking about just a small part of the job, not the all encompassing one that includes wining and dining clients, permanent fake smiles and meeting revenue targets – just the day to day flavour a Web Project Manager tends to encounter e.g. new business sales and new work requests from clients outside of any projects being currently run.

In this series of articles I’d like to discuss the following:

• Why Web Project Managers end up performing Account Management duties
• Why we should all embrace the opportunity rather as opposed to shun it
• Ways to manage the extra unexpected work load
• What makes a great Digital Account Manager

And of course, include a few movie references kowabunga!

I’m a Web PM, not an Account Manager!

You see the job advert, it sounds tempting, you apply and charm the pants off the interviewer (not literally, that would be highly inappropriate) and you get offered the Web Project Manager position which you happily accept.

A few months in, with a couple of projects under your belt and good rapports built with clients, suddenly they’re asking you about small little pieces of website work, new mini-projects they have budget for and for advice on what they should do next with their website and overall digital business strategy.

Instinctively you begin to reply promptly and before you know it you’re getting sign-off on new work and new money… well done you, super duper shiny gold star!

But wait! What’s happened here? The sly subtle beast of Account Management has crept up and is about to devour you and your day – clever girl…

I’ve actually met several Account Managers who look a little like this, but, in this case it’s meant just as a metaphor

Yes that’s right; as sure as the cowboy hunter dude from Jurassic Park was eaten alive, you’ve slipped into an Account Manager role by accident; but why did this happen, and why does it always seem to happen to Web Project Managers?

Web Project Manager, a client’s best friend

Quite simply, you’ve become a Digital Account Manager because you’ve been the primary contact for the client for weeks or months and at this point they probably trust you more than anyone else in your team.

In the preceding weeks or months you have more than likely demonstrated a level of web industry expertise that gives the client a confidence that you are the person to ask about their online business strategy – what a compliment right!?

Web Project Managers love their ego’s being massaged as much as the next person (it’s not just web designers or web developers, we just hide it better), so why do some Web Project Managers dislike Account Management tasks so much when it is clearly evident the client is completely loving and respecting you?

Why Web PMs hate Account Management

I have come across many Web Project Managers who completely throw their toys out of the pram when Digital Account Management tasks land on their to do list, and do you know what, I have secretly done the same from time to time (just not shown it), but the reasons for the hissy fit may not be what you think…

Ok ok, in some cases the reason for the toy throwing is because a Web Project Manager just doesn’t want to do any Digial Account Management because they feel it isn’t their job, but you’ll generally only find this reaction in larger web organisations, where both dedicated Web Project Managers and Digital Account Managers are employed.

In larger organisations it’s not unusual to find the Digital Account Manager is the client’s primary point of contact and the Web Project Manager works more internally, managing the project team, something closer to a Production Manager in my opinion, but hey, I digress.

More often than not the reason Web Project Managers will try to avoid Digital Account Management duties is because it simply isn’t something they had planned to do in their already busy day and it can put multiple project schedules in jeopardy – that’s enough to rile even the most relaxed of Web Project Managers!

The 5 minute myth of Account Management

While it seems obvious at the time that if a Web Project Manager handles new client requests on a regular basis then something they had planned to get done that day won’t get done, it’s something that is surprisingly, and disappointingly, rarely accepted as a valid reason for a web project being late.

This is usually because the Digital Account Management duties performed come in dribs and drabs over a period of weeks or months, thus being hard to track. Sometimes it’s a 15 minute phone call, others its two or three mornings compiling new web project quotes, there’s the little quick e-mail or the new business meeting or two… you know the things I mean, the little bits n bobs that take “5 minutes”.

These “5 minute” things, as I’m sure you’re all aware, tend to take anything from 15 minutes to 2 hours and above because they’re very rarely events in isolation. Yes the initial task may take 5 minutes, but the subsequent actions and waiting for items that come as a result will also take time to process.

These “5 minute” things are usually quoted as such by a person who will not have to see the action through to the end, and over the course of a web project’s lifecycle, perhaps 3-6 months, they can all add up to days worth of lost time that can ultimately cause web projects to be delivered late.

A typical Digital Account Management scenario

For example, to take a request from a client to quote on a couple of small new pieces of work that are separate from the current web project and thus not a change request, assuming they are in some way bespoke, will take you a good deal of time because you will probably have to do the following:

• Talk to the client to see what they want / what they’re trying to achieve
• Talk to the web development team to see how it would be best to implement the request and how long they would estimate it to take
• Speak to the web design team to get an estimate for the work required
• Create a structured quote that also accounts for any other tasks that will need to be completed as a result of the new requests e.g.:
  • Create mini-Sitemap
  • Create mini-Functional Specification document to eliminate ambiguity and scope creep
  • Create crude design mock-ups
• You’ll then need to factor in the potential new work into the project’s existing schedule and your web agency’s resource availability, in order to let the client know how / if the new work would affect the current project milestone dates
• You’ll then need to write a mail, send the quote and be prepared to answer questions about your proposed solution
• There will no doubt be time needed to negotiate price
• Once agreed, you will have to send off the formal documentation and await sign-off
• Once signed off you will have to schedule the resource needed to complete the work, brief all team memebrs and send updated project schedules / milestone dates to the client

Then, and only then is the Digital Account Management duty over and as you can image, all of this takes time, time you had almost certainly had allocated for something else.

No doubt there are many out there who would just “throw together a quote” and say yes to the client immediately, but I’m a firm believer that if you’re not following a structured process for taking new client requests and producing quotes then you’re immediately running big risks of over selling, under quoting and / or missing critical requirements – and I guarantee this will invariably result in someone needing to spend more time to fix than you would have estimating, and leave the client peed off which all would agree is bad Digital Account Management!

Of course some will argue that this is the job of the Web Project Manager, and in most cases I would agree, after all, who best to understand the requirement, estimate time and adjust web project schedules than the Web Project Manager? Plus, how often have we whined about an Account Manager who has sold some new work to a client without taking into consideration the current schedule, resource allocation and fact that you can’t build “a mix of Facebook and YouTube” for £3k?

However, if it happens frequently enough, and isn’t a change request to the current web project, it can severely disrupt a Web Project Manager’s personal schedule to the point where projects are suffering significantly and thus it’s always best to have someone to delegate too if possible – the perfect person being a dedicated Digital Account Manager.

As the seasoned Web Project Managers out there will know all too well, one day lost can potentially cause days or weeks worth of delay to a web project. It could be that you’d scheduled designers or developers to start work the next day which was dependent on you finishing the creative brief or functional specification and getting sign off from the client that day, and they were only available to review and sign that day and won’t be again for four or five days – disaster.

When Account Management makes projects late

While it’s incredibly frustrating to be berated by your manager or client for a web project being late, if you know part of the reason is due to you dealing with unexpected Account Management duties, mention it.

But be aware, if you mention it, it’s best to be prepared and able to produce some kind of evidence or log, of not only the time spent on Digital Account Management tasks but also the new revenue earned for the company, just in case it’s a particularly sensitive project and you run the risk of being crucified, burnt, hung, drawn quartered and fed to the Sarlacc Monster in the Great Pit of Carkoon, rather than simply ‘sighed’ at.

Pretty much how Web Project Managers feel when a project is late

Aside from keeping records of your work time to cover your arse when being thrown to the wolves, it’s also a good habit to get into so that you can begin to analyse your time and see just where it’s going and how long it tends to take you as a percentage to manage web projects – you can then use this information to assist you in identifying bottlenecks in your processes and estimating new web projects, as I discussed in my article Estimating Time for Web Projects More Accurately »

Hopefully this first article in the series explains why Web Project Managers always seem to end up performing Digital Account Management tasks and also why many dislike it. My counterparts out there will already know all of this, but perhaps it may offer a different perspective to others who work alongside Web Project Managers…

However, now the rant part of this series is complete, and I have all my fellow Web Project Managers agreeing in unison about how ridiculous it is to be expected to handle new work requests on top of their day job, in Part 2 I’m going to upset you all by talking about why Web Project Managers, despite it having the ability to seriously de-rail your projects, should actually embrace the opportunity rather than shun it and some techniques you can adopt so you can deal with the strain it puts on your workload.

• Account Management for the Web Project Manager: Part 2
• Account Management for the Web Project Manager: Part 3

About the Author

Michael Dlugosch works as a Senior Consultant at Kwantic Oy, a Web Analytics startup company in Helsinki/Finland.

In this final part of the Michael Dlugosch talks about Sloth, the last of the Web Project Management deadly sins. It deals specifically with the constant struggle Web Project Managers have when trying to allocate resource to their projects only to discover there is none available.

7. Sloth – “We don’t have more resources!”

As Sam Barnes comprehensively covered in his recent article “Web Projects: How to keep the peace when making decisions”, one of the saddest facts in a Web Project Manager’s life is indeed the multitude of expectations they to deal with, for example:

1. The client expects your organisation to be flexible enough to catch up with a five day delays in material preparation without any effect on the deadline
2. Your Accounting department expects that they can issue this phase’s invoice as planned before to ensure the cash flow
3. Your HR people are expecting you to make precise resource allocations for projects with an unknown scope, with a slipping deadline, and with a shrinking budget

But no matter what pressure you are under, please don’t ever give this article’s headline quote of “We don’t have the resources!” out to any of your clients! If you do, you will literally destroy the agency’s reputation that your Account Manager has built up over the years with his bare hands.

Here are two reasons why you should refrain from saying it:

1. You will ruin your reputation as you’re probably lying without even realising it!
2. One of your most important tasks is to keep your business away from the client

Of course your company has more resources! It will almost certainly be just a fraction of your agency’s workforce that you have allocated for your web project so far. As soon as more than one web project is handled at your company at one time there are more resources. The sad and brutal truth is that you probably do have the resource in-house, but just can’t access them or allocate them to your tasks – your organisation simply wouldn’t allow that to happen! So, admitting that you can’t get any more resources other than the ones you have assembled as workforce on their project is a bad thing to do. Just ask yourself the following question:

As for keeping your business away from the client, consider this example.

If you bring your car to a car repair shop – you don’t really expect the clerk to tell you intimate details about the workload of his staff, right? All you want to get is your car repaired. And thus you may accept the clerk saying: “Sorry. For this week we are already full. But you could bring in your car next Tuesday at 8 in the morning!” You really don’t expect any more information on the matter why you can’t get you car fixed before that.

The struggle for resources is one of the biggest challenges a Web Project Manager will face. It is however not the client’s concern how your web project staffing is addressed.

Dealing with resourcing issues

There are however a couple of techniques and replies which you can apply to situations where you are asked to stretch your project organisation beyond capability. They all boil down to the fact that it is essential for you to buy time, and to sequence the requests in a reasonable manner by constantly re-applying the distinction between urgent and important throughout a project.

If you have followed the advice assembled in this article so far you already have some good replies at hand to answer client requests about additional deliverables.

Several more re-usable Web Project Management snippets you may want to consider for any future resourcing situation include:

• “I would need to look into the implications on schedule and budget before I can give you confirmation on this matter.”
  • Remember, all the tasks and phases are deeply intertwined!
• “Upon initial thought it seems as if this request is enhancing the agreed functionality requirements. I’ll have this analysed by our technical experts first and get back to you.”
  • Remember, a significant scope enhancement will ruin one or more of the Assumptions and/or Prerequisites under which the Web Project Agreement has been issued originally and may result in filing a Change Request. Once clients see the price tag implied by their request, they may consider it “not that urgent / important”
• “I can only think of two people in my organisation that would have an instant answer to whether this is possible with the given system. Let me quickly see if I can contact any of them.”
  • Grab your phone while saying that. Remember, you are representing a team of experts, giving everything to satisfy client’s needs as they emerge!
• “The team for this week is completely allocated with coping for the unpredicted delay in the provision of material. We can have a look at this request next Tuesday at 8 in the morning!”
  • Remember to know where you and your team are with the tasks agreed and what is the most urgent thing, as opposed to important, to take care of is essential

For every additional task that ends up on your project team’s plate you have to consider one or two possible ways to deal with it. It depends a lot on the project team and the organisation you are working for and it also depends on how your organisation rates the importance of the project or client in question, but below is some general advice on how to try and squeeze in unexpected work into an already packed schedule if need be.

First, you could squeeze the task into the existing schedules, ordering your team to work overtime. You can promise compensation or certain gratifications for those who are volunteering for the extra work. Or simply assign the task to someone whom you consider fit for the job. This principle can be referred to as heroic management e.g. “It’s a shitty job – but somebody has to do it!”

Secondly, you could count on the advice and ingenuity of your project team. Make the task description as clear as you can and involve your project team in solving the matter. Discuss openly what other tasks can be shuffled around, postponed or distributed to more shoulders?

Is the new task truly a specialist’s task – or could anybody work on it? How would the team rate the chances to get the additional work equally distributed with only a couple of additional hours for everybody? This principle can be referred to as post-heroic management e.g. “It’s an inconvenience which forces us to re-shuffle already allocated tasks in a smart way!”

Last but not least, it largely depends on what kind of personality you are. If you are not able to contribute hands-on to the project (as you may not know how to operate a text editor, Adobe Photoshop, or a Content Management System) – you can always try to learn these things from your project team members and do the job yourself.

If you are not willing to contribute hands-on to the project because you do not consider this being a part of your responsibility – you can always try to get another job. The choice is yours.

In summary

Web Project Management, for which I sketched its shortcomings in the previous articles, will undoubtedly flop if it is carried out with the wrong focus and if it is aiming at the wrong goals.

The postulated deadly sins can, and shall be of course, all interpreted as examples of individual failure. In Web Projects, I have seen otherwise reasonable Web Project Managers being caught in selfish traps because they pig-headedly insisted on having the exclusively correct situation assessment and response for a particular question, issue, or project stage.

In the current economic climate it can prove deadly for a whole web agency if the management doesn’t see the wood for the trees – and each of the postulated deadly sins can easily obstruct the view on more important issues.

Web Project Management is far more a continuous business re-engineering strategy than simply the completion of pre-defined and well formulated task lists with known time, money, and competence allocations.

It requires, following one thought from the German sociologist Dirk Baecker, a type of management which sees its heroism no longer at the disposal of resources and the willingness to fight offending or unreasonable customer demands, but which requires serendipity for the factual and social dimensions of the organisation of work and the distribution of shared responsibility which comes along with that.

We are heading towards an age of post heroic management, for which two aspects seem essential to me:

1. The Web project Manager’s ability to let his personal motivations, goals and rewards fade into the background, and…
2. Each team member’s ability to re-think their own contribution beyond a structure of assessment, delivery and hierarchy

This concludes the Web Project Management: Seven Deadly Sins series. A big thank you to Michael for writing this incredibly extensive and enlightening article which has certainly taught me a thing a thing or two and I hope you feel the same too.

Related reading:

• Web Project Management: Seven Deadly Sins – Part 1 »
• Web Project Management: Seven Deadly Sins – Part 2 »
• Web Project Management: Seven Deadly Sins – Part 3 »
• 7 Deadly Sins of Beginning a Web Project »

About the Author

Michael Dlugosch works as a Senior Consultant at Kwantic Oy, a Web Analytics startup company in Helsinki/Finland. Follow Michael on Twitter »

In Part 1 Michael discussed the sins of Vanity and Envy. In this instalment he goes on to talk about how Web Project Managers can keep web projects on budget, and perhaps even add more value than expected for the client and your agency, and what it means to lead from the front as a Web Project Manager.

3. Gluttony – “We need to increase the project budget by 2 million”

Gone are the days when clients seemed to have endless budgets allocated to an emerging digital medium and where they hoped to mark their claims on the Western frontier.

Today, more and more payments are tied to specific milestones, preliminary approvals by the steering group and successfully conducted functionality tests that are based on the use case descriptions, which may postpone a web project phase’s payment for six weeks.

It all depends on what kind of organisation you are working in and whether you’re paid by the efforts your team has put in, for meeting certain functionality criteria or for something else judged by some obscure stakeholders somewhere else in the world – big money spends on web projects have become scarce over the last few years, and you had better be fully aware that there is no more budget for your project – even if the customer has changed the scope countless times at will.

Either way, in these difficult times for the digital industry a Web Project Manager needs to find ways to keep delivering with reduced budgets and less margin for error that ultimately hit your already financially fragile web agency.

Here are two ways to deal with the constant problem of web project budget overrun:

1. Overspending
2. Shadow budgeting

Overspending

This is always a calculated bet on the future. It is the technique whereby a Web Project Manager or Account Manager justifies web project overspend by assuming that future projects for the same client will allow them to claw back the project overspend for the current one.

Shadow budgeting

Shadow budgeting is the art of working to lower budgets than you actually have in order to cater for the inevitable overrun – best case is you deliver under budget and achieve some internal process or skills development while being paid, worst case is you deliver on budget – not a bad worst case scenario, I think you’ll agree.

You start by taking the budget which you have for a given project phase or deliverable and you simply reduce this budget by 20% and consider the remaining 80 per cent from now on your available budget for this phase or deliverable.

Your team may mourn, but here’s how you can explain it so that they are more likely to follow your approach…

Most project deliverables follow Pareto’s 80/20 rule – 80% of the outcome of a project deliverable is realised with only 20% of the effort put in. It usually swallows all remaining budget to complete a deliverable – particularly due to long review cycles and more iterations than planned.

Plus, your client may indeed be happy with a preliminary 20% deliverable to collect instant feedback from within their own organisation even before your agency has put in all the efforts in to complete the whole stage.

In the end the client’s organisation may scrap it all anyway because your deliverable may not meet their high expectations – so why not give them sneak previews instead?

My best advice is to involve your team in this from the start! Let your team decide how to share the most laborious tasks. As a Web Project Manager, get your hands dirty in the practical preparations. Touch code, review copy texts, cut images – simply suck in as many practical issues as you can and familiarise yourself with the strains of fatigue and boring repetitive tasks.

Encourage your team to divide labour, to share what they learn and discover along the way, to focus on tasks which require a lot of concentration only for an hour at a time and to review and question each other’s work.

Allocate half of the shadowed budget for this stage (10%) to scrutinise and streamline the team efforts for getting the original deliverable out with more nifty tools, better material preparation, machine-based data enhancements and a smarter repository structure.

Make it a team effort to elaborate on solutions for the never ending need for further streamlining! Equip every piece of material with hooks and handles so that you can re-process and re-use it along the way.

As plenty of the original budget for phase conclusion is usually spent on implementing what was originally agreed in the first place, you need to free the team from the inability to revoke their original ideas, and because some of these efforts are spent on repetitive tasks, you may be lucky enough to pocket the famous learning curve effect which usually come along with repetitive tasks and may account for as much as 30% of the original 80% phase budget.

Any Euro, Pound, Dollar or Zloty spent on thinking about how to solve a problem can lead to totally new, and unpredicted, ways to get things done, and with considerably less effort and thus more cost effectively for future projects – think long-term.

With the other 10% of your shadowed budget – spend it on thinking through the consequences of the chosen setup. You may find that with only a relatively small additional effort, you can put time into those mythical documentation and show cases!

4. Lust – “Non serviam!”

I can’t help but notice the occasional unwillingness among Web Project Managers to serve.

By this, I don’t mean the feeling that one would have to stoop when the customer lets the proverbial soap slip – I mean the ability to let your own Web Project Manager personality evaporate into the background in favour of something else more honourable and geared towards getting things done together for the team.

It is a platitude that any kind of management only has two ways to get anything done – action and communication.

Communication without action is simply pretending, and action without communication will never lead anywhere. Big gestures, speeches, or any other kind of ‘pep talk’ are not really well suited for motivating people’s participation without follow through.

The inability or unwillingness to serve can be easily attributed to what psychologists call: narcism. However, it may lead further to take another angle and approach this topic through the back door.

We have, thanks to the genius of the sociologist Max Weber, a term for coining what might make the essential difference here – it’s called work ethics. At its core it can be surmised as “working hard will please…later”.

The distinction between hard work in the present and a gratification in the future is the core personality attribute that distinguishes an average Web Project Manager from an excellent Web Project Manager.

Contrasting this approach with the mentioned distinction between “action” (from Latin “agere” – to do) and “communication” (from Latin “communicare” – to share, to make common) indicates the direction of the reference inherent in both terms – towards oneself vs. towards something beyond oneself.

I believe the trouble with the stated “unwillingness to serve” is the coherence between one’s actual deeds and the expected or well deserved gratification structure behind the deeds. Or from the opposite perspective, it is the inability to classify one’s own deeds into coherence beyond the benefit for oneself.

If a Web Project Manager is primarily concerned about their own reputation (their lust for praise from others), status or comfort, it will undoubtedly have a negative effect on the team’s motivation to walk the extra mile with them.

Who has ever met a Web Project Manager that leaves the office during a laborious end phase of a website production on the evening before go-live with the reasoning “I have to attend my dance class”? If you have you have every right to scorn at their own perceived right to call themselves a Manger of any description.

To manage means to lead, and leading is located in the action domain, not in the communication domain.

In Part 3 of the series, Michael discusses how to resist getting angry with clients when the temptation is overwhelming, and how to control the scope of web projects by defining clear specifications and project scope from the outset – Anger and Covetousness

Related reading:

• Web Project Management: Seven Deadly Sins – Part 1 »
• Web Project Management: Seven Deadly Sins – Part 3 »
• Web Project Management: Seven Deadly Sins – Part 4 »
• 7 Deadly Sins of Beginning a Web Project »

^ Back to top

About the Author

Michael Dlugosch works as a Senior Consultant at Kwantic Oy, a Web Analytics startup company in Helsinki/Finland.

Equipped with true passion for the Internet since his first encounter with it in 1996, Michael has been jumping around in Digital Agencies since 2000, running web projects, web productions and teams, consulting as Usability Specialist and, lately, as Web Analytics Consultant.

While not working, Michael can be found taking photographs or preparing home-made pasta.

We’ve all been tempted, we’ve all been there…

Tiresome web projects without end, endless discussions with the client, never ending resourcing problems, budget cuts, technical systems not working and changing scopes all over the place – everything turning upside down faster than you can spell change request!

No doubt about it, Web Project Management is not an easy job.

However, during my own involvement with web projects I’ve had to witness particular things which were said by team members, in front of the client, and within the team itself, and these things did nothing else but add to the confusion and difficulties that all web projects already have too much of even at the best of times, making the job of the Web Project Manager that much more challenging.

I tend to call these things the “Seven Deadly Sins of Web Project Management” and within this series of four articles I will describe and illustrate them, with examples – along with my best practice advice on how to deal with the temptations we all face.

1. Vanity – “We know better than the client!”

Let’s assume you work for an agency which has a certain experience in the field and has been running web projects for several years now, think how many projects have you and your team been involved in? 20? 50? Maybe even 100…

An average client has run only a few and often has only one primary goal; he or she needs to satisfy the expectations that have been set by their superiors.

While it has become commonplace in web agencies to internally share the most outrageous briefings and the insane functionality requests for a good laugh with the project team, it should always be coupled with attempting to help your client by communicating with them better.

Of course you know more about web projects and web project management – so why don’t you start educating your clients accordingly? Take the following example of client feedback we’ve all heard and laughed at:

“Thank you for the screenshot of the HTML newsletter you sent. The layout looks ok, and the copy looks good. But not a single link works in the .jpg file you’ve sent me. You are going to fix that before sending the campaign, right?”

There is a wrong and a right response to this request. If you’re pressed for time, simply reply:

“Yep, we’ll take care of everything before we send it out.”

Don’t reply with:

“This is a screen shot, you stupid butthole! Of course the links don’t work in it!”

If you’re a patient person with nerves of steel, you could say:

“Hey, thanks for your feedback. We’ll take this as approval for the newsletter layout and content, and will make sure that all the links in the final version are functional and being tracked. Our technicians cannot yet exactly predict how long it takes to complete the newsletter batch delivery for all 3428 addresses, but we have scheduled to send the first campaign blast with 500 addresses at 2am tonight.

The file you’ve reviewed represents just an image version (jpg) of the final newsletter file (HTML) and thus doesn’t include any active link functionality. This is to ensure we do not inflate the click-through numbers during testing…”

See the difference? Embedding your sharp reply inside a plethora of “this will happen next in the process” information is serving two purposes:

1. It gives the client more information that they can hand over to their respective superiors
2. It educates the client about some tiny details in web technology

A colleague of mine once labelled this approach as “killing with kindness”.

Admittedly it takes time to write such lengthy replies. But by tying your reply to the next steps in the agreed process you do yourself and your client several favours:

1. You’re re-assuring your own understanding of the tasks that need completing
2. You give them the correct language to frame the project status and next steps to their superiors

This makes it easier to deal with upcoming requests from the client’s organisation as you easily can prove how deeply intertwined the single tasks are.

Also, at all times you are depending on your client’s political position within their own organisation and are literally casting silver bullets for them that they can fire from their corporate rifle. They may use the additional and contextual information that you give them to brag, fight back unreasonable requests or to claim as their own, but in all cases you can assist in making your client appear in a brighter light by filling them with web project specific information and terminology.

Remember, as a Web Project Manager one of your many roles is to make the client look fantastic to their superiors, do this and you’ll only improve your chances of repeat business.

But wait, isn’t that the job of the Account Manager?

2. Envy – “Account Management… I could do a better job myself!”

Many times I’ve witnessed Account Managers leave the office, much to the envy of the web project team and Web Project Manager as they are still clocking the hours up long into the night. As the leader of a web project team you are of course, more often than not, sharing cold pizza with your project team rather than seeing your friends and family in the evening.

But remember this distinct advantage of being a Web Project Manager over an Account Manager… by definition – A web project is a temporary endeavour with a fixed start and end date and so sooner or later it will be over – Account Management is never over.

Nothing prevents any client from calling up your fellow Account Manager at 10pm to discuss an article about how the latest web trends in viral marketing will influence the company’s performance on social media perception within the next twelve months from now on.

What looks so easy during daytime often proves to require an “always on” mentality for Account Managers, and trust me, wining and dining with clients is not as much fun as it sounds (although the food and drinks are on the house, mostly).

The only currency that an Account Manager has is trust. However, gaining, and keeping, the client’s trust is essential for both Web Project Managers and Account Managers.

But while Web Project Managers have very clear boundaries – delivering web projects – Account Manager’s success criteria are a little more blurry. While Web Project Managers may get adulation and praise for their constant supportive role (aka pulling rabbits out of hats – aka saving the client’s butt), Account Managers often find it more difficult to get famous for their deeds.

Maybe that is the reason why Account Managers are so often interfering and messing around with web projects, and the people involved in them, when it is not necessary – because it seems so much easier and more instantly rewarding when compared with what they normally do.

It occasionally seems to me that it’s the Account Manager’s secret job to promise what others have to deliver with no real clear idea if it is even possible, but the reality is a usually more brittle than that – thus putting the Account Manager in a difficult position.

While Web Project Managers have to deliver within a defined scope, Account Managers have to account for future scopes. At any time, a current client can approach a direct competitor of yours to begin talks about receiving the same service with improved quality and lower costs.

The Account Manager’s job is precisely this – to decrease the likelihood of this happening.

Operational, tactical and strategic are the names of the fictional stages of the continuum that both types of Web Managers have to tackle on a daily basis. While the operational side deals more with things that have already been agreed (projects and deliverables), the strategic level deals more with the ‘yet unknown things to come’, involving, for example, planned co-operations with institutions nobody has yet heard of and the instant need for ramping up your agency’s workforce by 385% within the next eight months.

The really tricky thing is that the Account Manager is held responsible for is the substantial monetary growth of the account through targets based on many unknowns.

So as a Web Project Manager, while continuing to attempt to keep the Account Manager away from the day to day running of your project, understand why Account Managers may insist on doing this before berating them.

In Part 2 Michael discusses his next two Deadly Sins of Web Project Management. How to keep web projects on budget without having to ask the client for an additional 2 million, and how the Web Project Manager should be willing to serve the project first and themselves second – Gluttony and Lust.

Related reading:

• Web Project Management: Seven Deadly Sins – Part 2 »
• Web Project Management: Seven Deadly Sins – Part 3 »
• Web Project Management: Seven Deadly Sins – Part 4 »
• 7 Deadly Sins of Beginning a Web Project »

^ Back to top

In my experience, by consistently displaying a high degree of honesty, trust and integrity to everyone throughout the web project’s entire lifecycle helps improve your chances of success, cements your position as a solid leader and earns you respect from both client and project team alike.

“A relationship that is based on honesty and trust with staff should create an environment of mutual respect. This environment should produce a more efficient production environment where staff are willing to go the extra mile to deliver a truly excellent product.”
Ed Richardson, Honesty is the best policy

Honesty and Trust in Web Projects

Of the many things you can be sure of when running any web project, one of them is that at some point you will have the choice to be honest or not so honest with either the client or your team. This choice is only ever one that takes more than a minute to debate in your Web Project Manager brain when the truth is likely to upset someone.

These choices come in all sorts of shapes and sizes but invariably include:

• Explaining to the client why a deliverable is late
• Telling a team member their work isn’t up to scratch
• Admitting you made a mistake yourself

In each instance the temptation for most Web Project Managers, in fact all human beings, is to at least consider taking the easy route and delivering a distorted version of the truth, or in non-corporate buzzword bingo professional terms – lying.

The fact of the matter is, often not being honest is the easiest option and will immediately make everyone feel great, however it’s pretty rare for this short-term easy option not to come back and bite you right on the backside and this is far more damaging to a relationship with the client or project team in the long run.

As a Web Project Manager, by cultivating a reputation as an honest straight talking person who will always tell you the truth, no matter how bad the truth is, eventually results in most trusting you when you speak – in business no one wants to have the wool pulled over their eyes and most can spot it a mile off.

So the next time a client demands to know why the deliverable is late when the reason will make you or your agency look less than great, tell them the truth… It will hurt, it will sting and it will be an awkward conversation that you’ll want to end, but, in most cases once the anger has faded away the client will almost always respect you for having the balls to be honest when other weaker web project managers would’ve lied.

The key lesson is that once a client knows you have the courage to be honest with them when it’s really bad news, they’ll completely trust you to always be honest from that point on and trust pretty much everything you say which, over the course of a project lasting months or years, is an invaluable position to be in as opposed to the oh so common vague feeling of mistrust that often exists between client and web agency.

Integrity in Web Project Management

Defined by the English dictionary as “Steadfast adherence to a strict moral or ethical code”, integrity is something a Web Project Manager needs time to develop and demonstrate, but once you have established yourself to the client and your web team as a leader with a great deal of integrity you will find all your working relationships improve dramatically.

Although inextricably linked with honesty and trust, integrity in web projects is all about acting in the most professional manner possible in front of your client or web team when faced with situations that require you to choose between standing by your principles, or, forgetting you have any for fear of appearing to be going against the grain.

“Sometimes telling the truth will not make people happy, or make you the winner of a popularity contest. In some cases you may suffer from “loss of grace” for telling the truth or for standing up for what is right.”
Thomas M. Cunningham, US Naval Academy Fire Department, Leadership 101: Integrity

Examples of displaying integrity in a web project management role include:

• Accepting responsibility for a mistake that you or one of your project team made
• Openly defending a project team member or client when the temptation is to keep quiet
• Insisting quality standards remain despite the temptation to cut corners

Preceding each of the above examples comes a situation where as a Web Project Manager you will have a choice between staying quiet and letting someone else take the fall or, as Thomas Cunningham puts it, standing up for what is right.

In these instances it is you that may be hurt and stung by the response, but as with honesty, over time your team and client will respect you for choosing to take this position as your default one.

As a Web Project Manager, failure to act with honesty and integrity will undoubtedly be your undoing. Both clients and your web project team will at some point become very wise to the fact you are keeping quiet, blaming others and treat you accordingly – with mistrust – and there is nothing more damaging to a project.

Having the strength to take a few hits for your web project team or from angry clients on the phone is not easy. It will often feel like you’re getting a load of flak and stress that you really don’t need and know full well you don’t deserve, but, the trust and respect you win from the people that matter is infinitely more valuable to your projects when compared to the reputation you pick up from acting inappropriately.

If you are in a web project management position, or any other leadership or management position for that matter, I cannot recommend reading the Leadership 101: Integrity article enough – it has absolutely nothing to do with web projects but everything to do with what it means to be a great leader. If you can manage to apply even one part of it in your day job, you will be a better leader and manager for it!

Honesty, trust and integrity – go on, try it, you just might like it…

^ Back to top

Add to that the nature of running a business where cash flow is critical, other projects can knock your carefully thought out plan sideways or a key client ring up with urgent requests that require resource you booked months in advance, and you have a delicate situation indeed.

While web trends and technologies evolve around us at a rapid rate and business requirements can often change on a week by week basis, a Web Project Manger will have to make constant decisions on what solutions to ultimately deliver to the client and often these decisions will not please everyone involved in the agency or project.

So who are these people and why may they not be happy bunnies?

Who you may annoy as a Web PM

In short, as a Web Project Manager, making final decisions about which solutions to implement, the chances are at some point you will annoy absolutely everyone who is involved in projects… not an appealing part of the job, but sometimes a necessary and unavoidable one.

“The Project Manager can’t ensure that they’ll be loved by everyone – nor do they want to be. They aspire to be well respected by the customer, but even that can’t always be guaranteed no matter how well they perform and manage the project. But, the Project Manager can ensure that everything that is expected of them is being performed well and if that doesn’t always do it for the customer at least it should be noticed by the delivery organization.”
Brad Egeland, Reputation is a Fragile Thing

But before you get scared and begin to re-think that career move into web project management, let’s look briefly at what each team member generally wants from all projects.

Empathise and understanding

Empathy and an understanding of the business forces driving different people’s motives are key skills required by any Web Project Manager as it enables you to appreciate other perspectives when making project decisions.

Let’s take a look at the usual suspects, who they are and what they want from web projects and your web project management. *Stereotype disclaimer included afterwards.

Web agency directors

A web agency director wants the project completed on time, on budget, to a quality level that is fitting to the web agency and with the client feeling happy, wanting more work and willing to give referrals to potential clients.

Finance directors

A finance director wants the project milestones split up in such a way that cash flow/collection is maintained for the business and thus that the project is completed to schedule, on time and on budget.

Web designers

Web designers want to push the boundaries with each design, creating designs that make the client happy, are worthy of the web agency’s portfolio and any web design showcase site.

Web developers

Web Developers want to use the latest technologies in order to implement the most efficient solution possible and keep the web agency on the cutting edge of the industry.

Web project clients

Clients want to receive a website that is as future proof as possible and facilitates them being able to achieve their short and long-term business aims. Unless otherwise informed, they will assume the website has been built to excellent standards but probably won’t care what doctype has been used so long as it looks and works perfectly for their users.

Web project managers

In the middle of everyone is the Web Project Manager, and he or she will want, and often be expected, to meet ALL of the expectations above. But if you work with other Web Project Managers they will want your project to run on time so that their own projects can also be on schedule.

Web Project Managers: In the middle of everyone

Cool, that’s everyone nice and neatly packaged and stereotyped, so why is it not always possible to please everyone, and as a Web Project Manager, how can you try to make sure everyone’s as happy as possible?

Consider, analyse and communicate

It is vitally important to understand that, in most cases, everyone’s intentions are good! They are always geared towards delivering a great project and growing their companies!

Understanding this first fact is crucial when you’re being pulled in every direction trying to keep people happy. Failure to understand this results in a very defensive posture when challenged and that usually leads to bad things.

When you have to make a web project decision the key is to always:

1. Consider everyone’s perspective, goals and motives
2. Analyse and make a decision
3. Communicate why you made the decision

This sounds simple and thus you would think it easy to articulate in a paragraph, but after trying to do just that and failing quite dramatically, in much the same way as Greedo tried to apprehend Han Solo, it seems best to illustrate the point using a few scenarios Web Project Managers face every day.

Greedo apprehending Han Solo #fail

Developer: “Let’s use a new technology”

You have the client requirements, you communicate this to the development team and you hear the phrase you know both excites and scares you…

“We could use [insert_new_web_technology_here] for that feature.” – It’s time to and make a decision.

The first step is to consider why the developer is suggesting to use a new technology as opposed to the one the agency has experience using – it will generally be for one of the following reasons:

1. The new technology has the potential to be far more performance efficient than the current one
2. Using the new technology will mean less repetitive work in the future
3. The developer fancies trying out (playing with) the new technology

Next a Web Project Manager should analyse if using the new technology is a decision that will improve the project, web agency and/or client’s chances of meeting their business aims.

To do this it is important to make sure you fully understand the technology in question so you can assess the potential benefits and risks.

In order to make a decision a Web Project Manager needs one or all of the following because ultimately you are 100% responsible for the project’s outcome:

• Experience in the technology being put forward as a possible solution
• The aptitude and willingness to research the proposed solution
• Absolute trust in team members to make the right decision

Once you understand the technology, assess it against the project and decide if the long-term benefits justify going for it and then communicate your decision and reasons why to your team.

If you choose to go for it then you should communicate the possible benefits of using it to your boss and add the caveat that it is adding a certain risk to the project and thus could cause some overrun. Of course you may be overruled, but if you think it’s worth it, put your case forward and do everything you can to make sure the benefits are clearly visible.

If you choose to reject the idea you should do more than just say “no” to the development team, instead communicate to them the reasons why you are making this decision, which could include:

• Using the new technology brings too much risk to what is already a fragile client relationship that needs complete stability right now
• You feel the advantages of the new technology are not strong enough when compared to the current stable one you use
• The new technology is not mature enough to be used on a high-profile site
• The cross browser compatibility is not broad enough to warrant use
• The project budget is already extremely tight

It’s quite possible that, even after explaining your reasons, team members will still be unhappy and you will get the shaking heads and sighs that translate as “This Web Project Manager is really stuck in his ways and is holding this agency back technically!” It’s at times like this you just need to have a thick skin and have absolute conviction in your decision.

As I’ve said before, as a Web Project Manager you are responsible for the entire outcome of the project and thus the client satisfaction, deadlines, budgets, agency cash flow, reputation and whole host of other business critical factors – the technical solutions provided are the complete focus of the developers, but in the grand scheme of things only one part of many and you are the one with the complete overview.

Communicating this to the development team regularly will hopefully raise their awareness to this fact and make them more commercially aware, and that can only be a good thing for any web agency.

Always playing safe

As a little side note however, making the ‘safest’ decision is not always the best move, sometimes it’s best to just go for it even if you think the chances of success are smaller than you’d like…

This is how web agencies move forward, by occasionally throwing caution to the wind, taking risks and pushing the boundaries! If it works, you and your team are great, if it doesn’t, blame will be laid squarely with you – but hey, as a Web Project Manager you should be used to this situation right ;-) and better to have given it a go than always play safe!

MD: “Why are we going over budget?”

Oh the words any Web Project Manager fears… it inherently is coupled with the assumption the project has been managed poorly and thus you should be hung, drawn and quartered. On some occasions this is exactly the case and it’s best to just admit it, learn from it and try to make sure the same mistakes aren’t made again – it happens to us all, its how we become better.

However, on the odd occasion a Web Project Manager has consciously made decisions that they knew would cause the project to overrun, but in doing so have achieved, or gone part way to achieve, a web agency’s business goal that aligns with the long-term strategy.

Examples of this include using web project tasks or phases to:

1. Train a team member in a new skill and/or give them experience
2. Develop new web project management processes
3. Create a stunning agency portfolio site
4. Develop a new re-usable plug-in for a CMS
5. Make a very important client very happy

Of course an agency would ideally be able to satisfy all of these requirements on a regular basis within project timelines and budgets, but let’s face it this isn’t always possible so you have to grab any opportunity you can and go for it – remember, over budget doesn’t always mean zero profit.

The important things are to consider if this is the right task, project, client account or time in the business’s life to go over budget by using your knowledge of all four to analyse the best course of action.

If your analysis leads you to the conclusion it is worth it, then communicate to the big boss man (or lady), preferably before you announce the decision to the team, that this is why you went, or are heading, over budget on this particular project, but, the agency now has a:

1. Trained up team member who has a new skill that can be utilised on future projects
2. Happy team member who feels they are growing in experience and skill
3. More refined and efficient web project management process
4. Website or web application that will ‘wow’ potential clients and makes the whole agency proud
5. New, or vastly improved, CMS feature plug-in that can be deployed in minutes rather than hours
6. Great chance for repeat account business and glowing referrals

If you can communicate the reasons you made a decision that meant your project overran and demonstrate that it will provide a potential viable amount of return on investment, more than the over budget time spent, you should get the thumbs up and it’s full steam ahead.

Even Stormtroopers had to demonstrate ROI

Client: “I want to add a new feature”

Words from a web project client you could almost bet your life savings on hearing at least once per project and after all functionality has been agreed upon and budgeted for in terms of money and resource allocation.

However, in order to shy slightly away from the traditional Waterfall project management methodology, a Web Project Manager’s response to requests like these should never be an instant “no” because a specification has been signed off for several reasons:

• They could have additional budget and be willing to extend the project’s timeline in order to fit the new feature in
• Other parts of the project may be ahead of schedule and under budget, leaving room for additional work
• They may be willing to sacrifice a previously agreed feature to get the new one in
• There may be an alternative and quick to implement solution that will see the same aims achieved
• The feature in question may be one your web agency have been thinking about developing before to sell to other clients
• “No” should only ever be the words you use if after analysing the request it is deemed in no way possible

Before making any decisions a Web Project Manager should first consider why the client is asking for this feature and why now.

The common response to these requests is to huff and puff about how typical of a client this is, assume they are being cheeky and trying to squeeze the web agency as much as possible etc. But, for the most part, clients are savvy business people who know their industry, market and target audience better than you and thus the late feature request could well be a reaction to something happening in their field that makes a seemingly daft request quite a sensible one.

Start by having a discussion with the client about why they want this new feature, more importantly what business reason or web project KPI they feel it will help to satisfy.

Once you have fully considered why the client has made the request, the next step should be to analyse if the new feature:

1. Will help the client’s business or project aims
2. Can be completed under the current budget, timelines and required resources are available
3. Would require additional budget or timeline extension
4. Could be re-sold to other clients

Once you have analysed the information and made a decision, you should then communicate it to the client.

If you decide to allow the feature in the client will be over the moon and they’ll love you to bits, sweet.

If you decide that the feature should/will not be allowed in, then you will get a mixed bag of reactions depending on the client, but how you communicate this decision can influence the reaction immensely!

Take the client through your decision making process step by step, explain to them the hours you estimate the new feature would take just cannot be accommodated unless they agree to provide further funding or sacrifice another project deliverable, or how the feature would probably not in fact achieve what they would hope it too – the more transparent you are about your decision making process when communicating the decision, the more understanding you’ll generally find the client to be.

Learning how to say “no” to a client is an art form for most Web Project Managers.

Guaranteed happiness for one and all?

Web Project Managers are constantly pulled in every direction by everyone – they are always in the middle of everyone and their priorities. It requires a great deal of strength, understanding and negotiation skills to be able to deal with these pressures and end the project with all parties feeling positive – remember Web Project Managers’ motives are also always focussed on delivering value, not only for the client, but their web agency as well.

By following the consider, analyse and communicate decision making process during web projects will not always result in happiness for everyone involved, but being honest and transparent about how you reached the decision and why you believe it is the right one for the project, web agency and client should go some way to reducing any friction that could be caused otherwise.

What tips do you have for keeping everyone as happy as possible when making web project management decisions?