- Averaging over the past four weeks, approximately what fraction of your time did you spend on toil?
- Scale 0-100%
- How happy are you with the quantity of time you spend on toil?
- Not happy / OK / No problem at all
- What are your top three sources of toil?
- On-call Response / Interrupts / Pushes / Capacity / Other / etc.
- Do you have a long-term engineering project in your quarterly objectives?
- Yes / No
- If so, averaging over the past four weeks, approximately what fraction of your time did you spend on your engineering project? (estimate)
- Scale 0-100%
- In your team, is there toil you can automate away but you don’t do so, because that very toil takes time away from long-term engineering work? If so, please describe below.
- Open response
I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.
I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.
Find Trusted Cardiac Hospitals
Compare heart hospitals by city and services — all in one place.
Explore Hospitals
An additional perspective would be to focus on continuous measurement after identifying operational toil. Once repetitive tasks have been documented, teams should regularly evaluate whether automation and process improvements are reducing the workload. Monitoring trends such as manual effort, recurring operational activities, and the frequency of repetitive interventions can help verify that the changes are producing lasting improvements and guide future optimization efforts.