Maureen O'Donnell

Credibility comes from human specificity, not the product list. They say the technology differs by industry, but the storytelling problem stays the same.

A retrospective on Microsoft customer stories lists accounts across healthcare, fintech, manufacturing, energy, media, government and consumer brands, then makes the point directly: the best case studies "aren't really about the product list," and that human specificity is what makes an enterprise story credible and engaging.

Read original · Original 2

This framing moves beyond before-and-after results to show leaders what they can act on.

The post introducing an Enterprise Case Study Playbook opens with this pattern, then explains how O'Donnell handles narrative structure, stakeholder alignment and credibility in regulated and complex industries.

Years of case study work led to this conclusion: shift from reporting outcomes to depicting change.

Read original

On a project, that means establishing what changed and why it mattered, and what an organization believes, resists and wants decision-makers to understand before drafting. The discovery phase centers on questions for stakeholders and customers, not polishing existing copy.

The method statement ends with the line that the work that meant the most always started “with the right questions, not the right sentences.”

O'Donnell began their career as an editor, then moved into writing to become the thinker and interpreter connecting people with ideas. That early role change helps explain their question-first approach.

Read original

They describe translating mandates into material non-specialist decision-makers can act on, making compliance-heavy content a core specialty rather than an exception to general marketing work.

Recent projects include a 2025 CMMC 2.0 readiness framework that turned federal cybersecurity mandates into a practical roadmap for defense contractors, and structured case studies from technical customer interviews with global banks modernizing core systems with generative AI.

Read original · Original 2

It is aimed at teams building case study pipelines or supporting complex sales conversations. As a concrete artifact, the method can be examined and compared with an existing process, rather than judged only from finished drafts.

The playbook post invites conversations about narrative strategy and says the guide outlines how O'Donnell approaches structure, alignment and credibility. The post describes the playbook but does not publish its contents.

Read original

They describe collaboration—thoughtful stakeholders, honest conversations and a shared commitment to getting the story right—as the common thread across projects. The posts suggest project-based engagements begin with a scoping conversation, rather than a standing retainer.

A recent-projects post thanks the people who brought O'Donnell into complex projects and says they are available for focused work. They add that past collaborators are not taken for granted.

Read original · Original 2 · Original 3

Start here if you open only one piece.

O'Donnell lists the industries covered by Microsoft customer stories they say they have written: healthcare (Baptist Health, First Nations Health Authority), financial services and fintech (Banco Bradesco, Temenos), manufacturing and industrial (Hexion, Rolls-Royce), energy and sustainability (Hilo, Hydro-Québec), media and creative production (Jellyfish Pictures), professional services and government (KPMG, Washington DC CFSA), and consumer brands (Carlsberg, Sensei).

• The argument is about method, not the client list: the technology changes each time, but the storytelling problem stays the same.
• They follow the human and business impact, keep the technology in a supporting role, show the customer's challenges and initiative alongside the result, and use human specificity to make an enterprise story credible.
• The closing point: 'the best case studies aren't really about the product list.'

For brands planning a campaign

For an enterprise software company building a customer-story pipeline, this shows range across regulated, technical, and creative-industry accounts. It also sets expectations: stories focus on customer change and initiative rather than feature walkthroughs, so a campaign should include real customer access, not just product documentation.

O'Donnell describes starting as an editor and becoming a writer because they wanted to be the thinker and interpreter who connects people with ideas, not just a producer of polished prose.

• Their aim is to figure out what is true about something and help someone else see it.
• On a project, they work out what changed and why it mattered, and what an organization believes, resists, and wants decision-makers to understand, before thinking about wording.
• The domains named are cybersecurity, fintech, AI, SaaS, and regulated environments, where getting the narrative wrong has real stakes.
• The line that captures the method is that the work which mattered most began 'with the right questions, not the right sentences.'

For brands planning a campaign

This is a narrative-strategy profile, not just a drafting service. Companies commissioning case studies should expect an early phase of interviews and narrative definition with subject-matter experts and executives, and budget stakeholder time for it.

It also names the collaboration model plainly.

O'Donnell describes three kinds of recent engagement.

• First, turning technical customer interviews into structured enterprise case studies, including global banks using generative AI to modernize core systems.
• Second, developing executive guides in regulated environments, including a 2025 CMMC 2.0 readiness framework that translates federal cybersecurity mandates into a practical roadmap for defense contractors.
• Third, supporting pitch decks and content strategy so leaders can articulate a grounded, defensible point of view.
• Product managers, agency producers, marketers, and founders bring them into complex projects where clarity matters.
• The common thread, they say, is collaboration: thoughtful stakeholders, honest conversations, and a shared commitment to getting the story right.
• The post also states they are available for focused projects.

