lucjan-pic2Today’s guest post is by Lucjan Zaborowski.

Project prioritization sucks.

This is a frustration shared by both technical and non-technical teams.

However, mastering prioritization is crucial to successfully working with your developers because it is vital to their workflow.

So if you’ve caught yourself saying, “Why won’t the tech team push my marketing campaign live?” while overhearing an equally frustrated tech team say, “Marketers do not understand the process!” – LISTEN UP!

Prioritization does not need to be painful – we CAN stay sane while working with our tech teams. The trick is embracing project prioritization and knowing how to effectively communicate with more analytical minds.

Below are tips for effectively working with your tech team.

Follow them and you may find your marketing projects finally getting prioritized and launched within a reasonable turnaround time.

Build Trust

The relatively new mantra in marketing is to build trust with your customers rather than simply try to convince them of the superiority of your products and brand. This strategy also applies to your internal company relations. If you want the tech team to “buy” your idea as a project they should prioritize, you should gain their trust first.

Here are a few ways you can build trust with your tech team:

  • Invite members of the tech team to marketing meetings. This keeps them feeling included and updated on your project plans. It also leads by example: Include them and it is likely they will start including you.
  • Send regular emails to the tech team with updates on marketing efforts. This encourages communication, and allows the tech team to prepare for potential questions or problems.
  • Learn and use the tech lingo. Consider asking a tech team member to give your marketing team a lesson on basic tech terms and jargon. Try to use tech terms when communicating with developers. This will help you avoid sounding ignorant and losing the ability to influence their work.
  • When something goes well, celebrate together. By celebrating successes together, you are communicating to them you value their participation in your projects.

Agree on Collaboration Best Practices

It is much less stressful for marketers to work with tech teams if they use the same tools and processes. Make sure your teams are on the same page.

Discuss the use of project management software: Web developers use project management tools that allow them to collaborate on code they create. GitHub and BitBucket are some of the most common. However, these tech-oriented tools can be difficult to follow by less tech-inclined members of marketing teams. If possible, propose both teams use a simple project management tool, such as Basecamp.

Propose putting all prioritization decisions in writing: It is easier to avoid frustration, if all decisions can be tracked back to a specific time and stakeholders. You can suggest putting everything into emails or shared files accessible online. For example, use Google documents.

Recommend designating a prioritization owner: In Agile, the product owner is the “go to” person for prioritizing development tasks and it is likely the tech team already has a person like this. However, product owners are limited in their scope to a specific product being developed by the tech team. A prioritization owner, who keeps tabs on all projects in the organization, is of great assistance to marketers, who depend on techies picking up their projects.

Prepare a Project Prioritization Brief

Outline your “selling points,” which in the end should show the exact requirements of your project and the value it will bring to the company.

A clear description of the campaign and the resources you are asking for will show your tech team exactly what you need to execute the project. To include that “how this adds value” portion to your brief, include the following criteria for prioritizing projects:

Return-on-investment: How much financial return will the project bring for the amount of investment made?

Budget: What will be the project cost be and how high are the risks of overrunning it?

Human resources: Are there enough people with the right skills available?

Technology: Will the new technology offer long-term value and will it be useful?

Organizational priorities: Is the proposed project consistent with short and/or long term goals of the business?

The above five themes address concerns management and tech teams will likely have in regards to your project. Beating them to the punch will show you think like them, which will be good for the working relationship.

These answers also help the tech team assess if it should classify your tasks as high-priority, as tech team members usually works closely with the company’s decision makers to determine overall business priorities.

Finally, a brief will ensure project items are properly organized for the tech team, which ensures nothing is lost in translation during the transition.

Show Project Collaboration Evidence

A brief isn’t enough. In order for your prioritization brief to be convincing, you need to back your declarations on ROI, resource requirements, and organizational priorities with data.

Hence, before sharing your brief with the tech team, decide if you have collected enough data to support your claims.

Answer the following questions:

  • Did I include data from Google Analytics, Omniture, or another marketing product that my company uses?
  • Did I find publicly available resources (data from organizations or educational institutions) that help build my case?
  • Does my organization have an internal database, which contains “lessons learned” from previous projects, and did I use that information?
  • Did I use sales data or the company financial statements?
  • Did I consult an expert in the particular field?

If you answer “no” to most of the above, you may need to conduct primary marketing research to support your propositions. Of course, primary research can take a lot of time and resources. Carefully review how much time and money you can spend on research and get an approval from higher ups before taking this route.

Despite an often less than perfect relationship, you can in fact stay sane while working with tech teams. Just remember the end goal is prioritization.

Just remember, if everything else fails and tensions are high, resort to humor. After all, it is the language we all understand.

Lucjan Zaborowski is a marketing consultant at Simply Business, advising the company on online optimization and user experience projects. He has worked with firms in the United States, Poland, and the United Kingdom on growing their online presence via lean strategy. Lucjan holds a master’s degree in International Marketing from Boston University and is also a certified project manager with extensive experience in supporting large scale IT deployments for companies such as Dell, IBM, and Microsoft. Follow him on Twitter @GOcontent.