Idea Ripper // ArchiveCards: 1555 [Live] | Updated: 2026-10-14
Card #c1315IR // #c1315Synthesis

"Everyone thinks, ‘My data is my data, and that’s exactly the way I want it.’ My advice is to get your arms around your data and decide what you want and can do before you get started."

— In our words · Source: Digital Impact (Steve Lucas)

[Use when]

You're starting a project that merges information owned by several teams.

[Why it matters]

Cornell's integration architect, John Parker, found the hard part was matching data to satisfy parties who each wanted it their own way. Agreeing on scope first avoids building something no side accepts.

Filed under situations:When you’re building the thing, not just planning itWhen the other side has more leverage

More from Digital Impact

#c1300"“We’ve learned to bite off smaller pieces with our integrations, get them working well, and then expand." "When they ask for a car, they…You're building something large for non-technical stakeholders who need to see progress. #c1301"“Previously, we were built for large-scale project implementations. We’d take three to five years and roll them out only when they were as…Your team holds releases until they're nearly perfect and projects take years. #c1302"They want to pick up the phone because that might be their weekly conversation with somebody." "Efficiency isn’t always the right measure…You're automating away a customer touchpoint and measuring only time saved.

Same situation, different book

#c1274Unpack and reframeA negotiation is stuck on one big all-or-nothing issue.From The Oxford Handbook of Modern Diplomacy #c1270Signing is the beginningA hard-won agreement has just been signed and attention is moving elsewhere.From The Oxford Handbook of Modern Diplomacy #c1264Build a workaround when the formal check failsThe agreed method of checking compliance has been blocked by someone outside the deal.From The Oxford Handbook of Modern Diplomacy #c1561The Canon: Sensory Infallibility, Preconceptions, and "Waiting"Use when diagnosing why a high-stakes analysis, intelligence assessment, or debugging effort went wrong…From Lives of Eminent Philosophers