The First 90 Days

The sequence matters more than the pitch. This is the order that worked across all three provinces:

Days 1-2: Provincial government. The prefect's office or the relevant directorate (environment, planning). Even if they are not your institutional anchor, they need to feel like they were consulted first. Government officials track who was approached before them, and perceived slights create permanent obstacles.

Days 3-4: Indigenous authorities. The nationalities' governing bodies (in Amazonian Ecuador: Kichwa, Shuar, Waorani, Ai Cofan, Siekopai, Siona, depending on territory). Not the community leaders. The elected authorities of the indigenous governance structures. Approaching communities before their elected authorities is a protocol violation that can shut you out of entire territories.

Days 5-7: NGOs with territorial presence. Organizations already working in the territory, especially those with long-standing relationships with indigenous communities. They become your intelligence network and often your co-facilitators.

Days 8-9: Academia and research institutions. Universities and research centers provide technical legitimacy and can host early conversations in neutral venues.

Days 10-11: Municipal governments. Mayors and municipal councils. They have different political dynamics than the provincial government and need separate engagement.

Days 12-14: Private sector. Extractive industries, tourism operators, agricultural cooperatives. They come last because approaching them too early signals to indigenous authorities and environmental NGOs that this is an industry-friendly process.

Every bilateral meeting in weeks 1-2 should cover three questions. Not more. You are not presenting a plan. You are listening and building political intelligence.

1. "What is the biggest coordination failure in this territory right now?" This surfaces what they actually care about. If their answer does not connect to your platform's scope, you learn early that you need a different framing for this stakeholder.
2. "If this platform existed and worked, what would it need to do for your organization to stay engaged?" This is your design input. Not from a survey. From a face-to-face conversation where you can read what is said and what is not said.
3. "Who else must be in the room for this to be legitimate?" This validates your long list, surfaces actors you missed, and reveals political alliances and antagonisms you need to map before the first convening.

These phrases will damage your credibility in weeks 1-2:

• "We want to create a space for dialogue." Every failed initiative in the territory said this. It signals nothing concrete will happen.
• "This platform will coordinate all actors." No one wants to be coordinated. Frame it as a space where organizations protect their autonomy while aligning on shared territorial priorities.
• "We have funding for three years." The moment you mention external funding, every conversation becomes about who controls the budget. Discuss mandate and structure first. Budget comes later.
• "This is different from previous attempts." Everyone says this. Show it through your approach (starting with political groundwork instead of a launch event), do not claim it.

Venue: Neutral ground. Not a government building (signals government ownership), not an NGO office (signals external agenda), not a hotel conference room (signals transactional). The best venues are cultural centers, university halls, or community event spaces. In Orellana, the first convening was at a provincial cultural center. In Sucumbios, a university auditorium.

Duration: One full day, 8:00 AM to 4:00 PM. Not a half-day. You need enough time for every sector to speak without feeling rushed, plus buffer for the inevitable political speeches that will happen whether you schedule them or not.

Seating: Circular or U-shaped. Never classroom style. Never a head table with a panel. The seating arrangement is a political statement. If government officials are at the front and indigenous authorities are in the audience, you have already failed to communicate shared governance.

Block 1: Territorial Diagnosis (90 minutes). Present the state of the territory using data, not opinions. Deforestation rates, extractive concession maps, protected area coverage, indigenous territory boundaries, ongoing conflicts. Let the data create the sense of urgency. Every stakeholder should leave this block understanding that the status quo is not sustainable for anyone.

Block 2: Proposed Structure (60 minutes). Present the platform architecture: plenary, sub-tables, technical secretariat, rotating presidency. Present it as a proposal, not a decision. Use the Governance Canvas as a visual anchor. Make it clear that everything is negotiable except the principle of multi-stakeholder representation.

Block 3: Stakeholder Input (90 minutes). Structured round-robin. Every organization gets 3-5 minutes to state their position: what they need from this platform, what they can contribute, and what their non-negotiables are. This is the most important block. Document everything. This input shapes the constitutive agreement.