For brands planning a campaign

Two things to note when scoping work.

• The commercial model is project-based rather than retainer-style, so plan around discrete deliverables.
• The regulated-content example is a useful test case: if your buyers face compliance pressure, it shows how O'Donnell can turn a mandate into a document a non-specialist decision-maker can act on.

Request it first to assess method, then review samples.

After writing enterprise case studies across healthcare, fintech, manufacturing, and cloud, O'Donnell says the most effective customer stories do more than report outcomes: they help leaders see what change actually looks like.

• The playbook covers their approach to narrative structure, stakeholder alignment, and credibility in regulated and complex industries, for people building enterprise case study pipelines or supporting complex sales conversations.
• The post describes the playbook and invites conversation; ask to see its contents.

For brands planning a campaign

A playbook on structure, stakeholder alignment, and credibility is a low-risk way to test fit before commissioning a full case study.

• Its sections map directly onto the stages of a customer-story program.
• Ask to see the playbook and how it would be adapted to your industries, then compare its structure with your existing templates before committing to a build.

They describe writing Microsoft customer stories across healthcare (Baptist Health, First Nations Health Authority), financial services and fintech (Banco Bradesco, Temenos), manufacturing and industrial (Hexion, Rolls-Royce), energy and sustainability (Hilo / Hydro-Québec), media and creative production (Jellyfish Pictures), professional services and government (KPMG, Washington DC CFSA), and consumer brands (Carlsberg, Sensei luxury spa).

• Across those industries, the stated approach is consistent: follow the human and business impact, show the customer's challenge and their own initiative alongside the outcome, and keep the technology in a supporting role rather than leading with a product list.
• They argue that human specificity makes an enterprise story credible and that the best case studies are not really about the product list.

Lead with what changed for the customer and why it mattered, then show the technology as the supporting mechanism. Human detail and customer agency build credibility; product features take a supporting role.

For brands planning a campaign

For a B2B enterprise software company rebuilding its customer-story pipeline, this is a directly relevant capability: a writer who has repeatedly turned technical implementations into outcome-led narratives and interviewed customers to surface the human specifics that make a story defensible. Use the industry list to shape a sample request, not as proof of fit for your sector.

Examples: Source 1 · Source 2 · Source 3

Recent projects they name include executive guides in regulated environments, including a 2025 CMMC 2.0 readiness framework that translated federal cybersecurity mandates into a practical roadmap for defense contractors; structured enterprise case studies based on technical customer interviews, including stories about global banks using generative AI to modernize core systems; and pitch decks and content strategy to help leaders articulate a grounded, defensible point of view. Their stated background spans cybersecurity, fintech, AI, SaaS, and regulated environments where, in their words, the stakes of getting the narrative wrong are real.

Translates compliance and technical mandates into decision-maker-facing roadmaps and guides, drawing on technical customer interviews before drafting.

For brands planning a campaign

Useful when a customer story has to survive legal, compliance, or security review, or when the target reader is an executive rather than a practitioner. Ask for the CMMC 2.0 framework and an executive guide as work samples to see how regulated constraints are handled in the prose.

Examples: Source 1 · Source 2

They position it for teams building enterprise case study pipelines or supporting complex sales conversations. The playbook documents a repeatable method rather than an approach improvised for each project, giving clients a process artifact to evaluate before engaging.

Documented stages: narrative structure, stakeholder alignment, and credibility checks for regulated and complex industries.

For brands planning a campaign

Request the playbook early.

• For a software company building a repeatable customer-story process, a writer with a documented method is easier to plug into an existing pipeline than one who only delivers finished drafts.
• The playbook gives you a concrete artifact to compare with your current template.

Examples: Source 1

They describe starting a career as an editor and moving into writing to become the thinker and interpreter who connects people with ideas.

• Their aim is to figure out what is true about something and help someone else see it.
• On a project, they work out the story first: what changed and why it mattered, what an organization believes, what it resists, and what it wants decision-makers to understand.
• Understanding those things comes before finding the words; they say the most meaningful work starts with the right questions, not the right sentences.

Stakeholder questioning and theme discovery first; wording last.

For brands planning a campaign

Expect a discovery-heavy engagement built on interviews with executives, product managers, and customers rather than a rewrite of existing marketing copy. This suits a pipeline built from technical interviews and internal documents, but the schedule should allow time to secure access to stakeholders and customers.

Examples: Source 1

Collaboration is the common thread: thoughtful stakeholders, honest conversations, and a shared commitment to getting the story right. The work appears project-based rather than retainer-based, with explicit availability for focused projects and repeated invitations to discuss customer stories, strategic long-form, or executive content.

