Discover Before You Build
The biggest integration failures happen when teams skip this phase. Before touching a single API, understand how people actually work today — their workarounds, frustrations, and informal systems.
✓
Map the Human Workflows
Research
Interview or survey 8–12 people across teams who will be affected. Document not just what tools they use, but why and how they've adapted them. Shadow at least 2–3 people doing their actual daily work.
💡 People Angle: Ask "What would you never want to lose?" — the answers reveal what truly drives culture, not just process.
✓
Audit Existing Tools & Shadow IT
Technical
Catalog all tools in use (sanctioned and unsanctioned). Note which teams built their own spreadsheets, scripts, or workarounds. These unofficial systems often encode important institutional knowledge.
💡 People Angle: Never shame shadow IT. Recognize it as evidence of unmet needs and invite its creators into the design process.
✓
Identify Champions & Skeptics
Culture
Map out who will influence adoption. Find the informal leaders — the people others ask for help. Identify early adopters AND the most vocal skeptics (they're your best quality checkers).
💡 People Angle: Bring skeptics in early as advisors, not obstacles. Give them a formal role in the process.
✓
Define the "Why" in Human Terms
Strategy
Write a one-paragraph integration rationale in plain language — no jargon. It should answer: what problem does this solve for the people doing the work? Share it and test if people nod along.
💡 People Angle: If you can't explain it without mentioning "efficiency" or "scalability," you need to re-examine the real human benefit.
Align Before You Build
Integration projects stall because of misaligned expectations, not technical failures. Invest in shared understanding across stakeholders before any system design begins.
✓
Co-design with Cross-functional Teams
Culture
Run 2–3 design workshops that include IT, operations, and frontline users. Use journey mapping to design integrations that reflect how work actually flows across roles — not just org chart lines.
💡 People Angle: When people help design their tools, they defend them instead of resisting them.
✓
Set a Data & Access Philosophy
Technical
Agree upfront: who owns what data, who can see what, and what the integration will and won't do. Document this clearly. Ambiguity here breeds political conflict and erodes trust.
💡 People Angle: Transparency about data visibility reduces fear of surveillance. Be explicit that integration ≠ monitoring.
✓
Establish an Integration Council
Governance
Create a small steering group (5–7 people) with reps from each affected area. Give them real decision-making power on priorities and tradeoffs. Meet bi-weekly during the project.
💡 People Angle: Distribute ownership, not just information. People commit to decisions they helped make.
✓
Define "Done" Together
Strategy
Agree on success metrics that mix technical AND human signals: API uptime + user satisfaction score + adoption rate + qualitative feedback. Write these down and share them widely before work begins.
💡 People Angle: If the only success metric is technical, the human side will be forgotten.
Roll Out with Humans at the Center
A technically perfect integration that people don't adopt is a failure. Plan your launch around behavior change, not feature delivery.
✓
Phased Rollout with Pilot Groups
Technical
Start with a small, willing group (ideally 10–20 people). Run for 4–6 weeks. Use this group to surface real issues before broader launch. Treat them as collaborators, not test subjects.
💡 People Angle: Let pilots self-select when possible. Enthusiasm is contagious — willing early adopters become your best advocates.
✓
Build a Champion Network
Culture
Train 1 champion per team or department. These are peers, not IT staff. Give them slightly deeper knowledge, a feedback channel, and recognition for their role. They bridge the gap between technical teams and everyday users.
💡 People Angle: People trust their colleagues more than help desks. Peer support drives adoption more than documentation.
✓
Communicate the Story, Not Just the Update
Culture
Each communication milestone should tell a story: what's changing, why it matters for *this specific audience*, what's staying the same, and what to do next. Avoid generic "exciting news" announcements.
💡 People Angle: Segment your communications by role. What matters to a developer is different from what matters to an ops manager.
✓
Create Feedback Loops Early
Strategy
Set up a visible, low-friction channel for feedback (Slack channel, short weekly survey, office hours). Respond publicly to feedback — even if the answer is "not yet." Show people they're being heard.
💡 People Angle: Ignored feedback breeds cynicism. Acknowledged feedback — even when the answer is "no" — builds trust.
Embed & Sustain the Change
The integration isn't done at launch — it's done when it's invisible. The goal is for the new way to become the default, not an extra burden people tolerate.
✓
Measure Adoption, Not Just Uptime
Strategy
Track active usage rates, not just logins. Survey users at 30/60/90 days post-launch. Look for drop-off patterns — they signal friction points that need addressing.
💡 People Angle: Low adoption is information, not failure. Treat it as a signal to investigate, not a reason to push harder.
✓
Update Onboarding & Team Rituals
Culture
Integrate the new tools into new hire onboarding. Update team rituals (standups, retrospectives, planning) to use the new system as a natural part of work — not an add-on.
💡 People Angle: Culture is carried by rituals. If the new tool isn't part of daily rituals, it will slowly fade.
✓
Run a 90-Day Retrospective
Governance
Bring the Integration Council back together at 90 days. Review what worked, what's still broken, and what you'd do differently. Document it. Share the learnings broadly — this builds organizational trust and learning capability.
💡 People Angle: Public retrospectives signal psychological safety. They say: "We're not pretending this was perfect."
✓
Celebrate the People, Not Just the Tech
Culture
Recognize the champions, early adopters, and feedback contributors by name. Share stories of how the integration improved someone's actual workday. Make the human win as visible as the technical win.
💡 People Angle: What gets celebrated gets repeated. Recognizing adoption behaviors encourages them in the next change initiative.