[Pattern Draft] Career Booster

[spier]

Closes #794

Quick draft based on a ChatGPT suggestion.

Prompt used

Describe the concept of "InnerSource as a career booster" in the format of an InnerSource Pattern. Use the template for an InnerSource Pattern provided below.

# The concept:

One of the driving factors for individuals in an organization may (rightfully so) be personal objectives like furthering their own career. 

Therefore they may ask:

- How does it help me, when I contribute to a project outside of my own team (i.e. an InnerSource project)?
- What do I gain? 
- What do I learn?
- How does it make a difference for me personally?
- Should I just optimize all my work and doing towards the goals of my direct manager, or should I am to work towards to larger goals of the overall organize? in other words, should I work towards a local optimum (in my team), or a global optimum (in the organization)?

Try to work in ideas from various different fields into the solution below (e.g. psychology, game theory, etc)

# Template

## Title

Short Title Here

## Patlet

A two sentence description of the problem and solution.
The first sentence describes the problem you are looking to solve, while the second sentence describes the solution.
The first sentence of the Patlet should not mention anything about the solution.

Readers may quickly review dozens of these patlets to discover and browse the larger library of patterns.

## Problem

What is the problem - crisp definition of the problem.

Short description, usually not more than a couple sentences, that describes what the issues and challenges are.

Be careful not to morph into information found in other sections below.

## Story (optional)

Sometimes there is a story that helps people understand the pattern better.

## Context

Where does the problem exist?

What are the pre-conditions?

**Unchangeable** before the solution goes into place.

The content here is often tied to the applicability of the pattern for other readers: "Do I have this same particular situation?"

Use bullet points for this section, so that readers can quickly check if this applies to them.

## Forces

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.

Use bullet points for this section.

## Sketch (optional)

visual illustration

## Solutions

Verified resolutions and possible resolutions to the problem.

## Resulting Context

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.

## Rationale (optional)

Explains why this is the right solution; using totally different words WHY this solution balances these forces and this context to solve this problem.

Can expand on what-if's or theories.

## Known Instances (optional)

Where has this been seen before?

Helps to reinforce that this is a REAL pattern and that you match the context.

May mention:

* A particular business

* Anonymized instances ex: "3 companies have proven that this is a good solution" or "A large financial services org...".

## Status (optional until merging)

General pattern status is stored in GitHub's Label tagging - see any pull request.

Note that this GitHub label tagging becomes less visible once the pattern is finalized and merged, so having some information in this field is helpful.

You might store other related info here, such as review history: "Three of us reviewed this on 2/5/17 and it needs John's expertise before it can go further."

## Author(s) (optional)

Often, this is yourself.

If you need to, find someone in the InnerSource Commons to be the nominal author (As Told To).

Could also be no-one if you do not want to take on authorship (common with a donut looking for a solution).

## Acknowledgments (optional)

Include those who assisted in helping with this pattern - both for attribution and for possible future follow up.

Though optional, most patterns should list who helped in their creation.

## Alias (optional)

If this pattern is also known under a different name than what is listed unter **Title**, please list those alternative titles here.

e.g. if the pattern is named after the problem it solves, a helpful alias might be one that describes the solution that is applied.

[spier]

Trying to get feedback from @Morl99 and some others that I collaborated with on this idea during a conference this week.

[spier]

See this for inspiration

https://dirkriehle.com/wp-content/uploads/2015/04/r5rie-v3.pdf

[spier]

Are InnerSouce contributions the better equivalent to "company hopping" to further your career?

i.e. through InnerSource contributions you don't even have to switch teams (or companies), as you can get exposure to more people, and work on more different problems than when you just stick to your immediate team.

[MaineC]

https://github.com/MaineC/ribbit ... this might be helpful: a couple years ago I ran interactive sessions at OSS conferences gathering arguments for OSS upstream participation (from three different perspectives, personal, team and corporation). I suppose several would directly carry over to InnerSource.

[spier]

Closing this in favor of new PR #843.