Skip to content

Best practices

The patterns we see in teams that get the most out of DXDT, condensed.

Your first week

  1. Connect your main cloud first — everything DXDT does is grounded in what it can see. Target: first integration connected within the hour (each one has a step-by-step install guide in the marketplace).
  2. Let the first scan land. Pulse usually finds real money in the first 24 hours; review the findings with the team.
  3. Set your timezone and Morning Report hour (Team → Features) so "morning" means your morning.
  4. Teach your first five facts. The conventions everyone on your team knows and no document records — that's the highest-value memory.
  5. Run one incident through a war room, even a small one, to make the muscle memory real before you need it at 3am.

Daily & weekly rhythm

  • Morning Report as standup opener — under a minute, one decision, done. Send it to a channel, not inboxes.
  • Work finding statuses honestly — resolve and dismiss deliberately; your savings, MTTR, and value numbers are only as true as your statuses.
  • Teach instead of tolerating noise — anything you've explained twice to a human, teach to DXDT once.
  • Sweep the Memory page monthly — retire facts that stopped being true. Wrong memory is worse than no memory.

CI change gate

  • Roll out in report-only mode first: dxdt plan review --fail-on never for a week, so the team sees the annotations without being blocked by them.
  • Then gate production repos at --fail-on high. Critical-only is too lenient (you'll only ever see it after the incident); medium is usually too chatty for busy repos.
  • Treat "not in your mapped graph" as a signal — it means DXDT has no blast-radius data for something you're changing. Connecting the missing integration is usually worth more than the review itself.

Incidents

  • Open liberally, resolve honestly, keep the timeline in the war room — the record compounds into institutional knowledge.
  • Wire auto-escalation (Team → Incident Management) once your triage severity mapping is trustworthy, not before.

Security posture

  • DXDT's analysis surfaces (Pulse scans, plan review, resilience analysis) are read-only — see the security model.
  • Never put credentials in taught facts or chat: integrations are configured through the marketplace, where secrets are handled as secrets.
  • Use SSO and scope API tokens minimally; read-only tokens are sufficient for CI plan review.