Case study · Engineering
Three in the morning, one dashboard.
A backend engineer on a payments team gets paged at 3:10 a.m. Eleven windows are open from the evening. The one that matters is a Grafana tab whose title she can almost remember.
The desk
Priya carries the pager one week in six. Her laptop at night has a shape: Apple Terminal with a tab shelled into each of three production hosts, Chrome with a dozen Grafana and Datadog tabs left open since the last incident, the team runbook in Notion, Slack with the incident channel, and whatever she was reading before bed. All of it on a laptop screen, no monitor, in the dark.
The problem
The page says p99 latency, checkout. She knows there is a latency dashboard already open. The hunt used to go: Cmd-Tab to Chrome, the wrong Chrome, the one with the recipe, Cmd-` to the other window, scan twenty tab titles at ten-point type, give up, open a new tab, type the Grafana URL from memory, wait for it to load. Two minutes she will not get back, at 3 a.m., while a payment queue backs up.
What changed
Now she presses the front thumb button she mapped in VortexFlow and types lat. The spiral collapses to two cards: the Grafana tab titled "Latency, checkout" and a Datadog tab that mentions latency in its path. The first is already selected because it is the one she looked at most recently. Return. She is on the graph before the second Slack message arrives.
Then prod-db. Terminal's tabs are named after the host they are shelled into, so the spiral offers the exact session she wants rather than "Terminal." Then runb, the runbook. Then a hold-and-release of the button to bounce back to the graph. She has not used Cmd-Tab, and her eyes have not left the part of the screen she was reading.
The runbook and the incident channel are pinned into the spiral as links, so on a quiet week when neither is open, a tap still puts them one card away. When the incident closes she right-clicks the card for the Chrome window full of dashboards and picks Minimize; it is out of the recency order until the next page brings it back.
The setup
- Trigger
- Front thumb button on a Logitech mouse, found with Detect Button. Middle click left alone so links still open in new tabs.
- Layout
- Spiral. Icons only, so Screen Recording was never granted on a work laptop.
- Pins
- Runbook (Notion link) · #incidents (Slack link) · PagerDuty
- Search habit
lat,prod-db,runb, the first three letters of whatever she can remember.
What it did not fix
She still gets paged. The dashboards are still where the answers are, and the answers are still hard. What went away is the two minutes between the page and the graph, and landing in the recipe tab instead of Grafana.
A composite: the desk, the windows and the setup are drawn from how people actually use VortexFlow, but the person is a stand-in and nothing here is a testimonial. If this is your desk, tell us what we got wrong.