Major initiatives fail in multi-division companies for predictable structural reasons. The wrong division committed. The parent brand was implied without approval. Two divisions discovered they were building incompatible versions of the same public promise.
Governance checkpoints exist to surface those problems early.
What Counts as Major
At Null Space Productions, an initiative is treated as major when it includes one or more of:
- Cross-division resource dependencies (for example, NWP build work for NWMkt launch infrastructure)
- Public commitments referencing multiple division brands or the parent company
- New external partnerships representing more than one division
- Material changes to division web properties that affect portfolio navigation or structure
- Trading or risk-impacting changes within NWT that alter documented frameworks
Not every project is major. Division-internal work inside mandate should proceed without portfolio-level review by default.
Checkpoint Stages
The governance model uses practical stages rather than ceremonial committees:
1. Mandate check. Does this initiative belong to the proposing division's scope? If not, stop or reassign before planning deep work.
2. Cross-division scan. Does execution require NWP, NWM, NWE, NWT, or NWMkt resources outside the proposer's control? If yes, document owners and approvals.
3. Brand and messaging review. Will external audiences interpret this as a parent-company promise? If yes, parent-brand standards apply.
4. Resource alignment. Does allocation match documented priorities? Resource allocation principles apply, not ad hoc escalation.
5. Launch readiness. Are division sites, routing, and accountability clear post-launch? Ambiguous ownership creates post-launch governance debt.
Division Examples
- NWE creative launch distributed at scale through NWM channels: cross-division scan and messaging review
- NWMkt campaign depending on NWP infrastructure: resource alignment before build starts
- NWT operational change affecting documented risk frameworks: mandate check with oversight emphasis
- Parent site structural update affecting division routing: brand and messaging review
Examples illustrate patterns. They are not an exhaustive approval catalog.
What Checkpoints Are Not
Checkpoints are not permission to slow division autonomy. They are not a substitute for division leadership. They do not require parent involvement in routine operational decisions.
They are a filter for initiatives whose blast radius exceeds one division's mandate.
Portfolio Discipline
Five divisions create more coordination surface area than one. That is acceptable if governance checkpoints are habitual before major initiatives, not improvised after public embarrassment.
Five divisions. One governance model. Checkpoints are how the model stays real under growth.