top | item 27039855

(no title)

seem_2211 | 4 years ago

I’m saying those programmers should have secretaries to help them with all of the admin etc. They shouldn’t be booking their own flights, or making dinner reservations, or running expenses (or a lot of other manual work)

discuss

order

Jtsummers|4 years ago

My previous office went through that cycle.

Circa 2000 (and continuing through the 00s) there was a massive cutback in administrative personnel. By the time I got there (circa 2010) there were essentially no administrative support personnel except for those at the very top. During the 10s they realized that they were spending around $10k/year/person on travel related stuffs not because it was necessary, but because of the time lost to deal with the software that was supposed to remove the need for the full-time administrative staff.

By the end of the 10s, they'd restored the administrative teams and were spending much less per year on "overhead" (non-billable hour) even if you counted the admin teams as only overhead. Down from around $10 million to less than $1 million by just having a dedicated team that dealt with travel and finance stuffs.

The problem was that most people only traveled once a year, at best, and so they had no real experience with the unintuitive software. The average traveler was spending a week extra per trip, which was not billed to customers, dealing with reservations (1-2 days total pre-trip) and finances (2-3 days total post-trip).

closeparen|4 years ago

Mythical Man Month describes secretaries in a software context. What spoke to me about it was none of things, but instead: scheduling meetings, taking and distributing agendas and notes for those meetings, being the curator and librarian of project documentation. Just because these things are digital now, doesn’t mean any of the engineers on the team will step up to do them consistently or well. Many projects could run more smoothly with someone in that role.

ketzo|4 years ago

Many of those responsibilities have moved into the domain of the Product Owner / Scrum Master roles, which can work pretty well in my experience.