The five superpowers of a project manager

Bagsy Iron Man
Bagsy Captain America

I’ve been reading a lot recently about what makes a project manager – in particular, what makes a digital project manager. The best, I believe, have a set of superpowers that make them the perfect choice to manage projects. Here are five incredible superpowers you need to possess in order to become a digital project managing superhero…

1. Alter Egos – aka Tough and Vulnerable

Yes, you walk through ‘delivery’ walls. You never leave a co-worker behind. Your will is both iron and legendary, baby. Yet there’s a softer side. You make mistakes, you admit to them, you learn from them. You’re happy to involve others because you don’t have all the answers. You don’t flaunt your alter egos, but once in a while you show people you are for real – you take a bullet for the team or lift your shirt to reveal a hidden wound.

2. The Chameleon

You have a magical, highly developed ability to change. Your viewpoint, your worldview, your tone, your behaviour. You move from one environment to another with relative ease, from one audience to another, from one project to another, changing to suit the scene. You are accepted by any and all groups. You blend in.

That's you, that is
That’s you, that is

3. Flexible Thinking

You can adapt what you’ve learned in one area and apply this to another. You see dead people patterns everywhere. You can unlearn, let go of old ways of doing and thinking, and consider a new approaches. You use this power to foster creativity and improvisation. You know there’s more than one way to solve a problem, and you switch strategies to meet different types of challenges.

4. Intergalactic Communicator

Your silver tongue, quick wit and dazzling drafting skills are incomparable and out of this world. You speak and write in many languages – business, marketing, sales, design, programming, content and, most importantly, client. From small talk with coders – I know – to charming clients, you’re comfortable communicating with all walks of life. You know when the devil is in the detail, and when to be direct, like a mother funking laser.

5. Likability

Never underestimate the power of likability. You know this. You’re naturally curious about what makes people tick, and you always take time to find a connection with others. You charm, seduce, flatter, tease, cajole. You are fair, objective, inclusive. You buy the first round, and the last. You stand up for what’s right, you believe in the truth, you respect and accept people and their differences. You supply cake. And for this, people like you – and want to work with you.

Why do people like you? Because you're worth it
Why do people like you? Because you’re worth it

Remember, DPMs, with great power comes great responsibility, so make sure you use your powers for good. Got to go now, my sixth sense is a-tingling.

The Humble PM

Three little words…or how I will roll in 2016

About this time each year, I pick three words to act as goals to guide me through the next twelve months – I like to wait until the NY resolution craze dies down. Now, then, I’m not usually the sort of chap that goes in for new age business thinking. It’s mostly instantly forgettable cheap talk that’s unceremoniously dumped, like an unwanted puppy, when the next ‘thing’ comes along. This exercise, however, is useful mainly because it is easy to do. It does not require a great deal of thinking.  It keeps your mind on your priorities. Heck, just writing three words down is more than most of us do goal-wise, and we wonder why we list, drift, and lose focus.

But I digress, back to my three words…

Here are my picks for this year.

Plot

Storytelling, not shopping lists

A sequence of events, not a secret plan to blow up parliament. To focus on interrelated sequences, the storyline, if you will, rather than thinking in terms of shopping lists, of individual tasks. Explaining what I do, what I can do, what I will do, through storytelling, told as stories. Ultimately, that’s what people want to hear, what they can relate to and, eventually, believe in.

Rewild

Return to a natural state

When we operate in a world where conflict is seen as a bad thing, and questions are challenges to authority, we become domesticated.  We think in straight lines to survive. That was my 2015.  With batteries fully charged, I’m now ready to return to my natural state. The one that’s a positive force, a catalyst.  And it’s time to reboot my agile state of mind – to seek the truth, accept and respect others, show humility, be patient, revel in self-discipline and sow commitment.

Write

The medium of human communication

As much as I worship at the altar of doodling, I need to write more often. When I do ideas form, float, merge, and evolve. My thoughts become tangible, they move away from the light. The pleasure I get from writing, work or otherwise, is immeasurable, so there’s every reason to put pen to paper, digit to motherboard. And as an avowed disciple of speed writing this really ought not to be a problem. This post is part of that goal.

