The Workbench · Charter

The Ministry of Product Charter

How the Ministry of Product operates — written plainly, so anyone working with us or inside the Commons knows what to expect. This is the operating model behind the Venture Studio and the Advisory practice.

1. What this is

The Ministry of Product runs as two connected things:

  • A Venture Studio that builds, launches, and incubates its own products. Its engine is the Innovation Commons — an invite-only practice where builders explore ideas before they become companies.
  • An Advisory practice that works with external founders and executives, bringing the same judgment we develop building our own ventures.

You engage with us in one of two ways: by participating in the Innovation Commons (by invitation), or by working with the Advisory practice (as a client). The two are connected, but they serve different purposes.

2. The Innovation Commons

The practice at the center of the Venture Studio is an Innovation Commons — a shared environment where:

  • ideas are explored before they become companies
  • people contribute based on interest and conviction
  • ownership is earned through contribution over time
  • structure emerges only when something proves real

It is not a program, a network, or an incubator. It is a place to work on ideas, improve the craft of building, and develop judgment through repeated cycles of building and feedback.

The Commons is defined by participation, not membership. For the full operating detail — rituals, processes, and philosophy — read the Innovation Commons explainer.

3. Purpose

The purpose of the practice is to get better at turning ideas into real, profitable businesses. This happens through building, feedback, and iteration.

Some ideas become companies. The primary outcome is improved capability.

4. How participation works

The Commons is an ongoing environment. People bring ideas, join projects, and contribute to the work. Participation is active — there are no observers.

There are no predefined roles or ownership at the start. Structure forms later, when there is real signal.

Work is self-directed. People bring their own ideas or join others. Projects move forward through contribution, and momentum determines what continues. Most ideas are explored briefly; a few are pursued deeply. Nothing is assigned.

5. Practice rhythm

The Commons operates with a regular cadence. Each monthly session, a participant may:

  • Present for 3 minutes — what they built, what they learned, what they plan next
  • Receive 5 minutes of direct critique

This is the primary feedback loop. The goal is clarity, accountability, and improvement over time.

6. Ownership

Ownership is not assigned upfront. It is earned through contribution using the Big Slice / Small Slice (BSSS) framework:

  • Work is divided into milestone-based phases (Big Slices)
  • Contributors earn proportional ownership within each phase (Small Slices)
  • Ownership locks as milestones complete

This tracks contribution but is not legal equity. Formal ownership is defined only when a project becomes a company.

7. Product progression

Projects move through stages using the Product Path: idea → prototype → users → revenue → stable system.

Focus shifts over time — early on, understanding and usefulness; later, reliability, scale, and sustainability. Progress is measured by movement through these stages, not internal opinion.

8. Transition to company

When a project shows real signal:

  • A committed team forms
  • Expectations become explicit
  • Ownership can be formalized into equity

This happens at the last responsible moment. The Commons supports the transition; it does not force it. When a venture clears the bar, it spins out as its own company and milestone ownership freezes into a formal cap table.

9. Code of conduct

Participants are expected to:

  • Contribute through building, thinking, or feedback
  • Share progress openly
  • Engage with others’ work
  • Give direct, useful critique
  • Follow through on commitments

Participation is required. Membership is maintained through contribution.

10. Boundaries

To maintain quality:

  • The Commons is invite-only
  • Participation is active — there are no passive members
  • Membership may be limited or removed
  • The group does not optimize for scale

The goal is a high-trust environment for real work.

11. The Advisory practice

The Advisory practice works with external teams. Work is structured, outcomes are defined, and accountability is explicit. It applies the same thinking developed inside the Commons.

The Commons is not a staffing pool for advisory work. The two arms share judgment, not resourcing.

12. How we talk about this

When describing the Ministry of Product:

  • Speak plainly about how it works
  • Emphasize practice, contribution, and progression
  • Avoid hype or persuasion
  • Do not imply guaranteed outcomes

The tone should match the work.

Closing

The Ministry of Product is a place to practice. The work is to explore ideas, build real things, and improve over time.

Some of that work becomes companies. Most of it becomes experience.

Explore the Venture Studio → Read the Innovation Commons explainer → Back to the Workbench →