Balancing the Soft and Hard Skills Needed to be a Creative Project Manager

Let's talk about the basics of what it means to be a creative project manager.

If you've already cruised this site, I hope you get the idea that how organizations define the role and title of project managers can be very different. 

What your job description entails may also be very different. You may work in small or large teams, manage the client, or just production or projects end-to-end. To be a project manager in the big sense of the word, and not just a traffic manager your duties will most likely range from creation to management of scopes, budgets, timelines, resources (people and objects) and project goals. 

However, no matter where you stand, if you have the title of project manager or not, if you have project management responsibility, then you are a project manager.

For me, a project manager can handle the basics of building a project, estimating, handling a schedule and moving things along. These are part of the core competencies that we talk about in other parts of this site. (see the article on producers vs project managers for more info). 

A good project manager has the technical knowledge of the subject matter at hand, or the ability to navigate that gap. They have both the soft people skills and strong hands-on skills for managing projects.

Over the past several years there has been great debate over how technical a project manager needs to be in order to run projects that they may not have worked on before. Certainly you need enough knowledge to properly do the basics. 

The truth is, this happens all the time. Technology changes. Would I ask a broadcast producer to run an application development project with scrum methodologies, if they've never done it before? 

Yes and no.

It depends on the individual, and how much time I (or you would) need to invest to train and support them through the project. Project managers pick up a lot of specific technology knowledge by doing, asking questions and quite frankly failing. As a project manager, you only know what to do, by knowing what you shouldn't do and applying it. 

Almost nine years ago, I had a production manager who never spoke to a photographer or illustrator. In a safe environment, I supported that person in adding art buying skills and on-set producing to her arsenal of knowledge. Now she's running production and art buying at one of the top creative places in the country. 

She had kick-ass soft skills and could learn the technical aspect. A large aspect of being a great project manager is having solid people skills. You can have the technical knowledge, but if you can't work with or manage people, its going to be very difficult to get your project completed.

That's what makes a great project manager. They learn as much as they can, they ask a lot of questions, and in the process learn a whole new set of processes and procedures that they can apply for the next project. Managing creative projects means you are never going to stop learning something new. 


One of the things I learned early on in my career, was that there are always going to be things you can't control. I may raise an eyebrow, but I'm not going to go ballistic on anyone. 

As the receiver of some crazy things in my career, I've learned that internally I may get a little freaked out about something, but you shouldn't let the "hiccup" distract you from focusing on the outcome.

Not everyone communicates the same, some people are brash, some people you need to pull every detail out of them, and others leave you guessing. 

The fact is, is that any project will fail without people communicating with each other. How people communicate is different. How you need to react to them so that both of you are being heard is going to be different as well. 

Communication means nothing without generating understanding. 

This goes not only for how you communicate interpersonally, but with the team itself. As a PM the first rule of the road is establishing how the team is going to communicate with each other. Are you going to use Basecamp, google docs, Invision, or a scrum board? 

However, don't confuse the tool as a replacement for proper communication. We talk a lot about process on this site, but here's something I can't stress enough. When it comes to communicate with each other in teams, its not the tool or the process that fails. What fails is that the team doesn't commit on agreeing on a communication structure that works for everyone.

As a project manager you can not always dictate best practices. Because your project may require critical thinking and decision making that wipe out that best practice from the face of the earth. Some projects and groups of people require different strategies for communicating so the project becomes successful. 

Now, from an operations guy standpoint that might seem extreme. And indeed, if your project goes off the rails, the first thing your boss is going to point to, is that you failed because you didn't follow company-wide standards.

The thing is, process in an agency is a baseline. You still need to follow the basics. But making process your own and making it work for your team is really key. If you get to know your team, and put a plan in place that involves them means people buy in. That's what its all about, getting your team to communicate on the same page, making them comfortable enough so that they communicate with each other and deliver on your project.


There are a bunch of templates on the site for developing a project scope. In creative land, where there are a lot of deliverables to a client, having ownership as a project manager of the project scope is the most important business factor to successful projects.

