Adding files from #652.

Merge branch 'misappi/main'

README.md

@@ -83,6 +83,7 @@ Our mission
 * [Transitioning Contractor Code to InnerSource Model](/patterns/1-initial/transitioning-contractor-code-to-innersource-model.md) - *Contract developers are often not motivated to engage in InnerSource activities, which may be beyond the scope of their contract. This pattern describes how you can focus on transitioning the contractor project after the fact to an InnerSource project by setting expectations for specific InnerSource-related deliverables as part of the overall project delivery.*
 * [Incubator Pipeline](/patterns/1-initial/incubator-pipeline.md) - *A team maintaining a widely shared code library wants to accept contributions from other teams, without lowering the overall quality of their library. Therefore the shared library team uses an incubator pipeline to set a lower bar for contributions to enter and a higher bar to exit and become a top-level unit in the library.*
 * [InnerSource Customer Interview Questions](/patterns/1-initial/innersource-customer-interview-questions.md) - *An organization has decided to create an InnerSource program but are unsure which issues they should address first. Using a customer interview will help evaluate pain points across the organization, to prioritize the areas where InnerSource will have the biggest positive impact.*
+* [Creating an InnerSource Strategy](/patterns/1-initial/creating_an_innersource_strategy.md) - *Sometimes, it is difficult to convince people of the relevance of InnerSource for your organization and/or to get support from management. Creating an InnerSource strategy, that connects your InnerSource approach and activities to the goals and the overall strategy of your organization, can help in this regard.*
 
 <!--
 NOTE: The 'Initial' Patterns below don't have a Patlet yet, which is essential for readers to quickly browse our patterns.

patterns/1-initial/creating_an_innersource_strategy.md

@@ -0,0 +1,75 @@
+## Title
+
+Creating an InnerSource Strategy
+
+## Patlet / Summary
+
+Sometimes, it is difficult to convince people of the relevance of InnerSource for your organization and/or to get support from management. Creating an InnerSource strategy, that connects your InnerSource approach and activities to the goals and the overall strategy of your organization, can help in this regard.
+
+## Problem
+
+- Despite an organization has an InnerSource program, it is challenging to establish InnerSource in that organization
+- Missing management support and low awareness in some or many development teams are among the reasons
+- Potentially, the InnerSource program itself is missing clear goals and/or approaches how to achieve those.
+
+## Context
+
+- InnerSource is not an end in itself. It must deliver clear benefits to your organization and support its goals
+- If InnerSource and its benefits is mainly explained and positioned in a rather abstract way, it might be difficult to convince management and a critical mass of the development teams
+- People see InnerSource as a rather abstract methodology which does not really fit to their situation. They might say/think "InnerSource sounds great, but it is not relevant for our organization"
+- People struggle to make a connection between InnerSource and their goals/the goals of their organisation
+
+## Forces
+
+TODO
+
+<!--
+What makes the problem difficult?
+What are the trade-offs?
+These are constraints that **can be changed** at a cost.
+The solution might change one or more of these forces in order to solve the problem, while also in-turn changing the context.
+-->
+
+## Solutions
+
+Create an InnerSource strategy. Such a document describes how the application of InnerSource relates to the goals and business strategy of your organization. It explains why InnerSource is important (not only in an abstract way but specifically to your organization), why you should leverage it, what goals your organization should have with respect to InnerSource, and what actions to perform to achieve those.
+
+A high level table of contents of an InnerSource strategy document could look like so:
+
+- Executive summary
+- What InnerSource is
+- Why InnerSource is important for our organization
+- Current status of InnerSource in our organization
+- Target state
+- Recommended actions (to reach the target state)
+
+Such a strategy is effective in persuading colleagues who might not have seen the value of InnerSource so far. Also discussions with management will be easier if you can draw clear connections between your goals and recommended activities to establish InnerSource and the goals and business strategy of your organization. It can be helpful to mention what other organizations (your peer organizations and/or competitors, for example) do with respect to InnerSource. The sections "target state" and "recommended actions" can be used as input and guardrails for the work of your InnerSource program.
+
+If your organization has an approval process for strategy document, it is recommended to get an approval for your InnerSource strategy. Such a process can trigger discussions about InnerSource in your organization, raise awareness and make such a strategy document more "official".
+
+## Resulting Context
+
+TODO
+
+<!--
+What is the situation after the problem has been solved?
+The original context is changed indirectly by way of the solution.
+Often this section can include discussion of the next possible Patterns/problems introduced.
+This section can be short in content - the solution may not introduce new problems or change much context.
+-->
+
+## Known Instances
+
+- **SAP** has an InnerSource strategy (see blog post "[Cultivating InnerSource at SAP](https://community.sap.com/t5/open-source-blogs/cultivating-innersource-at-sap/ba-p/13575274)")
+
+## Status
+
+Initial
+
+## Author(s)
+
+- Michael Picht
+
+## References
+
+For discussions about this pattern idea please see [this PR](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/652) as well.