My challenge, then, is live by these goals. I carry a note pad now so that I can write storylines, capture narratives. The pad has my seven ‘rewild’ watchwords (emboldened above) nestling inside the front cover. And, dear reader, I can jot down little pieces of fiction, or fact, as I go about my day.

And so far I am winning.

The Humble PM

Ps Isn’t it time you set a few goals?

If no one methodology fits, create a new one

This is rule four in my *Code of the Project Manager* series. And just a couple of minutes to read. What a time to be alive!

Before I start this rant post, let me be clear about what I mean by a methodology.

The way something is done, a way of working, methods and principles.

I’ve highlighted the most relevant bit for me, so you know where I’m coming from. Project management is a way of working based around organising, scheduling, building, managing, controlling, tracking, communicating, learning and sharing. There are established ways of working – from waterfall through to agile. There is no right answer, however, in my opinion. Were bombarded with articles on which is the best, the most efficient, the most productive and so on. It’s my belief that the right way of working is the one that best fits your work culture – the beliefs, values and behaviours that create the environment in which you work.

Allow me to explain…

Three times in my working career, I’ve had the pleasure, sometimes dubious, of introducing a project management methodology across the company. Each time, I’ve looked at the company culture to identify what is most likely to succeed. For example, an organisation with a rigid hierarchy that operates along straight lines is never going to go all in agile-wise. Conversely, a company that embraces an almost collegiate approach to work is not ready for PRINCE2. Instead, I’ve looked at combining elements of different methodologies – ways of working – to create something that best fits the culture. That could be using RACI to define roles and responsibilities. It might involve drawing a visual representation of the project cycle on a wall so people could see it as a whole – and using this to record issues, decisions and lessons as they arise. Projects may have mini teams, run by team managers, to deliver each product, coached by the PM. We may choose to define requirements as User Stories so the team can see the whole picture. Perhaps we want to ‘Manage by Exception’ and we’ll inform the management team if anything goes wrong, along with a plan to fix it, otherwise we’re trusted to deliver. Team managers might run daily catch-up meetings (SCRUM style). As PM, I could run a weekly lessons learned meeting to share lessons and ideas to improve our work. It might be prudent to have a few simple templates for key documents based on what people will actually complete. We may need somesimple rules or a code that we use hold each other to account, and a set of defined terms so we all speak the same language. We may use sprints and involve the customer earlier on in the build process. Who knows?

YOU KNOW, THAT’S WHO….

So think beyond what you are told to do. Be pragmatic. Borrow, nay, steal the best approaches to form your own way of working based on the unique set of factors and people that create your company culture. And you decide what fits best.

Cheers,
The Humble PM

Create a common language to define what you will deliver

This is rule four in my *Code of the Project Manager* series. And just five minutes to read. Enjoy!

If I were forced to rank these rules, then this rule would be top or thereabouts.  Using a common language to define your products and services, the documentation and tools that enable your delivery and your project roles and responsibilities, is key to successful project management. To do this, however, you first need to create the common language. How, you ask?

Allow me to explain…

The Glossary

The first step is the construction of the glossary, an all-powerful document rather like the bible – but with fewer pages and slightly more serious in tone.

The first section should cover products and services. This should include the labels, terms, summaries and descriptions you use to describe your products, and the constituent components that make up your service(s). I’d suggest adding the version number, the estimated time to build and links to other products, too. Finally, list the product champion/owner and subject experts for each component, product and service, along with any training materials.

Section two covers project management terms such as benefits, business need, risk, issues, assumptions, decisions, lessons, success criteria, UAT, change and so on. This should be complemented with descriptions of each project document, template and tool you use – such as what we mean by a business case, project brief, project plan, team plans, the various project logs and project reports.

Section three covers roles and responsibilities. What we mean, for example, by the project board, project sponsor, account manager, project manager, team manager, team member, lead developer, lead designer, product owner and so on. And their responsibilities so there is no unintended crossing of boundaries or inadvertent land grabbing. If you’re feeling on a roll, or just plain crazy, you could knock up an RACI document for use across the company.

