Choose the Intervention

Assign system responsibilities and choose a maintainable solution to the actual problem.

Work in progress · 0/2 parts checked.

Understand the situation

Back at Northstar

Northstar now has evidence of missing owners and no shared acceptance event. That does not establish a need for AI scoring. It establishes work to do on ownership and measurement.

A GTM stack is a set of responsibilities. The CRM can hold current customer and ownership state. Messaging tools execute sends. An automation layer coordinates steps. A warehouse can join sources and preserve analytical history. AI can help interpret unstructured evidence. One product may cover several of these jobs.

I often keep shared operational logic in the CRM. That reduces duplicated rules, but it also increases dependence on that CRM. A separate orchestration layer can make migrations easier while adding another service to operate. No architecture removes the tradeoff.

“The best option might be a feature we already own. That still counts as engineering.”Taylor · Northstar Learning · Teaching case

Available now: A CRM with owner-assignment rules and editable acceptance fields.
Also available: An existing orchestration service operated by Taylor.
Known constraints: Do not create a second qualification policy or introduce unattended external sends.
Unknown: No evidence yet that a model would improve qualification.

Your GTM Engineering Project Brief

Your recommendation and notes from the example case.

Your notes or a problem you want to try next (optional)

Read the current brief

# GTM Engineering Project Brief

Learning exercise: Northstar Learning is a teaching example. These choices are not a deployed system or a claim of professional certification.

Current status: Draft or changed since validation

## Customer onboarding recommendation

### State the onboarding problem without blaming the team
- Observed problem: Not selected
- Who does this serve?: Not selected

### Choose the smallest recommendation that fixes the observed gap
- First intervention: Not selected
- Operating responsibilities: Not selected
- What still needs investigation?: Not selected

### Choose the evidence that would tell you whether the handoff improved
- Primary measure: Not selected
- Handling missing ownership: Not selected
- Review plan: Not selected

## Learning notes from the inbound case

### Problem brief
Sort what we know from what we are guessing: not currently validated.
Choose what to inspect before buying or building: not currently validated.

### Clients and outcome
Assign each responsibility to a real owner: not currently validated.
Choose the outcome all three teams can live with: not currently validated.

### GTM System Map
Build the five-part system map: not currently validated.
Say exactly what this handoff receipt proves: not currently validated.

### Architecture and decision note
Assign each fact or job to the system that should own it: not currently validated.
Choose a workable intervention and name the tradeoff: not currently validated.
Selected implementation: Not selected.

### Mini workflow contract
Route four requests into the right queue: not currently validated.
Put the recovery steps in the order you would actually run them: not currently validated.

### Measurement and review plan
Build the denominator from the actual records: not currently validated.
Choose the conclusion the evidence supports: not currently validated.

## My notes (not automatically graded)
No personal notes added.

## Source references
- https://gtmjosh.com/reference/gtm-engineer
- https://gtmjosh.com/reference/gtm-engineering-problem-solving
- https://gtmjosh.com/reference/gtm-engineering-vs-revops
- https://gtmjosh.com/reference/gtm-system-anatomy
- https://gtmjosh.com/reference/crm-entities-leads-contacts-accounts-opportunities
- https://gtmjosh.com/reference/gtm-tech-stack-architecture
- https://gtmjosh.com/reference/deterministic-rules-vs-ai-judgment
- https://gtmjosh.com/reference/gtm-engineering-use-cases
- https://gtmjosh.com/reference/gtm-workflow-specification-template
- https://gtmjosh.com/reference/handoff-contracts-between-systems
- https://gtmjosh.com/reference/retry-defer-and-escalation
- https://gtmjosh.com/reference/leading-and-lagging-gtm-indicators
- https://gtmjosh.com/reference/reporting-populations-and-denominators

Look it up in Reference

The explanation and implementation detail, without the exercise.

← Previous chapter Read next chapter →

Replay changes your reading position only. It keeps your drafts and earned history. Editing a checked answer makes that part need validation again.