Newsletter

You added the engineers. The throughput did not follow. Here is what we found in the calendar

There are two calendars to read before the next hire: your senior PE's day, and your jobs' weeks. The second one surprised me.

Updated · First published

For engineering firm owners

There are two calendars to read before the next hire: your senior PE's day, and your jobs' weeks. The second one surprised me.

Updated November 2026 from my April letter. What changed: I took out an engineer's story I never measured and a Microsoft figure I misread, and put in what our own records show.

Two panels. The person's day: 39 percent of senior engineers' activity fell on weekday evenings and early mornings, against 26 percent for the rest of production. The job's calendar: 68 percent of a typical finished job's days for one repeat client s
Figure: Two calendars: when senior engineers work, and how much of a finished job sits waiting. Our own records, measured Nov. 5, 2026.

You've been hiring. Licensed PEs are hard to find, and every hire came at a premium. You modeled the capacity those hires would add. A year in, throughput looks the same. Your COO can't give you a clean answer, and your board will ask again at the next quarterly.

In April I told you I'd found the answer in one engineer's calendar: most of his day was reactive, and his output doubled once we fixed it. I never measured either number, so the story is out. Here's what I can measure.

The first calendar is the person's day.

Microsoft doesn't break its numbers out for engineers. Check your own firm.

Microsoft's 2025 Work Trend Index, built on Microsoft 365 signals across every industry, says the average worker gets 153 Teams messages per weekday and 117 emails a day. Forty percent of people online at 6 AM are reviewing email. By 10 PM, 29 percent of active workers are back in their inbox.

We checked ours: twelve months of Teams posts, file saves and sent mail for our three senior engineers, one of them me, against the rest of our production team. Weekends came out even, about 10 percent of activity for each group. The edges of the weekday didn't. 39 percent of the senior engineers' activity fell on weekday evenings and early mornings, against 26 percent for everyone else. Only about half of theirs fell between 7 and 5 on a weekday. For everyone else, it was about two thirds.

Two stacked bars of measured active hours over the last four quarters. Senior engineers: about half on weekdays 7 to 5, 39 percent on weekday evenings or early mornings, 10 percent on weekends. Rest of production: about two thirds, 26 percent and 10
Figure: Teams channel posts, file saves and sent mail, last four quarters, weighted by person-hour. Three senior engineers, me included.

The log shows when, not why. Some of my early hours are mine by choice. But a senior PE doing plan review at 8 PM because the day went to questions is capacity you're paying for and not getting.

The second calendar is the job's.

This is the one I didn't expect.

Then I looked at jobs instead of people. On our finished jobs for our two biggest repeat clients, 68 and 64 percent of a typical job's calendar days sat in gaps of two weeks or more with no hours logged at all. For one-off project clients, a small sample of 20 jobs, it was 38 percent. Starting wasn't the problem: won to first hour was 0 to 2 days. The waiting came in the middle and at the end.

Three bars. Share of a typical finished job's calendar days in gaps of two weeks or more with no hours logged: repeat client A 68 percent, repeat client B 64 percent, one-off project clients 38 percent.
Figure: Finished jobs, our own time records, measured Nov. 5, 2026. No client is named.

Our time records can't say whose wait it was. An agency review, a client decision and our own queue all look the same. That matters for your next requisition. A new hire adds hours. A lot of a job's calendar isn't hours. If the wait is a reviewer's queue, the next hire won't move it.

Fix the day anyway. Just don't promise it fixes the job.

The day is the part you control.

Have you ever trained your engineers to work around these tools? For most firms the honest answer is no. You rolled out the communication stack and assumed everyone would figure out the rest.

Picture the morning. A senior engineer logs in to overnight email, Teams questions from yesterday and a client note marked urgent. He opens all of it because nobody taught him not to, and by 9:30 he's handled thirty things and produced nothing. Almost none of it was urgent. Nobody defined urgent, so everything gets treated that way.

And look at what's on the second monitor. If it's Teams and Outlook, every ping pulls him off the work that mattered.

Here's how we shape the day. Mornings are for production: design, calculations, plan review, reports. Our rule for meetings is writing first, and a meeting only when something can't be decided in writing. Every invite states its purpose and the outcome expected, and it goes around other people's focus blocks. Our calendar assistant can change only your own calendar, shows you the change first, and does nothing without your yes. It enforces nothing. People do. My own inbox runs through a sorter that files what doesn't need me and leaves anything it isn't sure of where I'll see it. That's my setup, not a firm rule.

I can't show you a clean before and after. We have three senior engineers and no single start date, and I won't dress that up.

Here's the exercise. Before you approve the next requisition, read both calendars. First, pull 90 days of sent-mail timestamps for five senior PEs, times only, never content, and see how much lands outside 7 to 5. Second, take your last ten finished jobs and count the calendar days that sat in gaps of two weeks or more with no hours logged. If the gaps are most of the calendar, the next hire won't fix it. One rule: keep the people maps out of performance reviews.

Tell me which calendar surprised you more through our contact page. I read every one.

Michael Groselle, PE

Founder and CEO

Modern Engineering Solutions

mike@mod-eng.com

(214) 833-6748

mod-eng.com

Talk to an engineer

Tell us about your project

  1. An engineer reads it

    Not a salesperson. Someone who can tell you whether the pathway is real.

  2. You get a first answer

    Your options, the agencies involved and the questions that decide cost and schedule.

  3. You decide

    No commitment to have the first call.

Prefer the phone? (214) 833-6748

Site location, what you are trying to build, and your deadline.

Plans, a site map or photos: up to 5 files, 10 MB each.

Read our privacy policy.