Craig Cooper writes about Lean and Six Sigma, operational improvement, and the governance needed to make digital and AI transformations work. The posts focus on practical questions such as who owns decisions, whether data can be trusted, and how organizations can tell if a transformation is delivering results.
Craig Cooper is most useful for practical governance tests and operational examples about digital, AI, and transformation decisions.
Best for
A manufacturing consultancy or governance-led transformation thought leadership campaign.
Not for
A cloud or AI vendor wanting high-volume sponsored video, demos, or hard reach targets.
Key takeaways
Failed transformations are governance problems wearing an execution costume.
Dashboards cannot settle a disagreement about which number is true.
Autonomous AI raises one question: who decides when the human disagrees?
Check first: Confirm terms, sponsorship slots, and recent LinkedIn performance and audience data before contacting them.
Main ideas
Shared technology is not an advantage; the organisation around it is · Failed transformations are governance problems wearing an execution costume · Dashboards cannot settle a disagreement about which number is true
Craig Cooper writes about Lean and Six Sigma, manufacturing improvement, and the governance behind digital and AI transformation.
Across their posts, they return to a practical question: when technology, data, or targets conflict, who has the authority to decide what happens?
They argue that organizations need clear decision rights and trusted measures before new systems can deliver results.
Their work is useful to readers who want concrete ways to spot transformation problems, not just arguments for adopting the latest tools.
Cooper makes governance problems visible through specific operational tests and examples.
In one post, they ask transformation leaders who can stop a project, which decision rights are changing, and what behaviours are being rewarded; they then compare a shop-floor supervisor’s authority to stop a line with the incentives finance uses to assess that supervisor.
In another, conflicting inventory figures across finance, operations, and a warehouse system show how dashboards can speed up confusion rather than resolve it.
They also use manufacturing history and a Roman supply-chain analogy to explain why management systems matter as much as technology.
The recurring argument is consistent, but the formats vary: some posts offer developed diagnostic reasoning, while others are brief prompts about AI or requests for practitioners’ experience, including in the NHS.
That range makes their work worth following for readers interested in how improvement principles apply to current organizational decisions; the short prompts are better read as conversation starters than as complete analyses.
Craig Cooper writes about Lean, Six Sigma and operational improvement, with an increasing focus on AI and digital transformation.
Read more
His recurring argument is that results depend on the decision-making system around a technology, not the technology itself: who owns an outcome, who can stop a project, who settles disagreements over which number is correct, and whether a vendor can deliver what it promised.
He backs that argument with historical comparisons, named company examples and diagnostic questions readers can take into a meeting.
As a practitioner, he seeks other practitioners' field experience rather than theory.
Shared technology is not an advantage; the organisation around it is
Cooper argues that when everyone can buy the same machines or models, the differentiator is how people are organised around them.
Read more
He makes the case through manufacturing history: in the 1980s, Western manufacturers attributed Japan's dominance to better robots and automation, then bought the same flexible manufacturing systems.
But a 1986 Harvard study by Jaikumar found that US plants using identical equipment produced 10 different parts while Japanese plants produced 93.
The MIT study published in 1990 as "The Machine That Changed the World" traced the gap to management philosophy, not machinery.
Cooper applies the same pattern to AI: organisations pulling ahead are not winning with better algorithms or more data, but with governance structures built for complex adaptive systems.
His refrain is "governance before systems, systems before tools."
The factor-of-nine comparison between US and Japanese plants running the same FMS equipment, followed by the fact Cooper cites: Toyota was half GM's size in 1990 and passed GM as the world's largest automaker twenty years later.
Failed transformations are governance problems wearing an execution costume
Cooper treats most failed transformation projects not as methodology failures but as unclear decision rights, and offers tests rather than slogans.
Read more
In a steering committee Cooper suggests asking three questions: who decides when we stop this project, what specific decision rights are changing, and which behaviours are being rewarded differently.
Confused or circular answers, in Cooper's reading, mean the project is already on a trajectory that ends in lessons-learned presentations nobody reads.
A second test crosses functions: ask a production supervisor what happens if they stop the line to fix a quality issue, then ask finance which metrics determine that supervisor's bonus, and compare the answers.
Cooper calls the gap between the org chart and who actually decides a "transformation tax," and sets a 90-day rule for getting clear answers.
A £47M MES implementation where IT chose the system, operations had to use it and finance measured success, but nobody owned the outcome.
Dashboards cannot settle a disagreement about which number is true
Cooper distinguishes data availability from data trust.
Read more
Better pipelines, real-time analytics and master data management do not answer who has authority to decide which version of a metric wins, or what happens when systems disagree.
Without that authority, organisations automate their data chaos and get faster chaos, while executives fall back on gut feel when the numbers conflict.
The hard part is often political: departments that have reported a metric for years must admit that the previous strategy relied on figures they cannot defend.
An FTSE 250 manufacturer where finance reported inventory turns of 8.2x, operations 6.7x and the warehouse system 11.3x.
When the managing director asked which was right, the room fell silent.
Cooper also notes twelve different "golden sources" for the same customer and no rule for who could override which numbers.
Vendor selection is a balance-sheet and delivery-risk decision, not just a capability comparison
Cooper extends his governance argument to suppliers and AI deployments.
Read more
Organisations announce transformational commitments before establishing how to fund and execute them, while procurement processes assess what a vendor can do more readily than whether it can financially deliver.
He contrasts two companies cutting roughly 30,000 people for different reasons: Amazon, which he says built mechanisms to scale decision-making and trims when layers accumulate, and Oracle, which committed to infrastructure at a scale that raises financing questions.
His summary: cloud strategy is no longer only an IT decision but a balance-sheet governance decision.
Chief information officers with cloud contracts should treat the buildout as an infrastructure delivery risk, not just a service agreement.
Oracle, where Cooper cites a TD Cowen estimate of roughly $156 billion in required capital expenditure, reports that banks had pulled back from Oracle-linked data-centre lending, with borrowing costs for that kind of financing reportedly doubled, and a reported plan to raise $45–50 billion in 2026 through debt and equity, alongside discussion of selling the $28.3 billion Cerner acquisition from 2022 to plug the gap.
Autonomous AI raises one question before any others: who decides when the human disagrees
When AI agents are given real authority inside regulated operations, Cooper argues the interesting question is not technical capability but conflict resolution.
Read more
Cooper frames it narrowly and concretely: if an agent recommends an action and a human reviewer flags it, whose judgment prevails, and where is that rule written down?
Cooper calls this a governance question rather than a technical one, and notes that deployments can proceed at enormous scale without that rule being answered publicly.
The post is short and works as a prompt for a risk discussion rather than a developed argument.
Goldman Sachs spending six months embedding Anthropic engineers to build autonomous agents for trade accounting, compliance reviews and client onboarding, described by the CIO as "digital colleagues," with Cooper asking who decides when an agent recommends approving a $500M trade and a compliance officer sends it back for manual review.
Pull systems expose the truth about process capability; buffers hide it
Cooper argues for demand-driven flow over forecast-driven building, and says a pull system's value is clarity, not efficiency.
Read more
When material moves only against actual demand, stockouts and excess inventory both signal process capability; buffer stock conceals those signals.
One failed implementation involved a supplier running Kanban while keeping an MRP-driven schedule: pulling from one system while pushing with another.
Cooper also cautions against treating inventory cuts as automatically safe: the post asks whether halving inventory would expose capability gaps or cause customer delivery failures, and treats that breaking point as where the real improvement work starts.
The Roman army built supply depots every 20 miles, each holding exactly three days' grain for the legion ahead. Every extra wagon of "just in case" supplies meant one less soldier in formation.
Test improvement claims by what is still running two years later
Cooper's stated priority for continuous improvement is durability rather than pilot wins, and goes outside the sector to pursue it.
Read more
Writing from 25 years of Lean and Six Sigma work in automotive, aerospace, pharmaceuticals and energy, Cooper asks National Health Service practitioners for their field findings and repeats the same standard in Cooper's questions: what patterns show up repeatedly, what fails predictably, and what is genuinely embedded and still functioning 18–24 months later without constant intervention.
The prompt came from personal experience as a patient, where the same hospital, department and staff produced two very different experiences within two weeks.
Cooper frames that as a gap between capability and consistency, not competence.
This post is a request for practitioner input rather than a finished position.
Two visits to the same hospital department within two weeks: one involving systemic failures and a near-miss safety incident, the other running with appropriate protocols and smooth flow.
Cooper relays Geoffrey Hinton's argument that AI development cannot be stopped because it is too useful and too internationally competitive, and that governments should push companies to invest heavily in safety research so superintelligence remains under human control.
Read more
He translates that for manufacturing executives: competitors, suppliers and customers are all moving toward AI, so declining to participate is not a viable position. Hinton's view is his own; Cooper's contribution is the business framing.
Cooper argues that manufacturers are exposed, not protected, if competitors, suppliers and customers are already deploying AI and they choose to sit it out.
This is the clearest statement of Cooper's core argument: failed transformations are governance problems dressed up as execution problems.
Read more
Newcomers should start here because it shows the diagnostic method, not just the thesis.
Cooper proposes three questions for the next transformation steering committee: who decides when to stop the project, what specific decision rights are changing, and which behaviours are being rewarded differently.
Confused or circular answers mean the project is already on a failing trajectory.
A second test goes to the shop floor and finance: ask a production supervisor what happens if they stop the line to fix a quality issue, then ask finance which metrics determine that supervisor's bonus, and compare the answers.
They cite a £47M MES implementation where IT chose the system, operations had to use it, and finance measured success, but nobody owned the outcome.
They call the gap between the org chart and real decision-making a "transformation tax."
The post ends with a 90-day rule: if the three questions cannot be answered clearly in the first 90 days, the organisation is locked into a trajectory ending in lessons-learned presentations nobody reads.
For brands planning a campaign
For a governance-led transformation thought-leadership partnership, this is the most reusable asset in the set. Its three-question test can become a checklist, workshop prompt, or co-branded diagnostic, giving the campaign a concrete method rather than a slogan.
This post answers the question a finance or operations leader is most likely to ask first: how does a digital transformation spend tens of millions and still return nothing?
Read more
It shows Cooper turning a governance failure into a number.
Cooper describes an FTSE 250 manufacturer with dashboards, real-time analytics, and AI-ready infrastructure where every department had different numbers for the same metric: finance reported inventory turns of 8.2x, operations 6.7x, and the warehouse system 11.3x.
When the managing director asked which was right, nobody answered.
They diagnose a company that automated its data chaos and got faster chaos, compounded by twelve different "golden sources" for the same customer and no rule for who could override which numbers.
The post argues the real blocker was that operations had reported those metrics for three years, and admitting they were wrong meant admitting the previous strategy was built on fiction.
It closes by separating data availability from data trust and identifying the missing piece as governance: who decides which version of truth wins, and what happens when systems disagree.
For brands planning a campaign
This is the strongest CFO-facing hook in the set. A partnership piece could expand the three conflicting inventory numbers into a worked example of how conflicting metrics quietly invalidate a strategy, suiting finance and operations audiences better than abstract data-governance language.
This post explains where Cooper's governance-before-AI argument comes from.
Read more
It gives the historical pattern behind the current advice, helping readers judge whether the recommendation is a slogan or a position backed by evidence.
Cooper retells a manufacturing history: in the 1980s, Western manufacturers explained Japan's dominance as the result of better robots and automation, then bought the same flexible manufacturing systems.
Jaikumar's 1986 Harvard study found US plants using identical FMS equipment produced 10 different parts while Japanese plants produced 93, a factor-of-nine difference with the same machines.
The MIT 14-country study published in 1990 as "The Machine That Changed the World" traced the advantage to management philosophy rather than technology.
They note Toyota was half GM's size when that book appeared and passed GM as the world's largest automaker twenty years later, then draw a parallel to AI: organisations pulling ahead are not winning on better algorithms or more data but on governance structures designed for complex adaptive systems.
The refrain is "governance before systems, systems before tools."
For brands planning a campaign
This post supplies the historical frame that makes an AI-governance campaign feel argued rather than asserted. It could anchor a long-form piece tracing the path from the 1986 study to current AI investment decisions.
This shows how Cooper writes directly to a manufacturing operations audience rather than to executives.
Read more
It demonstrates their range and accessible, analogy-driven style.
Cooper uses the Roman army's supply depots, placed every 20 miles and holding exactly three days' grain for the legion ahead, to explain pull versus push systems.
The argument is that the Romans pulled only what was needed because every extra wagon meant one less soldier in formation, while modern manufacturers run push systems, building to forecast and warehousing "just in case" inventory.
They give a concrete example: a Tier 1 automotive supplier spent 18 months implementing Kanban while maintaining an MRP-driven schedule and wondered why it did not work.
They attribute the failure to pulling from one system while pushing with another.
The post ends by asking what would break if inventory were halved tomorrow, and frames that breaking point as where real improvement work starts.
For brands planning a campaign
This is the best demonstration that Cooper can write operational explainers for a practitioner audience, not only governance commentary for executives. It supports a campaign brief that needs manufacturing-credible content with an accessible entry point.
This shows how Cooper applies governance thinking to a live news event.
Read more
It is the clearest example in the set of current-affairs commentary rather than an evergreen argument.
Cooper contrasts Oracle with Amazon, both cutting roughly 30,000 people but for different reasons.
In their reading, Amazon built mechanisms that scale decision-making and trims when layers accumulate; Oracle committed to infrastructure that TD Cowen estimates could require roughly $156 billion in capital expenditure while financing questions mount.
The post cites reports that Oracle is considering cutting 20,000 to 30,000 jobs, that US banks have pulled back from Oracle-linked data-centre project lending, that borrowing costs for this type of financing have reportedly doubled, and that Oracle is discussing selling Cerner, the $28.3 billion acquisition from 2022.
It also notes disclosed plans to raise $45 to $50 billion in 2026 through debt and equity.
They frame this as survival funding rather than restructuring, and argue that the analyst view of the buildout as an infrastructure delivery risk, not just a service agreement, is the governance point chief information officers with Oracle cloud contracts should take from it.
For brands planning a campaign
This post shows Cooper reacting to a specific corporate event through a governance lens while sourcing claims. A partnership could use that format for timely commentary, provided the sourcing discipline is maintained.
This shows what Cooper does when working outside their usual sector.
Read more
It is a request for practitioner input rather than a finished argument, offering a view of how they move into a new field.
Drawing on 25 years of Lean and Six Sigma work in automotive, aerospace, pharmaceuticals, and energy, Cooper asks NHS continuous improvement practitioners what they have found in practice and what has remained embedded 18 to 24 months later without constant intervention.
The prompt comes from a personal experience: the same hospital, department, and staff delivered two completely different experiences within two weeks, one with systemic failures and a near-miss safety incident and one with appropriate protocols and smooth flow.
They frame the gap as one between capability and consistency rather than competence, and explicitly ask for reality rather than theory, including what fails predictably and what surprised practitioners compared with other sectors.
For brands planning a campaign
This is a community-consultation post rather than a thought-leadership asset. It offers evidence of audience engagement and cross-sector curiosity, but should not be presented as a substantive position on healthcare improvement.
This answers what Cooper does with an AI deployment in financial services.
Read more
It is short, but it shows the single question Cooper uses to frame autonomous systems.
Cooper writes that Goldman Sachs spent six months embedding Anthropic engineers in its teams to build autonomous AI agents for trade accounting, compliance reviews and client onboarding.
Coverage focused on efficiency, while the CIO called the agents “digital colleagues.”
Cooper asks what happens when an agent recommends approving a $500M trade and a compliance officer flags it for manual review: who decides?
They frame that as a governance question, not a technical one, and note that the systems were deployed across $2.5 trillion in assets without a public answer.
For brands planning a campaign
A compact, provocative hook that could open a financial-services governance piece or panel discussion. Its brevity makes it a better starting point than a standalone campaign asset.
A concise example of how Cooper connects the AI safety debate to manufacturing executives’ choices, translating an abstract debate into a strategic decision.
Read more
Cooper summarises Geoffrey Hinton’s position: AI development cannot be stopped because it is too useful and internationally competitive, so governments should require companies to invest heavily in safety research to keep superintelligence under human control.
They bring the argument to manufacturing executives: competitors, suppliers and customers are all moving toward AI, so opting out is not a strategy.
The brief post works as a strategic prompt rather than a developed argument.
For brands planning a campaign
A useful secondary item connecting AI safety discourse to manufacturing strategy, but too short to carry a campaign on its own.
Across posts about AI, digital transformation, and manufacturing, Cooper argues that shared technology does not guarantee shared results: the decision-making system around it matters.
Read more
They illustrate the point by comparing manufacturing’s adoption of automation with current AI investment.
Uses historical comparisons to turn a current technology debate into an organizational-design question.
For brands planning a campaign
A thought-leadership partnership could help manufacturing leaders examine decision rights and operating structures before buying or scaling new technology.
Cooper frames transformation failures as governance problems and offers practical tests: ask who can stop a project, which decision rights are changing, and whether incentives match shop-floor priorities.
Read more
They also recommend comparing formal responsibility with who actually makes decisions.
Pairs pointed questions with examples of conflicting ownership and incentives.
For brands planning a campaign
Useful for a campaign offering leaders a concrete early diagnostic for transformation risk, rather than a general message about change management.
Cooper argues that dashboards and data pipelines cannot resolve disagreements over which figures are reliable or who has authority to settle conflicts.
Read more
A post about a manufacturer's conflicting inventory figures illustrates how better infrastructure can accelerate confusion instead of fixing it.
Uses a company example and conflicting metric values to make an abstract governance issue tangible.
For brands planning a campaign
Could support content about data governance, trustworthy operational metrics, and clarifying accountability before analytics or AI projects.
Cooper applies Lean thinking to inventory and process improvement.
Read more
One post contrasts pull with forecast-driven push and argues that excess stock can hide weaknesses in process capability. Another asks practitioners working in the NHS to share which changes endure, rather than relying on theory or short-lived pilots.
Uses a historical analogy and a shop-floor question, while inviting practitioners to contribute firsthand experience.
The inventory post warns that reducing buffers can reveal capability gaps and asks whether doing so could cause customer delivery failures.
For brands planning a campaign
A fit for practical manufacturing improvement content, especially when a partner can show how to expose process constraints without treating inventory cuts as automatically safe.
In AI-focused posts, Cooper shifts attention from capability to control and delivery: who resolves a conflict between an AI agent and a human reviewer, and whether a vendor can finance and execute its infrastructure commitments.
Read more
The posts extend the governance theme from internal transformation to external providers.
Uses current business examples and ends with questions for executives responsible for technology decisions.
For brands planning a campaign
A partnership could explore practical governance questions for AI deployment and vendor selection, including decision authority and delivery risk.
Craig Cooper's posts here document no sponsorship, affiliate, client, or investment relationship.
Read more
They describe themself as founder of Leancore Ltd and Human Tech Lab. Oracle and Goldman Sachs appear as subjects of their governance analysis, not as commercial partners.
Leancore Ltd
Owned business
Craig Cooper lists himself as founder of Leancore Ltd in the bio line of a post on how to spot failing transformation projects in the first 90 days.
Read more
Before hiring, ask what the business sells, who its clients are, and how long the founder role has run.
In an analysis post, Craig Cooper writes that Oracle committed infrastructure that TD Cowen estimates could require roughly $156 billion in capital expenditure, that it is reportedly considering cutting 20,000 to 30,000 jobs, that banks have pulled back from Oracle-linked data-centre lending, and that Oracle has disclosed plans to raise $45-50 billion in 2026.
Read more
They contrast these cuts with Amazon's, arguing Oracle is funding promises made without governance mechanisms to deliver them, and ask readers what governance mechanisms they use to assess a vendor's financial capacity to execute.
In a short analysis post, Craig Cooper writes that Goldman Sachs spent six months embedding Anthropic engineers to build autonomous agents for trade accounting, compliance reviews, and client onboarding.
Read more
They ask who decides when an AI agent recommends approving a $500 million trade and a compliance officer flags it for manual review.
Craig Cooper's posts are short, argument-led notes rather than long articles, and they repay a browse by theme rather than by date.
Read more
Start with the governance argument: shared technology does not produce different results on its own, and the deciding factor is who owns an outcome, who can stop a project, and who settles a disagreement over which number is correct.
From there, follow two branches.
One is diagnostic — the steering-committee questions, the shop-floor versus finance contradiction, the break-point question they ask about halving inventory.
The other is external — AI agents inside regulated operations, and whether a vendor can finance and deliver what it has promised.
They write as a Lean and Six Sigma practitioner who wants other practitioners' field experience, so the most useful material is the specific tests and examples a reader can carry into a meeting rather than a finished methodology.
Both write about what happens to industrial productivity when AI and automation move into the plant, and both treat the operating model as the variable that decides whether the gains hold.
Read more
Lilly's thinking-factory series and Cooper's posts on automation and AI reach the same conclusion from different directions: buying the same machines or models is not where the advantage sits.
Lilly works at national and industrial-policy scale — dark factories in China, Japan's reindustrialisation window, multi-part arguments built on labour and capital statistics.
Cooper stays at the level of a single organisation and meeting: decision rights, who owns an outcome, whether a supplier can finance its commitments.
They write short diagnostic posts rooted in Lean and Six Sigma practice rather than a macro thesis.
Both publish practitioner-led observations on why enterprise transformation programmes underdeliver, and both argue that the limiting factor is not the technology but whether the people, delivery realities and decision-making around it are in place.
Read more
Kumar makes the point about ERP and enterprise application programmes; Cooper makes it about data, governance and automation.
Kumar's posts double as recruitment marketing for Kumar's own sourcing business — the argument runs toward specialist Oracle, SAP and Workday talent and the firm's model for finding it.
Cooper names no service and offers diagnostic tests instead: questions to ask a steering committee, a comparison of shop-floor and finance answers, a question about vendor delivery capacity.
Read Kumar for the talent-market view and Cooper for the operating-structure view.
Craig Cooper's audience picture is narrow but specific.
Read more
The only published LinkedIn figure is the follower count: 2,636, recorded on 8 October 2026.
The profile publishes no reach, engagement, demographic or job-title data, and none of the eight posts includes audience measurements.
On size alone, treat this as a specialist placement rather than a broad-reach channel.
The posts show who the content addresses: people who run or approve operational improvement.
Posts dated 7 January to 9 February 2026 speak to production supervisors deciding whether to stop a line over a quality issue, buyers holding Oracle cloud contracts, operations and finance teams whose numbers for the same metric disagree, and continuous improvement practitioners working inside the NHS.
The arguments focus on decision rights rather than tooling, returning to the line "Governance before systems before tools."
Several posts close with direct questions to practitioners, including what would break if you halved inventory tomorrow and what governance mechanisms you use to assess a vendor's financial capacity to deliver.
The subject matter points toward operations, transformation and technology roles in manufacturing and asset-heavy businesses, but does not show how many people in those roles read the posts.
For a governance-led transformation partnership, ask them before contracting for recent LinkedIn post results on comparable governance topics — impressions, reactions, comment counts and any reposts by named practitioners — and any audience survey or follower-analytics data covering job titles, seniority and industry sector.
Those results are the direct test; if they show operations and IT leadership rather than only the improvement community, the small follower count matters far less.
LinkedIn followers
2,636
LinkedIn profile linkedin.com/in/craigmrcooper (follower count carried in the account record) · 2026-10-08
The eight posts provide no documented sponsorship offer, paid partnership, or way to commission work from Craig Cooper.
Read more
They contain no sponsored-content markers, partner hashtags, or disclosures of paid arrangements.
The posts do establish the subject matter a partnership would draw on.
Cooper writes as a practitioner of Lean and Six Sigma and operational improvement, applying that lens to digital and AI programmes: who owns a decision, whether two systems report the same number, and what governs the distance between a board announcement and a delivered result.
A manufacturing consultancy proposing a thought-leadership partnership on governance-led transformation would be working in their established territory.
The posts are specific and example-led: a FTSE 250 manufacturer whose finance, operations and warehouse systems each reported different inventory turns; a £47M MES rollout nobody owned; the Roman supply depot as a pull-versus-push analogy; and banks pulling back from Oracle-linked data-centre lending.
That is the kind of concrete drafting such a collaboration would produce.
Before costing a campaign, ask Cooper directly for current commercial terms, available formats, disclosure policy, and a booking route; none is published in the posts.
A manufacturing consultancy wants to partner with Craig Cooper on thought leadership about governance-led transformation.
Read more
Reasons
Governance-led transformation is Cooper's standing position, not a topic they occasionally touch. The signature line "governance before systems before tools" recurs across posts about AI adoption, transformation failure, and data trust, so a partnership would extend an existing argument rather than ask them to adopt the consultancy's line.
The material offers usable diagnostics, not just opinions. The transformation-failure post supplies three steering-committee questions (who decides when to stop the project, which decision rights are changing, which behaviours are rewarded differently), a shop-floor versus finance incentive check, a decision-rights audit, and a 90-day rule. These can become a checklist, workshop prompt, or scoring sheet without inventing anything.
Cooper reasons from specific numbers and named cases, which suits consultancy marketing better than abstract commentary: a £47M MES implementation where IT chose the system, operations used it, and finance measured it, but nobody owned the outcome; a FTSE 250 manufacturer where finance, operations, and the warehouse system reported inventory turns of 8.2x, 6.7x, and 11.3x with twelve "golden sources" for the same customer; an estimated $156bn in Oracle-related capex with a $45–50bn funding plan for 2026.
The historical framing broadens the campaign beyond one sector. The 1986 Jaikumar study and The Machine That Changed the World give the partnership a way to argue that AI investment is repeating a documented manufacturing pattern, a natural anchor for a long-form piece.
Cooper carries the same governance lens outward to vendors and autonomous systems—whether a cloud supplier can finance and deliver what it committed to, and who decides when an AI agent and a human reviewer disagree. That extends the partnership's territory from internal operating models to procurement and AI deployment.
The work speaks to the consultancy's buyers: production supervisors deciding whether to stop a line, CIOs holding cloud contracts, operations and finance teams with conflicting metrics, and continuous improvement practitioners. Ask for measured demographic and job-title data to confirm those roles are represented among readers.
Caveats
No sponsorship offer, format list, rate card, disclosure policy, or booking route appears in the posts, and the only account identified is a personal LinkedIn profile. Scope the collaboration directly with Cooper and confirm the terms in writing; ask whether fixed sponsorship slots are available.
Reach evidence is thin: the only measured figure is 2,636 LinkedIn followers, with no engagement, reach, demographic, or job-title data. Plan the partnership as expert-authored thought leadership, with Cooper supplying the argument and method and the consultancy supplying distribution, design, and audience—not as a reach buy. Ask for performance and audience data before setting reach targets.
Verdict
Strong editorial fit: the argument the consultancy wants to make is the one Cooper already makes, with methods and worked examples attached. Ask about commercial availability and terms.
When to choose a specialist
A cloud or AI product vendor wants a high-volume sponsored content series—short video or product-demo posts with hard reach, engagement, and conversion targets.
Read more
Reasons
The posts are all written argument; no video, audio, or transcript appears. Ask Cooper for a sample or confirmation before committing to a video or demo series in their voice.
There is no engagement history to plan against. Ask for impressions, reactions, comment counts, and repost data before costing or guaranteeing a brief built on reach or conversion KPIs.
The content posture works against product advocacy. Cooper's most recent corporate commentary questions whether a vendor can finance and deliver its commitments, calling a $156bn infrastructure buildout a governance and delivery risk rather than a service agreement, and asks who decides when an automated system and a compliance officer disagree. That is critical analysis of large technology suppliers, not product endorsement.
No sponsor policy or format history is documented. Ask whether Cooper accepts disclosed paid placements, branded video, or fixed deliverables before building the brief around them.
For a general consumer or non-technical audience, the vocabulary and examples—decision rights, inventory turns, MES rollouts, MRP-driven schedules—assume an operations or finance reader. Ask for audience data before targeting a broader readership.
Verdict
Poor fit on format, evidence, and editorial independence.
A worked campaign example
Angle
Open with the cost of getting it wrong: a £47M MES implementation in which IT chose the system, operations had to use it, and finance measured success, with no one owning the outcome. Frame the gap between the org chart and real decision-making as the "transformation tax."
Publish a four-step audit drawn from Cooper's published method: the three steering-committee questions, the shop-floor versus finance incentive comparison, a map of who actually decides versus who is supposed to, and the 90-day rule that says a project without clear answers at the outset is already on a failing trajectory.
Work one anonymised manufacturer through the audit end to end, using the conflicting inventory figures—8.2x in finance, 6.7x in operations, 11.3x in the warehouse system, and twelve "golden sources" for the same customer—to show how a governance failure becomes a number on a board paper.
Close with the historical frame: the 1986 finding that US and Japanese plants using identical equipment produced ten and ninety-three parts respectively, and the observation that the AI programmes now being funded may repeat the same mistake. Give the consultancy's readers a reason governance work precedes technology spend, not a slogan about it.
Lead the call to action with the audit itself. Readers complete the scoring sheet and receive their own transformation tax estimate; the strongest submissions can feed an anonymised benchmark piece in the same series.
Brief
A manufacturing consultancy commissions a thought-leadership partnership on governance-led transformation, aimed at COOs, CIOs, and finance directors in asset-heavy businesses.
Concept
The Transformation Tax Audit—a co-branded diagnostic and long-form article built from Cooper's own tests rather than a generic governance manifesto.
Deliverables
One long-form article with Cooper as named author, plus a downloadable audit worksheet the consultancy can brand and reuse
A short post series in Cooper’s established format, each ending with an audit question for the reader, as the posts already do.
An optional anonymised benchmark summary, if enough completed audits are collected to support one.
Open items
Agree the format, rights, disclosure wording and fee with Cooper in writing before commissioning. The posts do not publish commercial terms.
Ask Cooper for post-level analytics on comparable governance topics to understand what distribution the consultancy is buying alongside the content.
Decide who signs the editorial as author and reviewer. Confirm whether the £47M write-up linked from the data-trust post can be cited directly or whether the campaign must use the post’s own summary.
Confirm the four-step audit’s capacities with someone inside the consultancy who can defend it to a CFO. Cooper’s published version is a diagnostic prompt, not a validated assessment instrument.
Why it fits
It uses Cooper’s method, not just their name, so the partnership produces an argument readers can apply on Monday.
It speaks to the executives named in the brief through their own failure modes — conflicting numbers, unowned outcomes and unclear decision rights — using examples already published.
It keeps the argument honest: the audit asks clients whether they can answer the questions, not whether they should buy anything. That fits Cooper’s writing and avoids turning critical commentary into a sales pitch.
Choose Lilly when the consultancy's campaign makes the industry-level case for modernising manufacturing rather than focusing on one client's steering committee.
Read more
Lilly frames AI adoption in manufacturing as a national competitiveness problem: Japan's shrinking operator base and low generative-AI adoption versus China's dark factories; the argument that Japanese plants deploy AI beside the production lane while Chinese plants put it inside the lane; and a Western reindustrialisation sequence from AI implementation to productivity recovery to reshoring.
That material suits a piece aimed at government-adjacent audiences, industrial policy readers, or a consultancy selling a sector thesis to boards deciding whether to build domestically.
The same partnership need — governance-led transformation — would be argued from the outside in: why the productivity window is open, how cheap inference changes the reshoring maths, and what the missed driver of cognitive latency costs.
Lilly's figures include US factory construction peaking at $235.6bn in 2024, 3.8M US manufacturing workers needed by 2033 with about 1.9M potentially unfilled, and roughly 40% average labour-productivity gains in a recent McKinsey lighthouse cohort.
Lilly operates at country and sector scale, so a client cannot act on the content on Monday morning.
There is no decision-rights audit, no steering-committee test, no 90-day rule, and no worked client example with named failure costs.
The posts are thesis pieces built on third-party research and close with "views my own.
No affiliation," which suits an opinion campaign but gives a consultancy less of its own method to co-brand.
If a campaign aimed at buyers who need a diagnostic they can complete and score, Lilly supplies the strategic why, not the instrument.
Choose Kumar when the consultancy wants to sell the delivery side of transformation rather than the operating-model argument: finding Oracle Cloud, PeopleSoft, SAP, and Workday specialists who are not on job boards.
Read more
Kumar writes as the founder of a recruiting firm, describing a passive network built through long-term relationships, an active ERP and IT talent database, and AI-driven sourcing layered with human qualification.
The strongest overlap with a campaign on governance-led transformation is the observation that ERP programme success depends on consultants who understand delivery realities, stakeholder management, and business processes inside large organisations — not technical expertise alone.
For a firm whose buyers keep failing transformation programmes on skills and continuity, that offers a credible alternative angle with a named population: public sector, federal, higher education, financial services, manufacturing, healthcare, and CPG environments.
Kumar's posts aim to generate recruiting conversations, with a clear invitation to message the founder, so a co-branded campaign would carry a stronger commercial edge than Cooper's diagnostic content.
The governance argument is thinner: there is no published method or worked example of a governance failure with numbers attached.
Reach and audience composition are documented no better than Cooper's — two posts and no engagement data — so reach is no reason to switch.
The distinction is scope: Kumar sells the staffing answer; Cooper sells a way to tell whether the programme is worth staffing.
Choose Yu only if the campaign is reframed around capital rather than operations.
Read more
Yu's posts address investors: management meetings with a fund's chief financial officer and head of investor relations, confidence in 2028 financial objectives, fundraising and deployment trends in private equity and credit, valuation discounts, and the growth of Asia-Pacific and Middle East infrastructure private debt from $12.9bn in 2020 to $24.9bn in 2025, with a forecast of $49.5bn by 2030.
This is the right partner if the consultancy wants to address the finance side of transformation — the people who decide whether a plant, transmission line, or portfolio company gets funded — and argue that governance and delivery risk belong in the investment case.
That is the closest point of contact with Cooper's own vendor-financing post.
Yu writes as an analyst, not an operator, giving readers a view of valuation and funding but nothing to run on a factory floor.
There are no manufacturing examples, governance tests, or tools for a COO or production supervisor.
For a campaign on governance-led transformation for asset-heavy manufacturers, Yu covers the money behind the assets, not how decisions get made inside them.
The partnership would need a finance audience and a narrower campaign concept to justify the switch.
Cooper's eight LinkedIn posts dated January–February 2026 cover operational improvement, supply chains, data trust, transformation and AI governance.
The posts offer examples of Cooper’s ideas during this period, not a complete record of their work or a basis for assessing how their views have changed over time.