Two engineers investigating an issue together at a technical workstation.

Engineering

From the issueto a reviewable change.

Give engineering the customer evidence, code context and decisions behind the work. Prepare changes and explanations that the team can inspect before they ship.

Talk to our team See the examples

Example systems

GitHub

Linear

Slack

Notion

Google Docs

Engineering

Give the next engineer a clear starting point.

Carry customer evidence into a proposed fix, investigate recent changes and preserve the reasoning behind technical decisions.

01 / Code review

Give the bug a path to review.

Carry the customer screenshot into a proposed layout fix, a regression check and a pull request for an engineer to inspect.

Slack#engineering

Illustrative workflow

Engineer

The export button is off-screen on mobile. Use this customer screenshot to investigate the layout and prepare a fix.

Customer screenshot

MiloAI

Ready for review

Connected records and company memory reviewed.

Here’s the proposed fix and regression check.

Proposed pull requestReview requested

Keep export reachable on mobile

ExportActions.css+4 −1

  .export-actions {-   flex-wrap: nowrap;+   flex-wrap: wrap;  }+ .export-button {+   flex-shrink: 0;+ }

Proposed regression check

At 320px, the export button stays inside the viewport and remains reachable by keyboard.

Review details

SlackCustomer screenshot

The export button falls outside the mobile viewport.

GitHubExport toolbar layout

The action row does not wrap on narrow screens.

Company brainMobile release checklist

Export and adjacent controls must remain reachable at 320px.

Build this workflow with us

02 / Incident investigation

Start the investigation with what changed.

Milo assembles the release changes, linked tickets and earlier incident notes into a timeline, keeping confirmed facts separate from possible causes.

GitHub

Slack

Notion

Build this workflow with us

Checkout incident · illustrative events

Incident timeline

09:10
Release v2.18 deployed
Release notes: payment retry handling changed in PR #318.
09:18
First checkout error report
The on-call Slack thread reports failed checkout attempts.
09:26
Earlier incident linked for review
INC-072 describes a payment timeout; similarity is not evidence of the same cause.

Cause unconfirmed

Compare the failing requests with PR #318 and the earlier timeout before proposing a rollback.

03 / Technical decisions

The decision reaches the next engineer.

Milo records the chosen approach, rejected alternatives and unresolved tradeoff, then prepares linked updates for the engineering documents and ticket.

Slack

Notion

Linear

Build this workflow with us

Decision record + proposed ticket update

ADR-014 · preserve the existing endpoint

Decision: Keep /v1/accounts for existing clients.
Alternative rejected: Moving all clients to /v2 now would require a coordinated migration.
Open tradeoff: How long should both versions remain supported?

Proposed update · ENG-218

Add a compatibility check for current /v1 clients; leave the /v1 retirement date unset until the team decides.

Engineering

Bring us the issue your team keeps reconstructing.

Talk to our team