Thom Probus writes about coordinating offshore delivery teams and the effects of AI on professional services, organizational decision-making, and security.
Most useful for practical frames on offshore delivery coordination failures and questions about AI in professional services, decision-making, and security.
Best for
A professional services firm planning a leadership offsite on offshore delivery problems and AI.
Not for
A B2B software vendor seeking sponsored content, guaranteed distribution, audience demographics, and a rate card.
Key takeaways
Offshore delivery problems often reflect protocol mismatches, not capability failures.
A yes that does not mean yes and green-green-green-red status pattern.
AI can reproduce old institutional hazards, such as distance from execution.
Check first: Confirm whether Probus offers sponsored content and request scope, rates, timeline, and disclosure terms.
Main ideas
Offshore delivery problems are protocol mismatches, not capability failures · Accommodate inside the project; keep culture change off the critical path · AI ends professional services’ long insulation, and the scarce capability is what AI cannot do
Thom Probus writes about how organizations coordinate work across distance and respond to AI.
In the offshore-delivery writing, they argue that familiar complaints—weak estimates, limited initiative, and status that stays green until it suddenly turns red—often reflect mismatched communication and commitment expectations, not a lack of ability.
They also examine AI’s effects on professional services and the risks of deploying AI in institutional processes.
Read or follow Probus for practical ways to think about coordination failures and questions about what AI changes in work, training, and decision-making.
Probus connects organizational problems to specific failure patterns and offers a practical frame for understanding them.
In the offshore-delivery posts, they name the “green-green-green-red” status pattern and a “yes” that does not mean yes, then recommend adapting coordination within the engagement rather than putting culture change on the critical path.
Their AI writing examines institutional systems: they link possible harm from biased training data to the distance between approval and execution, and raise the risk that reduced entry-level work could weaken professional apprenticeships.
The security posts offer a counterpoint to the more hopeful close of the professional-services post, emphasizing that AI can reproduce old institutional hazards even as the broader transition may hold possibilities.
Thom Probus writes short LinkedIn posts introducing a longer weekly column, and the same few positions recur.
Read more
The central argument is that offshore delivery programs fail on protocol, not capability: American and offshore teams work from different assumptions about communication, commitment, and a manager’s role.
The fix is to redesign that protocol layer within the engagement rather than launch a culture-change program.
A second argument is that AI has ended professional services’ long insulation, framed through the “Frozen Clock” and the Apprenticeship Paradox, and that the capability most needed now is the one AI cannot supply.
A third is that a current AI security scare is really an old institutional hazard: distance from execution.
Across all three, they reframe a supposedly new problem as a familiar one in a new setting, then give the reader a short, practical list.
Offshore delivery problems are protocol mismatches, not capability failures
Management teams make remarkably consistent complaints about offshore delivery teams: they are not proactive, cannot estimate, and report green status for months before suddenly turning red.
Read more
After working across financial services, professional services, and technology organizations, Thom Probus concludes these are almost never capability problems.
They are protocol mismatches: professionals operating under different assumptions about communication, commitment, and a manager’s role.
The remedy is to redesign the protocol layer, not launch a culture-change initiative.
A “yes” that does not mean yes, and the green-green-green-red status pattern: a program reports green for three months, then suddenly turns red. The referenced column in The Meridian View walks through eight such coordination barriers.
Two near-identical posts make the same argument with minor wording differences: one names The Meridian View, the other does not. The consistency suggests this is stable framing, not a one-off.
Accommodate inside the project; keep culture change off the critical path
This priority follows from the protocol argument and is stated as a three-part rule: accommodate within the project, invest in relationships for the long game, and never put culture change on the critical path.
Read more
For anyone planning a talk or program about offshore delivery, the distinction matters: the recommendation is a set of practical accommodations American management teams can make within a single engagement, not a multi-year organizational change effort.
The post distills the recommendation into one closing line, giving the audience three actions rather than a transformation roadmap: accommodate, invest in relationships, and keep culture work off the delivery timeline.
AI ends professional services’ long insulation, and the scarce capability is what AI cannot do
For 150 years, displaced workers found new homes in professional services, a sector technology was expected to leave alone because it required judgment, synthesis, and human context.
Read more
Thom Probus argues that AI has ended that assumption and that this disruption is categorically different from earlier ones. The post previews a piece titled The Fog of Change and frames the moment through named problems rather than a forecast.
Two named concepts carry the argument: the “Frozen Clock” problem for innovation, and the Apprenticeship Paradox, which Thom Probus says may quietly hollow out the next generation of professional talent. The post closes by arguing that the most urgently needed capability is precisely what AI cannot provide.
A new AI security risk is an old institutional hazard: distance from execution
Thom Probus reports that CISOs have identified an AI-related security risk: institutional bias baked into training data lets bad actors get harmful requests approved by dressing them up as compliance work, audit methodology, or policy analysis—no jailbreak required.
Read more
The argument then turns: this is not really new.
It is the same distance-from-execution hazard that has always afflicted institutions, except the system was born at altitude, with no ground floor to fall back on.
The practical audience is anyone deploying AI in audit, procurement, hiring, or security operations.
The illustration is the approval itself: a harmful request passes review because it is presented in the language of compliance or audit. The risk lies not in a broken model but in a reviewer positioned too far from the work being approved.
Two versions of the post make the same argument: one includes a link description and a typo in the opening line; the other has a cleaner sentence and a slightly different closing pointer to the column. Both use the same framing and reach the same conclusion about distance from execution.
Start here to explore whether offshore delivery problems stem from skills or coordination.
Read more
The post lays out Thom Probus's central argument and the complaints and failure patterns it aims to explain.
The post opens with complaints management teams running offshore delivery programs make in the same words: the team is not proactive, the team cannot estimate, status was green for three months and then went red.
Thom Probus says these patterns recur across financial services, professional services, and technology organizations, and concludes they are almost never capability problems.
They attribute them to a protocol mismatch: two sets of professionals working from different assumptions about what communication means, what commitment means, and what a manager is for.
Examples include a "yes" that does not mean yes and the green-green-green-red status pattern.
A piece in a column called The Meridian View walks through eight such coordination barriers and practical accommodations American management teams can make within a single engagement.
The closing rule has three parts: accommodate within the project, invest in relationships for the long game, and never put culture change on the critical path.
For brands planning a campaign
This is the most directly usable talk spine for leaders who run or buy offshore delivery.
The eight-barrier list, the "yes" that does not mean yes, and the green-green-green-red status pattern can each anchor a segment.
The closing rule gives the audience something to do on Monday without launching a culture-change program.
Read this for the label Thom Probus gives the current moment and the vocabulary they use to describe it.
Read more
It explains what makes this wave of automation different—the framing a leadership audience will want before considering recommendations.
The post argues that for 150 years, displaced workers found new work in professional services—the sector technology was expected to leave alone because it required judgment, synthesis, and human context—and that AI has ended that assumption.
It previews a piece titled The Fog of Change and names three ideas: the "Frozen Clock" problem for innovation; the Apprenticeship Paradox, a quiet hollowing-out of the next generation of professional talent; and the claim that the capability most needed now is the one AI cannot provide.
The post closes by acknowledging that the fog is real and that possibility lies on the other side.
For brands planning a campaign
Pairs with the offshore delivery material for a professional services audience: the same buyer cares about delivery coordination and about what AI does to the people doing the work.
The three named ideas give a speaker three ready-made segments.
The Apprenticeship Paradox is likely to spark questions from partners who train junior staff.
Read this for the security and risk side of the same argument.
Read more
It shows how the coordination problem surfaces when AI is deployed in audit, procurement, hiring, or security operations, and introduces a second recurring idea in the work.
The post reports that CISOs have identified an AI-related security risk: institutional bias baked into training data can let bad actors get harmful requests approved by presenting them as compliance work, audit methodology, or policy analysis, with no jailbreak required.
Thom Probus argues the risk is not really new: it is the same distance-from-execution hazard that has always affected institutions, except this time the system was born at altitude with no ground floor to fall back on.
The post points to a column about what this means for anyone deploying AI into audit, procurement, hiring, or security operations.
For brands planning a campaign
Useful if the event audience includes risk, compliance, or security leaders, or the organizer needs one AI segment rather than several. The distance-from-execution framing extends beyond security and can explain why approval workflows fail more generally, keeping the talk relevant to non-technical attendees.
Offshore delivery coordination and protocol mismatches2
AI security risk and distance from execution2
AI-driven disruption of professional services1
Offshore delivery coordination and protocol mismatches
Thom Probus argues that familiar complaints about offshore delivery teams—not being proactive, being unable to estimate, or reporting green status for months before turning red—usually reflect protocol mismatches, not capability failures.
Read more
The two groups of professionals have different assumptions about communication, commitment, and a manager’s role. The post identifies eight coordination barriers, including “yes” that does not mean yes and the green-green-green-red status pattern, and outlines practical accommodations American management teams can make within a single engagement.
Pattern analysis drawn from financial services, professional services, and technology organizations.
Argues that culture change should not be on the critical path; teams should redesign the protocol layer and accommodate differences within the project.
For brands planning a campaign
A leadership event talk can give managers a concrete diagnosis of offshore delivery failure and a short list of protocol accommodations to apply in one engagement, rather than a broad culture-change program.
In a post tied to “The Fog of Change,” Thom Probus examines why AI disruption is categorically different from earlier waves.
Read more
The post raises the “Frozen Clock” problem for innovation and the “Apprenticeship Paradox,” which may quietly hollow out the next generation of professional talent. It describes professional services as a sector once insulated by judgment, synthesis, and human context, and argues that the most urgently needed capability is what AI cannot provide.
Historical comparison with previous disruptions, organized around named conceptual problems.
Treats this disruption as different from every previous one, not as another familiar wave.
For brands planning a campaign
Suitable for a talk on how AI changes professional services talent pipelines and innovation cycles, with named concepts to frame workforce and apprenticeship decisions.
Thom Probus discusses a new AI-related security risk recognized by CISOs: institutional bias in training data can let bad actors get harmful requests approved by dressing them up as compliance work, audit methodology, or policy analysis, with no jailbreak required.
Read more
They argue this is not really new: it is the same distance-from-execution hazard that has long affected institutions, except this system was born at altitude, with no ground floor to fall back on. The post addresses anyone deploying AI in audit, procurement, hiring, or security operations.
Reframes a current AI risk as a recurring institutional hazard.
Argues that the CISO framing of novelty misses the older pattern.
For brands planning a campaign
Good for a security or risk leadership session on AI deployment in audit, procurement, hiring, or security operations, and why review distance matters.
The posts follow a recurring format: a short LinkedIn post introduces a longer weekly column or newsletter and packages the argument into named frameworks or patterns.
Read more
Examples include “The Meridian View,” “The Fog of Change,” the “Frozen Clock,” the “Apprenticeship Paradox,” and the green-green-green-red status pattern.
Uses a hook, cross-sector observation, named concepts, and a pointer to further reading.
The posts do not include the full column text, so the frameworks are described only at the level of the post.
For brands planning a campaign
A brand considering Thom Probus for a keynote or workshop should request the underlying columns or a full outline before committing to depth.
The posts name no sponsors, clients, employers, or investments.
Read more
The only named outlets are two columns presented as Thom Probus’s own work: The Meridian View, on coordination barriers in offshore delivery programs, and The Fog of Change, on AI’s effect on professional services.
These are mentions, not stated business or employment relationships.
Ask who owns, publishes, or funds the columns before treating them as such.
The Meridian View
Mention
A post about offshore delivery programs points readers to “this week in The Meridian View” for eight coordination barriers and accommodations American management teams can make inside a single engagement.
Read more
The post presents the column as the creator’s own writing.
A post on AI and professional services says that “in The Fog of Change” the creator examines why this disruption differs from earlier ones, the Frozen Clock problem, the Apprenticeship Paradox, and the capability AI cannot supply.
Thom Probus is easiest to follow through a recurring move: take a problem that looks new and show the older pattern underneath.
Read more
Start with the two posts on offshore delivery.
They argue that familiar complaints — a team that is not proactive, cannot estimate, reports green for months and then red — reflect protocol mismatches rather than capability failures.
Each ends with three practical accommodations a manager can apply within a single engagement.
Next, read the post on AI and professional services, where the Frozen Clock and the Apprenticeship Paradox name risks to innovation and the next generation of professional talent.
The post argues that the capability most needed now is the one AI cannot supply.
The two AI security posts apply the same approach to institutional bias in training data, reframing an apparently new risk as distance from execution.
These three threads are natural entry points, and the named frameworks are useful search terms.
Offshore delivery coordinationProtocol mismatches across teamsAI disruption of professional servicesWorkforce and apprenticeship pipelinesAI security and institutional riskDistance from executionCross-border delivery managementColumn-led LinkedIn commentaryNamed frameworks and patternsManagement and delivery leadersSecurity and risk operations
Both write about workforce pipelines as an operational problem, not a headcount problem.
Read more
Danielle Lares argues that projects often name the craft or title they need without understanding the tasks, safety requirements, training and qualifications behind it.
A job title alone does not tell the full story.
Thom Probus makes an adjacent argument: offshore delivery failures stem from mismatched assumptions about communication and commitment, not missing capability.
Both treat compliance and reporting as project-critical deliverables, building their cases from named concepts and checklists rather than general encouragement.
Danielle Lares's examples sit in construction, infrastructure and energy skilled trades, covering apprenticeship systems, union training capacity, federal funding and Department of Transportation oversight. Thom Probus works in professional services delivery across financial services, technology and professional services firms, with separate threads on AI-driven disruption and AI security.
Both translate observations from the ground into short frameworks leaders can act on.
Read more
Sercan Esen reports patterns from customer onsites across manufacturing — EHS owns outcomes, operations owns reality, IT scales it; dashboards are not the ask, decisions are.
That approach resembles Thom Probus's pattern analysis across financial services, professional services and technology organizations.
Both argue that a technology layer matters only when it changes how work is done, and both write about AI in operational processes and the workforce roles that follow.
Sercan Esen's material is rooted in industrial safety, physical manufacturing floors, human-machine collaboration and safety technology. Thom Probus focuses on cross-border professional services delivery, institutional risk and AI's effect on professional talent.
Both write about enterprise adoption of AI in core business processes and why it lags business expectations.
Read more
Sarah Toomey describes procurement's contradiction — buying AI is often the slowest, most expensive purchase an enterprise makes — and argues that the teams pulling ahead build visibility to keep pace while knowing what they signed up for.
Thom Probus asks similar questions about deploying AI in audit, procurement, hiring and security operations without losing review discipline.
Both draw on practitioner experience in a specific function to explain friction rather than list product features.
Sarah Toomey writes from inside a procurement software company about sourcing and source-to-pay processes, and announces a platform launch. Thom Probus writes cross-sector columns that reframe problems and offer short practical lists, without a product position.
The posts say little about Thom Probus's audience, and that should shape how a professional services firm uses this profile.
Read more
The only quantified figure in the posts here is a LinkedIn following of roughly 1,066 people, observed on 10 October 2026.
The posts do not say where that audience sits geographically, how senior it is, which industries it works in, or how many people read the columns the posts promote.
A speaking slot cannot be justified on audience size or composition from the posts alone; topical match is the stronger argument.
On content appeal, the fit is direct.
The five posts published between 15 June and 4 August 2026 cover offshore delivery coordination, AI-driven disruption in professional services, and AI-related security risk — the same ground as the proposed leadership-event talk.
Two of the five 2026-07-14 posts are variants of one article promotion, not two separate pieces, so the posting cadence overstates how much distinct content a sponsor would sit alongside.
Two named columns, The Meridian View and The Fog of Change, appear in the posts as the home of the longer writing.
That points to a distribution channel beyond the LinkedIn feed, but the posts do not give subscriber, open, or readership numbers, so the size of that channel is unknown.
Concrete next step before committing a speaker: ask Probus for (1) LinkedIn follower demographics covering geography, seniority, and industry; (2) subscriber and open figures for The Meridian View and The Fog of Change; and (3) attendance or audience feedback from a talk on offshore delivery coordination or AI disruption in professional services.
Those three items answer the event team's real question — whether the room matches the room they are selling to.
Selected example of the content a professional-services audience would see: the post sketching eight coordination barriers in offshore programs, from a "yes" that does not mean yes to the green-green-green-red status pattern, with accommodations an American management team can make inside a single engagement.
It is written for delivery leaders rather than technologists, which is the audience a leadership event would want, but the posts do not say who actually read it.
The five posts describe no sponsorship or partnership offer.
Read more
Thom Probus publishes two written columns — The Meridian View, on offshore delivery coordination, and The Fog of Change, on AI and professional services — and posts about AI-related security risks.
None describes sponsored formats, branded-content terms, a media kit, rates, or a business inquiry route.
Speaker-booking or collaboration requests must go directly through their LinkedIn profile; no partnership channel, package, or lead time is published.
Before planning an event, buyers should ask about availability, fees, and disclosure requirements.
A professional services firm is planning a half-day leadership offsite for delivery leaders, engagement managers, and practice partners.
Read more
It wants one session on why offshore delivery programs go wrong and what to do about AI.
Thom Probus is a close fit, based on the content rather than audience scale.
The posts supply a talk spine that maps to the room.
The offshore delivery post starts with complaints management teams make in their own words — not proactive, cannot estimate, green status for three months and then red — and argues these usually reflect protocol mismatches between two groups of professionals with different assumptions about communication, commitment, and what a manager is for.
It offers checkable specifics for a session: a "yes" that does not mean yes, the green-green-green-red status pattern, eight coordination barriers, and closing guidance to accommodate within the project, invest in relationships for the long game, and keep culture change off the critical path.
That last point matters for a leadership event: the promise is a protocol redesign within one engagement, not a multi-year transformation program — something a delivery organization can approve after the offsite.
The AI disruption material extends the session to the same audience.
The Fog of Change post frames professional services as a sector once insulated by judgment, synthesis, and human context, and names three ideas: the Frozen Clock problem, the Apprenticeship Paradox, and the claim that the capability most needed now is what AI cannot provide.
Those are memorable hooks for partners concerned about junior talent pipelines.
For a room that includes risk or compliance leaders, a third post adds a security segment: institutional bias in training data lets harmful requests through when dressed as compliance or audit work.
Probus frames this as the old distance-from-execution hazard, with the difference that this system was born at altitude, with no ground floor to fall back on.
The method also suits the format.
The posts describe patterns observed across financial services, professional services, and technology organizations, rather than a single anecdote.
A session based on them can offer cross-industry observations instead of one client war story.
The recurring use of named frameworks gives an event team ready-made segment titles and a handout structure.
Two planning points remain.
First, the posts show no public speaking: no talk recording, event listing, or audience feedback.
The event team should ask for a speaking sample before signing.
Second, the only audience figure is roughly 1,066 LinkedIn followers as of 10 October 2026; there is no demographic, newsletter subscriber, or readership data.
That matters little for a closed firm offsite, where the firm supplies the audience.
If the event doubles as external promotion, ask for audience data and do not rely on Probus's following to fill seats.
When to choose a specialist
A B2B software vendor wants a sponsored content series tied to its AI governance product, with contracted deliverables, guaranteed distribution, audience demographics for reporting, disclosure terms, and a rate card.
Read more
The posts do not establish that offer; the mismatch is structural, not a judgment about quality.
The commercial format is unproven.
The posts provide no sponsorship offer, media kit, branded-content terms, rates, lead time, or published business inquiry route.
The partnership section does not say that Thom Probus never accepts sponsorships, so the vendor would need to establish terms from scratch through the LinkedIn profile.
Before proceeding, it should ask whether Probus offers sponsored content and request a scope, rates, timeline, and disclosure terms.
A vendor needing signed deliverables within a campaign calendar cannot assume those are available.
Measurability is also unproven.
The only quantified audience figure is roughly 1,066 LinkedIn followers as of 10 October 2026; there is no data on geography, seniority, industry, or readership of The Meridian View and The Fog of Change.
The vendor should request audience data and confirm whether distribution or performance guarantees are available before planning a campaign.
The posts are column announcements and commentary, not examples of sponsored content showing how Probus handles a client's product, message, or approval process.
Scope is another open question.
The five posts are short-form announcements of longer columns, which are not available here.
A brand considering a technical sponsored paper on AI deployment in audit or procurement should read the underlying columns before committing.
If the need is instead a practitioner deep-dive on security operations for a large public audience, ask for a talk transcript or training record; the posts provide neither.
A worked campaign example
Need: A professional services firm is booking a 40-minute keynote plus a 20-minute working session for its annual delivery leadership offsite.
Each attending practice should leave with one protocol change to try in its next engagement.
Working title: "Green for Three Months."
Opening (5 minutes).
Start with the complaint set: the team is not proactive, they cannot estimate, status was green for three months and then red.
Ask the room which of the three it hears most often.
The offshore delivery post presents these complaints as common among management teams running offshore programs, giving the audience a point of recognition before the argument begins.
First segment, diagnosis (10 minutes).
Move from complaints to the protocol-mismatch explanation: two groups of professionals operating under different assumptions about what communication means, what commitment means, and what a manager is for.
Use the "yes" that does not mean yes as the clearest example, and explain why it is a translation problem rather than a capability problem.
Keep the cross-sector framing — financial services, professional services, technology — so practice leads do not mistake it for one industry's anecdote.
Second segment, the failure pattern (8 minutes).
Present the green-green-green-red status pattern as a coordination artifact rather than a reporting failure.
Show how the same protocol assumptions produce smooth green reporting followed by a sudden red, then ask what a status update commits to in each operating culture.
Third segment, what to change inside one engagement (10 minutes).
Apply the post's three-part closing rule: accommodate within the project, invest in relationships for the long game, and never put culture change on the critical path.
Give the room the eight coordination barriers as a handout checklist, then have tables pick the two they can address within their current engagement scope.
Fourth segment, AI and the next cohort (7 minutes).
Bring in the professional services disruption material: the sector was insulated for 150 years because it required judgment, synthesis, and human context; the Frozen Clock problem describes stalled innovation cycles; the Apprenticeship Paradox describes junior talent quietly going unbuilt.
Close with the claim that the capability most needed now is the one AI cannot provide, and tie it back to the protocol point: if communication norms are already mismatched, adding AI makes the distance from execution worse, not better.
If risk or compliance leads are in the room, add the training-data bias example: harmful requests get approved when dressed as compliance or audit work.
Connect it to the distance-from-execution framing and its roots as an older institutional hazard.
Working session (20 minutes).
Each practice drafts a one-page protocol change specifying the barrier it addresses, the current sentence or expectation causing the mismatch, replacement language, and a check to show in 30 days whether it worked.
Close with the firm's own next step, not a sales pitch.
Before confirming, the event team should request the full text of The Meridian View column on the eight coordination barriers and the Fog of Change column, so the session reflects the deeper writing rather than just the announcements; a prior talk example or recording, since no speaking record appears in the posts; and direct confirmation of availability, fee, and format through the LinkedIn profile, since no booking channel is published.
If external promotion depends on Probus's following, request audience data: they have roughly 1,066 LinkedIn followers, with no readership data for the columns.
The firm's own invitation list should carry the attendance plan.
Pick Danielle Lares over Thom Probus when the offsite is about project readiness and the workforce pipeline, not cross-border delivery coordination.
Read more
For a firm trying to find, qualify, and schedule the craft and technical workers a project needs, Danielle Lares's posts address the task directly.
They argue that the question has shifted from "do we have enough workers" to whether a team understands the tasks, phases, experience, certification, and training the work requires—and where that talent exists.
The posts describe a Project Success Team model that brings owners, investors, contractors, unions, workforce partners, educators, and municipalities together around investment, project scope, skills, workforce strategy, compliance, and community impact, with stated payoffs for each group.
A second post treats compliance as part of delivery, not an administrative track, covering DOT oversight, apprenticeship standards, grant deliverables, contractor bid eligibility, and federal funding eligibility.
It closes with pre-planning, communication, trust, and due diligence.
Both posts target infrastructure, energy, and manufacturing audiences and name specific systems and documents, including the MDOT OJT program manual and a pilot running 2018 to 2021.
For owners, contractors, or funded-project teams working out how to staff and document a project, these posts offer more usable specifics than the offshore-protocol material.
Thom Probus's posts focus on domestic skilled-trades workforce systems, apprenticeship pathways, and labor compliance—not offshore delivery teams, communication and commitment mismatches between two professional cultures, or AI's impact on professional services.
A firm seeking a session on why an offshore program reports green for three months and then red would be changing the topic, not just the speaker.
The profile offers two posts, with no talk recording, event listing, or audience data.
Ask directly about availability, fee, and prior speaking experience.
Pick Sercan Esen over Thom Probus when the audience shifts from professional services delivery leaders to industrial operations and safety leaders, and the focus shifts from offshore coordination to frontline adoption of AI and automation.
Read more
Sercan Esen's posts are built for that room.
One describes contributing to a World Economic Forum framework on human-machine collaboration and lists five operating points: trust in new vision, robotics, and autonomous equipment; behaviour as the frontier of safety innovation; emerging roles such as EHS AI specialist, safety agent supervisor, and human-machine workflow designer; automation that removes exposure rather than people; and safety data treated as operational data, with safety teams as workflow architects.
The second post reports a three-month field run across 22,487 miles, 11 states, 12 cities, 27 onsite visits, 16 customers, and 12 industries, with roughly 94 stakeholder conversations.
It draws five patterns from that experience: EHS owns outcomes, operations owns reality, IT scales it; hardware will matter more than expected; EHS compliance platforms are being challenged; teams want decisions rather than more dashboards; adoption is the strategy.
For a manufacturer or industrial operator planning a session on putting AI and monitoring systems into live operations, that firsthand detail better matches the need and the room's daily reality than a cross-industry argument about protocol mismatch.
The tradeoff is subject matter, not quality.
The posts cover plant-floor safety, manufacturing operations, and human-machine collaboration inside industrial sites—not offshore delivery programs, the assumptions that separate an American management team from an offshore one, or AI disruption in professional services.
A professional services firm would be buying a different session.
The profile offers two posts, no recording or event listing, no independent confirmation of the sites or customers described, and no audience figures.
Ask directly for details that matter to the booking.
Pick Sarah Toomey over Thom Probus when the offsite is for procurement and finance leaders deciding how to move an enterprise AI purchase forward, not how to run cross-border delivery teams.
Read more
One of Sarah Toomey's posts frames procurement's current challenge: buying AI is often the slowest and most expensive enterprise purchase; security reviews and stakeholder counts have grown; and the same rigor once called diligence is now treated as a bottleneck.
The argument is that teams pulling ahead build visibility to move at the business's pace while still knowing what they signed up for—a useful frame for a procurement leadership session.
The second post traces a career in sourcing across tech and into a procurement role, then introduces an autonomous source-to-pay platform that routes requests, pulls supplier and contract data, checks policy, and moves work toward a decision.
It argues that AI-native is a foundation rather than an add-on.
For a room deciding how to buy and govern AI tooling, that is closer to the decision at hand than a talk about why offshore programs go red.
Two constraints matter to a firm seeking a vendor-neutral perspective on procurement.
Both posts tie procurement process, sourcing technology, and enterprise AI purchasing to a product and company story: one is a launch announcement, and the other points readers to a colleague's take.
A firm seeking an outside perspective should weigh that framing and ask for disclosure of any relationship before booking.
More decisively, the posts do not cover offshore delivery coordination, delivery-team management, or the professional services talent pipeline, so they do not answer the firm's current question.
The profile offers two posts, no speaking record, and no audience data.
This profile draws on five LinkedIn posts covering three distinct pieces: offshore delivery and protocol mismatches, AI’s impact on professional-services work, and security risks in AI-assisted institutional processes.
Two pairs of posts are close variants.
The longer columns referenced in the posts were not included, so the analysis is limited to what the posts describe.