Small, focused engagements involving product, agency, and marketing stakeholders, opened by a scoping conversation.

For brands planning a campaign

Plan for a defined project with an agreed stakeholder set rather than a standing content retainer. Confirm current availability, scope, and which stakeholders in your organization will be available for interviews before committing to a pipeline calendar.

Examples: Source 1 · Source 2 · Source 3

They describe the stories as tracing the human and business impact of change, with technology in a supporting role. Ask whether the work was contracted directly or through an agency or production partner.

View example

The posts announce Zayo as a founding member of a communications-sector security information sharing centre, describe a board role, and explain in plain terms why trusted information sharing across telecoms providers strengthens the whole sector. Like their CMMC 2.0 framework, the writing translates a technical security obligation into something a business or government reader can act on.

Edwards writes as a security executive inside a network operator, sharing programme news, industry collaboration and hiring calls. The posts offer sector context rather than insight into the craft or method of writing enterprise narratives.

Read original · Original 2

One walks through why a cloud company serving the Department of Defense needs FedRAMP Moderate authorisation rather than CMMC alone; the other frames FedRAMP certification as an eligibility gate rather than a feature advantage. Both writers explain the consequences of dense regulatory requirements for decision-makers.

Mayfield's posts make the case for a service: the FedRAMP thread closes by inviting readers to get in touch, and the compliance post promises help.

• The writing aims to win advisory work, while O'Donnell's posts describe editorial and narrative work and the reasoning behind it.
• Mayfield sells access to federal markets; O'Donnell sells the telling of the story.

Read original · Original 2

One post walks through an LHC windows and doors framework and what a bidder must evidence; another argues that AI-written bids have shifted the value of bid people toward solution architecture and win themes. Corcoran describes those themes as telling the client's story so the buying team believes delivery will happen.

Corcoran works on competitive submissions inside a live procurement, publishing under a service brand with an AI-disruption framing and a free advice offer. O'Donnell works on post-sale customer stories and executive content, focusing on narrative craft rather than procurement outcomes.

Read original · Original 2

Edwards writes about the formation of a communications-sector cyber threat-sharing body, naming the carriers involved and the director role held on its board, and about building compliance and government security leadership inside a large network operator, listing the frameworks that govern the work. A vendor whose reference customers are network operators or regulated infrastructure buyers gets the market’s vocabulary and context without a learning curve.

Sector fluency comes at the expense of demonstrated storytelling craft.

• The two posts cover industry collaboration and a hiring notice; neither shows an interview-to-case-study process, narrative structure, or finished customer story.
• A vendor seeking a customer-story pipeline would get topical authority it may already have internally, rather than the method it lacks.
• Before proceeding, ask for audience data and project availability; the recommendation otherwise rests on subject-matter proximity alone.

Examples: Source 1 · Source 2

Mayfield argues that FedRAMP authorization is an eligibility gate for selling to agencies, authorized vendors screen out competitors before a solicitation is issued, and cloud providers holding authorization or equivalency can win defense supply-chain business while others are locked out. For a vendor whose buyers are defense contractors or agencies, this argument-first, deadline-driven commercial writing is closer to the live sales conversation than a case study—and comes with the compliance detail those buyers test.

The posts are persuasive marketing aimed at software vendors and cloud providers, each closing with a direct commercial call to action.

• They don’t show research and writing a customer’s story with that customer’s participation.
• The subject is compliance eligibility, so a buyer seeking narrative discovery and published case studies would be purchasing a different service.
• Two posts are too thin a sample to judge writing range; ask for more examples.
• The emphasis on certification as a competitive gate is also a positioning argument a vendor would need to agree with before commissioning anything.

Examples: Source 1 · Source 2

Corcoran writes about what makes bids win: building solutions around the buying team’s problems, creating win themes, demonstrating delivery evidence, and treating bid writing as the output of solution architecture rather than the whole job.

• A second post walks through a named windows-and-doors framework for UK construction, facilities-management, and housing suppliers, listing the assurance, traceability, and installer-competence evidence evaluators look for.
• If a vendor’s technical material isn’t yet persuasive and the deadline is a scored tender, this is the closer match.

The method is bid-specific and tied to UK public-sector and framework procurement, so its transferability to an enterprise software vendor’s sales cycle is unproven.

• The deliverable is a scored submission, not a case study a sales lead can put in front of a prospect months later.
• Both posts promote a firm’s services, including through a shared contact address and a stated framework win rate; the win-rate claim is the firm’s own account.

Examples: Source 1 · Source 2