Dropbox Prism
Creating a unified learning ecosystem for Dropbox employees.
Industry
Technology / Learning & Development
What We Did
Naming, Foundational Strategy, Brand Personality, Playbook Development, Launch Strategy, Content Creation, Internal Communications
1
Unified ecosystem for learning at Dropbox
Dozens
of strategic materials produced for launch and ongoing rollout
Dropbox already had the pieces. What they needed was the architecture. Their L&OD team had run extensive research into what learning at Dropbox should embody, and they had real programs already running. What they did not have was a way to tie any of it together. The programs sat next to each other rather than inside something, and there was no shared language for what learning at Dropbox actually was.
This work became a natural expansion of our existing partnership with Dropbox.
The Challenge
The ask was clear on the surface: name the ecosystem, fold the existing programs into it, and ideate new layers to round it out. The actual work was more complex. You cannot name a thing well until you understand what it is, and what Dropbox needed this ecosystem to be was bigger than any of its current parts.
The learning programs had been built thoughtfully and independently. The risk in pulling them under one umbrella was flattening their distinct value. The greater risk was leaving them disconnected and watching the broader vision for learning at Dropbox stay theoretical, especially as AI began reshaping what capability at Dropbox would mean.
What We Discovered
The research told us something important about how Dropbox saw learning. It was not meant to function as a perk or a checkbox, but rather it was meant to reveal what was already there. As AI takes on more of the technical work, the capabilities that define performance at Dropbox are the uniquely human ones (awareness, judgment, adaptability, connection) and those capabilities already lived inside their people.
That insight led us to Prism. A prism does not add color, it takes light that is already present and reveals its spectrum. The metaphor held up because it described the philosophy underneath the programs. It gave us a name the existing components could live inside without losing their integrity, and a shape that future components could plug into. The naming process was iterative with dozens of directions for both the ecosystem and its components. The final naming ecosystem landed because it was strategy-led.
Our Approach
We applied Hoot's Brand Being Method™ to create the brand architecture.
The discipline of defining what a brand is and who it’s for before it does anything tactical is what kept Prism from becoming a marketing wrapper around existing programs. We treated Prism as a brand in its own right, with its own ethos, audience, and job to do inside Dropbox.
That meant foundational strategy first: what Prism stood for, who it served, and how it should function. From there we developed a proprietary Brand Tension Point which became the single reference point for every decision that followed. The tension captured what Prism had to hold at once: the authority of one interconnected system, and the warmth of a pathway built for the individual.
The Work
The Prism Playbook anchored the rollout.
It gives leadership and employees the language to understand what Prism is, how to use it, and why it matters so the ecosystem can scale beyond the L&OD team without diluting the brand.
We organized the ecosystem into five pathways and renamed the existing programs to live coherently inside them. Every name was built against the same principle: let Prism carry the conceptual weight, and let individual program names focus on clarity and function.
From there we executed across dozens of materials: experiential launch tactics, video teasers, blog and LinkedIn content for Dropbox leaders, internal messaging and communications to Dropbox employees, onboarding templates, slide decks, presentation talking points, and more.
The Impact
Prism gave Dropbox a unified architecture for something their team had been investing in for years. The existing programs kept their integrity but gained context. New programs can now be developed inside the ecosystem without re-litigating what learning at Dropbox means each time. Leadership has shared vocabulary for talking about development, both internally and in how Dropbox positions itself externally as a place to grow.
If you are ready to bring structure and shared language to something your team has been building, let's talk.