Skip to content

Team Structure #3

Description

@grandchildrice

About

This is the overview for our team.
You can understand

  • ✅ How many department do we have
  • ✅ How do the different departments relate to each other
  • ✅ What should you do as a member of a department

Structure

flowchart TB
	classDef class1 fill:#ffa23e
	Director:::class1 --> GrowthManager:::class1
	GrowthManager --> PR
	GrowthManager --> CM
	GrowthManager --> UX
	Director --> PdM:::class1
	PdM --> Designer:::class1
	PdM --> Engineer:::class1
	Director --> Corporate
	Director --> Finance
Loading

Depertment

Department Part Output
Director - Designing the Core of the product
- Planning & Making a decision of Roadmap Strategy
Good things
Growth Manager - Managing Community
- Planning growth strategy
- Planning and Executing Collaborations
Increasing User count & Engagement
Product Manager - Managing progress and deadline
- Managing workers
Keep up Speed
Engineer - Developing Source Code
Designer - Designing UI, UX
- Visualizing the Vision
Design

Flow

sequenceDiagram
	Director->>+Growth Manager:Plan Strategy
	actor user as Mass/Community/User
	Growth Manager->>user:Sale
	user->>Product:CV
	Director->>+PdM: Design System/Features/Techs
	Growth Manager->>PdM: Propose new Feature
	Engineer->>PdM:PdM: Propose new Feature/Techs
	Designer->>PdM:Propose new Feature
	PdM->>Designer: Define Feature Requirement
	Designer->>PdM: Design UI/UX/Graphic
	PdM->>Engineer:Define Task
	actor Product as Product
	Engineer->>PdM:Implement
	PdM->>-Product:Release
	Growth Manager->>-user:PR
	user->>Product:Retention
Loading

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions