Growth, Engineering, and Support

Departments are optional execution profiles coordinated by the organization operator. Oblive supports Growth, Engineering, and Support only. This small fixed model keeps routing, context, permissions, onboarding, and profile behavior understandable.

Growth

Growth owns acquisition, activation, retention, positioning, and experiments. Useful context includes audiences, channels, lifecycle stages, messaging constraints, analytics sources, campaign history, and approval rules for public communication or spend.

Typical work:

• research a market or audience;
• analyze funnel evidence;
• prepare campaign or lifecycle material;
• design a bounded experiment; and
• report verified outcomes.

Engineering

Engineering owns product delivery, reliability, technical planning, and implementation. Useful context includes repositories, architecture, environments, deployment procedures, quality gates, incident practices, and ownership boundaries.

Typical work:

• investigate a defect;
• plan and implement a bounded change;
• review architecture and risk;
• prepare or verify a release; and
• turn support evidence into technical work.

Support

Support owns customer issue analysis, response preparation, escalation, and follow-through. Useful context includes customer segments, channels, response standards, policies, known limitations, escalation paths, and authoritative customer systems.

Typical work:

• categorize support themes;
• prepare evidence-backed responses;
• identify escalation conditions;
• connect recurring problems to engineering; and
• maintain customer follow-through.

Organization-Wide Work

Keep strategy, cross-department coordination, and unresolved routing with the operator. The operator can create department-owned durable work after the scope and evidence are clear.

Extending Capabilities

Add a skill or integration to an existing department before proposing another department identity. See Agent Packs, Skills, and Profiles.