As a project manager, you need to have the ability to scope a project, which means you need the responsibility to determine costs, resources and timing. You also need to have your team members buy-in and agree to the scope as well.

It doesn't matter if you are running a traditional project as waterfall or agile. A project scope puts the project in a container of understanding between you and the team and you and the client.

It also guides you when stuff goes wrong or if the project goes off track or out-of-scope. Your corrective steps should be in the signed off project scope. Your first line of defense should be spelled out in the scope of work, and as a project manager, you should own what to do at this stage. That's not to say you don't always raise your hand and ask for help with a challenging situation. 

It means that you have and take ownership of both the success and failure of the project at multiple levels. 

You own it — and — your team owns it.

Project Ownership

Owning a project means taking responsibility for setting and managing expectations, both with your team and the client. The scope-of-work, is one of your main tools to set those expectations  and rules of the road for the project. I highly recommend that you do a scope-of-work and get client and team sign-off for every project you start. It doesn't matter if your firm is project based or under a retainer.

A scope of work documents what's going to happen, what will impact the scope, timeline and necessary resources. Even in an agile environment, where you are a product or program manager setting expectations and building backlogs, a scope is still important to build and create, even if your not using deadlines that are waterfall in nature. 

Having ownership of a project doesn't mean you are the only owner. Project managers should never become project dictators. You need to know when to involve your team in the decision making process when it effects the team. Here's the thing, as a project manager, you may have built the scope, budget and established guidelines, but project ownership is shared by the team. Bring your specialists in and let them answer the questions. Your job is to help the team accomplish the work, to act as a conduit for questions. 

When asked, if you don't have answer for someone that you can easily answer based on the scope and budget, tell them you'll get back to them after you talk to the team.

Team Management = Team Support

Part of what makes a great project manager is the support they give to the team. More than likely you are the person who helps the team overcome obstacles and helps push the process along. More than likely, your team members are communicating and solving problems of the project within the team itself, without having the support of a larger functional department.

While you aren't the team's boss, you are the closest they have when it comes to support. You are the one that can move around and adjust the process so that your team can be successful. You are the person who sets the stage for how the team treats each other. How you behave and react should be in support of both the team and the project. What makes a great project manager is knowing the basics, but engaging the team and supporting them.

Learning never ends, become a critical thinker

Once you understand the basics, you can apply it to new types of projects. Being a project manager today means that what you are working on today is probably going to be different than what you are working on tomorrow. 

If you are going to stick it out in the creative field (or almost any career!), you need to embrace life long learning thinking.

Never stop ask questions. As a project manager, you have an enormous opportunity to observe and ask questions. It is this learning that will help you become better at managing something new. Don't be a pain in the ass if you don't know something, but look to build opportunities where you get to know a new role, or make connections with the team. The best project managers have the ability to see things from multiple perspectives. To think about how a team member might perceive information from their own view. 

The more knowledge you gain about other views, the easier its going to be to communicate and anticipate questions, anticipate resource needs or build a project scope.

One of the reasons I started this site long ago was to share my perspective on process and how people may approach project management. Because I learned early on that if I understood the process of how the place works, I can better strategize with my teams and clients to find alternate ways to make process work for them and their projects.

While I don't have every process I ever built on this site, I do use the things I have done in the past in order to continually improve. This is something that every project manager can do on their own. As you gain experience in project management, you are going to build up a history of documents and methods that work best for you.

The first thing I ask for when I go into a new agency or creative firm is to ask for examples of their SOWs, estimates, schedules and any other project based material. Since where they are in the creation these types of materials, tells me where they are in their history of developing project management. 

As a project manager, build your own history that's readily accessible that you can repurpose. As a project manager, building up a history of templates and examples of former projects will help you cut down the time to build out a new scope.

I think this is why we find software or cloud-based project management systems important to the way we work. If I can run through a project, its history and its metrics, than I can build a better informed estimate and SOW.