The Difference Between Shipping and Advancing
One day I was at the neighbor's house, hanging out with friends, when I noticed a calendar with a quote for each month. Paging through it, I came across the one above. It impacted me deeply at the time, as it aligned with what I often felt I saw in the world. Movement without progress. As the years have passed the quote has stayed with me, and its meaning to me has evolved as I've progressed through my career. I can see that in today's business culture, we often confuse activity with achievement.
Let's consider the differences between shipping and advancing. "Shipping" means delivering something, releasing a feature, completing a sprint, publishing a post, or closing a ticket. Shipping is visible. It feels productive. It checks a box.
Advancing, on the other hand, means moving closer to a meaningful objective. It's creating durable value. Improving systems and not just outputs. It involves strengthening alignment, clarity, and capability. In other words, advancement is directional and requires intent. Good project and program managers have their eye on advancement in any project.
Here's the key distinction: shipping is motion. Advancing is progress. All movement is not forward.
Movement just feels so good! It's the dopamine we get from completing a task. It's the social reinforcement in the form of congratulations for getting something shipped. It's wrapped up in the metrics that reward output, like velocity, release counts, and deliverables. What it looks like in practice, the illusion of impact, is back-to-back meetings, constant Stack/Teams activity, endless Jira ticket closures, and frequent releases with marginal user value.
Are we producing more, or are we producing meaningfully?
In one cross-functional initiative I facilitated, the meeting itself became a perfect illustration of movement without progress. Engineering was debating technical dependencies. Product was pressing for feature completeness. Regional stakeholders were raising compliance concerns. Everyone was engaged. Everyone was talking. The conversation was energetic, intelligent, and nonstop. But no decision was made. No trade-offs were clarified. No owner was assigned. We left with more words than when we started. The lesson was unmistakable: activity without alignment is not progress. A room full of smart, busy people does not equal advancement unless their energy converges toward a shared decision and a defined direction.
I’ve also seen the phenomenon of the “feature factory.” Teams ship every sprint. Roadmaps are packed and meticulously color-coded. Release notes go out with impressive regularity. Yet customers are confused about what the product actually does for them. Adoption plateaus. Core metrics remain stubbornly flat. The machinery of delivery hums, but the value proposition grows fuzzier. Output without outcome is motion without advancement. Shipping becomes the goal instead of serving the goal.
Then there are the reorgs. New org charts. New titles. New acronyms. Announcements framed as bold transformation. For a moment, it feels like something significant has happened. But six months later, the same bottlenecks remain. The same decision delays persist. The same strategic ambiguity clouds execution. Structure changed, but capability did not. Not all change is growth. Sometimes it is simply movement wearing the costume of progress.
There are signals you can look for to tell that you are shipping but not advancing. Here's a diagnostic checklist:
-
Are we clear on the “why” behind this work?
-
Can we articulate the outcome in measurable terms?
-
Does this solve a real customer problem?
-
If we stopped doing this, would it matter?
-
Are we adding complexity faster than we’re removing it?
To begin, direction requires clear, achievable goals. That means defining success in concrete terms and ensuring genuine strategic alignment around what matters most. Without explicit criteria and shared understanding, teams can move quickly while drifting off course.
Discipline follows. It involves saying “no” (a responsibility that often, though not always, falls to the project or program manager), narrowing scope, and eliminating low-impact work. Focus is not accidental; it is enforced through intentional trade-offs.
Finally, advancement demands courage. You may need to slow the pace when others are pushing for speed, challenge vanity metrics, or pause a launch that is not ready. The truth is that advancement often feels slower than shipping, but it is far more likely to move the organization meaningfully forward.
Don't get me wrong here: shipping still matters. It simply is not enough. You can't advance without shipping, to be sure. Ideas must make their way to reality, and progress requires execution. However, execution without strategy is drift. You may be chugging out features but to what end? Velocity without direction is chaos.
You can think of it like a treadmill or a compass. One gives you the illusion of motion, while the other points you toward true north and orients you to the world. It is running hard vs. walking north.
Let's reframe what success means for a team and project. We can shift from "what did we ship" to:
-
“What did we change?”
-
“What improved?”
-
“What became possible?”
Encourage outcome-driven thinking by consistently anchoring work to what truly matters: customer impact, operational simplicity, revenue quality, and team capability growth. Ask how each initiative improves the customer’s experience in a measurable way, whether it reduces friction or complexity inside the organization, whether it strengthens sustainable and high-quality revenue rather than short-term spikes, and whether it builds the skills and resilience of the team over time. When these dimensions guide decision-making, work stops being about output alone and starts compounding into long-term value.
That quote from Ellen Glasgow: "All change is not growth, as all movement is not forward" can be applied in many ways and diverse contexts. When I was young I applied it to politics and to the world in general. I looked at my life ahead of me and hoped that I would grow and move forward, not stagnate even while I had the motion of passing time. Now, as an adult, it makes more sense than ever and has become a quiet diagnostic tool in my work.
Movement feels productive. It gives us the satisfaction of completion, the optics of momentum, and the reassurance that something is happening.
Growth, however, requires direction. It demands clarity about where we are going and the discipline to align our effort accordingly. The difference between shipping and advancing is the difference between activity and impact. Only one of those truly moves us forward..