Capstone: Building an Operating System for the Cooperative
The course’s tools become valuable when they operate as one management system. The capstone connects purpose, structure, money, people, contracts, meetings, measures, strategy, and risk into a 90-day implementation plan.
What you’ll be able to do
Week objectives
- Integrate the course artifacts into one coherent operating plan.
- Choose a small executive dashboard that supports decisions.
- Align meeting cadence, owners, measures, and escalation.
- Sequence implementation across 30, 60, and 90 days.
- Present the plan to governing and district stakeholders.
Core concepts
Build the mental model
Operating system
An organizational operating system is the repeatable set of roles, decisions, processes, meetings, measures, and review cycles through which the cooperative turns purpose into service.
Dashboard
A dashboard is a small, stable set of indicators designed for decisions. It should show definitions, owner, period, target, actual, trend, status, explanation, and action—not simply display available data.
Leading and lagging indicators
Lagging indicators report results, such as year-end cost or completed timelines. Leading indicators give earlier warning, such as vacancy days, open evaluations approaching due dates, or late district receivables.
Cadence
Daily exceptions, weekly operations, monthly performance, quarterly risk and strategy, and annual planning need different forums. Each measure and decision should have a home.
Integration
A strategic priority should appear in measures, initiatives, meetings, budget, ownership, and risk review. If it exists only in the plan, it is not integrated.
90-day implementation
Sequence foundations before complexity. Name deliverables, owners, dependencies, stakeholder engagement, measures, and decisions for each 30-day period.
Adoption
A template is not a system until people understand it, use it, improve it, and see leaders rely on it. Start with a minimum viable cadence and refine from experience.
In practice
What it looks like
- The dashboard shows staffing coverage, vacancy days, evaluation-timeline risk, district receivables, forecast variance, contractor reliance, priority progress, and top residual risks.
- A weekly leadership meeting owns staffing and service exceptions; a monthly performance meeting reviews finance and process trends; the governing committee receives quarterly strategy and risk reporting.
- The first 30 days clarify definitions and owners, days 31–60 run a pilot cadence, and days 61–90 evaluate and formalize.
Required viewing
Learn from trusted instructors
3 verified videos · 2 hr 49 min. Watch in order, then mark each complete.
How to Build a Dashboard for your Nonprofit: A Critical Strategic Tool Reveals Itself
The Nonprofit Quarterly
Explains dashboard design in a mission-driven organization rather than a sales environment. It reinforces the need to connect measures to governance and strategy.
Executive Dashboarding – Compelling Data Stories for Senior Leadership
Association Analytics
Shows how to turn measures into a senior-leadership narrative. The learner can apply the approach to district and governing-committee reporting.
Executive Dashboard Series: Operational KPIs
Club Benchmarking
Focuses on operational indicators and the decisions they support. The course adapts KPI language to staffing, service, finance, compliance, and shared public value.
Apply the ideas
Capstone Integration Workbook
Use `../templates/capstone-workbook.md` as the master artifact. This worksheet is the integration check before presentation.
Component alignment
Dashboard design
90-day implementation
Presentation plan
Weekly deliverable
Turn the week into working practice.
A capstone operating plan containing an organizational chart, stakeholder map, annual budget overview, staffing forecast, contract-review system, leadership-meeting cadence, executive dashboard, strategic priorities, risk register, and 90-day implementation plan.
- Select and revise the strongest artifacts from Weeks 1–11.
- Resolve conflicting names, definitions, owners, assumptions, and reporting periods.
- Build a dashboard of eight to twelve indicators with definitions, targets, triggers, and actions.
- Map each recurring review to a meeting or governance forum.
- Create a 30/60/90-day implementation sequence that fits real capacity.
- Prepare a ten-minute briefing and request specific decisions or sponsorship.
Every required component is present, definitions and owners align across artifacts, the dashboard is decision-oriented, the cadence is sustainable, the 90-day plan has dependencies and completion evidence, and the briefing makes explicit requests.
Executive questions
Questions worth carrying
- Which eight to twelve indicators would change a decision?
- Where does each indicator get reviewed, by whom, and with what action threshold?
- Which artifact contradicts another or uses a different definition?
- What is the smallest useful operating cadence we can sustain?
- What must be true by day 30, 60, and 90?
Optional AI practice
Use AI as a thinking partner—not a records system.
Protect sensitive information. Do not upload personally identifiable student information, protected student records, confidential personnel information, unredacted contracts, credentials, or sensitive financial information to an AI system without explicit authorization. Follow FERPA, IDEA, district policy, employment-confidentiality duties, contractual restrictions, records rules, and approved data-security procedures.
Week 12 in one sentenceThe capstone is a working management system, not a binder. A small set of aligned roles, measures, meetings, processes, and decisions should make the cooperative easier to understand and operate.