Work Classification Guide

This guide helps classify incoming work to determine the appropriate process and level of ceremony required.

The Three Categories

All work at Path2Response falls into one of three categories:

Key principle: PATH Epic Requirements apply to Initiatives and Non-Initiatives. Operational work can go directly to PATH with a clear problem statement and acceptance criteria.

Initiative

Initiatives are strategic projects that require full Stage-Gate process with executive oversight.

Qualification Criteria

An issue qualifies as an Initiative if it meets any of these criteria:

Process

Initiatives follow the full Stage-Gate Process:

1. Stage 1: Ideation — Problem validation, business case, success metrics
2. Gate 1 — Executive approval to proceed to planning
3. Stage 2: Planning — User stories, MVP scope, dev estimates
4. Gate 2 — Executive approval to proceed to development (PROD → PATH handoff)
5. Stage 3: Development — Build, test, deploy
6. Gate 3 — Executive approval to proceed to testing
7. Stage 4: Testing — Pilot, feedback, iteration
8. Gate 4 — Executive approval to proceed to launch
9. Stage 5: Launch — GTM execution, training, rollout
10. Gate 5 — Executive approval to close
11. Stage 6: Review — Metrics analysis, lessons learned, closure

Examples

• New product offering (e.g., Digital Modeled Audiences)
• Major platform capability (e.g., real-time scoring engine)
• Strategic partnership integration
• Compliance or security initiative with company-wide impact

Non-Initiative

Non-Initiatives are meaningful work that requires Product Management involvement but not full executive gate approvals.

Qualification Criteria

An issue qualifies as a Non-Initiative if it meets all of these criteria:

Process

Non-Initiatives follow a streamlined PROD flow:

1. PROD triage — Classify, validate need
2. Pre-development — Requirements, acceptance criteria (must meet PATH Epic Requirements)
3. Convert to PATH — Hand off to Development
4. Development — Build, test, deploy
5. Post-development — Training, documentation (scaled to size)

Key difference from Initiatives: No executive gate approvals required. COO + CTO provide oversight. Monthly reporting to executives for visibility.

PATH Epic Requirements Still Apply

Even though Non-Initiatives have streamlined approval, the work must still meet all PATH Epic Requirements before entering PATH:

1. The “Why?” — Problem from persona’s perspective
2. Acceptance Criteria — Clear, testable, binary
3. Source of Truth — Where data comes from
4. Impact Analysis — Effects on other systems
5. Priority & Stakeholders — Business value, who accepts
6. Release Parameters — Patch ASAP or standard release

Examples

• New report or dashboard for internal users
• Enhancement to existing product feature
• Client-specific customization
• Process automation for Production team
• Data quality improvement

Operational

Operational work is routine technical work that can go directly to PATH with minimal ceremony.

Qualification Criteria

An issue qualifies as Operational if it meets all of these criteria:

Process

Operational work follows a direct PATH flow:

1. PATH triage — Validate it’s a bug or clear technical task
2. Development Scrum Process — Prioritize, implement, test, deploy
3. Done — No post-development activities required

Key difference: No PROD involvement required. Development Lead (John Malone) owns triage and prioritization.

Minimum Requirements

Even Operational work needs:

• Clear problem statement — What’s broken or what needs to change
• Acceptance criteria — How do we know it’s fixed/done

Full PATH Epic Requirements are not required.

Examples

• Bug fixes and defect resolution
• Dependency updates and security patches
• Performance optimization (when scope is clear)
• Technical debt cleanup
• Configuration changes
• Documentation updates
• Routine data updates

Decision Flowchart

Use this flowchart to classify incoming work:

New Issue Arrives
        │
        ▼
Is it a bug or clear technical task? ─── Yes ──→ OPERATIONAL
        │                                         (Direct to PATH)
        No
        │
        ▼
Does it meet Initiative criteria? ─── Yes ──→ INITIATIVE
(Executive requester, strategic,              (Full Stage-Gate)
 high risk, cross-functional, large)
        │
        No
        │
        ▼
                    NON-INITIATIVE
                    (Streamlined PROD flow)

Quick Classification Questions

Ask these questions to quickly classify work:

1. “Is this a bug or obvious technical fix?” → If yes, likely Operational
2. “Did an executive request this?” → If yes, likely Initiative
3. “Does this affect company strategy or multiple departments?” → If yes, likely Initiative
4. “Is this a routine enhancement or improvement?” → If yes, likely Non-Initiative

Escalation and Reclassification

Work can be reclassified as scope becomes clearer:

Reclassification is normal. Initial classification is based on available information. As work progresses, reclassification ensures the right process is applied.

Summary Table

Related Documentation

• PROD-PATH Process — How PROD and PATH interact
• Stage-Gate Process — Full Initiative process
• PATH Epic Requirements — What “ready for development” means