Block 4: Commitments and Next Steps (60 minutes). Do not end with "we will follow up." End with specific commitments: who will participate in the drafting committee for the constitutive agreement, when the next meeting is (set the exact date before anyone leaves), and what each organization will contribute to the process.

Opening: The institutional anchor opens. This establishes the formal mandate. Keep it to 10 minutes.

Indigenous authorities speak second. Not third, not after the NGOs. Second. This signals that their governance structures are recognized as equal to the state's. In Amazonian Ecuador, this meant the presidents of the indigenous nationalities spoke immediately after the prefect.

Facilitation: An external facilitator who is not affiliated with any stakeholder group. Not the NGO coordinator. Not the government official. Someone whose only role is to manage the conversation. This person must understand indigenous protocol, government formality, and the tension between them.

Closing: Shared. Not one person. A representative from government and a representative from indigenous governance close together. The optics of the closing matter as much as the opening.

• Do not allow the first meeting to become a grievance session. If indigenous communities use the space to air historical complaints against the government (legitimate as they are), the government representatives will shut down. Acknowledge the grievances, document them, and redirect: "This platform can be the mechanism to address these. Let's design it."
• Do not present a finished structure. If stakeholders feel like the decisions were already made, they will participate as observers, not owners. Present options. Let them argue. The argument is the buy-in.
• Do not skip lunch. The informal conversations during meals are where the real political negotiations happen. Budget for a proper sit-down meal, not sandwiches people eat while checking their phones.
• Do not rush the commitments block. If you run out of time and skip concrete next steps, the meeting was a forum, not a founding event. Cut from the territorial diagnosis before you cut from commitments.

Seven elements. All non-negotiable in terms of inclusion, fully negotiable in terms of content:

1. Purpose and territorial scope. What the platform exists to do, and where. Be specific about geography: province, protected areas, indigenous territories, watersheds.
2. Membership criteria. Who can participate, how new members join, and under what conditions membership can be suspended. This is the first fight. Government will want to control membership. Indigenous authorities will want veto power over who enters their territories' governance space.
3. Governance structure. Plenary composition, sub-table mandates, technical secretariat functions, rotating presidency rules. Specify term lengths, rotation order, and what happens if a presiding organization fails to perform.
4. Decision-making rules. Consensus or majority? What constitutes a quorum? What happens when consensus cannot be reached? In all three Cooperation Tables, the answer was consensus with a fallback to two-thirds majority, with indigenous authorities holding a collective veto on matters affecting their territories.
5. Commitment and accountability mechanisms. How roadmap activities are tracked, what the reporting cycle is, and what happens when organizations do not deliver. This is where most platforms go soft. Define consequences.
6. Financial arrangements. How the platform is funded, who manages the funds, and how financial decisions are made. Separate from the programmatic budget of any single member.
7. Amendment procedures. How the agreement itself can be modified. Require a supermajority and a minimum notice period. This prevents the agreement from being changed by whichever faction happens to show up to a particular meeting.

Three predictable conflicts and how to navigate them:

Government wants permanent presidency. They will argue they have the institutional mandate. Counter: rotating presidency is what makes this a multi-stakeholder platform and not a government committee. Offer the government the first rotation as a compromise, but lock in the rotation schedule in the agreement.

NGOs want observer status. Some NGOs will argue they should observe, not participate, to maintain independence. Counter: observer status means no voice in decisions that affect their programs. Full membership with recusal rules for conflicts of interest is better than permanent sideline status.

Signature level negotiations. Government wants the prefect to sign. Indigenous authorities want their elected presidents. NGOs send country directors. The signature level communicates the political weight of the commitment. Push for the highest possible signatories. If the prefect will not sign, the agreement is weaker. If indigenous presidents do not sign, it lacks territorial legitimacy. These negotiations can take 2-3 weeks on their own.

Regardless of how the negotiation unfolds, these three elements must survive intact:

