Search creators⌘K
  1. Home
  2. Creators
  3. Frederic Brouillet

Frederic Brouillet

Frederic Brouillet applies Lean and continuous-improvement ideas to digital work, especially in Microsoft 365. Brouillet's work presents the Digital Lean Operating System as a way to make work visible, improve flow, and build improvement into everyday tools, with AI supporting people’s thinking.

4.4K followersContinuous improvementBased on 11 posts · latest Oct 2026
LinkedIn

At a glance

Useful for explaining Digital Lean and continuous improvement in Microsoft 365 through frameworks and everyday examples.

Best for

A Microsoft 365 consulting webinar or content collaboration on Digital Lean and AI.

Not for

Consumer lifestyle campaigns seeking broad reach, demographics, product demos, or paid post rates.

Key takeaways

  • Most organisations already run an operating system but never designed it.
  • Lean should be an operating model inside Microsoft 365, not a toolkit bolted on top.
  • Digital work has its own forms of waste, and the gemba has moved to Microsoft 365.

Check first: Confirm audience data, engagement or webinar results, and partnership formats or contact route.

Main ideas
Most organisations already run an operating system — they just never designed it · Lean should be an operating model inside Microsoft 365, not a toolkit bolted on top · Digital work has its own forms of waste, and the gemba has moved to Microsoft 365
Audience
4,383 LinkedIn followers
Read first
The Digital Lean Operating System™ in One Picture
Sources for this section

What they are known for

Frederic Brouillet writes about applying Lean and continuous improvement to digital work, especially in Microsoft 365.

  • They introduce the Digital Lean Operating System and argue that organisations should design how work moves through tools such as Teams, Planner and SharePoint, rather than layering more initiatives onto an accidental setup.
  • They connect that framework to Frontier Lean and also discuss LearningFrontier, an approach to helping people apply ideas through questions, scenarios and AI-supported interaction.

Brouillet makes abstract Lean ideas recognizable in everyday digital work.

  • They map familiar problems—searching for the latest file, losing decisions in Teams threads or waiting for reports—to Lean concepts, then use examples such as the layers of digital waste in Teams to show how those problems accumulate.
  • The seven-layer Digital Lean Operating System gives readers a way to connect priorities, people, visibility, workflow, improvement, AI and Microsoft 365 tools.
  • This combination of concrete workplace symptoms and a system-level framework is useful for readers exploring digital operations or continuous improvement.
  • One strand of their work, LearningFrontier, focuses instead on the gap between reading an idea and applying it when real situations are messy.
Sources for this section

Ideas and priorities

Frederic Brouillet’s recurring argument is that Lean and continuous improvement still work, but are usually applied on top of a digital workplace nobody designed.

Read more

In his account, Teams, SharePoint, Planner and Outlook already form an operating system — an accidental one.

  • The fix is to design it deliberately, layer by layer, so direction, flow, problem-surfacing and improvement live inside everyday work rather than in parallel programmes.
  • He translates classical Lean waste categories into digital terms, offers concrete ways to spot that waste and treats AI as a layer that extends how people think rather than replacing their judgement.
  • A related thread concerns learning: reading about improvement does not change behaviour, so he is interested in formats that let people test ideas against their own messy situations.

Most organisations already run an operating system — they just never designed it

This is the foundation of many of the other arguments.

Read more

Brouillet says an organisation’s real operating system is not written down or approved; it is the sum of what people do in Outlook, how Teams channels multiply, where documents actually live in SharePoint, how work moves or stalls in Planner, which dashboards anyone looks at and the workarounds in between.

  • That helps explain why Lean efforts struggle: Lean is typically layered onto an environment it did not shape, so organisations add initiatives, templates, dashboards and training waves while leaving the digital workplace untouched.
  • Brouillet compares it to improving flow in a factory without redesigning the layout.
  • His closing question: is a company improving inside its operating system, or ready to design it?

