# July 24, 2025

## Attendees:&#x20;

<table data-header-hidden><thead><tr><th width="166.83984375"></th><th width="122.2265625"></th><th></th></tr></thead><tbody><tr><td>Name</td><td>Attendance</td><td>Role</td></tr><tr><td><a href="mailto:simo.simovic@intersectmbo.org">Simo Simovic</a></td><td>Yes</td><td>WG Lead/Secretary</td></tr><tr><td>Phil Lewis</td><td>No</td><td>ISC Member</td></tr><tr><td>Thiago Nunes</td><td>Yes</td><td>Interim ISC Member</td></tr><tr><td>Pedro Lucas</td><td>No</td><td>OSC Chair, Representing two Enterprise Members</td></tr><tr><td>Nicholas Cerny</td><td>No</td><td>Civics Committee Chair</td></tr><tr><td>Vaibhav S</td><td>Yes</td><td>GMC Member</td></tr><tr><td>Naushad Fouze</td><td>No</td><td>Product Committee</td></tr><tr><td>Jose Iadicicco</td><td>Yes</td><td>Community Member</td></tr><tr><td>Maureen Wepngong</td><td>Yes</td><td>DRep</td></tr><tr><td>Terence McCutcheon</td><td>Yes</td><td>Intersect</td></tr><tr><td>Tevo Saks</td><td>Yes</td><td>Community Member</td></tr><tr><td>Lorenzo Bruno</td><td>Yes</td><td>Head of Product Curation at Intersect</td></tr></tbody></table>

<br>

Recording: [Intersect Governance WG Weekly - 2025/07/24 15:59 CEST - Recording](https://drive.google.com/file/d/1rApKZjIA6UaOQ06e49vAUVIDK1B2Oih_/view)

Transcript: [Intersect Governance WG Weekly - 2025/07/24 15:59 CEST - Transcript](https://docs.google.com/document/d/1-GF54_fU3vT6xkFbcWHxKwvA0RWpmqxPwc3w0PZxHA4/edit?tab=t.0#heading=h.1lpw7hod3co2)

## Agenda 24.07.2025

* Update from next week
* Decision-Making Process Workflow

## Decisions/Actions

<table data-header-hidden><thead><tr><th width="143.5703125"></th><th width="246.65234375"></th><th></th></tr></thead><tbody><tr><td>Discussion Point</td><td>Notes</td><td>Actions: Responsible / Note</td></tr><tr><td>Update on Board Election Application Discussion</td><td>The prior, additional meeting focused on board election applications. It resulted in more questions than answers regarding feasibility and implementation of potential features. No concrete actions were taken from that specific discussion, which was primarily for brainstorming.</td><td>Lorenzo will provide full clarification on the outcomes of the meeting, referencing the Miro board for details.</td></tr><tr><td>Review and Refinement of Decision-Making Process Diagram</td><td>A first draft of a Business Process Model and Notation (BPMN) diagram visualizing Intersect's decision-making process was created. The goal is to clearly document and visualize how ideas, proposals, and recommendations flow from initiation to execution within Intersect. The diagram aims to help members and associates understand where to submit ideas and how the process works. Key questions raised include: specific contact points for submitting ideas, timelines for committee review/response, and overall process duration. It was noted that this diagram represents the current state of the process, which is being documented before potential simplification.</td><td>All participants are to review the diagram and provide feedback. Simo Simovic will continue to refine the diagram and associated written explanations. The group plans to continue discussion on the decision-making process at the next weekly call.</td></tr><tr><td>Directional Flow and Feedback Loops in the Diagram</td><td>Concerns were raised about the diagram's unidirectional arrows, specifically regarding information flow from the Board back to the ISC or relevant committees after a decision is made and executed. It was clarified that this feedback loop already exists in practice (e.g., executive team updates ISC in meetings) but needs to be explicitly visualized in the diagram to accurately reflect the current state.</td><td>Simo Simovic will incorporate bidirectional arrows or notification points in the BPMN diagram to represent existing feedback loops, particularly from the Board back to the ISC/relevant committees.</td></tr><tr><td>Redundancy Checks for Proposals</td><td>A participant suggested incorporating a triage step at the beginning of the proposal submission process to check for redundancy with existing proposals or ongoing work. This would prevent duplicated efforts and encourage collaboration. It was also suggested to track how long proposals stay at each stage of the process to identify bottlenecks.</td><td><br></td></tr><tr><td>Software for Process Management &#x26; Democratic Participation</td><td>Discussion briefly touched on using open-source tools for process management (e.g., ClickUp, previously suggested “Camunda” by another member) and for democratic participation. An open-source software called "Decidim" was suggested for research, offering features like proposal creation, debate support, and vote traceability.</td><td>Simo Simovic expressed he would likely lead any internal development for such a platform if needed.</td></tr><tr><td>BPMN Diagram Notations &#x26; Consistency</td><td>Discussion occurred regarding the consistent use of colors and notations for comments, actions, and information items within the BPMN Diagram.</td><td>Simo Simovic will ensure consistency in notation.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://steeringcommittee.docs.intersectmbo.org/working-group/working-groups/working-group-meeting-notes/2025/july-24-2025.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
