There was a time in the not-too-distant past that the product design team at Learnosity didn’t have a defined set of design principles. Sounds strange now I say it, but with the accumulated knowledge on the team, our principles had just become an enshrined part of our day-to-day process. Sharing the drivers of our design practice with the wider team had simply never entered the conversation.
But that all changed while chatting idly to a newly hired product owner.
After shooting the breeze about the design team’s work and practice, she asked if they could take a look at our core design principles. My response was like something a a new-age guru or secret service agent might say: “Yeah we have them, but you won’t find them written down anywhere.”
The exchange was discomfiting because it revealed a problem that could have serious knock-on effects.
For one thing, if expertise of any kind is internalized, it’s siloed by default. And the danger with siloed information is that it not only lives with individuals, it leaves with them too, should they choose to move on.
Locking knowledge away like this is also contrary to our core values at Learnosity, which espouse collaboration (“Live to learn/Success is better shared”) and progress (“Aim higher”). To create a transparent work culture where everyone is rowing in the same direction you need to make knowledge and expertise available at all times. How can a company continue to evolve if guessing games are a surrogate for guidance?
The most-common misconception of design is that it exists solely to make stuff look good. A more sophisticated take is that design is most effective when fully integrated into a company’s overall product development strategy. It uses research to develop a deep understanding of users’ needs and employs creative problem-solving to try meet them.
"If expertise of any kind is internalized, it’s siloed by default. And the danger with siloed information is that it not only lives with individuals, it leaves with them too." Share on XIt’s no coincidence that the likes of Apple, Airbnb, Google, Zendesk, and IBM all give design a seat at the head table. Industry trendsetters employ design as a powerful differentiator. As InVision’s expansive “The New Design Frontier” report reveals, companies that invest in design tend to enjoy significant advantages over those who don’t:
“Companies with high design maturity in our model are more likely to see cost savings, revenue gains, productivity gains, speed to market, and brand and market position improvements through their design efforts.”
But it’s also important to recognize that design maturity is less a final destination than it is an ongoing process that only thrives when it has clear principles to navigate by.
If strong enough, those core principles can bring about positive outcomes in vital areas:
To expand on that last point a little – product design doesn’t just magically mature once you’ve put some principles in place. It begins to mature before then, during the very process of developing those core principles in the first place.
We kicked our own process off with some cross-industry research on how other companies approached things. This was purely illustrative for us since there is no “off the shelf” set of principles you can just take and run with; each company’s design principles should be unique to them because the problems they solve are unique. Still, there’s bound to be points of convergence you can use as a springboard.
Following this initial information-gathering phase, we began work-shopping using an “everything on the wall” approach. Basically, this involved getting the entire design team together to sound out thoughts and suggestions based on our individual experiences across a range of projects.
"Product design doesn’t just magically mature once you’ve put some principles in place. It begins to mature before then, during the very process of developing those core principles in the first place." Share on XWe followed this up by merging overlapping points into single overarching principles.
While we didn’t have a set number of principles in mind, we wanted to avoid over-complicating the project. Simplicity was key in getting other teams to buy into what we were doing and seeing the value in it. To keep on track, we conducted follow-up workshops and Q&A sessions with developers, product owners, and managers.
After some further tweaks and refinements, we finally settled on seven design principles that we were confident could serve as the foundation of our product design efforts.
Like anyone else, we use a ton of apps, software, tools, and documentation in our everyday lives and feel the same frustrations whenever we encounter a poor user experience.
Establishing a core set of design principles was our way of making sure that Learnosity’s products always offer a high-quality user experience even as our technology evolves.
Over time, we expect our principles will develop too. I hope this piece sheds some light on how we worked to raise our design standards at Learnosity in both our day-to-day and in the days (and years) to come.