90
edits
Engagement/Brand and Identity Guide: Difference between revisions
column width
(added table) |
(column width) |
||
| Line 22: | Line 22: | ||
{| class="wikitable" ; width: 900px;" | {| class="wikitable" ; width: 900px;" | ||
|- | |- style="width: 100px;" | ||
! | ! | ||
! Experiments | ! Experiments | ||
! Projects | ! Projects | ||
! Initiatives | ! Initiatives | ||
| Line 32: | Line 32: | ||
| the earliest stage. Maybe the work is still in a planning phase, or maybe just ideas. There are probably just a few people (or less) working on it || An experiment becomes a project when it begins to have more official work being done on it. This may mean more people contributing, or maybe a plan to dedicate additional resources. The naming structure doesn’t change from the Experiment stage, so from an outside perspective it might be a pretty seamless transition. || Initiatives are long-term strategic areas of investment. Initiatives don’t just have resources dedicated to them, but are also publicly identified as priorities for Mozilla. At this point the “Project” is dropped from the name. There might be a quick naming assessment done at this point to make sure that the name doesn’t have any legal issues or actively cause harm in any way. || Being a Product means that enough work has been completed to be released more broadly into the market with a well thought out value proposition for users and go-to-market strategy. A product must have more complete branding work done (like having an official name, logo, etc), so it’s at this time that a full product naming exercise and logo design process would occur. | | the earliest stage. Maybe the work is still in a planning phase, or maybe just ideas. There are probably just a few people (or less) working on it || An experiment becomes a project when it begins to have more official work being done on it. This may mean more people contributing, or maybe a plan to dedicate additional resources. The naming structure doesn’t change from the Experiment stage, so from an outside perspective it might be a pretty seamless transition. || Initiatives are long-term strategic areas of investment. Initiatives don’t just have resources dedicated to them, but are also publicly identified as priorities for Mozilla. At this point the “Project” is dropped from the name. There might be a quick naming assessment done at this point to make sure that the name doesn’t have any legal issues or actively cause harm in any way. || Being a Product means that enough work has been completed to be released more broadly into the market with a well thought out value proposition for users and go-to-market strategy. A product must have more complete branding work done (like having an official name, logo, etc), so it’s at this time that a full product naming exercise and logo design process would occur. | ||
|- style="text-align: center; | |- style="text-align: center; | ||
! Naming | ! Naming Structure | ||
Structure | |||
| [ Project + UniqueName ] || [ Project + UniqueName ] || [ UniqueName ] | | [ Project + UniqueName ] || [ Project + UniqueName ] || [ UniqueName ] | ||
drops "Project" prefix | drops "Project" prefix | ||