# June 02, 2025 ISC Meeting
## Agenda:
* ISC Actions/Update from last week
* Chair Election Discussion
* Update from Committees (If Any)
* AOB & Meeting Close
## Attendees:
| Name | Attendance | Role | Voting Seat (Y/N) |
| ---------------------------------------------------- | ---------- | ------------------------------- | ----------------- |
| [Simo Simovic](mailto:simo.simovic@intersectmbo.org) | Yes | Secretary | N |
| Jack Briggs | Yes | Interim Executive Director | Y |
| Nick Cook | Yes | Director - Operations (Interim) | Y |
| YUTA | Yes | Community Member Seat | Y |
| Phil Lewis | Yes | Community Member Seat | Y |
| Sheldon Hunt | Yes | Community Member Seat | Y |
| Fred Tanaka | Yes | Community Member Seat | Y |
| Pedro Lucas | Yes | OSC Chair | Y |
| Samuel Leathers | No | Product Chair | Y |
| Darlington Welsh | Yes | MCC Chair | Y |
| TBD | No | CBC Chair | Y |
| Kevin Hammond | Yes | TSC Chair | Y |
| Simon Fleck | Yes | Interim GMC Chair | Y |
| Nicolas Cerny | Yes | Interim CCC Chair | Y |
| Christian Taylor | Yes | Head of OSO | N |
| Lorenzo Bruno | Yes | Head of Product | N |
| Matt Davis | No | Head of Tech Operation | N |
| Duncan Soutar | Yes | Secretary of TSC | N |
| Lloyd Duhon | Yes | Secretary of Budget Committee | N |
| Larisa Mcfarlane | Yes | Secretary of CCC | N |
| Terence McCutcheon | Yes | Secretary of OSC | N |
Additional Attendees:
* Thiago Nunes - Observer
## Discussion/Action:
### 1. Opening the Meeting
The meeting opened with a review of attendance and the agenda. It was noted that some committee chair positions remain vacant and elections are in progress. The ISC secretary outlined the agenda, which included updates on action items, discussion of the ISC chair role, committee updates, and any other business members wished to raise.
### 2. ISC Action Items & Updates
The committee reviewed several key developments:
* New Committee Roles & Decision-Making Framework: There was broad agreement on the need for a clear, documented process outlining how ideas and proposals move from working groups through committees and onward to governance actions. Intersect staff will draft a comprehensive framework—including a visual mapping—to be shared in two weeks.
* Consultant Transition Plan: The board approved the proposed consultant transition plan, with rollout scheduled for July. While this change will affect some areas such as budget administration, teams are preparing to ensure a smooth transition. The Intersect team and ISC will finalize a draft of the plan and take it to the June board meeting for ratification and implementation.
* Monthly AMA Meeting: The first AMA meeting is scheduled for the end of June. Lara and the intersect team are preparing for the first AMA meeting.
* New Election Tool Onboarding & Elections: The new election tool is currently being piloted with select committees. Feedback from these initial elections will guide further improvements. Use of the tool is encouraged but remains optional. Committees may choose alternative processes if they prefer.
### 3. Board Update & Legal Workshop
The board is now meeting weekly with the executive team and has invited ISC members to attend the next board meeting in June to improve alignment and communication.
A legal workshop was held to review Intersect’s role as administrator, covering contractual responsibilities, internal procedures, and the phased rollout of the smart contract framework (July–December). The technical audit reported minimal issues. The need for clearer guidelines on transparency and vendor milestone reporting was discussed.
A presentation summarizing legal considerations will be shared with the ISC next week. An updated description of the administrator role has been published in the knowledge base.
### 4. ISC Chair Discussion
The committee revisited whether a permanent ISC chair is necessary. One perspective supported remaining chairless with representation on an as-needed basis. Another suggested appointing a chair to improve external visibility and communication.
A motion was raised and passed that the committee will nominate representatives on an as-needed basis rather than electing a permanent chair. The secretary will continue to drive meetings.
### 5. Transparency in Vendor Milestones & Issue Reporting
#### The committee discussed how to manage transparency in milestone reviews, especially when identifying potential issues that may or may not materialize. There was general agreement on the need for guidelines that balance collaboration and sensitivity, while ensuring accountability. Suggestions included establishing a framework for raising and tracking emerging risks without undermining vendor relationships. Follow-up actions include seeking feedback from relevant committees and refining documentation accordingly.
### 6. Cross-Committee Working Groups
The ISC explored how working groups should operate when spanning multiple committees. It was agreed that groups should maintain flexibility while being anchored to a primary committee for clarity and accountability. Excessive bureaucracy should be avoided to encourage active participation.
### Action Items & Next Steps
* A draft of the decision-making framework will be shared in two weeks.
* The legal/admin process deck will be presented at the next ISC meeting.
* ISC representation will be coordinated for the June board meeting.
* Administration Deck to be shared with Kevin (pass it to the TSC)
* Solutions for tracking documentation updates on Intersect knowledge base will be investigated and tested.
---
# 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/committee-meeting-notes/2025-meeting-notes/june-02-2025-isc-meeting.md?ask=
```
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.