1. Rotating presidency. If one sector holds permanent leadership, the platform belongs to that sector. Rotation is the structural guarantee of shared governance. Non-negotiable.
2. Indigenous representation at the plenary level. Not through an NGO proxy. Not through a government liaison. Direct seats for indigenous governance structures with voice and vote. If indigenous authorities are not at the table as equals, you do not have a multi-stakeholder platform.
3. Written accountability mechanisms. If the agreement does not specify what happens when commitments are not met, the commitments are aspirational. Accountability does not need to be punitive. It needs to be specific and visible.

One workshop per sub-table. Not a combined session. Each sub-table has different stakeholders, different technical requirements, and different political dynamics. Combining them dilutes the specificity you need.

4-hour structure per sub-table:

1. Hour 1: Problem framing. What are the specific issues this sub-table addresses? Not general themes. Specific problems with geographic coordinates and affected populations. Example: "Illegal mining in the upper Napo watershed affecting 12 Kichwa communities" not "environmental degradation."
2. Hour 2: Activity identification. What concrete actions can the organizations in this sub-table take in the next 12 months? Each activity must have a responsible organization, a timeline, and a measurable deliverable. "Raise awareness" is not an activity. "Train 40 community monitors in water quality testing by Q3" is an activity.
3. Hour 3: Resource mapping. For each activity, what resources exist (budget, personnel, equipment) and what gaps need to be filled? This surfaces which activities are immediately feasible and which require external support.
4. Hour 4: Prioritization and commitments. Not every activity can happen at once. Rank by feasibility and impact. Get verbal commitments from responsible organizations, documented in the session minutes.

The gap between what organizations promise in workshops and what they actually deliver is where most platforms die. The counter is a social accountability mechanism built into the workshop itself.

Make commitments public. Each organization states their commitment in front of the full sub-table. Not written on a card. Stated out loud. Social pressure works.

Assign a peer accountability partner. Each organization's commitment is paired with another organization that will check in on progress. Not the technical secretariat. A peer. This distributes accountability and creates bilateral relationships that strengthen the platform.

Set the first check-in date before anyone leaves. Not "we will follow up in a few weeks." A specific date, in calendars, with a specific format (15-minute phone call, email update, or brief in-person check).

To calibrate your expectations:

• Orellana: 79 roadmap activities across 5 sub-tables (Biodiversity, Water, Sustainable Production, Environmental Education, Environmental Quality). Average of 15.8 activities per sub-table.
• Sucumbios: 93 roadmap activities across 5 sub-tables. Average of 18.6 activities per sub-table. Higher count because of more active municipal government participation.

If your workshops produce fewer than 10 activities per sub-table, the stakeholders are not engaged enough. If you exceed 25 per sub-table, the activities are not specific enough. The sweet spot is 12-20 concrete, assigned, time-bound activities per sub-table.

The technical secretariat is the engine. This is typically 1-2 full-time staff (or the equivalent in dedicated hours from the institutional anchor). Their weekly routine:

• Monday: Review all activities due this week and next week. Identify any that are at risk of delay.
• Tuesday-Wednesday: Contact responsible organizations for at-risk activities. Not to nag. To ask what support they need to deliver.
• Thursday: Update the tracking dashboard. Flag overdue items.
• Friday: Send a brief weekly summary to sub-table coordinators. Two paragraphs maximum: what was completed, what is at risk.

This routine is non-negotiable. The moment the technical secretariat stops tracking, organizations stop delivering. Consistency is the mechanism, not authority.

Three escalation levels, triggered automatically by the tracking system:

30 days before deadline: Reminder to the responsible organization. Friendly, informational. "Your activity [X] is due on [date]. Do you need any support from the secretariat or other platform members?"

On deadline: Status request. "Your activity [X] was due today. Please confirm: completed, in progress (with expected completion date), or blocked (with description of obstacle)."

