Every organization is looking for ways to move faster: faster launches, faster approvals, faster responses to changing regulations, and increasingly complex product portfolios.
But in my experience, speed is rarely lost because people aren’t working hard enough or moving quickly enough. More often, speed is lost when work has to stop, back up, and be corrected before it can move forward again.
Anyone who has spent time managing packaging projects has seen it happen.
A design moves forward before production has had a chance to provide input. A versioning requirement creates challenges no one anticipated. A seemingly small regulatory update suddenly impacts multiple assets and triggers a series of revisions. None of these situations is unusual. They’re part of the reality of packaging and brand execution.
The real challenge isn’t the complexity itself; it’s discovering these issues after the work has already progressed to the next stage. By then, teams aren’t advancing the work—they’re recovering from decisions that could have been addressed earlier.
I’ve worked with teams that appear incredibly productive from the outside because calendars are full, meetings are constant, emails are flowing, and decisions are being made every day. Yet despite all that activity, progress can feel slower than it should.
Why? Too much energy is being spent revisiting decisions, resolving misalignment, and fixing problems that emerged late in the process. Activity and progress are not always the same thing.
The teams that consistently move the fastest aren’t necessarily operating in simpler environments, and they certainly aren’t facing fewer challenges.
What sets them apart is their ability to solve the right problems earlier.
When creative, graphic services, and production teams are connected from the start, execution realities become part of the conversation before decisions become difficult to change. Versioning, scalability, compliance, and production requirements are considered while flexibility still exists.
That doesn’t eliminate complexity. What it does is give teams a better opportunity to manage complexity before it becomes rework. Across one project, the impact might feel modest. Across hundreds of projects, the difference becomes significant.
When people talk about integration, they often think about organizational structure. I see it differently. To me, integration is about creating shared context. It’s about ensuring the right people are involved early enough to contribute their expertise when it can make the biggest difference. It’s about helping teams make informed decisions before the work moves downstream.
When creative and production operate as one connected team, fewer decisions need to be revisited. Fewer surprises emerge when timelines tighten. Teams spend less time solving issues that could have been prevented and more time creating value for the brand.
The result isn’t just greater speed; it’s greater confidence. Confidence that the work will continue moving forward, that decisions were made with the right information, and that teams can focus their energy on the future rather than on recovering from the past.
The longer I’ve worked in this industry, the more I’ve come to believe that speed has very little to do with rushing.
The organizations that stand out to me aren’t constantly asking people to work harder or faster. They’ve built processes that encourage better collaboration, better communication, and better decisions earlier in the workflow. As a result, there is simply less to fix later.
That’s why I don’t believe speed is something organizations pursue. I believe it’s something they create. And more often than not, it starts with bringing the right people together at the right time.