Most productivity frameworks are designed for individual output. Scrum is designed for teams working on complex problems where requirements change, outcomes are uncertain, and traditional planning fails. That describes almost every marketing project I’ve ever worked on.

Jeff Sutherland co-created Scrum for software development, but its principles apply well beyond code. After reading this book, I restructured how I approach brand campaign planning — and the difference was noticeable. Here’s what actually mattered.

1. Waterfall planning is built for failure

Traditional project management assumes you can plan everything upfront, execute linearly, and deliver on time. Sutherland’s argument is that this approach fails consistently on complex projects because requirements change, unknowns emerge, and the plan becomes obsolete before execution begins. Most marketing projects I’ve seen fail in exactly this way — over-planned at the start, under-resourced in the middle, scrambled at the end.

2. Work in sprints, not long timelines

A sprint is a fixed, short work period — usually 1-4 weeks — at the end of which you have a working, reviewable output. Instead of planning 6 months and delivering once, you plan 2 weeks and deliver repeatedly. The feedback loops tighten dramatically. Errors get caught early. This one principle alone changes how teams work.

3. The daily standup has one purpose: remove blockers

Three questions. What did you do yesterday? What are you doing today? What’s blocking you? That’s it. Fifteen minutes maximum. The standup is not a status report — it’s a blocker identification mechanism. Every minute spent on status reporting in a standup is wasted.

4. Velocity is the only productivity metric that matters

Sutherland measures team output in “story points” — units of work complexity completed per sprint. Velocity is how many story points a team completes consistently. The insight: once you know your velocity, you can predict delivery reliably. Without it, every timeline estimate is fiction.

5. Multitasking destroys output — it doesn’t enhance it

Sutherland cites research showing that switching between tasks has a significant cognitive cost. Working on 3 things simultaneously doesn’t produce 3x the output — it produces roughly 40% of the output of focused single-task work. One thing at a time, completely, before moving to the next.

6. Prioritise the backlog ruthlessly

The product backlog is the list of everything that needs doing. The key discipline is ruthless prioritisation — only the top items get worked on, and the list is constantly re-ranked based on value. In marketing terms: not everything on the brand plan needs to happen. What moves the most important needle this sprint?

7. Definition of Done eliminates ambiguity

Every task needs a clear, agreed definition of what “done” means before work begins. Without this, work expands indefinitely, quality varies, and handoffs break down. In my experience this is one of the most underused practices in marketing teams — “done” is often vague until someone is unhappy with the output.

8. Inspect and adapt — every sprint, without exception

At the end of every sprint, hold a retrospective: what went well, what didn’t, what will you change next sprint. The discipline is doing this even when the sprint went fine. Continuous improvement is not a crisis response — it’s a regular cadence.

9. Technical debt in projects works exactly like financial debt

Every shortcut you take — the quick fix, the process skipped, the documentation deferred — becomes debt that must be paid back later, usually at a worse time and with interest. This maps directly onto what Zero to Scale argues about business building. Shortcuts compound negatively.

10. Happiness drives performance, not the other way around

Sutherland references research showing that happy teams are significantly more productive than unhappy ones — and that happiness is measurable and manageable. The implication for team leaders is that morale is not soft — it’s a performance variable with measurable output impact.

11. The team must own the process

Top-down process imposition kills Scrum. The team decides how to work, how to structure sprints, how to run retrospectives. Management provides the goal and removes obstacles. Micro-management and Scrum are incompatible.

12. Waste is the enemy — identify and eliminate it constantly

Drawn from lean manufacturing principles: identify every activity that doesn’t add value to the final output and eliminate it. In marketing this includes meetings that produce no decisions, approval chains that add no quality, and reporting that nobody acts on.

13. Heroics are a failure mode, not a success story

When a project requires someone to work nights and weekends to deliver, that’s not a success — it’s a system failure. Sustainable pace is a design principle. Teams that regularly require heroics are teams with broken planning, not teams with impressive work ethic.

14. Cross-functional teams outperform specialist silos

A team with all the skills needed to complete work from start to finish outperforms a chain of specialist handoffs. In marketing this argues for integrated teams over siloed functions — strategy, creative, data, and execution in the same room.

15. The Scrum Master’s job is to remove obstacles, not manage people

The Scrum Master is a servant leader — not a project manager, not a boss. Their only job is to ensure the team can work without friction. This role is consistently misunderstood and misapplied in organisations that adopt Scrum without understanding its philosophy.

My honest take

Scrum is most powerful for software and product teams. Applying it wholesale to marketing doesn’t always work — campaign timelines, agency dependencies, and approval processes don’t always fit neatly into 2-week sprints.

But the underlying principles — short feedback loops, ruthless prioritisation, defining done, eliminating waste, sustainable pace — are universally applicable. I’ve taken these principles into brand planning cycles and they’ve made my work more focused and less chaotic. That’s worth the read.