NB: If you really want to supercharge your project management, you could record lessons learned, issues and risks against each product, template and role. Now that’s powerful stuff right there.

The Documentation

Step two is the construction of a library of project documentation. Master templates should be created for all standard documents, along with an explanation about its proper use and an example of what is required for each section.  Again, I’d recommend you list subject/domain experts for all templates.

The benefits

This is not an insignificant piece of work, and it will require the cooperation and involvement of pretty much every team in the company, BUT the benefits are HUGE!

  • Everyone using the same labels and terms to describe a product, or its constituent components when creating plans, writing documents/logs or managing delivery. Means you are always taking about the same thing, even account managers, sales people, biz dev folk…
  • Project management is at once demystified – no excuses now…
  • Clear roles and responsibilities mean processes, activities, people, and so on mesh seamlessly, with no overlaps
  • Consistency of approach and timings for what you build
  • Pulling together proposals is far easier with pretty much everything you need predefined/documented
  • A learning resource that can be used by everyone in the company – from new starters to people switching teams
  • Easier to share knowledge – with named experts who can deliver training, answer questions and share wisdom

There are a few short cuts you can take. Lift existing definitions for project terms, roles and responsibilities off the web and adapt these to fit your company. Start the glossary off as a wiki and build from there.  Appoint Admins/SMEs to oversee its development – if it’s not up to date, it won’t be used. These duties could be linked to specific roles, be part of ongoing staff development, the recognition of skills and/or knowledge. Consider Gamification if that suits your company culture. Just do something.

In the end, having a consensus will make the real difference, with everyone speaking the same language. Imagine that.

All projects are created equal

This is lesson three in my *Code of the Project Manager* series. And it’s a short one, too. Enjoy!

*All projects are created equal; that they are endowed by their sponsor with certain unalienable rights; that among these are management by exception, signed off requirements, and the pursuit of learning lessons*

Thomas Jefferson

Ok, I have paraphrased Jefferson, but projects, like people, are created equal – or ought to be.  This is self-evident in my opinion. The same rules. Same roles and responsibilities. Same processes. Same common language. Same learning of lessons. Same risks and issues management. Same set-up and planning. Same documentation. Same sign off procedure. Same monitoring and reporting. Same project close.

You get the picture…

And the SAME applies to your professionalism, your values, how you manage, how you lead, how you treat others. This is about having the right mind-set, as an individual and as a company, and leading by example, setting an example to others, setting the tone for the organisation… I could go on.

Yeah, I know, you can’t do this on the smallest projects, and bigger projects are our priority

Rubbish, I say. You adapt the approach to suit the project. That’s a fundamental rule of project management. And if you and your company roll this way, let me let you into a little secret: you’re demotivating those people working on smaller projects, which is a big problem. This is a slippery slop, and standards will slip, trust me.

In case you still need convincing…

Small projects can lead to much bigger ones, if delivered successfully. And smaller projects are where PMs cut their project teeth, earn their management chops. Think about that for a moment. It really could change the way you work.

The Humble PM

What can Socrates teach us about Project Management?

What can Socrates teach us about Project ManagementThere once was a bearded, ungainly man, that the Oracle of Delphi called the wisest man in Athens. His name was Socrates, and he wasn’t happy with this accolade. ‘I know that I know nothing’ he declared, and he set about proving the Oracle wrong. While this did not make him popular – it led to his death – it did mark the birth of Socratic questioning. This approach focuses on asking critical, systematic questions to achieve a goal by way of a dialogue – in Socrates’ case, that he was aware of his own ignorance. We can learn from this approach in project management, too, in my opinion.

*What?*, I hear you say. Pull up a chair while I explain.

This approach dictates that we should not assume that we understand what our clients need – or that the client knows either. That understanding is achieved by asking questions, not answering them, through an ongoing dialogue. That we examine and challenge all assumptions, always asking why. That we dive beneath the surface, cultivate deeper understanding, assess the plausibility of things, and force all concerned to think. But I digress…

How does this work in practice?

