As an open community, Open Collective Design aims for designing new ways to create, share and deliver value from a design point of view.
The exponential growth of mobile technology has ushered in an age where time and attention is an increasingly scarce resource. Instead of technology enhancing our abilities as humans, we’ve seen it become a vehicle for extracting our attention, monetizing our personal information, and exploiting our psychological vulnerabilities.
As designers, we play a key role in the creation of such technology, and it’s time we take responsibility for the impact that these products and services we build are having on people it should serve.
These principles are meant to provide guidance for designing Open Collective as an ethically humane digital product through patterns focused on user well-being.
Empowering products enhance our abilities as humans without dictating our behavior by enabling us to accomplish our objective when we need it, and remaining out of the way when we don’t. We can achieve this by ensuring products center on the value they provide to people over companies.
Give people the control they need to manage the algorithms that shape their experiences.
Give people the control they need to manage privacy and anonymity.
Enable focus by avoiding unnecessary notifications.
"Utility alone won’t assuage us. We want empowerment. We want to be better people. We want technology to enhance our capabilities and increase our sense of agency without dictating the rhythm of our lives.”
Bottomless feeds and auto-play keep users from leaving but lock them into an infinite loop of consumption. We can maximize the overall quality of time spent by bounding the experience and prioritizing meaningful and relevant content.
Thinking inclusively is about considering diverse groups of people, how they will interact with your product, and their environments. It's a methodology that puts people's needs first and foremost to expand the reach of the product to the largest range of users possible.
Attention has become the scarce commodity of the digital age. As designers, we must consider how we deliver notifications to ensure we are respectful of their time, attention and overall digital well-being.
The presumption that reducing friction is virtuous onto itself is dangerous. We can embrace thoughtful friction to prevent harm and abuse, protect people's privacy and security, and steer them towards healthier digital habits.
Lack of transparency erodes trust in a product. We can prevent this erosion by demanding that the products we design are clear and honest about the data that’s being collected from users and why it’s being collected, how this data will be used, and avoiding dark patterns that exploit human psychological vulnerabilities.
Understanding the context (Particular and general) that the project involves, and think about specific solutions to that project.
Flesh out the design solutions, documenting the process.
Prototyping and testing
Launching the solution with a public release.
Figma is the design tool of OC design, every interface design will be hosted inside this design repository. And it serves to fellow designers to contribute with their craft, and also for non-designers working with OC Design to obtain information and resources of the design toolkit of the organization.
The first thing you encounter with is this primary breakdown of the work:
Most of the projects related with interface design will be hosted inside the 02 → OpenCollective.com folder, that breaks down again the efforts with this organization:
The next level is each individual file, that may include several interface elements, pages and flows of the platform and the website, it looks something like this:
Here you can obtain assets, individual characteristics of each elements and make specific questions.
Every task is linked with the OpenCollective team and the code repository through GitHub.
To better understand GitHub and its functioning we encourage you to consult its knowledge base.
We break down big goals to specific tasks using the following logic:
There are different ways to get in the loop of design-related tasks in GitHub: