Joe Renz

The problem, they say, is not bad software but implementations that assume people will adapt to the system rather than the system adapting to people.

• Their benchmark: a system the newest operator on the floor can use on day one without prior training.
• Needing a manual, a training session, or an IT ticket signals an adoption problem that becomes a compliance problem.

One post describes facilities spending six figures on EHS software that reached roughly 20% adoption a year after go-live.

• Floor staff still filled out paper forms and emailed incident reports while the dashboards looked fine.
• The companion post lists five observable symptoms: only the EHS manager really knows the system; incident reports still arrive by email or paper and one person enters them later; training completion rates look fine on the dashboard but nobody can explain them; the last three corrective actions were closed the same day they were opened; and when OSHA asked for a record, the answer involved a spreadsheet.

The later five-signs post turns the argument into a checklist managers can use at their own facilities, replacing broad adoption-rate framing with concrete, checkable symptoms.

Read original · Original 2

The five questions probe different parts of the inherited safety system — incident closure, shift coverage, reporting behavior, front-line ownership, and regulatory exposure. They say the answers reveal the safety culture someone has walked into.

The list asks: When was the last incident, and was the corrective action actually closed?

• What does training compliance look like across every shift, not just day shift?
• Are near-misses being reported, or only recordables?
• Who owns safety on the floor when the manager is not there?
• What would an OSHA inspector find on a walk-through tomorrow?

Read original

Commenters’ sharpest correction was to raise these questions at the interview, not on day one. Renz concludes that experienced EHS professionals assess not just whether systems exist, but whether the organization is designed to let safety work.

Joe Renz credits commenters individually.

• Bradley York asked about the EHS budget, specifically whether corrective actions come out of it; Renz says the answer tells you more about organizational priorities than any policy document.
• Michael Kary asks everyone, from ground level to the CEO, the same question: what gets in the way of making the safe choice?
• Renz says the gap between those answers is where the real work lies.
• Shannon Dickson Rand added questions about who investigates incidents, who is trained to investigate, and who is accountable for unsafe behavior at the front line.

The format shifts from a single list to a two-stage exchange: a direct question to the audience, followed by a credited round-up that turns the crowd’s answers into a stronger argument.

Read original · Original 2

The follow-up highlights questions about who owns investigations, who is trained to run them, and who is answerable for unsafe behavior at the front line.

• Renz locates the real work in the gap between what leadership says and what floor staff say.
• The software posts make the same point operationally: if one person is quietly holding the system together and corrective actions close the day they open, the compliance record does not reflect what is happening in the facility.

The five-signs post makes the point most clearly: training rates nobody can explain, corrective actions closed the same day they were opened, and a spreadsheet produced when a regulator asks for a record. Joe Renz concludes that adoption, not the system itself, is the problem — in practice, nobody owns the work well enough to get it done.

Read original · Original 2 · Original 3

The post gives five questions: When was the last incident, and was the corrective action actually closed?

• What does training compliance look like across every shift, not just day shift?
• Are near-misses reported, or only recordables?
• Who owns safety on the floor when the manager is away?
• What would an OSHA inspector find if they walked in tomorrow?
• Joe Renz says the answers reveal the safety culture a new manager has inherited.

For brands planning a campaign

For a safety software company, the five questions offer a natural collaboration starting point: turn them into a first-30-days checklist or worksheet for practical conversations about incident closure, shift-wide training, near-miss reporting, floor ownership, and inspection readiness.

Joe Renz argues that the most expensive safety program is the one nobody uses.

• They describe seeing six-figure EHS software stuck at 20% adoption a year after go-live, while floor workers still use paper forms and email for incident reports.
• The problem is implementation that expects people to adapt to the system instead of adapting the system to people.
• The benchmark: the newest operator on the floor can use it on day one without prior training.

For brands planning a campaign

For an EHS software vendor, this opens a direct conversation about onboarding, floor usability, and adoption metrics. A collaboration could ask Joe Renz to turn the day-one usability benchmark into a practical assessment or post series.

The post lists five signs: only the EHS manager knows the system; incident reports still arrive by email or paper and one person enters them later; training completion rates look fine on the dashboard, but nobody can explain how; the last three corrective actions were closed the same day they were opened; and when OSHA asked for a record, the answer involved a spreadsheet. Joe Renz concludes that the system isn't the problem—adoption is.

For brands planning a campaign

A software company could build a self-assessment, carousel, or webinar around these five signs. Each is specific enough to prompt a question that leads into a product conversation about adoption, training data, corrective actions, and record retrieval.

Joe Renz says a previous post asking what questions a new EHS manager should ask reached 35,000+ readers.

• This follow-up distills the comments: ask at the interview, not day one; Bradley York asked about the EHS budget and whether corrective actions come out of it; Michael Kary asks everyone from ground level to CEO, 'What gets in the way of you making the safe choice?'; and Shannon Dickson Rand added questions about who investigates incidents, who is trained to investigate, and who is accountable for unsafe behavior at the front line.
• The pattern, Joe Renz writes, is that experienced EHS professionals assess whether the organization is designed to let safety work.

For brands planning a campaign

This post shows Joe Renz hosting a practitioner conversation and synthesizing responses. A brand collaboration could use a question-driven format, turning audience answers into a guide, webinar, or follow-up post.

One describes facilities that spent six figures on EHS software reaching about 20% adoption a year after go-live, while floor staff still used paper forms and emailed incident reports.

• The conclusion: implementation assumed people would adapt to the system, rather than the reverse.
• The other post lists five symptoms: only the EHS manager really knows the system; incident reports arrive by email or paper and are entered later by one person; training completion rates look fine but nobody can explain them; the last three corrective actions were closed the same day they were opened; and an OSHA record request is answered with a spreadsheet.
• The stated benchmark is a system the newest operator can use on day one without prior training.

A short declarative opener leads into a numbered symptom list, with each item a concrete, checkable observation rather than an abstraction.

Neither post names a vendor, product, or category leader; the criticism focuses on implementation practice, making the framing usable for sponsored content.

For brands planning a campaign

This is the closest fit for a workplace safety software vendor's brief: the audience is EHS leaders, and the argument prioritizes adoption over features. Joe Renz could apply the same symptom-list format to a vendor's onboarding or floor-usability claim, keeping the criticism general rather than turning it into a product review.

Examples: Source 1 · Source 2

Joe Renz frames the answers as a read on the safety culture the manager has inherited.

A question list covers different parts of the safety system: incident closure, shift coverage, reporting behavior, front-line ownership, and regulatory exposure.

The list is presented as universal; no sector-specific or company-size variation is offered.

For brands planning a campaign

Useful as a hook for content aimed at EHS practitioners rather than buyers. A vendor could build a companion worksheet, shift-level compliance checklist, or near-miss reporting prompt from these five questions, with Joe Renz introducing the list to their EHS audience.

Examples: Source 1

It credits commenters by name and reframes their answers: ask these questions at the interview rather than on day one; find out whether corrective actions come out of the EHS budget; ask everyone from ground level to the CEO what gets in the way of making the safe choice; and establish who investigates incidents, who is trained to investigate, and who is accountable for unsafe behavior at the front line. Renz concludes that experienced EHS professionals assess whether the organization is designed to let safety work, not just whether systems exist.

Two-stage posting: a direct question to the audience, followed by a credited round-up that turns the crowd's answers into a sharper argument.

For brands planning a campaign

The format creates a repeatable engagement loop: a prompt post, followed by a synthesis post that names contributors.

• A brand collaboration can plug into either end by supplying the initial prompt or the follow-up resource.
• The format generates comment volume a sponsor can be associated with, without requiring Renz to write product copy.

Examples: Source 1

The follow-up post highlights questions about who owns investigations, who is trained to run them, and who is answerable for unsafe behavior at the front line.

• It locates the real work in the gap between what leadership says and what floor staff say.
• The five-symptom software post makes the same point operationally: if one person is quietly holding the system together and corrective actions close the day they open, the visible compliance record is not the real one.

For brands planning a campaign

Gives a vendor a credible way into the accountability conversation rather than a tooling conversation: audit trails, ownership assignment, and closure evidence can be framed as ways to close the gap Renz describes, while keeping accountability at the center.

Examples: Source 1 · Source 2 · Source 3

Esen’s account of meeting 47 EHS, 32 operations and 10 IT leaders and finding the same dynamic in every industry echoes the three-way tension Renz describes when asking who owns safety when the manager isn’t there.

Sercan Esen writes at the level of a vendor’s customer base and a global framework, covering human-machine collaboration, engineered risk removal, and new safety roles emerging from vision systems and robotics.

• Joe Renz stays closer to one manager’s first weeks and one facility’s symptoms, using short lists rather than a portfolio of site visits.
• Follow Esen for where safety technology is heading; follow Renz for how to test whether it’s working where you are.

Read original · Original 2

Green offers a renewal defense pack sent to an internal champion a month early or three questions to ask five recent customers, then converts the answers into a repeatable exercise. Renz takes the same approach in the five questions for a new EHS manager.

The subject is B2B revenue rather than safety: renewals, budget defense, champion enablement and sales storytelling. That makes Matt Green a useful companion read rather than a substitute if you came for EHS content — Joe Renz's question about whether corrective actions come out of the EHS budget is exactly the kind of internal funding conversation Matt Green writes about arming a champion to win.

Read original · Original 2

Renz uses the same structure with adoption rate and training completion rates that look fine on a dashboard but cannot be explained.

Justin Rowe writes about paid-media measurement and CRM attribution for B2B marketers, and his posts promote a measurement tool.

• Renz writes about safety operations, names no vendor and promotes no product.
• Read Rowe for the same blunt diagnostic style applied to marketing numbers; read Renz for safety practice.

Read original · Original 2

The posts describe three months of U.S. manufacturing site visits, 27 onsite visits and 97 stakeholder conversations with EHS, operations, IT and senior leaders.

• They argue that EHS owns outcomes, operations owns reality, and IT scales it—a direct fit for a safety-software campaign aimed at operations and executive reach.
• They also treat adoption as strategy, criticise compliance platforms that have not evolved, and describe human-machine collaboration, new safety roles and automation removing exposure.
• These themes support a LinkedIn collaboration on why safety technology gets used or ignored.

The tradeoff is perspective and commercial context.

• This is a senior manufacturing-safety and operations voice with visible ties to Intenseye and a WEF human-machine collaboration framework, not a neutral EHS-manager checklist or comment-led practitioner round-up.
• A sponsor would be buying a strategic vendor-side view of adoption.
• Before booking, ask for audience demographics, sponsorship terms and a rate card; two posts also offer less evidence of a repeatable collaboration format than the first-30-days question post and credited follow-up.

Examples: Source 1 · Source 2

The posts offer concrete sales-enablement material: a renewal defense kit containing a usage story, one peer benchmark and pre-answered finance questions, and a method for calling five customers and turning their answers into a five-part story for sales teams. For a safety-software vendor whose obstacle is getting a champion to defend the budget line, this is closer to the actual decision than another safety-culture prompt.

The tradeoff is subject matter.

• Matt Green's work is about sales, renewal and storytelling, not EHS, workplace safety or the EHS-leader audience named in the campaign.
• Joe Renz's posts do not address safety.
• A sponsored piece here would reach a general B2B software audience and would need the brand to supply all safety context, risking content about buying software rather than EHS adoption.
• Ask for EHS audience data before booking if reaching EHS leaders is essential.

Examples: Source 1 · Source 2

The posts explain LinkedIn's optimisation gap, the Conversions API, why cost per click is a poor proxy for the buyer's real question, and how to report engaged accounts and CRM movement before revenue appears. That is specific, practical content for a safety-software vendor whose immediate problem is attribution and qualified pipeline rather than topic alignment with safety practitioners.

The tradeoff is audience and intent.

• The posts are B2B marketing measurement posts and include promotion of DemandSense with a 30-day trial.
• They do not address EHS, manufacturing-floor adoption or safety culture.
• A collaboration here would serve a different buyer and success measure, so ask for EHS audience data before booking if reaching EHS leaders is essential.

Examples: Source 1 · Source 2