Imagine eighty construction workers on a job site. Every couple of weeks, there is a safety issue on the site, and work stops until the issue is resolved. Pausing work delays when the building can start collecting rent. It's easy to put a price tag on the safety issues because there's a clear line between them and lost revenue as a function of time. It's also visceral—the job site is empty.
What you describe is about leadership and company culture. Safety is not tradable and needs to be solved completely before you can continue to work. The good thing about paper cut tax is there are loads of incremental improvements anybody can start with. That is a huge opportunity.
Price tag: improving process step X will reduce the risk of having to redsign product component Y by Z%. You can usually find out or estimate what a product iteration costs.
I once wrote a article about the cost of bad meetings that are not facilitated well.
It is all pretty easy to implement compared to a forgotten sprinkler system in a buikding.
This issue is compounded in Engineering, where on the surface, engineers appear to have a straightforward task. However, beneath that simplicity lies a web of complexities, dependencies, and issues waiting to surface. But then, the complexities accumulate over time. One of the ways this can be solved is via tooling. Check out this podcast: https://console.dev/podcast/s04e07-why-engineering-sucks-eli-schleifer
What you describe is about leadership and company culture. Safety is not tradable and needs to be solved completely before you can continue to work. The good thing about paper cut tax is there are loads of incremental improvements anybody can start with. That is a huge opportunity.
Price tag: improving process step X will reduce the risk of having to redsign product component Y by Z%. You can usually find out or estimate what a product iteration costs.
I once wrote a article about the cost of bad meetings that are not facilitated well.
It is all pretty easy to implement compared to a forgotten sprinkler system in a buikding.
This issue is compounded in Engineering, where on the surface, engineers appear to have a straightforward task. However, beneath that simplicity lies a web of complexities, dependencies, and issues waiting to surface. But then, the complexities accumulate over time. One of the ways this can be solved is via tooling. Check out this podcast: https://console.dev/podcast/s04e07-why-engineering-sucks-eli-schleifer