Newsletter
You do not stop the work to fix the work. You just write it down
Four more months of our ticket log, and what it says about who is really writing things down at an engineering firm, and how to fix work without stopping it.
For engineering firm owners
Four more months of our ticket log, and what it says about who is really writing things down.
Updated November 2026 from my July letter. What changed: four more months of ticket data, which show fewer bugs, faster fixes, and that I file far more of them than the team does.

One of our engineers is closing out the month. He opens his timesheet to log his hours before the period ends. The system shows the wrong date. It is not urgent enough to stop what he is doing, and it is not something he should have to chase someone down about.
Before April, that was a Teams message sent at an odd hour, half explained, probably read as low priority by whoever saw it first. Maybe it got fixed. Maybe it got forgotten until it caused a real problem.
Instead, he filed a ticket and kept working. The ticket sat in a queue with a priority and an owner, and the fix happened in the background while the actual work of the firm kept moving.
That is the entire point. You do not stop operations to improve the tool. You capture the friction the moment you feel it, and whoever builds the tool works from the list.
We turned on tickets inside our own platform on April 14. When I first wrote to you in July, we had about 70. As I write this, we have 387. I want to tell you what the log shows now, because it is not the clean story you might expect from a CEO writing about his own software.
The bugs fell. The speed rose.
Four months changed what people write down.
In July I told you about 61 percent of our tickets were bugs, and that it meant we were early. That was true then. By the month each ticket was opened, the bug share since April runs 50, 72, 57, 48, 48, 52 and 32 percent, and 22 percent so far in November. In October, improvements to things that already work showed up in numbers for the first time: 44 of them, after none in September. People stopped writing "this is broken" and started writing "this could be better."
Speed changed too. A typical ticket opened in July took about 16 days to close. Of the 117 opened in October, 84 were closed within a day. Two honest limits. We did not stamp a finish date on many of the early tickets, so for those I used the last update. And the building changed hands: most fixes are now written in AI-assisted coding sessions, which is a different letter.

The part I did not want to print
The habit narrowed to one person, and that person was me.
In July I wrote that the team had used it hard. Here is the fuller picture. I have filed 60 percent of all 387 tickets. In September I filed 64 of 66, and only two people filed anything at all. A queue that only the CEO writes in is not a team habit. It is the CEO's to-do list with a nicer form.
If only the boss writes things down, the list fixes the boss's friction. The engineer with the wrong date on his timesheet goes back to sending a message at an odd hour, or to living with it.
It came back, partly. Since mid-October, other people have filed on 19 different days, and they wrote 34 of November's first 50 tickets. But most of that came from one or two people each month. Nine people have filed a ticket since April. In the last 90 days, 28 people logged time with us.

The ticket that changed my mind
It was not a bug at all.
I needed a comment response letter for a city's review comments. I pasted the reviewer's letter into a chat and asked the AI to build a response. It searched our own skill library, found we had no standard for that document type yet, and built the letter anyway. The whole exchange, the message and the reply, went into the queue as a ticket.
That ticket did what a ticket should. We now have a written standard for comment responses and a tool that builds the letter. The rule changed on the way. The tool lays out the reviewer's comments in their order, and the engineer writes every response. It never writes one for him. The AI drafted that first letter. It does not draft them now, and I think that is the better system.
In July I told you a team that gets two percent better every week becomes a different company. I cannot show you two percent a week. I can show you what the log did: more tickets, fewer of them bugs, faster fixes, and too many of them mine.
Here's the exercise for this week. Find wherever your team reports problems with its tools: a shared inbox, a chat channel, a list on someone's desk. Take the last 30 items and write down who raised each one, by role, not by name. If one person raised more than half, ask everyone else what they are living with instead of writing down.
Tell me who files yours, and how much of it comes from the top through our contact page. I read every one.
Michael Groselle, PE
Founder and CEO
Modern Engineering Solutions
mod-eng.com
Keep reading
More to read
- Your project manager inherits the files. Everything that actually matters stays with whoever sold the work
- 192 hours worked. $50,000 short on billing. The problem was not effort
- I spent eight rounds making a blind tool smarter. A plain chat beat it, so I closed it
- I told you to audit the setting. I didn't audit mine
What we do
Planning a project?
Talk to an engineerTalk to an engineer
Tell us about your project
An engineer reads it
Not a salesperson. Someone who can tell you whether the pathway is real.
You get a first answer
Your options, the agencies involved and the questions that decide cost and schedule.
You decide
No commitment to have the first call.
Prefer the phone? (214) 833-6748