Skip to content

Team & Organization Management ​

EM-OS uses the concept of "Team Topologies" to define and visualize organizational structure, helping optimize cognitive load.

Team Topologies ​

You can define four types of teams based on their roles:

1. Stream-aligned Team ​

Teams that act on a continuous flow (stream) of product value. They handle everything from development to deployment and operation.

2. Enabling Team ​

Specialized teams that support stream-aligned teams in acquiring and practicing missing knowledge or skills.

3. Platform Team ​

Teams that provide the foundation (infrastructure, deployment tools, etc.) that other teams can use as self-service, increasing overall development efficiency.

4. Complicated Subsystem Team ​

Teams that specialize in developing and maintaining subsystems requiring high mathematical algorithms or complex processing.

Interaction Modes ​

There are three categorized ways teams collaborate:

  • Collaboration: Two teams work closely together temporarily to solve a common problem.
  • X-as-a-Service: One team provides a library or tool as a service for another team to consume.
  • Facilitating: An enabling team or similar supports and promotes the autonomy of other teams.

Tech Skill Management ​

Centrally manage and evaluate team members' tech stacks and proficiency.

  • Skill Matrix: Visualize skill sets like languages, frameworks, and tools in a grid format.
  • Approval Flow: When a member updates their skill level (self-declaration), the Team Lead receives a notification. The lead reviews and approves the update based on work output and 1on1 discussions.
  • Skill Evidence: Members can attach links to project outcomes or artifacts to increase evaluation transparency.

Team Analytics ​

Team Capability Analysis (Capability/Gap Analysis) ​

Visualize the gap between the skills the team currently possesses and the "expected requirements (Ladder)" needed to fulfill the team's mission.

  • Visualizing Gaps: Identify issues such as "We need one more senior Go engineer" or "Front-end knowledge is lacking across the team."
  • Use in Planning: Decide on next-period training focus points or define priorities in hiring based on the analysis.

Team Condition ​

Visualize the team's sentiment trend and engagement based on 1on1 data and survey responses.

  • Sentiment Trend: Graph positive and negative trends to detect early warning signs.
  • Keyword Analysis: Extract frequently mentioned topics (e.g., "tech debt," "pressure") from daily notes and records.

Member Management ​

Profiles & Permissions ​

  • GitHub/Google OAuth: Automatically sync profile info and avatars upon login.
  • RBAC (Role-Based Access Control):
    • Org Admin: Full permissions within the organization.
    • Lead: Team management, evaluation, ADR creation, and skill approval.
    • Member: General use.

Onboarding ​

New members complete Account Settings and a Skill Self-Check when they join. Admins assign teams when they invite members. See the Start Guide.

Integrated platform for engineering management · Terms · Privacy