Context:
A development organization where roles are being defined. Patron works only if Developer Controls Process is in place.
Forces:
Centralized control can be a drag.
Anarchy can be a worse drag.
Most societies need a king/parent figure.
An organization needs a single, ultimate decision-maker. The time to make a decision should be less than the time it takes to implement it.
Solution:
Give the project access to a visible, high-level manager, who champions the cause of the project. The patron can be the final arbiter for project decisions, which provides a driving force for the organization to make decisions quickly. The patron is accountable to remove project-level barriers that hinder progress, and is responsible for the organization's "morale" (sense of well-being).
Resulting Context:
Having a patron gives the organization a sense of being, and a focus for later process and organizational changes. Other roles can be defined in terms of the patron's role.
The manager role is not to be a totally centralized control, but rather a champion. That is, the scope of the manager's influence is largely outside those developing the product itself, but includes those whose cooperation is necessary for the success of the product (support organizations, funders, test organizations, etc.). This role also serves as a patron or sponsor; the person is often a corporate visionary.
Design Rationale:
This relates to the pattern Firewalls which in turn relates to the pattern Gatekeeper.
Block talks about the importance of influencing forces over which the project has no direct control [Block].
The etymology of the term patron is instructive.
Next: Architect Controls Product