In the example below, I’ve adapted this approach to project start up, when we ask what problem we are trying to solve for the client. Remember, you’re challenging the thoroughness and accuracy of the client’s thinking, so put your hard balls away and be patient.

1) Clarify the problem

Start nice and gently. Tone here is critical. Think Martin Bashir interviewing the People’s Princess.

Typical questions: What is the problem you are facing? Why do you think this is happening? What needs to be fixed? Why do you say that? Could you explain further?

Here are a few real world questions and answers to give a bit of context:

What is the problem you are facing? *Our online sales are very low*.

Why do you think your online sales are low? *Our website is not great and we think it puts people off*.

Could you explain further? *The Shopping Cart is very clunky. It takes several clicks to buy a product*.

And so on.

2) Challenging the assumptions

Now we probe the client’s assumptions by gently digging into the reasons behind their thinking, by not accepting it as a given, and by considering exceptions. Tone: think Pamela Stephenson, not Frazer Crane.

Typical questions: Why do you think these assumptions hold here? How do you know this to be true? Can you verify or validate your assumption? Are these the only explanations?

Real world examples: Why do you assume the shopping cart is the main barrier to online sales? Can you verify this? Is there any other explanation for low online sales?

3) Probing the evidence

Now we help the client set out their supporting evidence for the cause of the problem. This is cross-examined in a nice and friendly way. Tone: think Oprah, not Jeremy Kyle.

Typical questions: What tells you your assumption here is true? What evidence is there? Is there reason to doubt this evidence? What do you think caused this to happen? Has anyone else expressed a different opinion? Why do you think that is?

Real life examples: What tells you the Shopping Cart is the main problem? Does your customer feedback and data to support this? What caused the website to end up this way?

4) Establishing alternative viewpoints and perspectives

It’s time to look at other perspectives to show the client that there are equally valid viewpoints. Tone: think exploring the benefits of tidiness with your *creative* other half.

Typical questions: What is another way to look at it? What would be an alternative? Does this seem reasonable? What are the strengths and weaknesses of the perspective? How does *x* compare with *y*?

Real life examples: Could it be that your site is hard to find? Is your site as user-friendly as it ought to be? Is it mobile friendly? Did you have a marketing plan? Could that have contributed to low sales? Do any of these seem reasonable alternatives?

5) Implications and consequences  

Now we probe the implications and consequences of the client’s assumption that we can forecast. Tone: think Kirsty Walk, not Paxman.

Typical questions: What generalisations can you make? What are the consequences of that assumption? Do these make sense? Are they desirable?

Real life example: If we fix the shopping cart what then? What are the implications of focussing on the shopping cart? How will this affect the rest of the site/sales? How does that fit with the alternatives we discussed?

6) Question the business problem

The home straight. Now you can also get a bit deep and turn the problem on its head.

Typical questions: Is this the real problem? Could there be other elements to the problem we need to consider? Does the problem go deeper than this? What should we do with the new information (the alternatives)?

Real life examples: Is the Shopping Cart the real problem here? Could there be other elements, such as a lack of web presence and poor user experience, which are contributing to the real problem? Could there be a deeper problem, such as the product strategy? What does this tell us about the approach to online sales?

And now the real dialogue can begin about the true nature of the problem based on a mutual understanding.

So, embrace your inner Socrates* and use this client-centred and inquiry-led approach to explore problems or issues, and to make decisions. It promotes collaboration, helps move clients toward their goals, and makes for a great customer experience.

The Humble PM

*The toga and beard are optional

Always ask why

Kids are born philosophers
Kids are born philosophers

This is lesson two in my *Code of the Project Manager* series. Enjoy!

Always Ask Why*

I love the word why, almost as much as my hero Socrates does – more about him in my next post. Why and I can often be found together, basking in the sun, frolicking in the surf, enjoying quality time. I tuck why up in bed at night because why is one of the key weapons in the project manager’s armoury. Sure, there are other questions, why’s siblings *what*, *how*, *when* and *who*, but why is the gateway to ace delivery. Let me explain why (sorry).