The post lists the everyday artefacts that make up the accidental system — Outlook habits, multiplying Teams channels, where documents actually live in SharePoint, Planner workflows and the dashboards people actually open — then contrasts them with a deliberately designed digital workplace where direction is visible in daily tools and problems surface naturally.

The same logic is formalised in the seven-layer Digital Lean Operating System, where each layer names something to design rather than inherit.

Read original

Lean should be an operating model inside Microsoft 365, not a toolkit bolted on top

Brouillet’s provocation is that if you cannot draw your operating system, you probably do not have one.

Read more

He offers a seven-layer architecture — direction, people, visualisation, flow, improvement, intelligence (AI) and platform — as an operating model for the AI-powered enterprise, not another toolkit.

  • The layers specify how improvement should work: strategic priorities visible in Teams and Planner; live metrics and real-time problem signals instead of monthly dashboards; flow designed and instrumented rather than reduced to task tracking; and A3s, experiments and PDCA loops embedded in the flow of work instead of managed from the sidelines.
  • AI is one layer among seven, extending how people think and decide rather than replacing them.
  • Microsoft 365 is the digital factory floor.

The post sets out the seven layers in a numbered structure and names the tools behind the platform layer — Teams, Loop, Planner, Power BI and Power Automate. Individually, these tools are familiar; together, they form a coherent system in which Lean stops being a programme and becomes how the organisation runs.

Read original

Digital work has its own forms of waste, and the gemba has moved to Microsoft 365

Brouillet maps muda, mura and muri onto everyday digital friction, arguing that these wastes do not crash machines but erode focus, drain time and make improvement harder.

Read more

His response to the usual remedy — more templates, dashboards and rules — is that what is missing is a system designed for how work happens in Microsoft 365. The argument’s central line: Lean did not stop being relevant; the gemba just moved.

He names five wastes: search waste (motion), from hunting for the latest version across email, chat and folders; version chaos (inconsistency), when five files, three drafts and two files called final coexist; notification overload (overburden), from scattered pings, mentions and inbox noise; conversation drift (defects), when decisions get lost in long Teams threads instead of driving action; and insight latency (waiting), when teams stall for reports or for someone to pull the data.

Read original

Look at what has accumulated before asking where the waste is

Rather than start with a process diagram, Brouillet proposes reading the digital workplace as an archaeologist reads sediment: what is visible at each depth reveals what the organisation has normalised.

Read more

He identifies decisions made multiple times, conversations that never really closed, work that moved but never flowed, and knowledge that existed but was never reused.

  • These are not signs of chaos but the slow accumulation of handoffs, rework, unclear ownership and invisible waiting.
  • The useful question, he argues, is not where the waste is but what layers have been normalised — a diagnostic shift, not a tooling recommendation.

He asks readers to open Microsoft Teams and picture four layers: this week’s active chats and decisions in motion; last month’s half-finished conversations and unanswered requests for an update; last quarter’s channels that used to matter but now sit silent and pinned; and files of unknown age, duplicated, differently versioned and identically named.

Read original

Reading about improvement does not change behaviour — application does

Brouillet describes reading widely on Lean, leadership and continuous improvement, then reaching the point of asking, “What now?”

Read more

When ideas meet a real team, the situation may not match the example, the team may push back and the right answer may no longer be obvious.

  • The book stays silent: no feedback, coaching or way to test thinking in the moment, leaving knowledge theoretical.
  • His proposed response is to work with ideas, not just read them: ask questions in context, challenge ideas, explore real scenarios and talk on demand with an AI avatar of an author.

He names books that shaped how he thinks about improvement, including Better Thinking, Better Results, Leading Excellence and The Lean Tech Manifesto. He highlights and rereads them, and recommends them to others, but applying their ideas to a specific team, its pushback and an example that does not fit can still leave readers without guidance.

This post promotes a named product concept rather than a framework. Ask about delivery, availability and commercial terms before considering it.

Read original

Sources for this section

Start with their work

