No Stupid Questions

I help our customers make their business processes less stupid, time consuming and riddled with errors. Practically speaking it means I go to meetings, documentation process changes, build out business process automations, and attempt to convince an unwilling workforce that no, 17 spreadsheets is not the only or best way to run a business (change management).

I’ll just give some examples.

We know that construction workers build things, but many office workers are behind them. When you hear “office worker,” think “information worker” as that will help.

What information?

Someone has to pay the construction workers. This involves accounting and payroll tasks best done at a computer.

Architects design the project being constructed and this is done in an office.

There are permits, inspections, regulations, taxes, real estate licensing etc to clear the project and this is done through computers and telephones.

Coordination of the different work crews must be planned - we don’t just ask concrete, civil engineers, plumbers, electrical, and landscaping to all show up on the same day and just figure things out. These things are scheduled out and arranged with many different companies / subcontractors and this is mapped out on a computer and agreed to over the phone.

The new apartments being constructed will need tenants to rent them. Billboard space is going to be rented near the building. A graphic designer is designing the billboard on a computer in an office. Someone else is calling the billboard company to arrange the large scale printing of it and to purchase the time it will be displayed.

I’ll stop. This is off the top of my head. If construction workers, with their obviously valuable and easy to understand work have this many office workers behind them, you can imagine how it’s even more complex for things like tech companies.

In Office Space the main character seems like some kind of analyst, maybe a project manager who makes sure things are getting done as planned and addresses. The other two guys from the office were software developers if I remember correctly. The annoyimg lady answering phones was a receptionist.

So it varies widely depending on what needs to be done and who it is assigned to. I have worked in the same IT department for over 15 years and had four different positions working with the same large software systems doing very different work (help desk, testing, requirements, project management). I interact with security people, administrative assistants, and even directors as part of the work.

'Office work' is more of a description of the location and setting than the work itself.

Account Manager at a marketing agency, I run ~5 marketing departments with a mix of my own staff, outsourced contractors and employees at my clients' businesses.

We create marketing campaigns that consist of a set of emails, social posts, ads, thought leadership articles, blogs, landing pages, downloadable PDF reports and the attendant reporting on how they performed, plus finding and targeting the audiences in various segments. It's a mix of database management, creative writing and design, project planning and communication meetings.

I generally spend about a 1-2 hours a day on each client, plus meetings. We make and send the collateral, get approval, execute, track, measure, compare, make a strategic conclusion, repeat

I work as Adminstrator and Developer for Medical Software in a Hospital.
Most of my days are either spend preparing for future planned Software deployments, checking if they can meet our needs. Fomulating out the requirements and data imports and exports to various existing systems. On others like today I'm a bit more hands on and actually fix a bug in an application, laid out a plan for QA testing and eventual deployment of the new release and wrote some documentation so that should I vanish from the face of the earth, the stuff I do can be picked up by someone else.

Insurance:

For this "industry," it varies wildly by department and position. The lower your are (entry level, etc.) the worse it's going to be. People are always in accidents, so you'll be working customer service on nightmare mode. No real meetings, maybe a "huddle," and then back to work.

I've moved up slightly and it is night and day. I get work/claims, but I'm usually done by noon, and that's with me fucking around (on my phone, messing with the cat, chores, etc.). The projects are PowerPoints and excel sheets in my area, which are simple. Since I'm at home, when I'm done, I usually just keep myself online and work on crafts. If I'm extra bold, I'll take the laptop downstairs and play a game. The more specialized you get, the less work you have.

I can only give my experience and I think mine is a bit unusual but here goes.

Like the Office Space folks, I'm a dev in a large (admittedly, non profit and really good) organization. Since covid, I've worked remotely but my day to day hasn't changed.

We have a help desk where people send questions/issues. Someone on our team generally splits those roughly based on workload, skills, knowledge etc. Our goal is about half our work should be those one off requests.

I also have client units within the organization. They usually come to me with wild, bold ideas that I help make a reality or explain (gently) why what they are asking for is insane. Some of thr projects are based on what folks have heard are best practices in our industry, others are about cutting down manual work/seeing what we can automate.

Any of those projects can take anywhere from a couple hours to a couple of months. Some require buy in from other units, so on those I end up on a lot of meetings and email threads answering questions, hearing suggestions etc. I then (usually) coordinate with my manager to make sure I'm not stepping on any toes or there aren't considerations which I had yet to consider.

Today for example, I spent about half the day working on help desk tickets, about 1/3 of my time was clarifying "what the hell are you trying to say?" Or pointing out logical gaps etc (much easier to do this upfront than write a bunch of code and have someone realize they meant something else entirely... People are dumb.) The other 2/3 was coding.

On my major projects, I spent an annoying amount of time emailing around to get approvals so a project manager would accept that my clients were fine with something I built, even though it was a bit unorthodox. Then a couple hours actually working on another project.

Plus, y'know, Lemmy time, cat skritching time and a bit of cooking.

Admittedly, my experience is unusual. I'm hihhly skilled but slightly underpaid in a non profit, so folks compensate by giving a lot of leeway. So a nice work environment plus I think what I do makes the world a better place, I'm pretty happy. I understand most office jobs are not quite like that but I don't think they're far off.

Let me take a liberty to answer for everyone.

Most of human activities now generate a lot of data, or require a lot of data to happen.

It can be anything from construction blueprints and software, to more subtle things like goods distributions on the shelves or schedules or whatever.

Behind everything you see in the world there is a data management, and behind this data management there are layers of people making those decisions from top to bottom.

Some of those people managed to create spaces where all they have to do is to say "nothing on my side" during the meeting.

Others are the opposite, have to take the toll and process the massive amounts of this data.

This is what the office job is nowadays.

Just look up the movie “Office Space” it pretty well summarizes it all.

Office work is largely paperwork, even if very little is on actual paper nowadays. Much of the work involves creating records or communicating with others to get things done. A salesperson will try to find clients for the product or service. They’ll typically create a record of customers or prospects with their contact information and notes about the negotiation. They’ll create a formal quotation or estimate for the customer and if the customer wants to move forward they’ll create an order confirmation. That document will trigger some other department to fulfill the order, either by providing a service or product to the customer. A work order might be provided to a service technician specifying what work is to be done and where. If a product needs to be delivered a picking slip might be created to tell someone in a warehouse where to get the product and how many to get. Once it’s been picked the product will go to the shipping department to be packed and shipped. An item fulfillment will be created saying what items were packed, how many, and what the tracking number is. Once the order is fulfilled an invoice will be created. If the customer paid in advance the payment will get applied to the invoice automatically or by someone in the accounting department. If the customer is on credit terms they’ll be sent the invoice with instructions on how to pay and when payment is due.

There are so many steps like this. The records help the business plan. They know how many parts and supplies to order. They can track if they’re selling more or less than forecast, if they need to place a rush order for more parts, ask people to work overtime or hire more employees. If something starts costing more they can look to see if they need to raise prices or redesign the product to use a different component, or find an alternate source. At the end of the day, it all comes down to accounting, making sure the company is generating enough income to pay the bills, suppliers, and employees, and hopefully make a profit.

