Skip to content

Commit 1933253

Browse files
committed
fix: markdown list errors
1 parent 6d364c6 commit 1933253

File tree

2 files changed

+19
-0
lines changed

2 files changed

+19
-0
lines changed

patterns/1-initial/change-the-middle-management-mindset.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,31 +63,36 @@ This pattern applies when:
6363
## Solutions
6464

6565
### Manager Education and Value Demonstration
66+
6667
* **Educational outreach**: Provide formal training to help managers understand InnerSource benefits and value
6768
* **Demonstrate time savings**: Show how InnerSource practices free up time for core development work.
6869
* **Strategic alignment**: Clarify how InnerSource contributions align with broader organizational goals
6970
* **Make managers look good**: Demonstrate how InnerSource can make the manager look good and improve team efficiency.
7071
* **Friction reduction**: Show how InnerSource reduces technical friction (e.g., standardizing library versions) and improves team productivity
7172

7273
### Performance Management Integration
74+
7375
* **OKR integration**: Use [Objectives and Key Results (OKR)](https://en.wikipedia.org/wiki/OKR) to form horizontal teams across Business Units and align middle-management goals with quarterly objectives (L2s). OKRs provide a broader view than KPIs, fostering durable cross-unit teams connected to quarterly goals they set.
7476
* **Cascading goals**: Ensure InnerSource goals cascade down from high-level organizational objectives without conflicting with existing team goals
7577
* **Manager recognition**: Reward managers who promote InnerSource participation and enable their teams' involvement
7678
* **Team efficiency metrics**: Demonstrate how InnerSource reduces friction and improves team productivity
7779
* **Performance measurement**: Include InnerSource participation in performance reviews and manager evaluations
7880

7981
### Strategic Alignment and Communication
82+
8083
* **Focus on reuse and collaboration**: Frame InnerSource benefits around measurable reuse and collaboration metrics rather than abstract concepts.
8184
* **End-of-life process integration**: Incorporate InnerSource into EOL processes to reduce redundancy and demonstrate resource efficiency
8285
* **Clear ownership definition**: Define what code pieces teams own and identify opportunities to consolidate competing solutions
8386

8487
### Community Building and Recognition
88+
8589
* **Trusted evangelists**: Identify and empower core team members and influencers to act as ambassadors for InnerSource contributions
8690
* **Champions program**: Recruit champions from all groups, including middle-management champions who have successfully implemented InnerSource
8791
* **Badge system**: Implement recognition badges in organizational directories to highlight InnerSource contributors, or even cardboard cut-outs of champions with InnerSource t-shirts
8892
* **Cross-BU accountability**: Create goals that transcend individual business units and demonstrate top-down support
8993

9094
### Events and Engagement
95+
9196
* **Dedicated InnerSource events**: Organize hackathons and innovation days for developers to collaborate on cross-team projects with management support. Include ShipIt Days, innovation days with 10% time, and InnerSource days focused on contributing to others' code.
9297
* **Gamification**: Create point systems for InnerSource contributions: opening an issue = 1 point, filing a PR = 5 points, merging a PR = 20 points, with rewards like two weeks off in Hawaii (paid, with family), 3-6 months off to innovate, or 6 months part-time.
9398
* **Fellows program**: Establish programs allowing trusted committers one day weekly for cross-platform work, reporting success instead of loss.
@@ -109,16 +114,19 @@ This pattern applies when:
109114
When this pattern is successfully applied, the following outcomes emerge:
110115

111116
### Manager Behavior Changes
117+
112118
* **Support for InnerSource is automatic, standard, and expected from Middle Management.**
113119
* **Managers become more supportive** of InnerSource initiatives as they see clear value and recognition for their teams.
114120
* **Middle management gains a deeper understanding** of InnerSource benefits and how they align with organizational goals.
115121

116122
### Organizational Improvements
123+
117124
* **Enhanced cross-team collaboration** and knowledge sharing across the organization
118125
* **Reduced friction and improved team productivity** through standardized practices and reduced duplication
119126
* **Better training for middle management** in negotiation and facilitation skills becomes necessary.
120127

121128
### Measurement and Process Evolution
129+
122130
* **More sophisticated measurement systems** are required, as it is easier to measure your own team's work but harder to measure others' contributions.
123131
* **Time tracking for cross-project work** becomes more critical and systematic.
124132
* **Engineering cost vs. benefit balance** emerges: teams support others while other teams allow them to make PRs, creating long-term time savings.

patterns/1-initial/incentive-mechanisms-for-voluntary-contribution.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,27 +28,32 @@ At a large financial services company, a developer found an InnerSource project
2828
## Forces
2929

3030
**Time and Resource Constraints**
31+
3132
- Employees have limited time and must prioritize their primary responsibilities
3233
- Teams are expected to maintain full capacity on their primary projects
3334
- Manager resistance to allowing team members to work on external projects
3435

3536
**Recognition and Visibility Gaps**
37+
3638
- Contributions to InnerSource projects lack visibility to direct managers or HR
3739
- No clear path for acknowledging voluntary contributions
3840
- Performance evaluation systems ignore cross-team collaboration
3941

4042
**Career and Incentive Misalignment**
43+
4144
- InnerSource work may not advance career progression or promotion
4245
- Managers' bonuses depend solely on business unit results
4346
- Cross-team collaboration reduces capacity for primary business unit goals
4447

4548
**Individual vs. Organizational Motivations**
49+
4650
- Contributors want to expand networks and gain technical knowledge
4751
- Organizations need to balance individual growth with business unit objectives
4852

4953
## Solutions
5054

5155
### Financial Incentives
56+
5257
- **Gratitude budgets**: Allocate specific budgets for recognizing InnerSource contributions
5358
- **Performance bonuses**: Include InnerSource participation in annual performance evaluations
5459
- **Project-based rewards**: Provide financial incentives for completing specific InnerSource tasks
@@ -58,20 +63,23 @@ At a large financial services company, a developer found an InnerSource project
5863
- **Engineering bonus allocation**: Allocate 15% of engineering bonuses based on InnerSource contributions
5964

6065
### Institutional Recognition
66+
6167
- **Badging programs**: Implement digital badges for different levels of contribution (Acclaim, Credly)
6268
- **Public recognition**: Feature contributors in company newsletters, blogs, or town halls
6369
- **Manager awards**: Recognize managers who enable their teams' InnerSource participation
6470
- **First contribution celebration**: Automatically celebrate and publicize first pull requests
6571
- **Cross-team recognition**: Promote recognition at the company level, not just within teams
6672

6773
### Career and Professional Growth
74+
6875
- **Goal alignment**: Allow employees to align InnerSource work with individual performance goals
6976
- **Skill development**: Use InnerSource projects for upskilling in new technologies
7077
- **Leadership opportunities**: Create pathways for contributors to become project leaders or champions
7178
- **Promotion support**: Use peer recognition and contributions as evidence for career advancement
7279
- **Mentorship roles**: Enable experienced contributors to mentor others
7380

7481
### Manager Incentives
82+
7583
- **Management recognition**: Reward managers who promote InnerSource participation
7684
- **Team efficiency metrics**: Demonstrate how InnerSource reduces friction and improves team productivity
7785
- **Strategic alignment**: Show how InnerSource contributions align with broader organizational goals
@@ -82,6 +90,7 @@ At a large financial services company, a developer found an InnerSource project
8290
After implementing incentive mechanisms, organizations experience:
8391

8492
**Positive Outcomes**
93+
8594
- Increased voluntary participation in InnerSource projects
8695
- Better cross-team collaboration and knowledge sharing
8796
- Managers become more supportive as they recognize the value for their teams
@@ -90,12 +99,14 @@ After implementing incentive mechanisms, organizations experience:
9099
- A stable contributor group emerges, with some becoming trusted committers
91100

92101
**Strategic Benefits**
102+
93103
- Top management's 85%/15% capacity allocation shows executive support and makes InnerSource part of corporate goals
94104
- Corporate funding for InnerSource projects prevents cost center budget impacts
95105
- Manager bonuses tied to InnerSource success motivate participation encouragement
96106
- Strong InnerSource community develops with committed contributors
97107

98108
**Potential Challenges**
109+
99110
- New challenges in measuring contributions and ensuring fair recognition across different contribution types
100111
- Need for ongoing management of incentive programs and recognition systems
101112

0 commit comments

Comments
 (0)