Sometimes, the best description of what software does comes from the people who use it every day.
Recently, WebCenter user Laurens Tytgat, Process Expert Lead at Shell, shared a list with us: 40 reasons why Esko WebCenter makes his workday brighter.
While the number of reasons was impressive, it was how familiar they felt that really spoke to us.
Think about the various tasks you perform throughout the day: Finding the right file, keeping track of approvals, cutting down on unnecessary emails, knowing which version is actually the final version, and so on.
These are small moments in a working day, but when they’re repeated across projects, teams and deadlines, they sure can add up.
Laurens’ list captures something that’s easy to overlook when talking about workflow technology. Its value lies in the everyday problems people no longer have to think about.
So rather than translate his thoughts into marketing speak, we’re sharing all 40 reasons.
Keeping Work Moving
Packaging projects rarely follow a perfectly straight path. Priorities change, revisions happen, stakeholders come and go, and a seemingly simple project can quickly become complicated.
For Laurens, part of WebCenter’s value is bringing structure to that complexity. He said:
- It keeps projects moving when inboxes would bring them to a halt
- It turns chaos into workflow
- It keeps stakeholders connected
- It makes reviews easier
- It is patient with our endless revisions
- It survives our changing priorities
- It handles complexity better than most humans
- It makes handovers smoother
- It brings structure to creative work
- It helps us meet deadlines
- It helps keep teams aligned
- It scales from simple requests to global projects
- It helps turn ideas into finished products
- It provides order when things get busy
There’s plenty of technology behind those benefits. But from a user’s perspective, the outcome can be much simpler: work keeps moving.
Finding the Right File, and the Actual Final Version
Version control might not be the most glamorous part of packaging, but anyone who has worked on a project with multiple files, reviewers, and rounds of feedback knows how quickly it comes to matter.
Laurens puts it rather clearly:
- It knows where my files are, even when I don’t
- It remembers approvals so I don’t have to
- It speaks the universal language of version control
- It prevents “final_v3_really_final_FINAL.pdf”
- It gives everyone a single source of truth
- It keeps artwork organized
- It saves time searching for documents
- It tells me who approved what and when
- It provides visibility into project status
- It doesn’t judge our naming conventions
- It gives transparency where spreadsheets cannot
- It remembers project history better than any meeting minutes
- It keeps information accessible
- It helps us avoid duplicate work
We could call that centralized artwork management, version control, and project visibility.
Or we could just say: fewer FINAL_FINAL files.
Sometimes the customer says it better.
Making Collaboration a Little Less Complicated
Packaging is collaborative by nature. Artwork can pass between teams, departments, external partners, and stakeholders in different locations before a finished product ever reaches the market.
That makes the small friction points of collaboration particularly noticeable. For example, the email someone missed, the document someone can’t find, or the update that didn’t reach everyone.
Several of Laurens’ reasons come back to making those everyday interactions easier:
- It makes collaboration possible across teams and continents
- It helps reduce misunderstandings
- It reduces unnecessary emails
- It connects people who may never meet in person
- It helps us work smarter
Maybe “reduces unnecessary emails” isn’t the kind of benefit that makes its way into a technical specification.
But one less reply-all still makes a workday brighter.
Supporting Consistency, Quality, and Compliance
Not everything that matters needs to be highly visible.
Some of the most important parts of a workflow happen quietly in the background: maintaining consistent processes, preserving a project history, supporting quality and making sure the right information is available when it’s needed.
Laurens’ list recognizes those less visible benefits too. He stated:
- It helps us stay compliant
- It supports consistent processes
- It supports quality and accuracy
- It continues to evolve and improve
- It quietly supports success behind the scenes
- It has become part of our daily routine
- It reminds us that good tools can make a real difference
And perhaps those final reasons get closest to what makes the whole list both fascinating and relevant.
Good workflow software doesn’t necessarily need to be the star of the workday. It hums away in the background, making the complex simple, the information accessible, and the work happening as it should.
40 Reasons, One Simple Idea
Laurens ended his list of 40 reasons why WebCenter makes his day brighter, remarking:
“So, thank you, Esko WebCenter. For every approval, every workflow, every project launch, every carefully tracked version, and every small moment where things simply worked as they should.”
We think that’s a darn good description of what successful workflow technology should ultimately do.
Want to explore what WebCenter could do for your team?
Learn more about Esko WebCenter or book a discovery call with our team.
