Two academies. One rebrand. A platform migration running at the same time.
250+ assets moved from Skilljar to Docebo. Eight months of full-time internal work, by their own estimate.
Learn more
Iterable rebranded company-wide while moving their customer and partner academies from Skilljar to Docebo. More than 250 assets across courses, videos, documents, webinars, and certifications, a job they sized at eight months of full-time internal work. We completed the work inside their systems and to their standards.
Results at the three-month milestone.
The figures below reflect what had been delivered at the three-month point, rather than final project totals.
Videos produced
Rebuilt and rescripted, not re‑cut.
Learn more
Including both the ones embedded inside courses and the standalone Product Bites. Scripts rewritten where the narration needed it, not just re-cut to carry the new brand.
Full courses delivered
Every one signed off by Iterable before it counted.
Learn more
Every one rebranded, improved with instructional design where applicable, and signed off by Iterable’s team before it was marked done.
Weeks ahead of schedule
On Foundations, the path with the hardest deadline.
Learn more
On Foundations, their most-accessed learning path and the one carrying the hardest deadline. Rebuilt, rebranded, and live well ahead of both the platform launch and the internal completion date.
Foundations delivered four weeks early.
Foundations learning path from project start on May 18th, completion against Iterable’s internal deadline of August 13th. Delivered July 15th. Shape is illustrative; the endpoints are not.
Same course. Rebuilt, not re‑skinned.
Building a Base Template, live on both sides. Scroll in place or open full screen.
Before. Previous brand, original example, unchanged structure.
After. New example company, restructured lessons, two sections written from scratch.
Learn more
Rebranded and rebuilt around a new example company we designed for the Iterable audience, carried end to end. Lessons restructured to flow better with the content, plus two sections written from scratch, video included, covering features the original course predated.
Hosted for demonstration only. Some in-course links point to destinations inside Iterable’s own environment. Those destinations may have changed since delivery, so some links may not resolve here.
They have been a genuine extension of our team.
“Rebranding our entire customer and partner academies while migrating from Skilljar to Docebo was a lot to take on at once, and having [Acromodo] alongside us is what made it manageable. They jumped in with our team on hundreds of assets, implemented our folder structure throughout our entire tech stack, and got our Foundations courses redone ahead of our internal completion deadline.
What stood out was that they didn’t just re-skin content; they rewrote scripts and reworked material with real instructional design behind it, and built the use cases that now carry through our Product Bites and Foundations tracks. They followed our conventions instead of pushing their own, and their work came back clean, so our QA reviews were always quick.”
Rebranding is the reason. Instructional design is the work.
Most rebrands stop at the surface. Every asset had to be opened, so we used the opportunity to improve how the content informs, not just how it looks.
One story, all the way through
One company, one continuous thread, every lesson building on the last.
Learn more
The original example used in the Product Bites and Foundations learning path was not designed for the people learning from it. We built one that is, and it runs as a single continuous story. Learners follow the same company through the same kinds of tasks they will encounter themselves, from one lesson to the next, so each lesson builds on the last instead of restarting with an unfamiliar scenario.
Workflows a learner will actually run
Captured from the product, so the lesson matches the screen.
Learn more
Video and stills alike were captured from the product itself, following workflows a learner will actually run, so what they see in a lesson matches what they see when they open the platform. The closer the example sits to the real task, the less translation a learner has to do on their own.
Rewrite, then reproduce
New branding on unclear content is still unclear content.
Learn more
Where narration buries the point or a lesson loses the thread, the script and the flow were fixed before anything was reproduced. The rebrand was the reason to open every asset, not the only thing that changed.
Four gates. Every asset passed all four.
Audit verification
Turn their list into something the work can run on.
Learn more
Iterable built the initial audit. Working with their team, we turned it from a list into something the work can run on: duplicates removed, every asset notated with the learning path it belongs to, source links attached across the set.
Structure across every system
Their folder structure and naming, applied in every tool.
Learn more
Those 250-plus assets lived across authoring and development tools, video projects, design files, shared drives, and two LMS platforms mid-migration, and none of those shared a file structure or naming standard. Iterable set the standards. We applied their folder structure and naming in every one of those places, not just in storage.
Design and rebuild
Scripts, flow, brand, video. Asset by asset.
Learn more
Instructional design applied asset by asset: scripts and flow reworked, the use case threaded through, brand applied, video rebuilt. We designed the branding for a fictional company as well, so every asset referencing it looks like the same business when used in example scenarios.
Client QA gate
Nothing goes live on our say-so alone.
Learn more
Iterable’s team reviewed every deliverable before it was signed off as done.
We learned their product. Not just their brand.
You cannot build an accurate demo of software you have not used. We learned Iterable’s platform until moving through it was second nature. Along the way we built examples inside their demo environment that their team can pull from for future content.
That shows up in the work. Screen demos follow real workflows instead of staged clicks. Scripts use the product’s own language. And because we knew the platform, we could build without waiting on their team to explain it.
Built in the tools their team already uses.
One naming standard, carried through every one of them, including both LMS platforms mid‑migration.
Good content is not the same as content people actually use.
If your content is moving platforms, changing brand, or both at once, we can help you keep it usable through the transition.