Testing recognition when pre-packaged solutions prevent custom coordination architectures
Overview
This diagnostic tests whether you can recognize when pre-packaged coordination solutions (templates, frameworks, playbooks) force integration thinking on federation problems.
You’ll see 10 scenarios where ready-made solutions promise efficiency but create coordination failures because they assume authority you don’t have, standardization stakeholders won’t accept, or uniformity that doesn’t match your coordination context. The pattern to recognize: templates optimized for one coordination model fail catastrophically when applied to different structural realities.
Time to complete: 10-12 minutes
Question format: Multiple choice (1 correct answer per scenario)
Scoring: 7/10 = Pass (you recognize template trap patterns)
Result interpretation: Generates personalized guidance based on patterns
Note on answer choices: Some scenarios include responses that favor template adoption because it’s easier than custom design. The “correct” answer represents the response that best matches coordination solution to structural reality, not the path of least resistance.
Want to understand how each template trap manifests? You can retake the diagnostic and select different options to see the feedback for each scenario. Each represents a different mismatch between template assumptions and coordination reality.
What These Results Mean
These patterns emerged from observing coordination offices that adopted pre-packaged solutions (enterprise collaboration platforms, governance frameworks, standard operating procedures) without examining whether template assumptions matched their authority structures and stakeholder constraints.
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 template traps show up as:
- Templates assuming integration authority when you need federation approach
- Pre-packaged governance frameworks requiring stakeholder compliance you can’t compel
- Standard operating procedures ignoring legitimate stakeholder variation
- Enterprise platforms forcing uniformity that degrades local effectiveness
If you scored low, you’re probably applying templates right now that don’t match your coordination structure. The symptoms show up as:
- “The governance framework says stakeholders must comply but they won’t”
- “The template worked for the vendor but doesn’t fit our stakeholder constraints”
- “We implemented the standard process but stakeholders create workarounds”
- “The collaboration platform assumes everyone uses same tools – they don’t”
These aren’t implementation failures. These are template-reality mismatches where pre-packaged solutions assume authority structures, compliance capability, or stakeholder uniformity you don’t have.
Before Adopting Any Template
Ask these questions about the template:
- Authority assumption: Does this template assume I can compel stakeholder compliance? Do I actually have that authority?
- Uniformity assumption: Does this template require stakeholders to standardize? Do they have legitimate reasons for variation?
- Integration assumption: Does this template require tight coupling? Or can I adapt it for federation (loose coupling, strong interfaces)?
- Context match: Was this template designed for coordination context like mine? Or different authority structure?
- Customization cost: If template doesn’t fit, what’s the cost to customize versus building from scratch?
If template assumptions don’t match your reality, the template will fail regardless of how well it worked elsewhere.
Next Steps
If you passed this diagnostic: You recognize template-reality mismatches. Consider taking the Escalation Sink diagnostic to identify deputization traps, or the Meeting Proliferation diagnostic to see when coordination infrastructure becomes governance theater.
If you didn’t pass: Start with these foundational resources:
- Read Doctrine 01: Federation vs Integration to understand when templates force integration on federation problems
- Review Doctrine 15: Architecture Must Accelerate Teams to see when templates become bottlenecks
- Study Field Note: When You Cannot Force Compliance to see federation approach succeed where integration templates failed
Remember: Templates are optimized for specific coordination contexts. Before adopting any pre-packaged solution, verify its assumptions match your authority structure and stakeholder constraints. Template-reality mismatch creates coordination failure regardless of how well the template worked elsewhere.