The Digital Lean Operating System™ in One Picture

What does Brouillet mean by Digital Lean, and is it a framework or a slogan?

Read more

This is their clearest single statement of the model and the best place to start.

Brouillet names the Digital Lean Operating System (DLOS) and describes it as an operating model for the AI-powered enterprise, not another toolkit.

  • The post lists seven layers: Direction, where strategic priorities become visible in Teams and Planner; People, covering skills, coaching, and digital and AI literacy; Visualisation, with live metrics and real-time problem signals instead of monthly dashboards; Flow, designed and instrumented rather than reduced to task tracking; Improvement, with A3s, experiments, and PDCA loops run inside the flow; Intelligence, where Copilot, summaries, nudges, and detection extend how people think and decide; and Platform, meaning Microsoft 365 tools such as Teams, Loop, Planner, Power BI, and Power Automate.
  • Their provocation: if you cannot draw your operating system, you probably do not have one.
  • They present this framework as the foundation of Frontier Lean, which they say was built for teams navigating AI, Copilot, and digital transformation inside Microsoft 365.

For brands planning a campaign

The seven layers give a webinar or article a ready-made agenda: one segment per layer, each supported by a client example. The “draw your operating system” challenge gives firms an interactive exercise to run live, while the layer names work as slide titles or a diagnostic checklist.

Most companies already have an operating system. They just didn’t design it

This explains why Brouillet thinks ordinary Lean programmes stall—the problem the framework is designed to solve.

Read more

Read it for the diagnosis without the layer list.

Brouillet argues that most organisations run on an “accidental operating system”: the sum of what people do in Outlook, how Teams channels multiply, where documents really live in SharePoint, how work flows or stalls in Planner, which dashboards people actually look at, and the workarounds and personal habits in between.

  • It was never designed or approved, yet it runs the company every day.
  • They say Lean efforts struggle because Lean is often layered onto an environment it did not shape.
  • Organisations add initiatives, templates, dashboards, and training waves while leaving the digital workplace untouched.
  • They compare this to improving flow in a factory without redesigning the layout.
  • The post asks whether an organisation is improving inside its operating system or is ready to design it.

For brands planning a campaign

This makes strong opening material for a thought leadership piece because it gives the audience something to disagree with. A firm can ask prospects which named Microsoft 365 surfaces are accidental in their organisation, turning the post’s closing question into a live poll or discovery-call prompt.

Five types of Digital Waste inside Microsoft 365

It shows how Brouillet translates classical Lean vocabulary into everyday digital work.

Read more

Read it to see whether their ideas hold up outside a factory.

Brouillet maps the three Lean wastes—muda, mura, and muri—onto Microsoft 365.

  • Search Waste (muda, motion) is hunting across email, chat, and folders for the latest version.
  • Version Chaos (mura, inconsistency) is five files, three drafts, and two “finals,” with no one knowing which is real.
  • Notification Overload (muri, overburden) is cognitive fatigue from scattered pings, mentions, and inbox noise.
  • Conversation Drift (muda, defects) is decisions lost in long Teams threads instead of driving action.
  • Insight Latency (muda, waiting) is teams stalled while waiting for reports or someone to pull the data.
  • They note that these problems do not crash machines; they erode focus and drain time.
  • Organisations usually respond with more templates, dashboards, and rules, when what they need is a system designed around how work actually happens.
  • Their line: the gemba just moved to Microsoft 365.

For brands planning a campaign

The five wastes work as diagnostic categories firms can use in a client or audience audit checklist.

  • Each points to a concrete pain point that a Microsoft 365 consulting offer can address.
  • The post also shows how Brouillet speaks to a non-manufacturing audience while retaining Lean’s vocabulary.

Digital Waste Archaeology

This is the clearest, most memorable demonstration of what Brouillet means by digital waste.

Read more

Read it for a piece that makes the abstract argument land in about a minute.