If the project management angle interests you, my take on Getting Things Done covers the individual productivity side of the same problem. And the structural thinking in Zero to Scale applies the same “build correctly from the start” logic to business building.

The post Scrum Changed How I Run Projects. Here Are the 15 Lessons That Actually Stuck appeared first on PRASHANT AGGARWAL.

I have a complicated relationship with Getting Things Done. I’ve tried to implement the full GTD system twice. Both times I maintained it for about three months before the system itself became another thing to manage.

But the parts of GTD that I’ve actually kept — the principles underneath the elaborate methodology — have permanently changed how I work. The system is too much. The ideas are excellent.

The core insight: your brain is for thinking, not storing

Allen’s central argument is that the human brain is terrible at tracking open loops — unresolved tasks, pending commitments, things you need to remember. Every open loop consumes cognitive bandwidth, creates low-level anxiety, and reduces the mental space available for actual thinking.

The solution: capture everything outside your head into a trusted system. Not because you’ll necessarily do everything — but because the act of capture closes the loop psychologically, freeing up mental resources.

This one idea, properly applied, is worth the entire book.

The two-minute rule

If a task takes less than two minutes, do it immediately. Don’t add it to a list. Don’t schedule it. Just do it. The overhead of capturing, tracking, and revisiting a two-minute task costs more than the task itself.

I apply this constantly and it eliminates a significant amount of low-level clutter from my work and personal life.

Next action thinking

The most actionable GTD principle: every item on your to-do list should be a specific, physical, visible next action — not a project or an outcome. “Prepare Q3 brand review” is not a next action. “Open last year’s Q3 review file and identify three key changes” is a next action.

Vague to-do items create procrastination because the brain can’t execute on ambiguity. Specific next actions remove the decision-making step from execution. This principle alone transforms most to-do lists from source of anxiety to source of clarity.

The weekly review

GTD requires a weekly review — a regular pass through all your lists, projects, and commitments to ensure the system is current and trusted. Allen is emphatic: without the weekly review, the system breaks down and your brain stops trusting it.

This is both the most important and most commonly skipped element of GTD. I’ve settled on a lighter version — 20 minutes on Sunday evening — which maintains enough system integrity without requiring the full 90-minute GTD review.

Projects vs next actions

GTD defines a project as any outcome that requires more than one action. Most items on most to-do lists are actually projects, not tasks. Recognising this is important because projects need to be broken down — the to-do list should contain next actions, not projects.

The capture habit

Allen advocates for ubiquitous capture — capturing every idea, task, and commitment the moment it occurs, before it’s lost. The tool doesn’t matter: notebook, phone app, voice memo. What matters is having a single trusted inbox and clearing it regularly.

For people whose work involves creative thinking — which includes most marketing work — this habit is probably the highest-leverage change you can make to your productivity.

What I actually kept from GTD

The full system — with its elaborate folder structures, context lists, tickler files and weekly reviews — is more than most people will maintain. What I’ve kept: capture everything immediately, convert everything to specific next actions, do the two-minute tasks immediately, and review weekly.

That’s roughly 20% of the GTD system and it delivers roughly 80% of the value. The rest is for people who enjoy the system itself as much as the output it produces.

If you’re thinking about how to manage complex project work in teams rather than just individually, my Scrum summary covers the team equivalent of GTD’s individual principles. And the underlying psychology of why these systems work is well explained in the Thinking Fast and Slow summary.

The post Getting Things Done by David Allen: What Actually Works, What Doesn’t appeared first on PRASHANT AGGARWAL.

The title is designed to make you think this is a book about caring less. It isn’t. It’s a book about caring more selectively — about understanding that attention and emotional energy are finite resources and that most people exhaust them on things that don’t actually matter to them.

Manson is drawing on Stoic philosophy and acceptance-based psychology, but writing for an audience that would never pick up Marcus Aurelius. That’s not a criticism — it’s a genuine service. Here’s what he gets right.

The feedback loop from hell

Manson opens with what he calls the “feedback loop from hell” — the anxiety about anxiety. You feel bad about something, then you feel bad about feeling bad, which makes the original feeling worse. The solution is not to stop feeling bad — it’s to stop judging the feeling as a problem that needs to be solved.

This is not a new idea — it’s the core of acceptance-based therapies. But Manson states it accessibly and applies it practically.

You always choose your problems

Manson’s most important argument: happiness is not the absence of problems. It’s having problems you find meaningful. The question is not “how do I get rid of my problems” but “what problems am I willing to have?” This reframe is genuinely useful. Every goal produces its own problems — the question is whether those problems are worth it to you.

The value of negative experiences

