Add NatWest Group as Known Instance across three patterns

From Pooi Ling Cheong's InnerSource Commons Community Call talk
"Growing InnerSource through OSPO Enablement" (October 2026).

- InnerSource Portal: tag-based self-registration in the existing
  Engineering Portal software catalog, grown to 40+ projects by a
  communications campaign
- Standard Base Documentation: OSPO blueprint embedding the base
  documentation standards, plus a readiness assessment; also adds a
  Resulting Context bullet on cross-project consistency
- Praise Participants: contributor recognition awards at the quarterly
  internal InnerSource meetup

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QLLkUURGbsa8r5Xzq4xNGP

Author: rrrutledge

patterns/2-structured/base-documentation.md

@@ -125,6 +125,7 @@ started right away: [README-template.md](templates/README-template.md),
 * The time for contributors to get up to speed is significantly reduced.
 * Time spent on answering initial questions for [Trusted Committers](trusted-committer.md) is significantly reduced, leaving them more time to work on other tasks.
 * Escalations due to misunderstandings and misalignment are significantly reduced.
+* When many InnerSource projects in an organization follow the same base documentation standard, contributors moving from one project to another find the same information in the same place. Each new project they engage with costs them less to learn, which lowers the barrier to contributing across the organization.
 
 ## Known Instances
 
@@ -134,6 +135,7 @@ started right away: [README-template.md](templates/README-template.md),
 * **Analog Devices Inc.**
 * **Airbus**
 * **Siemens** automatically creates a checklist issue for every new InnerSource project to make maintainers aware of mandatory requirements (e.g. business approval, license & copyright, export control, contributing guidelines, maintainer maturity) as well as best practices (e.g. documentation as code, semantic versioning, continuous integration/deployment).
+* **NatWest Group** - The OSPO's InnerSource playbook includes a blueprint, a checklist for setting up a project for InnerSource with the base documentation standards (README, `CONTRIBUTING.md`, a communication section) embedded in it. The goal is consistency across projects, so contributors find the same information in the same place in every project. The OSPO also offers a readiness assessment against the standard, with must-have and nice-to-have recommendations - for example, rewording a "contact us" section so it invites users to contribute fixes rather than only report problems. See: "Growing InnerSource through OSPO Enablement" (InnerSource Commons Community Call, October 2026, by Pooi Ling Cheong).
 
 ## Authors
 

patterns/2-structured/innersource-portal.md

@@ -109,6 +109,7 @@ It is a good solution for a portal with a few dozen projects, though.
 * **Mercedes-Benz** is [using](https://opensource.mercedes-benz.com/news/sponsor_innersource_commonsoss) the SAP reference implementation mentioned above for their InnerSource Portal.
 * **WellSky** has a simple _Confluence Wiki_ page were InnerSource and reusable projects are listed.
 * **Siemens** has set up an internal portal that provides documentation for InnerSource maintainers, contributors, users and their managers. It also serves as an entry point to explore available projects and gives hints to improve project visibility.
+* **NatWest Group** reuses the software catalog in its existing internal Engineering Portal instead of building a separate portal: projects self-register by adding an InnerSource tag to their catalog config file, and engineers find them by searching on that tag. Registering and tagging is part of NatWest's InnerSource readiness standard. Few projects registered at first; a follow-up communications campaign run with an internal practice team brought the catalog to over 40 discoverable projects. Their InnerSource lead uses the catalog to make the point that a project people can't find effectively doesn't exist. See: "Growing InnerSource through OSPO Enablement" (InnerSource Commons Community Call, October 2026, by Pooi Ling Cheong).
 
 ## References
 

patterns/2-structured/praise-participants.md

@@ -75,6 +75,7 @@ Overdoing it may feel insincere and mechanical and defeat your purpose in reachi
 * **SAP** - InnerSource initiatives like the Dojo and Everest projects are elevated by the 'Praise Participants' pattern, where the SAP Appreciate program plays a key role in fostering a culture of gratitude and recognition, driving innovation and collaboration to new heights. See: [InnerSource: First Contribution Explored](https://community.sap.com/t5/open-source-blogs/innersource-first-contribution-explored/ba-p/13644916)
 * **Siemens** awards successful InnerSource projects and contributors at their yearly internal InnerSource Summit.
 * **Thales Group** - The Thales ISPO explicitly applies this pattern organization-wide, during "Thales I/O Days" event, where top contributors and community advocates across InnerSource and open source receive awards. See: [Why People Matter Most: Building a Sustainable InnerSource Strategy](https://www.youtube.com/watch?v=r0dx84lUDYY) (InnerSource Commons, 2026, by Marius Moulis).
+* **NatWest Group** - The OSPO presents InnerSource Ambassador and Contributor Recognition Awards at its quarterly internal InnerSource meetup, a hybrid event that rotates between UK and India offices. See: "Growing InnerSource through OSPO Enablement" (InnerSource Commons Community Call, October 2026, by Pooi Ling Cheong).
 
 ## Status