Brouillet asks readers to open Microsoft Teams like an archaeologist and describes four layers of what accumulates there.

  • This Week holds active chats, urgent threads, and decisions in motion.
  • Last Month holds half-finished conversations and “Any update?” messages that got no reply.
  • Last Quarter holds channels that used to matter, now silent but still pinned.
  • Unknown Age holds duplicate files and different versions with the same name.
  • They name the patterns: decisions made multiple times, conversations that never really closed, work that moved but never flowed, and knowledge that existed but was never reused.
  • They call it sediment rather than chaos: the slow accumulation of handoffs, rework, unclear ownership, and invisible waiting.
  • They reframe the useful question from “Where is the waste?” to “What layers have we normalised?”

For brands planning a campaign

The four layers describe what any firm can see in its own Teams, making this a natural workshop or lead-magnet exercise. It also suits skeptical audiences who find operating-model language abstract, giving a content collaboration an inspectable, low-jargon hook.

Reading doesn’t change behavior. Application does

It explains what Brouillet is building beyond the framework and why they think the usual route from book to practice fails.

Read more

Read it to understand their commercial and product direction.

Brouillet describes reading widely on Lean, leadership, and continuous improvement, naming Better Thinking, Better Results, Leading Excellence, The Lean Tech Manifesto, Blockchain for Lean Systems, and Lean Management Beyond Manufacturing, yet still hitting a “Now what?” moment when applying the ideas.

  • They describe the gap specifically: the team pushes back, the situation does not match the example, the right answer is not obvious, and the book offers no feedback, coaching, or way to test your thinking in the moment.
  • They present LearningFrontier as work they have been involved in, built around asking questions in context, challenging ideas, exploring real scenarios, and talking on demand with an AI avatar of an author.
  • Their summary of the shift: from reading ideas to working with them.

For brands planning a campaign

This reveals the AI and interactive-learning side of Brouillet’s work, offering a different webinar angle from the operating-system material that may appeal to learning and development buyers. Discuss LearningFrontier explicitly with Brouillet in any collaboration: it is a named venture, not the general Digital Lean message.

Sources for this section

Topics and approach

Digital Lean Operating System: a seven-layer architecture for Microsoft 365

The central framework in this material.

Read more

Frederic Brouillet presents the Digital Lean Operating System as an operating model, not a new toolkit.

  • It comprises seven layers: direction, people, visualisation, flow, improvement, intelligence (AI) and platform.
  • Strategic priorities should be visible in everyday tools such as Teams and Planner, metrics should be live rather than monthly, and improvement loops such as A3s and PDCA should be embedded in the flow of work instead of managed from the sidelines.
  • AI is one layer, extending how people think and decide rather than replacing them; Microsoft 365 is described as the digital factory floor.

The model appears in a single image and numbered list, then is contrasted with the common habit of naming Lean tools without describing the system they are meant to run on.

For brands planning a campaign

A webinar could guide attendees through the seven layers, ending with the post’s question: which layer would be weakest if they sketched their current system? That gives a consulting audience a structured diagnostic to take away, rather than a tour of Microsoft 365 features.

Examples: Source 1

Digital waste inside Microsoft 365, mapped to Lean concepts

Brouillet names five kinds of digital waste and ties each to a core Lean idea: search waste (motion) from hunting for the latest version across email, chat and folders; version chaos (inconsistency), where several drafts and two "final" files coexist; notification overload (overburden) from scattered pings and mentions; conversation drift (defects), where decisions are lost in long Teams threads; and insight latency (waiting), when teams stall for reports or someone to pull the data.

Read more

These wastes do not crash machines but erode focus, the argument goes. Organisations usually respond with more templates, dashboards and rules, when what is missing is a designed system.

Naming each waste type, pairing it with a familiar Lean label and adding a workplace example makes abstract digital friction inspectable.

For brands planning a campaign

The five named wastes offer a shared vocabulary for a session or article. A brand can ask the audience to score each one, producing a concrete, self-diagnosed problem statement that the presenter can respond to live.