Why is the first question the PM should ask when they start on a project. Why assumes nothing and challenges everything. Why stops people in their tracks, it focuses the mind. Why helps highlight the problem you’re trying to solve. Why provides a glorious opportunity to derive knowledge, to cultivate understanding, to get beneath the surface. Why helps establish that most elusive of things: the business need driving the project. With the business need defined, the PM can ensure they deliver what the customer needs, and never lose track of what is required.

Beware, though, because why is designed to make you and others think.  It can, therefore, be seen as a challenge to authority. It can be taken personally. Remember to preface any why question(s) with the following: the more I understand, the better I am at my job.

So next time someone asks why, don’t take it personally. It could be the start of something beautiful, delivering what you (or your customer) need.

* This lesson does not apply to children. There should be a statutory limit on their use of the word why, IMO…

Why I’m for hire…or why you should hire me

Why I’m for hire…or why you should hire me

hand drawn CV

I left my job. There, I said it. As I’m always open and honest, I thought I should share what happened here…

During my time as Head of Projects, much work was done, and a great deal was achieved. By many, I might add, this was no one man job. We were on a long journey: to create and implement a new project management methodology within the company. We had passed through many stations along the way: indifference, bargaining, acceptance, understanding, commitment and belief.  Our final destination was in sight: Project Nirvana, or super engagement as I like to call it. The highest levels of buy-in, focus and confidence in delivery. We had the momentum. The pieces were falling into place. We reached our last crossroad. I wanted to take the express train, the fastest way to connect to super engagement, with fewer stops to boot. Instead, the company wanted to take the slower cross county route, with several changes, albeit with less risk involved. In my humble opinion, and based on my experience, I felt this was the wrong train. And this was one I could not be the driver of (sorry), so this was my signal (sorry again) to depart (thrice sorry). So there you have it.

We parted on good terms. Nobody got hurt. We move on. Which moves us onto why you should hire me….

‘To make a difference, you need to be different’

Who said that? Well, me. Am I different? I think anyone who has worked with me would say so – and hopefully in a good way. Though I was raised in the House of Waterfall, agile working is in my blood. Mine is a rational and logical PM approach supercharged with emotional edge – that’s energy, passion and belief to you and me. Humour is my weapon of choice to alleviate team stress and to raise morale, and I make work fun even during the dark times. My drive and enthusiasm enable me to gain and maintain momentum when it comes to delivery, and my sometime tendency to rebel means I’m always looking to improve. I make understandable strategy believable, always pay heed to business need, and build relationships based on trust to last. Finally, the team’s needs always come first, and I will sacrifice my own interests for what is right for all. Many would bear witness to that.

Rest assured, I can do the bread and butter stuff, think in straight lines, which is important, but that’s half the story. There’s the side that involves and engages people, the one that stimulates new thinking, the one that challenges assumptions, the one that coaches others to lead. My corkscrew thinking drives me to turn things on their head, to pivot. From creating a common language to improve planning and delivery to using sensemaking to predict the project landscape to my hand drawn C.V. (image above), I have a knack for creative problem solving.

I’ll leave you with this thought. For me, project managers, nay, leaders should be imaginative, resourceful, out of the ordinary and capable of flashes of inspiration. And, as Raymond Chandler once wrote, ‘as honest as you can expect a man to be in a world where it’s going out of style.’ I am all of these things. I think.

Open, honest and ready to talk

Lesson one: 

*Be open and honest, and never shy away from difficult conversations*

Be open

Let me clear. I’m not saying you walk around with the winds whistling through your ears while your brains drip down your shoulders. Instead, open your mind when in project manager mode because a closed mind is an empty mind – or so they say.

Approach your working day with an open mind. Be open to ideas, to solutions, to arguments, to logic, to facts, to people, to new ways of working, to possibilities. As PM, you ought to lead by example, too, and demonstrably give time to other’s ideas. Keep your door open, too, so people can approach you for advice or to raise a concern. Take time to see things as other people do, walk a mile in their shoes for change. Park your prejudices – we all have them, even you – and remember that things aren’t always black and white.

