How They Do ItBETA
TREN

COMPANY PLAYBOOK

Red Hat

Red Hat presents transparency, inclusivity, collaboration and adaptability as organizational practices, not only software-development practices.
Operating system
  1. Open participation
  2. visible information
  3. multiple contributions
  4. adaptation and learning.

System principles

  • Transparency.
  • Inclusivity, collaboration and adaptability.

Tensions and trade-offs

  • Openness increases contribution but requires separate management of context, security and decision boundaries.

PRACTICES

How Red Hat builds its operating system

01
Transparency

Transparent work

Open culture defines transparency as a core principle.

How it works
Information and work are made visible so more people can inspect and contribute.
Why it is used
Visibility broadens access to context.
Trade-off
Visibility can create noise or expose information that needs boundaries.
Best fit
Work where information can safely be shared widely.
Open original source ↗
02
Participation

Inclusive contribution

Open organizational culture treats inclusivity as a foundational principle.

How it works
People are invited to contribute perspectives and work rather than being limited to a narrow hierarchy.
Why it is used
It expands the range of ideas available to solve problems.
Trade-off
More voices can add coordination and decision costs.
Best fit
Knowledge work benefiting from diverse expertise.
Open original source ↗
03
Community

Support open-source participation

Red Hat strongly encourages associates to participate in open-source projects.

How it works
Guidelines frame participation in open-source projects as a supported form of contribution.
Why it is used
It connects company learning and product work to external communities.
Trade-off
External participation needs clarity about time, IP and priorities.
Best fit
Organizations whose work genuinely benefits from open communities.
Open original source ↗
04
Decision making

Scale decision process to impact

Reversible everyday decisions proceed with an announcement and invitation for concerns; as impact and complexity rise, stakeholder mapping, structured feedback, and regular updates are added.

How it works
The tool prescribes announcing intent/timing and collecting concerns for simple decisions; for broad impact it identifies stakeholders, responds in aggregate even to unused feedback, and updates results.
Why it is used
Matches openness to decision risk without imposing a heavy participation ritual on every choice.
Trade-off
Misclassifying impact at the start creates either needless delay or insufficient participation.
Best fit
Knowledge work with distributed stakeholders and varying reversibility.
Open original source ↗

Primary sources