Examples: Source 1

The accidental versus designed operating system

Every company already has an operating system, but most never designed it, argues Brouillet.

Read more

It is the sum of what people do in Outlook, how Teams channels multiply, where documents actually live in SharePoint, how work moves or stalls in Planner, which dashboards people look at and the workarounds in between.

  • In this account, Lean efforts struggle because Lean is layered onto an environment it did not shape — like improving flow in a factory without redesigning the layout.
  • A Digital Lean Operating System deliberately designs the digital workplace so direction is visible, flow is designed, problems surface naturally and improvement lives in the work.

The post moves from familiar everyday artefacts (Outlook, Teams, SharePoint, Planner) to a single reframing question, keeping the argument concrete while making a larger organisational point.

For brands planning a campaign

This is a strong opening frame for a thought leadership session: the question "designed or accidental?" invites self-assessment before any recommendation and positions the work as operating-model design rather than tooling.

Examples: Source 1

Digital waste archaeology: reading Teams as sediment

Another diagnostic angle in the same body of work.

Read more

Brouillet asks readers to open Microsoft Teams like an archaeologist and describes layers: this week's active chats and decisions in motion; last month's half-finished conversations and unanswered "any update?" messages; last quarter's channels that now sit silent but pinned; and files of unknown age in duplicate, differently versioned, identically named.

  • The patterns behind them are decisions made multiple times, conversations that never closed, work that moved but never flowed, and knowledge that existed but was never reused.
  • The closing question shifts from "where is the waste?" to "what layers have we normalised?"

A physical metaphor — sediment and archaeology — makes slow accumulation visible without requiring Lean training.

For brands planning a campaign

This is a ready-made workshop exercise: have attendees excavate one channel or workspace and report what they find. It pairs naturally with the seven-layer framework and gives a live audience something to produce, not just absorb.

Examples: Source 1

From reading to application, and conversations with an author's AI avatar

Brouillet describes the gap between knowing and doing: books such as "Better Thinking, Better Results," "Leading Excellence," "The Lean Tech Manifesto" and "Lean Management Beyond Manufacturing" shaped how they think about improvement.

Read more

But when ideas meet a real team, pushback and messy situations leave the book silent — no feedback, no coaching, no way to test thinking in the moment.

  • The response is LearningFrontier, where readers can ask questions in context, challenge ideas, explore scenarios and talk on demand with the AI avatar of the author.
  • The shift is from reading ideas to working with them.

The post draws on personal reading experience and specific titles before introducing the tool, so the product appears as an answer to a stated problem.

This is the only item promoting a product concept rather than a framework. Before considering a collaboration, ask about delivery, availability and commercial terms.

For brands planning a campaign

For a content collaboration, the angle is applied learning rather than book summaries: a session or series where the audience brings live improvement problems and tests ideas against them. It also signals interest in formats beyond static content.

Examples: Source 1

Sources for this section

Brands and businesses

Brouillet's posts name few outside businesses.

Read more

Microsoft 365 is the environment Brouillet's Digital Lean work targets — Brouillet describes teams, Planner, Power BI, Power Automate and Loop as the "digital factory floor" — but no sponsorship, client, employment or other commercial relationship with Microsoft is disclosed. Brouillet presents Frontier Lean as Brouillet's own book and framework, and Brouillet sends readers to LearningFrontier as work "we've been working on," without saying whether Brouillet owns, works for or advises that company.

Microsoft 365

Mention

Microsoft 365 tools — Teams, Outlook, SharePoint, Planner, Power BI, Power Automate and Loop — form the setting for Brouillet’s Digital Lean Operating System, which they describe as embedding Lean “directly inside Microsoft 365, where work actually happens.”

Read more

They name the platform as the seventh layer of their seven-layer model and the place digital waste accumulates. Ask whether they have a sponsorship, partnership, client or employment relationship with Microsoft.

View example

Frontier Lean

Owned business

