So maybe you've decided that it's now time to expand your SharePoint service to support partnership collaboration.  If so, a common architectural design for this use case is to build out a dedicated SharePoint farm on your company's extranet/DMZ.  While this design aligns to architectural best practices, it often presents a few user experience challenges for your internal knowledge workers.  The SharePoint Governance Kit has been designed specifically for this use case and has been built to govern mutli-farm environments,  Here are some of the benefits it provides in this scenario:

• Intelligent & Centralized Provisioning into Either your Intranet or Extranet SP Farm
  Through the online provisioning wizard, users can be asked several questions during the site request process.  Depending upon their answers, the SharePoint Governance Kit will determine if the site should belong on the intranet or extranet farm.  Users no longer need to burden themselves with understanding the underlying architectural design of the environment and can just fill out the request form when they need to collaborate.
   
• Topical Based Site Directory (across SP Farms)
  Suppose I am a knowledge worker that is on a project team working on "Product ABC".  This project team has several SharePoint sites that support the development of "Product ABC", some of those sites are internal and some of those sites are on the extranet supporting collaboration with vendors doing work on "Product ABC".  We often hear knowledge workers saying "I wish I could simply get a view of all sites related to 'Product ABC' independent of where they are located physically".  Well, the SharePoint Governance Kit meets this need via the management of site metadata and the availability of a mulit-farm site directory.  This site directory allows users to navigate, search and/or facet on any topics/metadata captured about any site across your company's SP ecosystem.
   
• Partner Identity Onboarding
  Every company has a slightly different approach for onboarding a partner/vendor and granting them access to IT services.  Since SharePoint is often used in partner collaboration scenarios, the request for a collaboration site is often done in parrallel with the need to setup partner identies.  Consider the use of the Site Provisioning wizard to help out with this process.  For example, one question that could be asked at the time of the site request could be "Do you need to setup a partner account for use on the collaboration site you are requesting?".  The response to this question could trigger a notification to the identity management group for fullfillment of that request.  Or, some organizations may want to automate this process through additional customization of the wizard that automatically creates accounts in the partner AD instance.  In either case, the provisioning wizard is a great place to capture all of the business user's requests that will support their partnership collaboration.