I’d totally like to share what I do at my office job at the equivalent of the IRS in my country, but that’s classified :(

Does finance count? I'm usually studying something in the alternative data space (that is, using non-financial data to make decisions on investments) so I can, in the end, make a presentation or deliver a product to someone. For example, an analyst decides to study a clothing company and asks me to scrape their prices in the main Latin American markets (because he thinks they can grow there or something). So I do that for a while and report back to him what I found. If it is interesting, I may be tasked with implementing something in our Excel add-in so he can plug that information into his own models, or I'll need to develop a model myself.
Lots of spacing out, browsing lemmy and playing bullet chess on my phone, too

I worked in software development as a QA engineer. Every day I'd load the current build of the OS and test for bugs, check that fixed bugs are truly fixed, and write bug reports. Once a week it was on me to come in early and do a quick rundown to see how usable the build was and then send a report to the entire org so people knew if it was too problematic to install and remain productive.

I worked in IT at a place that was perpetually under water. I spent all day troubleshooting either end-user computers or servers. We never had a break from tickets, so there was always work to be done unless the holidays were in season and users were taking time off.

I worked IT Exec Support for a high-up individual. It required being on-call and meeting them at their office in different cities and being the personal IT for their staff. It was pretty unpleasant in that the exec never communicated effectively and was insulated by their staff such that they had unrealistic expectations about how things should work. I was proud to land the job, but I'm glad to be done with it.

I now work in IT at a place that is super organized. I mostly wait for someone to call with an issue. Most things are pretty easy to fix. Some days I have to administer our inbox and direct users or create tickets. During that time, I'm always busy. On the days when it's not that, I surf Lemmy (on wfh days) or read a book (on in-office days) between calls. I also configure devices for people and the like (think upgrades and new employees). I'll probably stay here until retirement cause it's the easiest job I've ever had.

In my case, I work IT for a healthcare company. Current major projects of mine include trying to migrate servers from our data centers to the cloud and setting up Disaster Recovery options. These are 2 of my 22 current projects.

On the day to day, I'll determine what it takes for an application to run and how does it communicate to find the most optimal way we can build it within vendor and enterprise specifications. An example might be...

• Application is a hosted Web Page
• It stores all of its data a SQL Database
• Is used by locations outside of our network, so this will require
  • A Public Endpoint to be accessible outside of our network
  • DMZ'd Network Security Group or Application Security Group to manage exactly what and be accessed from where
• Is a low-tier application that does not require low latencies

In this case, I can decide to use a PaaS Web Server and PaaS SQL Server, so that I don't have to manage security and updates of the Operating System in the future. After deciding this, I might diagram how everything will connect and communicate, then build the infrastructure to fulfill this design. Lets say that means going to Azure (the cloud provider), building the Web Server and SQL Server, creating the DMZ rules (443 inbound from anywhere to WebServer and 1433 only from WebServer to SQLserver) I set up a backup system for both of these to take daily backups in case anything goes sour, then determine what steps are necessary to make sure that I can minimize the downtime for the migration, since it will take time to restore a backup from the data center's version into the Azure version.

I'm trying to keep things simple-ish for this example because there's a wide variety of tools, environments, and processes that come into play for any one of these builds. Most of the time is spent not in actively moving things, but in determining best courses of action and minimizing downtime, especially being a healthcare environment where an application could be actively impacting a patient's care.

Of course there's all the other stuff you might expect, like emails about a server not working right and meetings about how management wants to use more AI while needing to cut costs to the organization because we're "not currently economically sustainable."

While by no means a comprehensive view into the work, I hope it grants some insight into the role!

Here's my office work:

Since 2005 I worked as a TV news producer. We started the day with a morning meeting where reporters pitched stories and it was decided what they covered that day. Then as a producer I organized the stories in the newscast and found other stories which I was responsible for. That ranges from finding a worthwhile press release to interviewing people myself (usually by phone, and someone's video chat,) or just finding info by going through data. I would write those, then decide what visuals, audio elements, camera shots, graphics, and anchor reads went with it.

Then during the live newscast I timed it, and made adjustments on the fly when necessary. (Killing stories, finding ones to insert, and adding breaking news.)

I let my contract end almost two months ago, choosing not to stay in news. I've been applying to mostly other non-TV news office jobs. That's including producing other video projects, but also technical writing and marketing positions.

I work for a consulting firm, so a project is whatever our client has contracted us to do, for the objectives and timeline we've agreed to in the contract. We do workforce readiness, largely. So the client might be adopting a new software and wants us to create the employee training on it.

We contract with them for training to help their leaders deliver workshops, maybe some e-learning modules and assessments, and to have it done in a certain number of weeks. That's an example of a project, and typically we'll have a small team on the deliverables for it: the modules and the workshops. Meetings are to check in on progress, fix any issues, meet with the client or their subject matter experts. So that's my office job, though luckily it's been remote for me since covid.

I work with computers to map things.

Across my various jobs in this field, the days were usually varied but fairly busy.

I worked for a government agency that would map abandoned mines and locations of mishaps to better understand what kind of environmental issues were posed. This involved meetings with hydrologists, miners, drone pilots, and field workers. It also had some field visits, itself.

Another one, I worked for a city's outreach program and I often was in meetings explaining what I could do, and then I'd have to gather maps and data to put together the product they wanted.

For another job, I had to cross reference a ton of city and county data to find land lots that were large enough for a developer to potentially purchase and then build housing on. This included looking at zoning laws and reading a ton of documentation about new zoning and votes for such a thing. Also included learning about what each category of zoning meant.

Currently I work for an energy company and it's varied in a lot of ways. My day to day is never the same and is kind complicated to the average bear.

Other people's work