Engineering process
Operators decide what we build next.
The people running a fleet all day see what the software is missing long before we do. This is the route from the thing you noticed on a Monday morning to the thing that ships.
The route
Where a request goes.
Every request lands in the same place and moves through the same five stages, whoever sent it.
01
Request
The idea, the operation behind it, and a screenshot of the screen you are fighting with.
02
Triaged
Read against what is already in flight and what other operators have asked for.
03
Shaped
Written up properly: the operation affected, the edge cases, the screens it touches.
04
Built
Engineering picks up the shaped brief, not the original sentence. Scope is settled by then.
05
Shipped
Out with the rest of the platform, usually landing in more than one product at once.
Writing one
Three things that move a request along.
None of this is a form to fill in correctly. It is the difference between a request that can be shaped and one that sits waiting for a conversation.
Describe the operation, not the control.
The first is one solution. The second is the problem, and it usually contains a better one.
Add a bulk edit button to the trips table.
On a school contract we move the pickup time for forty trips at once. Today that is forty edits in Overwatch, on a Monday, when we have the least time to do it.
Say how often, and what it costs.
Frequency is how one request gets weighed against another.
The driver list should be sortable.
Our controller looks for the longest-waiting driver around sixty times a shift, and every one of those is a manual scan down the list.
Show what you do instead today.
A workaround is a specification. It shows the shape of the thing to build.
We need better reporting.
Every Friday we export trips to a spreadsheet and rebuild the same account summary by hand. The spreadsheet is attached.
Tell us what is missing.
A couple of minutes, and it helps to have a screenshot ready before you start.
Already running on MyRide?
Something broken, or urgent, is a support conversation rather than a feature request. Your operations contact will get to it faster than this form can.
Contact usNot on MyRide yet?
Requests are open either way. If you would rather see the platform working before you ask it for anything, start here.
Get started