Pursuing positive experiences is itself a form of negative experience — it creates anxiety, comparison, and the constant sense of not having arrived. Accepting negative experiences — difficulty, failure, discomfort — as inherent to a meaningful life reduces the meta-suffering that comes from resisting them.

You are not special — and that’s fine

Manson takes aim at the “everyone is special and exceptional” cultural narrative. The problem with exceptionalism as an expectation: it makes ordinary, meaningful, and satisfying lives feel like failure. Most good lives are ordinary lives lived well. That’s not a consolation prize — it’s the actual prize.

Responsibility vs fault

One of the clearer distinctions in the book: fault and responsibility are different things. Many situations are not your fault. They are, however, your responsibility — in the sense that you’re the only person who can determine how you respond to them. Conflating the two produces victimhood. Separating them produces agency.

The do something principle

Manson’s practical antidote to paralysis: action produces motivation, not the other way around. Don’t wait until you feel motivated to start. Start badly. Action → results → motivation → better action. This maps onto Morita therapy’s insight from the Ikigai book, and onto the research on habits — behaviour precedes identity.

My honest take

The book is better than its reputation in both directions. It’s not as shallow as critics claim — the philosophical underpinning is real. It’s not as original as fans claim — most of the ideas are variations on Stoicism and acceptance-based psychology. But it’s well-written, honest about its author’s own failures, and consistently readable.

Worth reading if you haven’t. If you have, the ideas hold up better on reflection than they might seem at first pass.

The “choose your problems” framework connects well to the Ikigai concept of daily purpose — both are essentially asking what you’re willing to suffer for. My Ikigai review covers that angle. And for the deeper psychology of why we resist negative experience, the Thinking Fast and Slow summary explains the loss aversion and negativity bias mechanisms underneath.

The post The Subtle Art of Not Giving a F*ck: What Mark Manson Gets Right — and What He Oversimplifies appeared first on PRASHANT AGGARWAL.

This is a book that really has mixed reviews everywhere. Hence, in this book review I want to share my views on this book. So let’s get started.

Freakonomics is written by 2 authors(mentioned above). One is an actual economist and then the other is a book author and they met because the author was interviewing the economist for The New York Times magazine. That was the time when they decided to write a book together. The interesting thing about this book is that there’s no unifying theme. Each chapter is like a separate entity in itself. But, the names of each chapter are super interesting.

What’s Inside Freakonomics?

The first chapter talks about how school teachers and sumo wrestlers are common. It talks about the incentives and how it is used to control human behavior. The author shares a story of incentives in the school system and how teachers used those incentives for their benefit. Similarly, how Sumo wrestlers used it for theirs. Some of it may look far-fetched but the comparison is purely from the eyes of the author. Some readers feel this comparison to be completely rubbish. This is completely fine because the author himself acknowledges this fact.

In another chapter, he talks about how a simple law on abortion was responsible for bringing down the crime rate. He gives an example of when abortion was legalized and how eventually the crime rate dropped in that city.

Another chapter that talks about what makes a perfect parent talks about nature versus nurture and if parents actually have an impact on how children turn out. There’s another chapter on How old people name their children so there’s a story about a guy named the winner and that his brother was named loser and whether their name had any impact on the success and outcomes of their life?

The chapters of the book are on a longer side (200 pages) but you could read it quickly because there is no unifying theme and each chapter is separate. People who are into statistics, data, and analysis would like this book.

This book really makes you stop and think about things going on around you. Why things are the way they are? This book would give new perspectives of how a normal person would look at the economics of the world. That’s the book of curiosity and if you read it let me know in the comments.

If you found my post useful then do share it with your friends and colleagues. If you have any feedback/questions, you may leave a comment below. I will reply.

Click here to know more about me

The post Freakonomics Review: Brilliant Storytelling, Thin Framework” appeared first on PRASHANT AGGARWAL.

Probably, he is simply personally taking responsibility for his career development.

It is logical to expect your boss to give you a promotion once you’ve earned one. It is logical to anticipate the HR division to have a succession plan that includes promotions for everyone in the organization including you.

Seth Godi writes in his book Linchpin on how you can avoid being a cog in a big machine and be a linchpin instead. He refers to cog as a part of the big machine that is easily replaceable. However, a Linchpin is irreplaceable.

In this post, I’m sharing three steps that can boost your career in a big way.

Become an Artist at work

If you continue to do what you are doing, you’ll continue to get what you are getting right now. You may have heard that the art is of great value, Ever wondered why? It is because art is not easy to find that creates value. That art makes the artist unique and irreplaceable.

Career Growth Tip 1 – Whenever you do any work, try to add your value to make it unique. 

For example – Your boss tells you to do research on a topic and submit a presentation. Now, what you could do is – after the presentation is finished, write your takeaways and put it as a summary in the mail while sending it to your boss. This simple step will make a huge difference.

