I’ve spent more than 25 years working for software companies, and for most of that time I’ve been a Product Manager. My job is to envision a better future for customers using my product, then lead teams through ambiguity, break big features into small deliverables, and adjust quickly when things don’t go as planned.
It’s funny that I used Agile principles every day at work but for some reason it took me a long time to se how they translated to managing my own weight loss journey.
I’ve talked a lot about how I’m a master at building grand plans, setting overly ambitious goals, and then… burning out and falling apart.
As I began to reflect on what sustained habits look like in the real world and as I thought about how I worked in small increments (one meal at a time, one workout at a time) it dawned on my that I was really unconsciously using the same practices I had learned over the years at work.
It’s proven very true that Agile processes can be applied to all kinds of large tasks so if you’re looking for some well-researched practices to help ground your transformation journey look no further.
The Problem with “Waterfall” Weight Loss
Way, ‘back in the day’ most software products were developed with a software process called Waterfall where an entire project traveled through a single step in the process and not until everything had passed that step did the whole project move on. This process required a lot of planning before anything could even begin and because each step took so much effort making any kind of changes along the way was discouraged. In short, the process was design to be thorough but rigid. A typical diagram of the process looks something like this:
Most of us approach weight loss like a classic waterfall project. We set a huge goal—“Lose 50 pounds by summer!”—and try to map out every step in advance: diet, workouts, supplements, you name it. No room for error. No flexibility.
But life isn’t linear, and neither is transformation. Things break. Schedules get messy. Motivation dips. And when your perfect plan gets derailed, what do you do? You quit.
I know I did. More than once.
Discovering Agile for Health
In the world of Agile software development, we ditch the massive upfront plans and focus on iteration. We test, learn, and adapt. We ask, “What’s the next smallest step we can take toward our goal?”
So I asked myself: what if I treated my health like a product I manage? Not a perfect, fully realized product, but one that is always in development. Much like software or lives require regular updates, debugging, and the occasional patch note that says, “Sorry for the glitch. We’re working on it.”
Building the MVP: Just Show Up
In Agile, we start with a Minimum Viable Product (MVP)—the simplest version that delivers value to our customer. For me, that meant one thing: track my food using the Weight Watchers app every day. Do it honestly and consistently. That’s it.
Not crush a 90-minute workout. Not eat flawlessly. Just show up today, and do it again tomorrow.
So I did. I tracked one meal. I drank more water. I focused on consistency over intensity.
It wasn’t sexy, and it took time. But it worked.
Daily Standup
In Agile practice a development team does a quick check-in each day and each team member talks about what they worked on the day before and what they will be working on during the current day. This gives others on the team an opportunity to offer insights or ask questions about the work of other team members and also provides daily accountability.
I brought the same practice of the daily standup to my weight loss process by plotting out my meals for the day ahead of time so I knew where my Weight Watchers points would be going. It’s still true today, most days I plan my workout for the day even going so far as to get dressed in my workout gear as soon as I wake up. I also lock in my meals (especially breakfast and lunch) for the day so I know where my points will be spent. This daily check in keeps me honest and focused. It also lets me get small daily wins and spot areas where I’m falling off track.
Sprint Reviews and Retrospectives
In Agile software development most teams work in one or two week ‘sprints.’ Before beginning a sprint the team identifies the work they will do in the sprint increment and what the key deliverables will be. These are typically memorialized so everyone on the team knows what the goals are. When the sprint ends the team spends time assessing how they did against their goals and commitments. The team reviews what went well and what didn’t, ideally not as a form of judgment but in order to foster honest communication and a learning mindset.
A key point here is that nothing ever goes perfectly. There’s always room for improvement and something to be learned.
Every week or two, I pause to review: What’s working? What’s not? Where am I struggling?
Sometimes I realize I need more sleep. Other times, I notice I’m snacking too much or not eating as clean as I should. Lately, we’ve been doing a lot of work on our house and I’ve been skipping workouts to make time for working outside, building decks or planting gardens or putting in walkways. I know this work burns calories, but I have had to make efforts to ensure I keep my workouts going–even if they are shorter and on fewer days. These little retrospectives gave me permission to adjust—not abandon—the plan.
Agile Isn’t Just for Software
Today, I’m healthier, stronger, and more grounded than I’ve been in years—not because I followed a perfect plan, but because I gave myself room to iterate.
Weight loss, like any big challenge, is rarely about willpower. It’s about systems. Feedback loops. Patience.
So whether you’re trying to lose weight, write a book, or just build a better version of yourself, try going Agile. Start small. Adjust often. Celebrate the wins, learn from the misses, and keep shipping new versions of yourself.
You might be surprised at what you can build.