Testing ability to choose the right coordination model for your structural reality
Overview
This diagnostic tests whether you can determine when federation (loose coupling, strong interfaces) versus integration (tight coupling, shared standards) is appropriate for a given coordination scenario.
You’ll see 10 situations requiring coordination decisions. The pattern to recognize: who pays coordination costs, who controls standards, and whether you can force compliance determines which model works. Choosing integration when you need federation (or vice versa) creates predictable coordination failures.
Time to complete: 10-12 minutes
Question format: Multiple choice (1 correct answer per scenario)
Scoring: 7/10 = Pass (you understand federation vs integration trade-offs)
Result interpretation: Generates personalized guidance based on patterns
Note on answer choices: Some scenarios include responses that favor integration because it’s technically cleaner or federation because it’s politically safer. The “correct” answer represents the response that best matches coordination model to authority structure and mission needs.
Want to understand how each model choice creates different outcomes? You can retake the diagnostic and select different options to see the feedback for each scenario. Each represents a different context where model selection determines coordination success or failure.
What These Results Mean
These patterns emerged from 20+ years coordinating federated systems (NATO partnerships, federal interagency coordination, coalition operations, multi-agency disaster response) where authority structures and stakeholder constraints determined which coordination model could succeed.
If you recognized patterns you’re currently experiencing and want to discuss your specific coordination challenges: moc.irtlevynohtna@ynohtna
What This Diagnostic Reveals
If you scored high, you already know that model selection depends on:
- Whether you can compel compliance (determines if integration is possible)
- Whether standardization serves entities better than local optimization (determines if integration is appropriate)
- Who pays coordination costs (integration = entities pay, federation = you pay)
- Whether local variation is legitimate or failure to standardize
If you scored low, you’re probably choosing models based on technical preference rather than structural reality. The symptoms show up as:
- “We implemented shared standards but stakeholders won’t comply” (integration forced on federation problem)
- “We’re maintaining interfaces to 20 different systems when we have authority to consolidate” (federation when integration would serve better)
- “Stakeholders resist our enterprise platform because it doesn’t fit their operations” (integration degrading local effectiveness)
- “We can’t force them to adopt standards so coordination fails” (didn’t recognize federation requirement)
These aren’t implementation problems. These are model-selection problems where integration assumptions meet federation reality, or federation approach wastes resources when integration authority exists.
The Two-Question Framework
Use this framework for every coordination decision:
Question 1: Can I compel compliance?
- Yes (you have authority, direct reports, contractual leverage) → Integration is possible, proceed to Question 2
- No (sovereign stakeholders, different legal entities, can’t force adoption) → Federation required, don’t proceed to Question 2
Question 2: Does standardization serve entities as well as local optimization?
- Yes (shared model benefits everyone, eliminates redundant custom development) → Choose integration
- No (entities have legitimately different needs, standardization degrades local effectiveness) → Choose federation despite having authority
Critical insight: Having authority to compel doesn’t mean you should integrate. Authority determines what’s possible. Value to entities determines what’s appropriate.
Common Model-Selection Failures
- Integration forced on federation problem: You design shared platform requiring stakeholder adoption, but lack authority to compel. Stakeholders decline. Platform fails.
- Federation when integration would serve better: You maintain expensive interfaces to 15 different systems when you have authority to consolidate and shared system would serve everyone better.
- “Consistency” used to justify harmful integration: You force field offices to standardize operations when local variation serves different regulatory/demographic contexts better.
- Seeking consensus when you have authority: You delay integration decision requiring unanimous agreement when you have authority to decide and integration serves mission.
Next Steps
If you passed this diagnostic: You understand model selection. Consider taking the Template Trap diagnostic to see when pre-packaged solutions force integration assumptions, or the Escalation Sink diagnostic to recognize deputization without authority.
If you didn’t pass: Start with these foundational resources:
- Read Doctrine 01: Federation vs Integration in Mission Networks to understand core model differences
- Study Field Note: When You Cannot Force Compliance to see federation succeed at scale
- Review Field Note: When You Choose Integration over Federation On Purpose to understand when integration serves better
Remember: Federation and integration aren’t preferences – they’re structural requirements determined by authority and stakeholder constraints. Can you compel compliance? Does standardization serve entities? These questions determine which model works, not which you prefer.