Brouillet presents Frontier Lean — subtitled “The AI-Augmented Lean Enterprise in Microsoft 365” — as their own work, stating “in Frontier Lean, I developed the Digital Lean Operating System” and “that's what I built in Frontier Lean.”

Read more

They direct readers to the book and its interactive experience. Ask about any company, service offering or licensing arrangement tied to the title.

View example

LearningFrontier

Disclosed partnership

Brouillet points readers to LearningFrontier to work with improvement ideas, describing question-and-answer sessions and an AI avatar of an author.

Read more

They call it “the gap we've been working on,” indicating their involvement. Ask whether they own, work for or advise the company.

View example

Sources for this section

Topics and similar creators

Frederic Brouillet writes about what happens when Lean thinking meets the tools people actually work in.

Read more

Start with the Digital Lean Operating System material: a seven-layer model that puts direction, flow, problem-surfacing and improvement inside Microsoft 365 rather than in a parallel programme.

  • Posts on digital waste and on reading Teams as accumulated layers show how the same argument applies: most organisations run an accidental operating system that nobody designed, and the useful question shifts from where the waste is to what has been normalised.
  • If applied learning interests you more than operating models, the post on why reading about improvement does not change behaviour takes a different angle, arguing that ideas need to be tested against a reader's own messy situation.
  • The tags below group the work by subject, setting and format, so you can follow whichever thread matters to you.
  • Similar creators were selected because their published work meets Brouillet's at a specific point: each applies improvement thinking to a particular software ecosystem or to AI, and each differs in setting, method or audience.
Lean management Continuous improvement Digital workplace Operating model design Microsoft 365 Microsoft Teams AI-augmented work LinkedIn posts Operations and continuous improvement leaders

Prasad Velaga, PhD

Velaga works the same seam as Brouillet: both take Lean as a starting point and then argue about where it falls short in practice.

Read more

Velaga's posts on waste-reduction efforts in production systems and on how Lean is taught critique practitioners who pursue every visible opportunity without assessing the benefit first. That is close to Brouillet's complaint that organisations add more initiatives, templates and dashboards without redesigning the environment they sit on.

Velaga stays in manufacturing, offering an analytic rather than architectural answer: a production model and scheduling software that predict work progress, WIP and bottlenecks so improvement opportunities can be assessed in advance. Brouillet works in the digital workplace, with a designed operating model layered through Microsoft 365.

Read original · Original 2

Misty Murray

Murray is the closest match on setting.

Read more

Like Brouillet, they argue that organisations usually use the Microsoft 365 tools they already pay for without a strategy. They work through Planner, Excel, SharePoint and Copilot to make work visible, spot bottlenecks and standardise improvement — the same move Brouillet makes by placing improvement loops inside the flow of work rather than beside it.

Murray's audience and examples are specifically legal: contingency-fee cases, matter management, post-case evaluation and intake criteria for law firms. Brouillet writes for a general operational audience, framing the work through a seven-layer operating model rather than a series of how-to tips within one profession.

Read original · Original 2

Paul D'Souza

D'Souza and Brouillet both refuse to treat AI as a layer simply added on top of existing work.

Read more

D'Souza's argument that automating a broken process only produces faster waste matches Brouillet's position that Lean is often layered onto an environment it did not shape. Both see improvement discipline as the precondition for AI doing anything useful.

D'Souza's mechanism is Lean Six Sigma paired with agentic AI and a digital twin used as a simulation sandbox for enterprise process work.

  • Brouillet keeps AI as one of seven layers inside a Microsoft 365 operating model and stresses that it should extend how people think rather than replace their judgement.
  • D'Souza also writes about business owners' lives and exit planning, a subject Brouillet does not touch.

Read original · Original 2

Sources for this section

Audience

Frederic Brouillet's measurable audience footprint is a LinkedIn following of about 4,400 people, seen on 11 October 2026.

Read more

