Embedded Files
Run Something
Run Something
Move from planning to execution without reinventing how the work gets done.
These pathways help ASG teams and affiliates coordinate people, activities, resources, information, and learning while keeping enough flexibility to respond to changing conditions.
What are you running?
What are you running?
2.1 Run a Partnership 🤝
2.1 Run a Partnership 🤝
Keep an institutional partnership active after the agreement has been signed.
Use this pathway to move beyond the MOU by maintaining relationships, coordinating commitments, identifying opportunities, resolving bottlenecks, and creating new collaborative work.
2.2 Run a Fellowship 🎓
2.2 Run a Fellowship 🎓
Manage the complete fellowship experience from onboarding through learning, action-research, mentoring, outputs, and completion.
Use this pathway to keep fellows, faculty, mentors, partners, and the ASG team aligned.
2.3 Run a Course 📚
2.3 Run a Course 📚
Deliver an ASG course consistently while adapting to the needs of actual learners.
Use this pathway for faculty preparation, participant onboarding, sessions, learning activities, assignments, feedback, and course improvement.
2.4 Run a Lab 🧪
2.4 Run a Lab 🧪
Operate a lab as an ongoing platform for collaboration, inquiry, experimentation, and learning.
Use this pathway to manage convenings, portfolios of initiatives, stakeholder engagement, experiments, knowledge, and emerging opportunities.
2.5 Run an Event or Conference 🗓
2.5 Run an Event or Conference 🗓
Coordinate a workshop, conference, summit, dialogue, or other convening from final preparation through delivery and follow-through.
Use this pathway to align the team, participants, speakers, logistics, documentation, and post-event actions.
2.6 Run a Research Initiative 🔬
2.6 Run a Research Initiative 🔬
Coordinate research from startup through data collection, analysis, outputs, dissemination, and use.
Use this pathway to keep researchers, partners, timelines, evidence, decisions, and intended users connected.
Run Research →
2.7 Run a Country or Affiliate Operation 🌍
2.7 Run a Country or Affiliate Operation 🌍
Coordinate ASG activities across a country or affiliate organization.
Use this pathway to manage programs, partnerships, opportunities, communications, finances, reporting, and connections with the wider ASG network.
Run an Affiliate →
2.8 Run a Project 🚀
2.8 Run a Project 🚀
Keep a project moving from launch through implementation, learning, and completion.
Use this pathway to clarify priorities, coordinate the team, track commitments, manage risks, and adapt as conditions change.
How Running Pathways Work
How Running Pathways Work
Every running pathway follows a common operating rhythm.
1. Orient
1. Orient
Know where things stand.
Review objectives, commitments, people, resources, deadlines, previous decisions, and current conditions.
2. Prioritize
2. Prioritize
Identify what matters now.
Not everything deserves equal attention. Determine the few outcomes, decisions, bottlenecks, or opportunities that require attention during the current operating cycle.
3. Coordinate
3. Coordinate
Make ownership and next actions visible.
Know:
Who is doing what?
By when?
Who else needs to be involved?
What is blocking progress?
4. Execute
4. Execute
Do the work.
Use the relevant templates, AI tools, trackers, communications, meetings, and organizational systems to move commitments forward.
5. Sense
5. Sense
Pay attention to what is changing.
Look for:
progress
delays
emerging risks
stakeholder reactions
unexpected opportunities
new information
assumptions that appear wrong
changes in the surrounding environment
6. Adapt
6. Adapt
Change the plan when the situation requires it.
A pathway provides a default route. It should not prevent teams from responding intelligently to reality.
7. Learn
7. Learn
Capture what should influence the next operating cycle.
Important learning should become part of ASG's institutional memory rather than remaining inside individual conversations, inboxes, or AI threads.
Your Operating Rhythm
Your Operating Rhythm
Most initiatives should have a simple recurring cycle:
Review → Prioritize → Act → Update → Learn → Repeat
The frequency depends on the work.
Some projects may require weekly cycles. A fellowship may operate around monthly learning cycles. A country affiliate may use weekly operational reviews and monthly portfolio reviews.
The pathway should establish the rhythm without creating unnecessary meetings.
Your Operating Dashboard
Your Operating Dashboard
Each initiative should have one place where its current state can be understood.
At minimum:
Objective
What are we trying to accomplish?
Current Stage
Where are we?
Next Milestone
What needs to happen next?
Owner
Who is accountable?
Next Actions
What needs to be done now?
Risks / Bottlenecks
What needs attention?
Partners
Who else is involved?
Decisions Needed
What requires judgment or approval?
Recent Learning
What have we discovered?
[Open My Active Work]
Help Me Run It
Help Me Run It
Use the tool that best fits the work.
[Ask ChatGPT]
Think through problems, analyze options, draft outputs, challenge assumptions, and make sense of emerging information.
[Work with Claude]
Continue work within a persistent operational workspace and institutional knowledge base.
[Open Google Workspace]
Access trackers, working documents, templates, references, and collaborative files.
[Open Odoo]
Manage formal organizational records, projects, CRM, finance, contracts, and workflows.
The pathway should tell you which tool to use. You should not have to decide which system contains the next step.
Country Context
Country Context
[Global] [Pakistan] [Nepal] [Senegal] [Philippines]
The core operating pathway remains common across ASG.
Country and affiliate contexts can add local:
partners and contacts
operating requirements
examples
calendars and milestones
funding information
templates
institutional arrangements
lessons and adaptations
When the Pathway Does Not Fit
When the Pathway Does Not Fit
Do not force reality to fit the pathway.
[Something is Different]
Record:
What happened?
What was different from the pathway?
What did you do instead?
What happened as a result?
Should the pathway change?
Exceptions are not merely problems. Repeated exceptions can reveal where ASG needs to redesign a pathway or create a new one.
The Principle
The Principle
Make routine execution easier without making adaptive work rigid.
Paved Pathways should handle much of the coordination and recurring work so teams can spend more attention on relationships, judgment, learning, adaptation, and the difficult problems that cannot be standardized.
Choose what you are running →
Page updated
Google Sites
Report abuse