# May 19, 2025 ISC Meeting ## Agenda * Meeting Introduction * ISC new elected members * ISC Actions/Update from last week * Contract Template * Update from Committees and Business Function (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 | Yes | Product Chair | Y | | Darlington Welsh | Yes | MCC Chair | Y | | Prof. Steven | No | Chair of Board of Directors and CBC Chair | Y | | Kevin Hammond | Yes | TSC Chair | Y | | Simon Fleck | No | GMC Chair | Y | | Jose Miguel De Gamboa | Yes | CCC Chair | Y | | Christian Taylor | Yes | Head of OSO | N | | Lorenzo Bruno | Yes | Head of Product | N | | Matt Davis | Yes | 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 | | Kyle Solomon | Yes | Product Co-Chair | N | Additional Attendees: * Adam Rusch - Community Board Seat - Observer * Thiago Nunes - Community - Observer ## Discussion/Action: ### 1. Welcome & Introductions The meeting opened with introductions from ISC members and representatives from various Intersect committees. Newly elected members participated for the first time, helping establish connections and shared context within the group. ### 2. Chair Position Discussion A discussion was held around whether the ISC should elect a formal Chair or continue operating through shared facilitation. Members shared differing views regarding the benefits of structure versus informality. It was agreed that this discussion would be added as a formal item for the next meeting, where a decision could be made collectively. ### 3. ISC Action Items & Updates from Last Week **a. Intersect Organizational Chart** An updated organizational chart was presented, reflecting the current team structure and consultant roles. Members requested that all known contributors be included in the public-facing version to ensure full transparency. This version is expected to be finalized and shared soon. **b. Consultant Transition Plan** An update on consultants' transition plan was shared, outlining a 12-month timeline to replace 12 consultant roles with full-time staff. The objective is to reduce dependency on external contractors while maintaining delivery continuity. The plan includes phased hiring and knowledge transfer. The plan to be finalized and presented to the ISC for discussion and feedback on the next ISC call. **c. Committee Roles Document** A draft document defining the roles and expectations of Intersect committees was introduced. Members were asked to review the draft and provide feedback. Once finalized, it will be published in the knowledge base to support onboarding and clarify committee mandates. **d. Delivery Assurance Concerns** Concerns were raised about the current capacity and visibility of the delivery assurance function. Discussion emphasized the need for more robust monitoring of funded projects, with a potential re-evaluation of how this function is staffed and prioritized. ### 4. Milestones in Contracts The committee discussed the inconsistent use of clear, measurable deliverables in contract templates. There was a strong recommendation to improve milestone-based accountability for all funded work, particularly as treasury contract implementation ramps up. ### 5. Intersect as Administrator It was noted that Intersect is currently listed as the administrator on 39 budget proposals. The implications of this designation were discussed, with a shared understanding that clear expectations, boundaries, and risk mitigation strategies are needed going forward. ### 6. Treasury Withdrawal Strategy The committee discussed a plan to avoid a single large withdrawal of 275M ADA from the treasury. Instead, a phased strategy was proposed, grouping similar proposals into themed withdrawals. This approach is intended to enhance transparency, reduce risk, and facilitate community communication. ### 7. Independent Audit Requirements Clarification was provided on audit expectations: * Delivery assurance audits monitor whether funded work is being executed. * Financial and technical audits focus on how funds are spent and whether deliverables meet quality standards. Members noted the importance of specifying these requirements clearly in contracts and proposals. ### 8. Platform & Voting Tools Concerns were raised about Discord being overly cluttered and unstructured for decision-making. Members expressed interest in exploring more structured platforms for documentation and alternative voting tools that offer transparency and traceability. ### 9. Action Items & Next Steps * Add Chair discussion to one of the next meeting agenda for resolution. * Finalize and publish updated interim Intersect org chart. * Share formal consultant transition plan with the ISC/add to agenda and allow enough time for discussion on the next ISC call * Circulate the committee roles document to the ISC for review and feedback so we can finalize the document * Establish ISC–Budget Task Force Coordination Meetings --- # 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/may-19-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.