Spend your time on architecture and your team, not on admin
Half your week disappears into the coordination around incidents and hiring instead of the IC work you signed up for. this+that reads every channel for you, pulls out the action items, and routes each one where it belongs. The hours you get back go into the technical decisions and the team development that nobody else can do.
Engineering management lives across too many systems
An alert fires and you are in two places at once, fixing it in Slack while briefing stakeholders over email, all the while trying to remember the postmortem items nobody has written down yet. Meanwhile a strong candidate who cleared the phone screen on Tuesday still has no technical round booked by Friday, because the scheduling email is buried under a Slack ping and a review request.
A pull request sits open for three days, the reviewer is heads-down, and the sprint quietly slips. You hear about it in the retro. And underneath all of it runs the steady drip of management work: 1:1 prep, a team ask, a cross-team thread waiting on your call. None of it is hard on its own. The context switching is what eats the day.
Everything that needs you, in one place
DoBox is one task list fed by your GitHub notifications, your team Slack, and your email at the same time. It does not just collect, though. It reads what comes in and extracts the actual work. The P0s buried in a postmortem email and its trailing Slack thread get scanned out for you, so nothing important is left to memory once the adrenaline wears off and you are no longer the single point of failure for what the team agreed to fix.
Hiring stops leaking the same way. A candidate follow-up or an interview that still needs scheduling surfaces while it can still be saved, not after the offer has gone cold. Even a PTO note or a promotion conversation shows up with its full thread attached and a link back to the source, which means you are never rebuilding what was said from a one-line notification.
The overhead that fragments your day, handed to a workflow
You write the rule in plain English and this+that wires it across the tools you already use. With GitHub and Jira connected, it fires the moment the trigger happens, with nothing to log by hand. Tell it "after an incident, open Jira tickets for every action item in the postmortem email, tagged P0 with owners assigned," and incident cleanup stops being a manual chore. A recurring one is just as easy: "Monday morning, which PRs have been open more than 3 days with no review activity?" Two others that earn their keep here:
It also quietly handles the smaller stuff: a PTO note updating the team calendar, an after-hours alert paging the on-call engineer, whatever your team keeps doing by hand.
The difference is who does the wiring
Most tools show you a notification or hold a task, then leave you to be the wire between the two: read the alert, work out what it means, open the ticket, find the owner, send the message. this+that does that part. The time you used to lose to it is yours again.
See what this+that can do with your inbox.
Connect your inbox and watch the work already buried in it surface in under 2 minutes. No signup required.