Posts published between 9 February and 31 March 2026 offer Lean and continuous-improvement thinking applied to Microsoft 365, Digital Lean Operating Systems, digital waste, and AI-augmented improvement.

  • Those topics align well with a Microsoft 365 consulting firm's webinar, making topical relevance the strongest audience signal.
  • The posts provide no information about followers' geography, age, gender, employer type, occupation, or seniority, and publish no engagement totals or webinar or registration results.
  • Ask Brouillet for recent results from comparable activity, such as registrations or attendance for a similar webinar or reach and engagement figures for posts on Digital Lean and AI in Microsoft 365, and for any audience survey covering relevant professional attributes such as job function, seniority, and company size.

LinkedIn followers

4,383

LinkedIn profile follower count · 2026-10-11

Sources for this section

Partnership options

Frederic Brouillet's five LinkedIn posts from February–March 2026 discuss Lean and continuous improvement in Microsoft 365, the Digital Lean Operating System, digital waste, and AI-supported learning.

Read more

None sets out sponsorship formats, rates, audience specifications, editorial terms, or a contact route for commercial collaborations.

  • Two posts link to first-party project pages for the Frontier Lean book and the LearningFrontier product, their own work rather than a media kit or partnership inquiry page.
  • Brands considering a webinar or content collaboration should contact them to establish scope, format, deliverables, operational requirements, and terms.
Sources for this section

Campaign fit

A campaign to shortlist

Strong topic fit; check audience fit before proceeding.

Read more

Brief

A Microsoft 365 consulting firm wants a thought-leadership webinar on Digital Lean and AI-supported continuous improvement, followed by a content collaboration.

Reasons

  • Brouillet’s posts explain a distinctive framework, the seven-layer Digital Lean Operating System, and connect it to familiar Microsoft 365 tools, including Teams, Planner, Power BI and Power Automate.
  • Frederic Brouillet makes digital-work problems concrete. Their posts give five examples: searching across folders for the latest file, competing “final” versions, notification overload, decisions lost in Teams threads and delays while waiting for reports.
  • The material lends itself to a useful webinar exercise: ask attendees to identify the weakest of the seven layers in their organisation, then connect that diagnosis to examples from their own work.
  • Frederic Brouillet's posts show a LinkedIn following of about 4,400 but do not specify follower roles, seniority, company size, engagement or webinar results. Before relying on reach, request audience and performance data relevant to the brief.
  • The posts do not specify available partnership formats or how to inquire. Discuss scope, deliverables and terms directly with Brouillet.

When to choose a specialist

Poor fit based on what Frederic Brouillet's posts say.

Read more

Brief

A consumer brand wants a broad-reach lifestyle campaign with a guaranteed volume of product demonstrations, audience demographics and paid-post rates ready to book.

Reasons

  • Their posts focus on Lean, organisational improvement and Microsoft 365 work practices, not consumer lifestyle products.
  • The posts do not establish a consumer audience, audience demographics, campaign reach or conversion results.
  • The posts also do not document sponsorship formats, rates, deliverables or a booking route. The brand cannot assess the requested reach or book a defined package from this evidence.
  • This is an evidence-based mismatch for this brief, not proof that Brouillet would refuse the work.
A worked campaign example
Campaign angle

“Where is digital work getting buried?” A practical webinar that starts with Brouillet’s digital-waste archaeology idea, then uses the seven-layer Digital Lean Operating System to discuss what organisations might change.

Sample run of show

Open with the contrast between a designed operating system and an accidental one: everyday habits around Outlook, Teams, SharePoint, Planner and dashboards can shape how work runs, even when no one designed them.

Run a five-minute diagnostic: attendees identify one example of search waste, version confusion, notification overload, a decision lost in a Teams thread or waiting for information.

Use the seven layers—Direction, People, Visualisation, Flow, Improvement, Intelligence and Platform—to discuss where the example sits and what the organisation should investigate next.

Close by asking attendees which layer seems weakest in their own system, and invite them to bring one concrete workflow to a follow-up discussion.