Don’t wait for the Orders

In this highly competitive world, it is more important than ever to be proactive in the work we do. Consider these two scenarios mentioned below –

1. Your boss comes to you and gives you some work to do. You would do it.
2. You proactively figure out what needs to be done and do it. Your boss then comes to you and gives that work. You tell him that it is already been taken care of.

Now in the above scenarios, the second scenario is where all the difference will happen.

Career Growth Tip 2 – Always try to proactively look for things that need to be done and are likely to come to you eventually.

Find Solutions

It is easy to find problems and difficult to find solutions. Many executives take a back seat and rely on the boss to have solutions to every problem. This is one mistake I also did at the beginning of my career. I was under the impression that my job is to find the problem and flag it before it gets bigger. But, I realized after the first couple of years that I was putting no value addition on the table.

So, I figured out that the best way is to first identify the problem and think of a solution all by yourself and then go to your boss and say “I have found this problem and I think this could be the solution”. You will be surprised that in most cases your boss will say “let’s go ahead with your solution”.

Career Growth Tip 3 – Always have a Solution centric approach and go to your boss with a solution and not just a problem

This attitude not only changes your image but also gives confidence to the boss of your work. And to an extent, it also reduces your boss’s anxiety. When you start your career, your goal is to do things yourself and do the value addition. But, the more you move up the ladder, more accountability comes on your shoulders and lesser control as now you have to get things done rather than doing it yourself. Hence, the right way would be to put yourself in his shoes and empathize. Going to your boss with a solution will also calm his anxiety.

Just put these 3 points in your career growth plans/ professional development plans and start following them daily in your work. I guarantee that you would start feeling the change around you. Ultimately, every action you take will get reflected in the year-end evaluation as well.

If you found my post useful then do share it with your friends and colleagues. If you have any feedback/questions, you may leave a comment below. I will reply.

Click here to know more about me

The post 3 Career Decisions That Compounded for Me Over 12 Years in Marketing appeared first on PRASHANT AGGARWAL.

• Someone who is facing difficulties in interpreting the data.

• Someone who wants to improve the data interpretation/reading skills

In this post, I will give you 2 important tips which will change the way you approach any type of data. This will definitely help you in interpreting data like a pro.

“Our problems are not with the data itself, but arise from our interpretation of the data” – Bruce. H. Lipton

1. Perspective/Hypothesis

The importance of having a perspective before looking at the data is a bit under-rated in the real world. When I started my career in market research back in 2011, not having a perspective before looking at the data was one of my biggest mistakes. I used to get so lost in the data that I would forget what I was really looking for. I see this challenge with many new professionals in the industry which is why I am sharing my learnings over a period of time.

Now, as a first step before jumping into a data ask yourself what you are really looking for or what you are expecting the data to tell you?

For Example – You are about to look at the monthly car sales data and see if the trend is increasing/decreasing. Now, before jumping into the data you should have a perspective/view on the trend beforehand as well. Suppose, you have a view that the car sales would be declining because the economy is in bad shape.

Now with this perspective when you look at the data, you would immediately get your answer.

• If the data shows that the car sales are declining – you’ve successfully understood that data.
• But, supposing the data shows that car sales are increasing against your perspective. You will find a feeling on inquisitiveness inside you to find the underlying reason for this.

As a result, you will automatically start looking for answers and deep dive further.

This is just a simple example to explain the power of perspective before reading the data. This is applicable to any data you want to read.

2. Data Type

Many times we do the mistake of reading qualitative data quantitatively and vice versa. It is important to have clarity in the back of your mind whether you are looking at quantitative data or qualitative data. For the purpose of this post, I’m not going into details about these data types as these are wide topics to cover.

Knowing the data types reduces the chances of misinterpretation of the data.

For Example – Qualitative data can tell you exhaustively what are the various car segments available in the market. But, only Quantitative data will be able to tell you the size and growth of each of these segments.

When you are analyzing the Quantitative data, the concept of the Significance test plays a very important role. For example, the size of the hatchback segment in two independent populations comes out to be 25% to 26% respectively. Now, this may look like 1% more in 1 data set than other but it is not statistically significant to be able to confidently say that.

Similarly, in Qualitative data, if a particular segment size of the car seems bigger than others it only gives a hypothesis and not a conclusive picture.

These are small examples to explain how these data sets can be misinterpreted.

Following the above 2 points will definitely improve your data analyzing skills. these are also the 2 big mistakes that I did when I started my career and hence, wanted to share my learnings for the benefit of everyone.

If you found my post useful then do share it with your friends and colleagues. If you have any feedback/questions, you may leave a comment below. I will definitely reply.

Click here to know more about me

The post Interpreting Data like a Pro in 10 mins appeared first on PRASHANT AGGARWAL.