Revised: 2017-02-13  (Original title: OLE Community Product Council Charge)

The FOLIO Product Council guides the functional development of the FOLIO Library Services Platform.  The Product Council manages the scope of the FOLIO project and is responsible for the relevance, cohesiveness, and transparency of the FOLIO project.  The Product Council provides a locus for discussions about strategic library management issues that lead to collective action.   Issues may be referred by the Product Council to the tripartite  for guidance and arbitration. Decisions are made by “lazy consensus” (see definition below) by the PC and documented to the public.

The Product Council will form an Executive Committee to aid in the accomplishment of the goals/activities below.  The Product Council should refer SIG concerns to the Executive Committee if the concerns require more information, more analysis, and consultation with other groups.


Primary functions:


The Product Council is comprised of key FOLIO partner representatives.  Each OLE Partner is a member of the Product Council as a key benefit of OLE membership.  Members are appointed by their stakeholders, and may be replaced with appropriate notice.  The Product Council may request a replacement of an appointed member if the member does not maintain acceptable engagement and performance as defined in this document.  While each Member represents a stakeholder, the goal of the Product Council is to further the overall goals of the FOLIO projectProduct Council membership and organizational size will be reviewed yearly.

A Product Council member is expected to:





“Lazy Consensus” is a form of decision-making that assumes that a stated path forward is acceptable to all in the group unless objections are raised (also known as “yes becomes the default”).  Typically this means that someone will state a decision and a plan to act on that decision unless someone objects in a timely fashion (usually 72 hours).  Assume best intent.  See a description of how Lazy Consensus is used in the Apache OpenOffice project and how it has been applied to library operations.