Why this works

The angle combines two approaches demonstrated in Frederic Brouillet's posts: naming specific Microsoft 365 friction and using a structured operating-model framework. It gives attendees a recognisable problem and a guided way to discuss it, rather than a product-feature tour. Before confirming the collaboration, agree the format and responsibilities directly with Brouillet and request audience information relevant to the firm's target attendees.

Sources for this section

Who else to consider

Prasad Velaga, PhD

Choose Prasad Velaga for a webinar or content collaboration aimed at manufacturers and job shops comparing improvement opportunities before committing resources.

Read more

The posts argue that Lean practitioners often pursue every visible waste-reduction idea without reliable what-if analysis, and propose production scheduling software and discrete-event simulation to predict throughput, work-in-progress and lead-time effects.

  • Another post focuses on true high-mix, low-volume job-shop production and scientific scheduling.
  • For a campaign assessing the value of manufacturing improvements or scheduling complex job shops, this alternative is closer to the audience than Brouillet’s Microsoft 365 digital-workplace material.

The tradeoff is a narrow manufacturing-scheduling lens.

  • The posts do not cover Microsoft 365 tools, digital workplace design or AI-augmented continuous improvement inside Teams, Planner or Power BI.
  • A Microsoft 365 consulting firm would miss the Digital Lean Operating System and workplace examples that make the material directly usable for an M365 audience.

Examples: Source 1 · Source 2

Misty Murray

Choose Misty Murray for a webinar or collaboration aimed at legal professionals and law firms that want to use Microsoft 365 more deliberately.

Read more

The posts present a Copilot blog series for legal operations, covering Planner, SharePoint, OneNote, Lists and Excel to give visibility into how a legal team works, insight into contingency-case profitability and a roadmap for growth.

  • Another post describes post-case evaluations with Copilot and Planner, including spotting workflow bottlenecks and refining intake criteria.
  • For a campaign about legaltech, case management or Copilot for law firms, this alternative matches the vertical more closely.

The tradeoff is a legal-sector focus rather than a general enterprise Lean or Microsoft 365 thought-leadership frame.

  • The posts do not develop a Digital Lean Operating System, manufacturing-style waste analysis or a broad AI-augmented continuous-improvement method.
  • A firm seeking a cross-industry Digital Lean webinar would get a narrower legal operations angle.

Examples: Source 1 · Source 2

Paul D'Souza

Choose Paul D'Souza when the campaign is specifically about grounding Agentic AI in Lean Six Sigma and testing it in a digital-twin simulation.

Read more

The post argues that enterprise AI projects fail when they automate broken processes, and proposes mapping value-add versus non-value-add work, using a digital twin as a safe sandbox and turning DMAIC into a continuous loop.

  • That makes it a close match for a webinar on Lean Six Sigma and autonomous agents in operational excellence.
  • The second post covers a different topic: SMB owner coaching, exit planning and personal wisdom.
  • For a campaign aimed at small-business owners considering life design, that post is relevant.

The tradeoff is a mixed body of work that is less specific to Microsoft 365.

  • The reviewed agentic-AI post names Lean Six Sigma, digital twin and DMAIC but does not centre on Microsoft Teams, Planner, Power BI or Power Automate as the delivery platform.
  • The SMB coaching post sits outside operational excellence, so a buyer seeking one consistent Digital Lean and Microsoft 365 narrative would need to select carefully or accept a broader, less focused frame.

Examples: Source 1 · Source 2

Sources for this section

Build your campaign brief

Editable Markdown templates for planning a campaign with this creator.

Worked example: Digital Lean webinar and follow-up content

Sources for this section

Research methodology

  • This profile draws on the full text of five LinkedIn posts about digital waste, the Digital Lean Operating System, and applying Lean ideas in everyday work.
  • The posts describe Frontier Lean and LearningFrontier from Brouillet’s perspective; this summary does not independently assess either project.

Brands they talk about