본문으로 건너뛰기

Understanding Roles at Kyndof

At Kyndof, roles define what work gets done and who's responsible for outcomes. Unlike job titles that can vary between companies, roles represent consistent sets of responsibilities, authorities, and expectations.

Position Over Person: How We Think About Roles

We organize by positions (roles) rather than individuals. This distinction matters:

Position/Role = A defined set of responsibilities, authorities, and expected outcomes Person = The current owner/occupant of that role

Why this matters:

  • Roles persist even when people change
  • Responsibilities stay clear regardless of who fills the role
  • Career paths become visible (what roles lead to what other roles)
  • Organizational continuity survives turnover

Example: The "CMO" role owns brand strategy and marketing leadership. Today, that role might be filled by Alice. Tomorrow, if Bob becomes CMO, the role's responsibilities don't change—just the person executing them.

Role Categories at Kyndof

We group roles into several broad categories:

Leadership Roles

Examples: CEO, COO, CMO, Brand Lead, Department Heads Characteristics: Strategic decision-making authority, team oversight, cross-functional coordination

Leadership roles set direction, make high-stakes decisions, and ensure teams execute effectively. These roles are often Accountable in RABSIC matrices.

Explore Leadership Roles →


Design Roles

Examples: Fashion Designer, Pattern Maker, Graphic Designer, Creative Director Characteristics: Creative output, aesthetic judgment, technical craft skills

Design roles transform strategy and customer insights into tangible products and communications. They balance creative vision with practical constraints.

Explore Design Roles →


Operations Roles

Examples: Production Manager, QC Specialist, Logistics Coordinator, Operations Engineer Characteristics: Process execution, quality assurance, system maintenance, efficiency focus

Operations roles make things happen—they execute production, manage logistics, ensure quality, and maintain systems. These roles turn plans into delivered outcomes.

Explore Operations Roles →


Sales & Marketing Roles

Examples: Marketing Manager, Sales Lead, Social Media Manager, Partnership Manager Characteristics: Growth focus, customer interaction, brand building, revenue generation

Sales and marketing roles drive growth, build brand awareness, and manage customer relationships. They connect Kyndof's products with customers and partners.

Explore Sales & Marketing Roles →


Support Roles

Examples: Customer Support, Customer Success Manager Characteristics: Customer-facing, issue resolution, relationship management

Support roles ensure customers succeed with Kyndof products. They handle questions, resolve issues, and proactively help customers get value.

Explore Support Roles →


How Roles Relate to RABSIC

At Kyndof, we use the RABSIC framework to assign accountability for decisions and projects. Every role participates in RABSIC based on its authorities and responsibilities:

RABSIC RoleWhat It MeansCommon Kyndof Roles
ResponsibleDoes the actual workIndividual contributors, specialists, executors
AccountableOwns the outcome, approves final decisionsLeadership roles (CEO, CMO, Department Heads)
BackupSteps in if Responsible is unavailableCross-trained team members, deputies
SupportHelps Responsible complete workSupporting functions, enablement teams
InformedReceives updates after decisionsStakeholders, adjacent teams
ConsultedProvides input before decisionsSubject matter experts, advisory roles

Key principle: A role's RABSIC assignment can change based on the decision. The CMO might be Accountable for brand strategy but merely Consulted on technical infrastructure.


Role Attributes

Every role at Kyndof has several defining attributes:

Responsibilities

What outcomes this role is expected to deliver. These are results, not just activities.

Example (Production Manager):

  • Deliver products on schedule with acceptable quality
  • Manage vendor relationships to ensure supply reliability
  • Coordinate production planning across design and operations teams

Authorities

What decisions this role can make without seeking approval.

Example (Production Manager):

  • Approve vendor selection up to $X budget
  • Shift production schedules within tolerance ranges
  • Halt production for quality issues

Relationships

Who this role reports to, who reports to them, and key collaboration partners.

Example (Production Manager):

  • Reports to: Department Head (Brand Lead or CMO)
  • Collaborates with: Designers, QC team, Logistics, Procurement
  • Manages: Production staff, vendor relationships

Success Metrics

How we evaluate whether this role is performing effectively.

Example (Production Manager):

  • On-time delivery rate
  • Defect rate
  • Vendor performance scores
  • Budget adherence

Career Paths: How Roles Connect

Roles aren't isolated—they connect to form career progression paths. Understanding these paths helps you see where your role can lead.

Individual Contributor Path

Roles deepen expertise within a function:

  • Junior Designer → Designer → Senior Designer → Creative Director

Management Path

Roles expand scope and team leadership:

  • Individual Contributor → Team Lead → Manager → Department Head → Executive

Cross-Functional Path

Roles move across functions to gain breadth:

  • Designer → Product Developer → Brand Strategist

Specialist Path

Roles develop deep technical or domain expertise:

  • Designer → Pattern Maker → Master Craftsperson

Role Ownership

Every role has an owner—the current person filling that role. Role pages in this wiki describe the role itself, not the current owner's personal details.

What you'll find in role pages:

  • Role responsibilities and authorities
  • Common RABSIC assignments
  • Collaboration patterns
  • Success metrics

What you won't find:

  • Owner's personal information
  • Owner's individual performance data
  • Owner-specific interpretations of the role

For information about current role owners, use internal tools (org charts, Slack, HR systems).


Geographic Distribution

Many roles note a location (e.g., "Seoul"). This indicates:

  • Where the role is based for coordination purposes
  • Timezone considerations for collaboration
  • Local market context if relevant

Some roles may be remote or distributed. Location is noted for coordination, not as a requirement.


Reading Role Descriptions

When you explore a specific role page, you'll see:

  1. Role Overview: What this role exists to accomplish
  2. Core Responsibilities: Key outcomes expected from this role
  3. Key Relationships: Who this role works with most frequently
  4. When to Reach Out: What kinds of requests or questions to bring to this role
  5. RABSIC Context: How this role typically participates in decisions
  6. Skills & Expertise: What capabilities this role needs
  7. Related Roles: Similar or complementary positions

Next Steps

Explore specific role categories to understand what each type of role does:

Or browse by team or function to see how roles fit into the organization.


Navigation:

Back to: Wiki Home

Last Updated: 2026-02-03