Consolidate overlapping tools by integration quality…
When two tools provide overlapping functionality, consolidate to the tool that integrates better with your stack even if the eliminated tool has superior standalone features—integration quality dominates feature quality in compound workflows.
When This Fires
- When two tools in your stack serve the same function and you need to eliminate one
- When Map tool stack as a graph's visual mapping reveals redundant nodes
- When choosing between a feature-rich tool with poor integration and an adequate tool with excellent integration
- Complements When two tools hold the same data, designate one canonical… (single source of truth) and One tool as hub for thinking/synthesis, others as spokes… (hub-and-spoke) with the consolidation criterion
Common Failure Mode
Feature-first consolidation: keeping the tool with more features regardless of integration quality. The superior features are used 20% of the time; the integration friction is experienced 100% of the time. Net result: the "better" tool produces a worse daily experience.
The Protocol
(1) When two tools overlap, evaluate each on two dimensions: Standalone capability (how well does it perform the overlapping function?) and Stack integration (how smoothly does data flow to/from this tool within your overall stack?). (2) If one tool wins on both → easy choice. (3) If there's a trade-off (Tool A has better features, Tool B has better integration) → choose Tool B unless Tool A's feature advantage is critical (you literally cannot accomplish a necessary task without it). (4) "Critical" means you've identified specific tasks that require the feature, not that the feature "might be useful." (5) After consolidation, verify: has the integration friction decreased? Is data flowing more smoothly? If yes, the consolidation succeeded regardless of the feature trade-off.