Practice this whenever you can. Take a deep breath. Stand still. Swallow your pride. Be prepared to listen, observe, learn and discuss.

Tips:

  • Hold weekly ‘Lessons Learned’ meetings where each team member talks about what they’ve learned, good and bad
  • Make time to do great things by organising regular team sessions to explore new ideas and new approaches – anything can and should go here. Do this in an unfamiliar setting if you can
  • Look beyond the realm of project management for new ideas. For example, inspired by an article on Leadership capabilities, we applied the principles of sensemaking to improve our project delivery through a better understanding of the context in which we operate

Be Honest

Ah, our old friend *honesty*. Some folk think the truth should be hidden under the stairs like an unwanted child. Not me, although being honest is one of the hardest things to be and do. Most people want something beautiful, not the truth. There are a few exceptions around appearance, dress sense, body mass/shape, cooking, how many drinks have you had, whether you like your partner’s friends, what you’d save in the event of a fire (I’m very fond of my snow shaker collection, we’ll leave it at that), things you’d rather be doing, your favourite child and your love of Steven Segal films. But I digress…

The PM’s job is to create the team culture, to show people that being honest is ok and encouraged.  Always be polite, and never raise your voice, as you want to encourage honesty, not force it underground. When honesty goes to ground, prevarication becomes infectious, obfuscation spreads and, before you know it, obscurantism takes hold. People start to diddle. Hoods are winked. You may find yourself taken for ride while someone gently pulls the wool over your eyes. It may even give rise to hornswoggling – happened to me once, but that’s another blog. This can all be prevented if you make probity your watchword. Show your team you have principles and high standards. If you don’t know the answer to a question, say so. If you cannot deliver a work package on time, say so. If you disagree with an approach, say so. If you need more resources…well, you get the picture. Wear your thoughts on your sleeve and others will follow.

Tips:

  • Make clear the inextricable link between honesty and learning your lessons, where being honest can solve future problems and improve delivery. If your team see being honest as an integral part of the project approach and process, they are more likely to embrace it
  • Don’t over-promise. If you’re always honest about the status of the project you’ll eventually get – in the words of the late, great James Brown – the big payback: TRUST
  • Don’t have secret meetings, never have an inner-circle, keep your team in da loop

So, people, plant the flag of honesty, raise it high and give it a resolute salute daily. People will respect you for it.

Difficult conversations

Honesty and difficult conversations are very closely related and are often joined at the hip. One tends to follow the other around, so be prepared.

Now, no one enjoys difficult conversations, but let’s get some perspective here. You’re not telling someone they have weeks to live, telling your adversary you’re their father or finishing a long term relationship. So get a grip, and don’t procrastinate – putting off a difficult conversation is an excellent way to induce insomnia and stress.

The conversation should be done face to face, or at least by phone or Skype – no emails! Think of all sides and perspectives to the conversation. Collect your thoughts and rehearse your view, but be prepared to see where the conversation takes you. Be open and honest during the discussion, and agree the outcome, including any decisions, with the other party/parties. This should be noted and shared with all concerned afterwards – let there be no doubt.

There is no right or wrong in terms of the outcome here. Sometimes it’s just about clearing the air, finding common ground or agreeing a plan of action. So embrace those tense and awkward conversations, they could save a project, improve customer relationship or win over a senior manager

Quite often these conversations are about saying no, politely and firmly. I’d say think of a compromise you’re prepared to live with, just in case. Battles, wars and all that.

Tips:

  • Be sincere, honest and direct
  • Use logic, evidence and reason to support your view
  • That being said, emotion can play a part here. A heart felt plea can go a long way sometimes if used wisely
  • Remember this is not a blamestorm
  • Try to find a way to link the topic of the conversation to the greater good of the project and the team
  • Record any decisions in your Decisions Log along with the context – the circumstances surrounding the decision – so that you do not dwell on the past

Lesson one over. Phew. The best way to remember this advice is to become a child again. They have open minds. Children take everything at face value without looking for ulterior motives or hidden meanings. And the sense of wonder hasn’t been knocked out of them – yet.

Good luck!

The Humble PM