Marketers Need to Do Less
Conflicting priorities are a plague on marketing productivity. To focus on the right work and say “no” or “not now” to everything else, we need effective workflows, empowered teams, and supportive leaders. If you’re ready to focus, we're ready to help.
Pesky Prioritization Problems
When we try to spread out effort and energy out over multiple priorities, a funny thing happens: all of those things we thought we were focused on take way longer than they should have. Context switching – jumping back and forth between tasks – is the culprit.
Effects of Context Switching
Source: Quality Software Management
How Marketers Can Accomplish More by Doing Less
Instead of splitting our attention over lots of projects, activities, or campaigns, we need to ruthlessly prioritize just the most important ones. This means debating and agreeing with other teams, leaders, and stakeholders on what really matters to the business right now.
-
Get all the interested parties together and put everyone’s ideas out in the open. Brainstorm freely, focusing on the marketing work that’s most likely to support well-known organizational goals.
-
Choose a rigorous approach to determine which ideas bubble up to the top. You don't want to default to choosing only ideas from senior leaders; the best ideas should prevail.
-
Once priorities have been agreed on, don't let them get derailed (unless there's a really good reason). Marketing leaders should protect their teams so they can focus their efforts.
What Is Agile Prioritization?
At its core, Agile is all about working smarter instead of harder. By working on the right tasks at the right times, you’re able to deliver far more value with the same amount of effort. The trick is finding a consistent way to identify what those tasks are. That’s where Agile prioritization comes in.
By applying Agile values and principles to the work prioritization process, you can identify those high-value tasks that will really move the needle for your stakeholders. But how exactly does this work? You can find a more detailed breakdown below, but Agile prioritization starts with understanding what your stakeholders value, alongside your own goals and objectives.
Once you know what you want to achieve, you can begin building a backlog of all the work you could be doing. Then, by applying your knowledge of what you want to achieve and estimating the amount of work required to complete tasks, you can prioritize them based on which will deliver the most value with the least amount of effort.
There are many ways to go about this, various methods of estimating workloads, and even gamifying the entire process. But the core always remains the same: identifying what work will deliver the greatest ROI. Over time, you’ll consistently hone the prioritization processes you use to make that determination.
How to Do Prioritization
in Agile
Now that you have an understanding of what Agile prioritization is, let’s dive into the practical steps you can take to realize its full potential in your organization. Start making time for vital work.
-
Here at AgileSherpas, we’ve seen countless examples of teams seemingly “doing things in an Agile way” without actually seeing the benefits. The reason usually ties back to a lack of a true Agile mindset. With so many different ways to handle prioritization, it’s easy to fall into the “practices only” trap and undermine your entire effort. A solid understanding of the Agile mindset helps ensure your approach to Agile prioritization gets you the benefits you want.
Every step listed below is built on Agile ways of thinking. From understanding your stakeholders, choosing the right objectives, and prioritizing work on a backlog, Agile ways of thinking are fundamental.
Building that mindset takes time, but you can start with simple online learning or instructor-led courses. Then, taking the time to apply those principles to real-world situations on your marketing teams will help solidify them. That may mean having teams practice Agile prioritization with the help of an Agile coach.
However you approach it, be sure to consider mindset before diving straight into Agile ways of working. Be warned: Skipping this step may make effective Agile prioritization far more difficult!
-
As with any practice, trying to implement Agile prioritization for its own sake is unlikely to get you the benefits you want. Why? Because you need to approach the process with a clear idea of what those benefits are to begin with. Otherwise you’re taking a road trip without considering the destination and getting frustrated you’re not getting there.
The first step towards setting Agile marketing objectives is shifting from a focus on outputs to one of outcomes. Launching a set number of campaigns, emails, blog posts, etc. is meaningless unless those actions produce the kinds of outcomes your stakeholders want. Understanding those outcomes by communicating with your stakeholders is crucial for success.
Next, you want to ensure the goals you set are SMART (Specific, Measurable, Achievable, Relevant, and Time-bound). These criteria help ensure the goals you use can serve as an effective north star for your Agile prioritization efforts.
Then, once those objectives are set, remember they can and should evolve when needed. When circumstances change, you should be changing to meet them. For example, if your stakeholders decide on a new strategic priority or if a campaign reaches your intended goals early, you can adapt and set new goals.
-
Armed with a solid Agile mindset and a clear idea of what you want to achieve, it’s time to build a backlog. Agile backlogs are lists of all the work your team intends to do, usually in the coming quarter or so. Those items can be big or small, which is why estimating their size (described below) is important.
Of course, in addition to this kind of team-level backlog, you can have others which encompass longer-term goals for your marketing function or organization. You may have a vision backlog that senior leaders use to track strategic initiatives. From there, backlogs get more granular until you have the task-level backlog used by execution teams.
Once you’ve built this list of all your intended work, you’ve got the raw material needed for Agile prioritization. That process begins in the next step with backlog refinement.
-
Backlogs are great, but without refinement they’re not truly ready for use. So what is backlog refinement? In short, it’s the process of ordering your backlog by priority and adding details to the items as needed.
Because if you’re going to put all the work you have for an entire quarter in your backlog and then add details like who work is assigned to, due dates, definitions of done, etc. much of that information will be irrelevant by the time someone is ready to work on the task. This is why you want to gradually increase the amount of detail on tasks as they get closer to being high priority.
Of course, that requires prioritization. Using your understanding of your team and stakeholders, you should be able to order all the items in your backlog by priority. The idea here is to consider how much value work items will deliver to stakeholders against the effort required to complete that work. You may also want to consider the cost of delay. By prioritizing this way, you set yourself up to work smarter instead of harder, completing tasks that deliver the maximum ROI.
Don’t forget that your backlog should be a living and evolving thing. That means backlog refinement isn’t just something you do once a month or quarter, it should be a regular activity. This ensures your backlog is current and relevant, something everyone on your team knows reflects current realities.
That said, if everyone is able to change the backlog at all times, you’re going to have chaos. It helps to have clear processes for how work items get added to the backlog and taken from the backlog to be worked on.
-
Effectively refining your backlog requires estimating how much work is required to complete a task. The problem is, we’re terrible at doing this. Not we as in marketers, we as in human beings. Even seasoned marketing leaders typically fail to reliably guess how long projects or individual tasks will take to complete. So how can you ensure your estimations are reliable enough to base your Agile prioritization on?
The first step is deciding how you want to estimate: based on the hours a task takes or its difficulty. In general though, we recommend estimating based on complexity as this tends to be more accurate and useful for estimating how much work a team can complete in a set period. Difficulty estimation also accounts for unknown factors better than hourly, as a task may be marked as difficult simply because it’s complex and hard to estimate.
When it comes to the estimation itself, there are a few techniques you can use. Some teams assign tasks t-shirt sizes, while others will use abstract ideas like fruit or dogs to represent size. Here at AgileSherpas, we use the fibonacci sequence (1, 2, 3, 5, 8, 13, and so on) because it reflects the reality that as task complexity increases, the duration, dependencies, and unknowns increase as well. Thus the exponentially increasing scale of fibonacci numbers automatically accounts for that factor.
However you approach estimation, it’s vital you check your accuracy so you can iterate over time. If your estimates are always wrong but you never track this and try ways to improve, that improvement is just never going to happen. One way to gamify this process is called planning poker. But however you approach it, estimation needs to be taken seriously and viewed as a multi-faceted approach.
-
You can talk about prioritizing the right work to deliver value to your stakeholders all day, but without measurement, you’re going to be doing so blind. Identifying and tracking the right Agile metrics is crucial to seeing how your prioritization efforts are translating into real value. Armed with this information, you can then experiment and improve your processes further.
One way to get feedback on the value you’re delivering is by getting regular feedback from your stakeholders about the work you’re delivering. But tracking how well you’re functioning is also important. One important metric to use here is lead time. This is the time between when a piece of work is requested by a stakeholder (or when you begin actively working on it, depending on how your team functions) and when it’s delivered.
This helps you track your team’s process efficiency. Of course, you can still experience delays in reviews, handoffs, etc. leading to longer lead times, which should be addressed. But overall, tracking and iterating on your team’s process efficiency enables you to supercharge the impact of your prioritization. If Agile prioritization is enabling you to do the right work at the right time, tracking and iterating to improve lead time enables you to do more of that valuable work.
-
As you’re going through your Agile prioritization process, stakeholder management is vital. It’s how you can ensure you get enough information to understand their priorities without getting overwhelmed with constant feedback. It’s also how you can understand how effectively you’re ultimately delivering that value.
The first thing to consider is who is responsible for this stakeholder management. In general, marketing owners will take the lead on more strategic issues while Agile leads can handle operational ones. For Agile prioritization, this means marketing owners can work to understand stakeholder priorities while Agile leads manage the day-to-day delivery of work and feedback on that work.
Just be sure to structure this relationship. In most cases, you want to interact with and get feedback from your stakeholders on a set cadence. This can help prevent lots of unplanned work and confusion among marketers. One way to do this is with Service Level Agreements (SLAs) that explicitly lay out precisely how that relationship should function and what each side can expect from the other.
Finally, as with all things in Agile, be ready to troubleshoot. If you’re not getting information on shifting strategic priorities enough, maybe you need more frequent touchpoints. Experimentation is key to finding the right stakeholder management strategy for you.
Key Agile Prioritization Techniques
While you can simply decide what tasks are high priority with your judgment, having a formal process is extremely helpful. These are a few of our favorite techniques.
Stack ranking is what most of us use when prioritizing things. It’s simply listing them in order of priority. This can be useful when most or all the tasks you’re tackling are of a similar size/difficulty, but once things get more complex you’ll want to consider a system designed for that complexity.
No, there’s nothing Russian about this approach. MoSCoW is an acronym for the four categories this system breaks items down into. Mo for Must Have, S for Should have, Co for Could have, and W for Won’t have. Instead of simply listing by priority and assuming all work will get done, MoSCoW helps teams think about whether a task should be done at all.
Unlike MoSCoW, this technique does come from where you imagine it might. Popularized by President Eisenhower, this prioritization matrix breaks work down into four categories based on two factors. The first is Important and Not Important. The second is Urgent and Not Urgent. Obviously work that is urgent and important gets prioritized while things that are not important and not urgent gets deleted - you just don't do them. Not Urgent & Important gets scheduled, Urgent & Not important gets delegated to someone else, another team or vendor for example.
Another more advanced prioritization framework to consider is cost of delay (CoD). This framework helps to quantify the economic value of completing work sooner rather than later by calculating the cost of not doing the work compared to the time required to complete it.
This calculation considers the value of the work to the business or customer, and its urgency over the duration of the initiative. The results are more data-driven and can provide useful data points to stakeholders asking for changes in priority.
-
Stack ranking is what most of us use when prioritizing things. It’s simply listing them in order of priority. This can be useful when most or all the tasks you’re tackling are of a similar size/difficulty, but once things get more complex you’ll want to consider a system designed for that complexity.
-
No, there’s nothing Russian about this approach. MoSCoW is an acronym for the four categories this system breaks items down into. Mo for Must Have, S for Should have, Co for Could have, and W for Won’t have. Instead of simply listing by priority and assuming all work will get done, MoSCoW helps teams think about whether a task should be done at all.
-
Unlike MoSCoW, this technique does come from where you imagine it might. Popularized by President Eisenhower, this prioritization matrix breaks work down into four categories based on two factors. The first is Important and Not Important. The second is Urgent and Not Urgent. Obviously work that is urgent and important gets prioritized while things that are not important and not urgent gets deleted - you just don't do them. Not Urgent & Important gets scheduled, Urgent & Not important gets delegated to someone else, another team or vendor for example.
-
Another more advanced prioritization framework to consider is cost of delay (CoD). This framework helps to quantify the economic value of completing work sooner rather than later by calculating the cost of not doing the work compared to the time required to complete it.
This calculation considers the value of the work to the business or customer, and its urgency over the duration of the initiative. The results are more data-driven and can provide useful data points to stakeholders asking for changes in priority.
Steps You can Take for Better Marketing Planning
-
Your top priority should be the task that shows the best ratio between effort required and value delivered. That might be a very difficult task that will substantially move the needle or it might be a task that’s extremely easy but still will do something important for your stakeholders. The mantra you should follow to make that decision should be doing “the right work at the right time.”
-
This is a crucial question because when anyone or everyone sets priorities, you get chaos. First, marketing leadership sets the vision, goals, and overarching priorities for the marketing department. On Agile teams themselves, the marketing owner should be the one to prioritize the backlog and thereby set team priorities. However, this doesn’t mean they do so alone. The team itself should also have input in things like estimation while stakeholders will help set the strategic priorities the marketing owner will aim to achieve.
-
Information on task deadlines should be contained in the cards connected to those tasks. Those deadlines are one of the aspects that need to be considered during prioritization; important work with a tight deadline would rank lower than important work with a later deadline. Often, deadlines are informed by stakeholders, events like product launches, seasonal events like Black Friday, etc. Knowing deadlines upfront can assist with prioritization, but it's not the only determining factor.
-
Trying to prioritize multiple tasks, particularly complex ones with varying levels of complexity, can be extremely difficult. But the best approach is to be structured and deliberate. By using the Agile prioritization process laid out on this page, you can estimate and prioritize multiple tasks in a way that delivers maximum value to your stakeholders without putting undue pressure on marketing teams.
-
While it’s important to take deadlines into consideration, they shouldn’t be what drives your prioritization. If something is “due today,” but won’t deliver any real value to stakeholders, then it probably shouldn’t get done at all. That’s why Agile prioritization considers value delivered and effort required above deadlines. So when a task has no deadline, you should simply rely more on those basic considerations or contact the stakeholder to understand when something is due so you can factor that into your prioritization.
-
Agile ways of working don’t have specific set levels of priority. Instead, there are many different ways to break down tasks by their levels of priority like stack ranking, MoSCow, etc. Rather than focusing on what the levels are, it’s best to simply adopt a structured approach that works for you and iterate on it as needed.
-
The Pareto Principle has become a core idea for Agile ways of working. It says that 80% of the impact can be generated by focusing on 20% of your work. In other words, most of the value you create likely comes from a small fraction of the work you actually do. This is a key reason why prioritization is so important in Agile. It’s how you determine what that 20% is so you can focus your efforts there.
-
A prioritization framework is a systematic approach for prioritizing work. Importantly, Agile marketing does not have a single prioritization framework that everyone uses. Instead, different teams can apply Agile values and principles in their own ways to find an approach that works best for them. Experimenting and iterating is crucial to figuring this out for your team.
Ready to Tackle Your Prioritization Problems?
AgileSherpas’ prioritization bootcamp takes this thorny problem and breaks it down into manageable steps. In just 6 weeks you’ll have a handle on one of the biggest barriers modern marketers face.
Created by Marketers Just Like You
If you work in marketing and ever feel overwhelmed by the amount of work you have to do, this course is for you.
It's designed and taught by professional marketers who know what it's like to have 27 to-dos all marked "high priority".
Well structured, professional course and I feel confident applying new practices after completing it. Big shout out to our instructor who really customized the course to our organization, so we could see from start what to change, where to improve to be fully Agile. Team exercises and homework after each chapter were all beneficial and helped me understanding each topic better. Big thanks, it was a great experience.
I now feel like I have a good understanding of the concepts and how to put them into practice. The course content was engaging and informative. I'm excited to see the way my marketing team transformas as we move to Agile. Highly recommend!"
Our trainers were outstanding! Through this training I was able to learn more about Agile Coaching and Facilitating, grow personally and professionally, and simply have fun. They were able to create an environment where everyone could voice their thoughts/opinions and feel comfortable doing so. I am blown away by how the training felt like it flew by and I didn't want it to end.
It was a great experience. I knew almost nothing about the topic when I entered, but our coach was able to bring me along with more experienced participants in a way that we all got something out of it. I'm grateful for the experience and look forward to taking it forward!
The course was nicely articulated, the trainer very accommodative and extremely prepared, easy to follow thought the lessons on line and always eager to have us engaged. Not one single lesson was boring despite the use of Zoom, very interactive sessions, and nice group excises that made us learn and bond.
It was an absolute pleasure for me to take this course. Our trainer did a great job leading the sessions, and each week was a fine balance of course material, peer exchange, and exercises. The course was engaging and, at times, inspiring. It was truly valuable for me beyond just the coursework.
In just 3 months, we are seeing a significant improvement in project duration and while our project volume is actually increasing across all of our Agile teams
AgileSherpas helped us build an Agile culture by giving us a strong sense of the lay of the land in terms of what Agile really means, how Agile teams behave and how we can evolve from we are to where we need to be.
Enrolling in the Agile Marketing Leadership course was a game-changer for me. The practical insights and actionable strategies I gained have transformed my leadership approach. Highly recommended!
First let me say our instructor was able to break down the obtuseness of Agile into understandable blocks of how to put together manageable marketing teams and integrate them into solving issues for diverse divisions of our company. She was skilled in offering solutions to issues that may cause road-blocks or painpoints. Her attitude was always over-the-top positive. I look forward to her insight as we continue our journey in our 90 day testing period.
As a Creative Manager, I have been intrigued by Agile for almost 10 years but didn't know where to start. In just 8 short weeks I have an excellent understanding of the principles and how to start to apply them. I only wish I would have done it sooner.
Reading "Mastering Marketing Agility" made the benefits of Agile clear -- and choosing AgileSherpas was the right decision. With their guidance, we'd summit the biggest challenges of implementing Agile marketing: moving away from the mantra of "how we've always done things" to more efficient, effective workflow management.
The experience was great. The course made us reflect on what we can do better and how we can do things better. I like that it's very interactive and fun. Our instructor had real mastery of the subject and delivered the course very well. Considering that we were different marketing groups in 1 company (coming from different countries and even different work structures), our instructor was able to piece things together and present her perspective in relation to the realities of our organization. It is a great way to start teaching teams to shift paradigms and get out of their comfort zones.
I had previously completed Certified Scrum Product Owner certification training, but this course was vital to my understanding of how to apply agile framework to my marketing work. The course leveraged case studies and group activities, combined with an informal lecture style that was both engaging and informative. I particularly appreciated that AgileSherpas take a flexible approach to scrum - the goal isn't to apply a framework rigidly, but to be thoughtful and informed as you concerned what will work best for your team and organization. Thanks for all of your support!
Our trainer did a great job in explaining Agility to our Online Customer Experience team. She gave us a good mix of theory, exercise and reflection. She called out misperceptions gently but clearly and was very appreciative towards the group. She was also ready to adapt to the language and marketing approach we use internally, which helped tremendously in bringing people on board with the new concepts. It was great working with her and AgileSherpas.
Agile Sherpas' Train the Trainer program was easily the best training experience I have had in a decade. The mix of activities, ability to immediately apply lessons, and customizations to our challenges enabled real skill building to occur. I saw growth in every single participant, myself included, from the Monday where we got started to the Friday where we concluded. I cannot wait to see the positive outcomes that will come from a renewed coach approach and improvements to my agile ceremonies, staff meetings, and facilitated workshops. The opportunities to level up as a result of what I learned are endless. I would recommend this course to anyone looking to collaborate with others to achieve success, personally and professionally.
Until I took the course, Agile felt mostly like conceptual buzzwords to me. But, the hands-on exercises helped me mentally take agile from theory to real-world application. So, I have even more excitement about applying agile ways of working to our marketing department to generate powerful outcomes for our customers and employees.
The Leading with Agility Course really helped to cement the leadership capabilities & values needed to enable agility and how we as leaders must embrace new roles in order to bring about change. Currently at the start of our Agile transformation, the course has provided me with both practical tools & frameworks, alongside the mindset required to guide the marketing department through this change. Would highly recommendour trainers and the course to my peers - their wisdom, knowledge and facilitation were second to none.
Our AgileSherpas coach was joining all of our ceremonies and helping us resolve situations right then and there. We worked very closely with them to establish the value of Agile, set up the new processes, and skill up the whole team in preparation for what was to come. Other training is more technical, whereas AgileSherpas leadership and team training was focused on marketing.
The Agile Fundamentals course helped shape and consolidate Agile marketing concepts in practical ways that I can apply to my role and organization. I would recommend this course to both marketing professionals and organisations embarking on an agile transformation journey
AgileSherpas helped us cut the time it took to scale Agile out to more parts of the marketing organization massively.
Our trainer was upbeat and engaging. Training in a methodology we're already employing can be a tough pill to swallow for employees who already have limited bandwidth, but this class was absolutely worth the time and effort. I have found each week that I'm referencing and applying lessons almost immediately following class, and, what's even better, the implementation of these strategies has been cumulative, where I've not cycled through them, but built upon them each week. Thank you for the thoughtful instruction and authentic conversation, I have come away with a new perspective on and understanding of Agile methodology.
The course was a great mix of concepts, practice, and action. The training was engaging and interactive. I certainly took some concepts away that will be put into practice. Thank you!
A highly recommended and extremely valuable for marketing and project management techniques. Our trainer was outstanding and took every opportunity to make the content real for my unique role. Sessions are to the point without drag-on. My deepest thanks for this insightful experience.