15 days overdue: Escalation to the sub-table coordinator and the plenary presidency. "Activity [X] by [Organization] is 15 days overdue. This will be reported in the next sub-table meeting." This is the social pressure lever. No one wants their organization named as non-performing in front of peers.

Accountability requires visibility. Three options, from most to least resource-intensive:

Option A: Dashboard. A shared digital dashboard (Google Sheets at minimum, a custom web dashboard if budget allows) that shows every activity, its status, responsible organization, and deadline. All platform members have view access. Updated weekly by the technical secretariat.

Option B: Quarterly progress report. A one-page summary per sub-table distributed before each plenary meeting. Shows completion rates, highlights achievements, names delays. Lower tech investment, but less real-time visibility.

Option C: WhatsApp group updates. For contexts where digital literacy or internet access limits dashboard use. The technical secretariat posts a weekly voice note or text summary to a sub-table WhatsApp group. Simple, low-cost, high reach. Used as a complement in all three provinces.

Choose based on your context. The mechanism matters less than the consistency. A WhatsApp voice note every Friday is more effective than a beautiful dashboard updated once a quarter.

Four metrics that tell you whether the platform is alive or on life support:

1. Completion rate. What percentage of roadmap activities due by week 12 were completed on time? Benchmark: 40-50% in the first cycle is healthy. Below 30% signals structural problems. Above 60% means you set the bar too low.
2. Reporting rate. What percentage of responsible organizations submitted status updates when requested? Benchmark: 70%+ means the accountability system is working. Below 50% means organizations are not taking the tracking seriously, and the system needs reinforcement.
3. Attendance persistence. Compare attendance at the first convening (weeks 3-4) to attendance at the first progress check (week 12). Benchmark: retaining 75% of original organizations is strong. Below 60% means something is driving people away. Investigate what.
4. Sub-table activity. Are all sub-tables meeting regularly, or have some gone dormant? Benchmark: each sub-table should have met at least 2-3 times between weeks 7 and 12. If a sub-table has not met, it either lacks a motivated coordinator or its mandate is not compelling enough.

One-page summary per sub-table. Format:

• Total activities assigned / completed / in progress / overdue / blocked
• Top 3 achievements (specific, with evidence)
• Top 3 challenges (specific, with proposed solutions)
• Attendance record (organizations present at each sub-table meeting)
• Recommendation: continue as-is, adjust mandate, merge with another sub-table, or escalate to plenary

Present this at a plenary session. Not as a report that gets emailed. In person, projected on screen, with the sub-table coordinator presenting their own results. This creates ownership and peer accountability at the structural level.

Hour 1: Data review. Present the four metrics from weeks 11-12 to the full plenary. No spin. If the completion rate is 35%, say it is 35%. If two organizations have not attended since the first meeting, name them. Transparency builds the credibility that allows for honest conversation.

Hour 2: Structural assessment. Five questions for the plenary:

1. Are the sub-table mandates right, or do some need to be merged or split?
2. Is the technical secretariat resourced enough to maintain tracking?
3. Are the right organizations in the right sub-tables?
4. Is the rotating presidency working, or is one sector carrying the load?
5. What is the single biggest obstacle to this platform delivering on its roadmap?

Hour 3: Decisions. Not recommendations. Decisions. Who is responsible, by when, with what resources. If the plenary cannot make decisions in this meeting, the governance structure needs to be examined. A platform that can only discuss, never decide, is a forum, not a governance mechanism.

At day 90, you need to be able to answer one question honestly: is this platform adding value that did not exist before it was created?

If the answer is yes, even partially, you have something to build on. Double down on what is working. Fix what is not. Invest in the sub-tables that are delivering.

If the answer is no, you have a harder conversation. It might mean the institutional anchor is not strong enough. It might mean the constitutive agreement does not have enough teeth. It might mean the territory is not ready for this level of coordination.

The worst outcome is not failure. It is continuing to operate a platform that everyone attends out of obligation but no one believes in. That consumes resources, burns political goodwill, and makes the next attempt harder.