top of page


Project is one of the most important core features of 1TM - after all, 1TM is all about collaborating with creators - and the goal of Project is to create a theme-driven collaborative hub for passionate creators who want to connect and make an impact together. We want to make it a place where creators can be free to be creative on a specific theme, while at the same time attracting supporters to spark their own ideas.

Role - UX, UI
Year - 2022

Project - 1TM

A 'theme-driven collaborative hub' may sound abstract, but it should be better understood through the following examples:

  • Titan, a PC case manufacturer, wanted to launch a series of Star Wars-themed cases with a strong personal touch. It was able to create a contest through 1TM to select the best creators and launch a co-branded creation with them.

  • Kevin and Elizabeth are both fans of science fiction and have always wanted to publish a collection of short stories based on the Matrix concept, but on the other hand were concerned that the content was not diverse enough. They could use 1TM to invite submissions from other fans and select suitable stories to publish the novel together.

  • Mary and her classmates in philosophy would like to start a series of courses to promote Jungian psychology and how it can be applied to life, and they can also use 1TM to create an experimental online course together to test the acceptance of such a course in the general market.

Creating a project is a straightforward function, but how can the concept of 'multi-person collaboration' be integrated into the project creation process in a way that is easy to understand and operate? "Theme-driven' means that we want every project to be on the same theme and we expect most of the content to be of a certain quality from a platform development standpoint. However, as a platform that is open to anyone, we cannot mandate the quality of user-generated content, so can the process be designed to guide the creators to create high quality content? In addition, given that projects can be created by individuals, teams or brands for different purposes, do we need to design different types of projects for different usage scenarios? We have integrated these requirements into the following three challenges:

  • How can a multi-person collaborative project be implemented?

  • How do we ensure high quality content and consistency of theme for the content in the project?

  • Can any kind of project be built using the same modular process?

In order to design a project function that allows multiple people to work together, the first step is to define what 'co-collaboration' looks like. Drawing on the concepts of crowdsourcing and co-creation, the goal of a project on the 1TM platform is to find partners who are interested in the same theme, create it together, make a profit from the results and share that profit together. In the final version we have chosen to achieve this goal with a submission system, which allows project founders to set up their projects as closed projects - where only team members can contribute - or as open projects - where anyone can participate in the creation of content. Multi-person collaboration also raises potential issues of access control, especially for large projects. Therefore, we have added the role of 'editors' as a management layer between the project founder and the general team members, who can accept or decline content submitted to the project by anyone other than the project founder.

1. Implementation of collaborative projects
Schematics - Project creators can set up various details of their projects
  • The project creator can decide how accessible the project is, how open the submission system is, how long it is open for submissions, etc

While it is common for platforms to use feedback mechanisms from other users (e.g. likes, comments, paid subscriptions, etc.) to promote interactivity and encourage creativity, 1TM is no exception, but for content in theme-driven projects, further mechanisms are needed to ensure consistency and quality. We believe that when starting a new project, the project founder has an initial idea of the outline of his/her project and is the one who cares most about the quality of the project content, and should be given the right to decide how the project's content should look like. The project founder can set the level of openness of the project, freely accept or decline any content submitted to the project, and decide the composition of the team. By giving project founders full control over the quality of their content, they are expected to control the quality of their own content, but this is only possible when the majority of project founders want their projects to succeed.

2. A review mechanism is in place to ensure that submissions are thematically consistent and encourage creators to create high quality content
Schematic - In the team page of a project, the project creator can invite and remove team members
  • On the project's team page, the project founder can invite and remove team members

Based on demand, we have finally defined three project types: topic, contest and course.

  • Topic-based projects are the most widely used of all types and can be used for basically any type of work.

  • Contest-based projects, as the name implies, are for competitions and require a set time, rules and rewards.

  • Course-based projects are for publishing a series of online courses.

To reduce the ease of creating projects, the backend user interface for each of the three types of project has been modularised and designed to fit as closely as possible with the frontend layout.

3. The three types of project that can be modularised
Schematic - Project Interface for Specific Topics
  • A topic-based project

Schematic - Design of different privileges for four types of project members
  • The four tiers of project members

Schematic - Only Founder and Editors can access the submission review page
  • The founder and editors-only submission review console

Schematic diagrams - Different states of the review system and the history of submissions
  • The review process is also displayed in the contributor's submission history, with the various statuses in the review system

Schematic - On the Review Submissions page, the project creator can decide whether to accept the submission or not
  • On the Review Submissions page, the project founder can decide whether to accept the submission or not

Schematic - Project Interface for Competitions
  • A contest-based project

Once a project has been created and officially launched, it will be exposed on a number of different pages on the 1TM platform, such as a landing page for all projects, a personal dynamic wall for project team members and followers, a dynamic wall for specific types of creations, keyword search results, etc., to maximise the impact. In terms of profitability, we plan to launch a project subscription system as an initial profit model, whereby subscribers' sponsorship money will be automatically sent to team members' wallets through the team wallet mechanism (link) according to a percentage set by the project founder. A positive cycle is created through the process of content creation, subscriptions, profit sharing, increased creation, increased subscriptions and increased profit sharing. In addition, we are also trying to develop web3 type projects and will be developing more diverse projects in the future.

Project exposure and profitability
Schematic - Project interface for Courses
  • A course-based project

Schematic - Modularized Project backend settings
  • Modular backend user interface

bottom of page