Capstone
Capstone
Full-Cycle Implementation
Capstone Project
Framework and Requirements
The capstone project demonstrates competence in the Discipline of Orchestrated Intelligence. Learners apply the complete A.C.O.R.N. (Assess, Calculate, Orchestrate, Realize, Nurture) methodology to a real organizational opportunity, creating measurable value and documenting the process with enough rigor for independent replication.
Capstone Purpose
The capstone serves four purposes:
1. Prove Independent Competence
Throughout the course, learners developed capabilities with instructor support, peer collaboration, and structured guidance. The capstone removes those scaffolds. Learners execute the methodology alone.
The solo flight after training with an instructor. The capstone proves readiness for independent practice.
2. Apply the Full A.C.O.R.N. Cycle
The course progressed through modules sequentially, building understanding phase by phase. The capstone integrates all five phases into one complete cycle:
- ASSESS: Identify friction and opportunities
- CALCULATE: Build the business case with measured baselines
- ORCHESTRATE: Design the human-AI workflow
- REALIZE: Execute the pilot and validate results
- NURTURE: Establish sustainability for ongoing value
Partial completion disqualifies the submission. The capstone demonstrates mastery of the complete discipline, every phase working together.
3. Create Real Organizational Value
The capstone addresses a genuine organizational need and delivers measurable value. Simulated exercises, theoretical analyses, and hypothetical opportunities do not qualify.
Real value means:
- Time savings measured in reduced hours
- Throughput improvements measured in increased output
- Quality improvements measured in reduced errors
- Stakeholder satisfaction measured in surveys or feedback
The organization should be measurably better because of this project. Professional practice, not academic exercise.
4. Demonstrate Without Hand-Holding
The capstone tests whether learners can navigate ambiguity, make judgment calls, and recover from setbacks without constant guidance. Instructors and mentors answer questions. The work itself is independent.
Success requires:
- Self-directed problem-solving
- Appropriate judgment under uncertainty
- Resilience when plans don't work as expected
- Professional communication with stakeholders
Capstone Requirements
Requirement 1: Select a New Opportunity
The capstone opportunity must be:
New: A different opportunity from R-01, from any course case study, and from any project already in progress before the course began.
Real: An actual organizational need with genuine stakeholders. A live situation, not a hypothetical scenario or simulation.
Yours: An opportunity where the learner has or can obtain authority to implement. Approvals must be realistically attainable.
Rationale: R-01 was guided through the course, so it cannot demonstrate independent capability. A pre-existing project would skip the assessment skills. The capstone requires fresh application of the methodology.
Requirement 2: Execute the Complete Cycle
The capstone requires completion of all five A.C.O.R.N. phases:
| Phase | Minimum Requirements |
|---|---|
| ASSESS | Friction inventory (≥5 friction points documented), opportunity assessment, selection with rationale |
| CALCULATE | Baseline metrics using all three lenses, ROI model with transparent assumptions, business case presentation |
| ORCHESTRATE | Current-state workflow documentation, future-state design with collaboration pattern, implementation blueprint |
| REALIZE | Pilot scope definition, measurement plan, pilot execution, results documentation |
| NURTURE | Sustainability plan including monitoring, ownership, knowledge management |
Each phase produces the deliverables specified in its corresponding module. Quality standards from course materials apply.
Requirement 3: Document All Deliverables
Documentation serves three purposes:
- Evidence of work completed
- Reference for future replication
- Basis for assessment
Documentation requirements:
- All templates completed with actual data
- Narrative explaining methodology application
- Decisions and rationale recorded
- Results compared to projections
- Lessons learned captured
The capstone submission forms a complete package: another practitioner can reference it to understand what was done and why.
Requirement 4: Measure Results Using Three Lenses
Results must be measured using the Module 3 framework:
| Lens | Measurement Required |
|---|---|
| Time | Before/after comparison of time investment per unit of work |
| Throughput | Before/after comparison of volume processed |
| Focus | Before/after assessment of cognitive burden and discretionary time |
Projections from the business case must be compared to actual results. Variance analysis is required. Where results differed from projections, explain why.
Requirement 5: Present to Stakeholders
The capstone includes a formal presentation:
- Duration: 20-30 minutes plus Q&A
- Audience: Organizational stakeholders, peers, evaluators
- Purpose: Communicate value delivered and lessons learned
Presentation is not optional. The discipline includes communication. Practitioners articulate what they did, why it matters, and what they learned.
Selection Criteria for Capstone Opportunity
Select your capstone opportunity with care. These criteria separate viable projects from wasted effort:
Criterion 1: Real Organizational Need
The opportunity addresses a genuine friction point or value gap. Signs of a real need:
- Stakeholders express frustration with current state
- Measurable costs or delays exist
- Previous attempts to address the issue have been made (or desired)
- Resolution would provide visible benefit
Avoid: Pet projects without stakeholder interest. Solutions looking for problems. Opportunities where only the learner cares about the outcome.
Criterion 2: Appropriate Scope
The opportunity must be completable within the capstone timeframe and substantial enough to demonstrate competence.
Too small: Fixing a single spreadsheet formula. Automating one email template. Changes that take hours.
Too large: Enterprise-wide transformation. Multi-year initiatives. Projects requiring dozens of stakeholders.
Right size: Process improvements affecting a team or department. Workflow changes with 3-10 key stakeholders. Initiatives achievable in 8-16 weeks of active work.
Criterion 3: Accessible Stakeholders
The learner must engage stakeholders for:
- Baseline measurement and observation
- Workflow design collaboration
- Pilot participation
- Feedback and evaluation
Avoid: Opportunities where key stakeholders are unavailable, hostile, or behind approvals that will never come.
Criterion 4: Measurable Outcomes
The opportunity produces outcomes that can be measured:
- Time savings quantifiable in hours
- Throughput improvements quantifiable in units
- Quality improvements quantifiable in error rates
- Satisfaction improvements capturable in surveys
Avoid: Purely subjective outcomes resistant to measurement. "Better communication" without specific metrics. "Improved morale" without an assessment mechanism.
Criterion 5: Not Already Solved
The opportunity requires the A.C.O.R.N. methodology. If a simple solution already exists or the problem resolves without systematic intervention, the capstone cannot demonstrate methodology competence.
Avoid: Problems with obvious solutions that bypass the methodology. Issues already being addressed through other means. Opportunities where the difficult work is already finished.
Deliverables Checklist
The complete capstone submission includes:
Module 2 Deliverables: ASSESS
- Friction inventory with ≥5 documented friction points
- Evidence for each friction point (observations, data, stakeholder input)
- Opportunity assessment using strategic value and complexity criteria
- Selection rationale explaining why this opportunity was chosen
- Scope boundaries clearly defined
Module 3 Deliverables: CALCULATE
- Baseline metrics across all three lenses (time, throughput, focus)
- Data collection methodology documented
- ROI model with transparent assumptions
- Sensitivity analysis for key assumptions
- Business case presentation (even if not formally presented during capstone)
- Stakeholder approval documentation (if required by organization)
Module 4 Deliverables: ORCHESTRATE
- Current-state workflow documented (narrative or visual)
- Friction points mapped to workflow steps
- Future-state design with human-AI collaboration pattern identified
- Handoff points and decision authorities specified
- Implementation blueprint with sequence and dependencies
- Stakeholder communication plan
Module 5 Deliverables: REALIZE
- Pilot scope definition (minimum viable scope)
- Pilot timeline and milestones
- Measurement plan aligned with baseline metrics
- Pilot execution log (what happened, what was learned)
- Results documentation with before/after comparison
- Variance analysis (projections vs. actuals)
- Production deployment plan (if applicable)
Module 6 Deliverables: NURTURE
- Monitoring framework with metrics and thresholds
- Ownership structure with RACI for key activities
- Knowledge management plan (documentation, training, succession)
- Lifecycle assessment and management approach
- Sustainability budget and resource allocation
Capstone-Specific Deliverables
- Executive summary (2-3 pages covering entire project)
- Presentation slides
- Peer review response (addressing feedback received)
- Self-assessment (honest evaluation of own work)
- Lessons learned document
Timeline Guidance
Recommended Duration: 12-16 Weeks
The capstone requires sustained effort over an extended period. Compressing it below 8 weeks typically produces superficial work.
Suggested Milestone Schedule
| Week | Milestone | Key Activities |
|---|---|---|
| 1-2 | Opportunity Selected | Screen candidates, select opportunity, obtain stakeholder commitment |
| 3-4 | ASSESS Complete | Conduct friction inventory, document opportunities, confirm selection |
| 5-6 | CALCULATE Complete | Measure baseline, build ROI model, present business case |
| 7-8 | ORCHESTRATE Complete | Design workflow, create blueprint, plan implementation |
| 9-12 | REALIZE Complete | Execute pilot, measure results, document outcomes |
| 13-14 | NURTURE Complete | Create sustainability plan, transition to operations |
| 15-16 | Submission and Presentation | Compile documentation, prepare presentation, present |
Checkpoint Reviews
Optional but recommended checkpoints:
- After Week 4 (ASSESS complete): Confirm opportunity is viable before investing in business case
- After Week 6 (CALCULATE complete): Confirm value justifies continued investment
- After Week 12 (REALIZE complete): Confirm results sufficient for capstone submission
Support Available
During capstone execution, learners may:
- Consult with instructors on methodology questions
- Seek peer input on specific challenges
- Request review of draft deliverables (limited to 1-2 reviews)
Support is consultative. Instructors answer questions. They do not solve problems for learners.
Assessment Criteria
The capstone is assessed on five dimensions:
Dimension 1: Real Work Transformed
Did the capstone create genuine organizational value?
- Evidence of real friction addressed
- Measurable improvement documented
- Stakeholders confirm value delivery
- Results are sustainable, not temporary
Weight: 25%
Dimension 2: Methodology Applied Correctly
Did the capstone follow the A.C.O.R.N. methodology with fidelity?
- All phases completed appropriately
- Deliverables meet quality standards
- Decisions reflect methodology principles
- Adaptations are justified, not arbitrary
Weight: 25%
Dimension 3: Documentation Sufficient
Could another practitioner replicate this work from the documentation?
- All required deliverables present
- Decisions and rationale explained
- Results compared to projections
- Lessons learned captured
Weight: 20%
Dimension 4: Results Measured Appropriately
Were results measured with rigor and honesty?
- Baseline established before intervention
- All three lenses applied
- Variance analyzed and explained
- Limitations acknowledged
Weight: 15%
Dimension 5: Sustainability Planned
Will the value persist after the capstone project ends?
- Monitoring framework established
- Ownership assigned
- Knowledge documented
- Lifecycle appropriate for system stage
Weight: 15%
Capstone Integrity
Academic Integrity
The capstone must be the learner's own work. Collaboration is acceptable during execution with stakeholders and colleagues. Methodology application is individual. The learner demonstrates personal competence.
Prohibited:
- Having someone else complete deliverables
- Submitting work from prior projects not done for this capstone
- Copying from other learners' capstone submissions
- Fabricating results or data
Honest Reporting
Results must be reported honestly, including:
- When projections weren't met
- When pilots failed and required adjustment
- When stakeholders were dissatisfied
- When the learner made mistakes
Honest reporting of challenges and failures is valued. Documented setbacks addressed appropriately carry no penalty. Dishonest representation of results does.
Stakeholder Protection
Learners must:
- Obtain appropriate permissions before including stakeholder information
- Anonymize sensitive data if required by organizational policy
- Not share confidential business information inappropriately
The capstone is a professional work product. Treat organizational and stakeholder information with corresponding care.
What Success Looks Like
A successful capstone demonstrates:
Competence: The learner independently executes the A.C.O.R.N. methodology.
Value Creation: The organization is measurably better because of the work.
Professional Quality: Deliverables meet the standards of professional consulting or internal improvement work.
Learning: The learner articulates what they learned, including from mistakes and challenges.
Sustainability: The value persists beyond the capstone project itself.
A successful capstone is complete, honest, and demonstrates genuine capability development. Perfection is beside the point.
The capstone marks the transition from learner to practitioner. Approach it as a professional engagement. The organization you serve and the stakeholders you work with are real. Deliver value worthy of their investment in your learning.
Capstone Project
Templates and Examples
This document provides templates for capstone project management and an abbreviated example demonstrating expected quality and completeness.
Template 1: Capstone Proposal
Submit this proposal before beginning capstone execution. Approval required before proceeding.
Capstone Proposal Form
Learner Name: _______________
Date Submitted: _______________
Organization: _______________
Proposed Start Date: _______________
Proposed Completion Date: _______________
Section 1: Opportunity Description
Opportunity Title: (Give your capstone opportunity a clear, descriptive name)
Organizational Context: (2-3 sentences describing the organization, department, or team where this opportunity exists)
The Problem: (3-5 sentences describing the friction, inefficiency, or value gap you intend to address. Be specific about the current breakdown and who is affected.)
Preliminary Friction Points: (List 3-5 initial friction points you have observed or hypothesize. These will be validated and expanded during ASSESS phase.)
Section 2: Strategic Rationale
Why This Opportunity? (Explain why you selected this opportunity over others. Reference selection criteria: real need, appropriate scope, accessible stakeholders, measurable outcomes.)
Strategic Alignment: (How does this opportunity connect to organizational priorities? Why would stakeholders invest in addressing it?)
Preliminary Value Estimate: (Rough estimate of potential value. This will be refined in CALCULATE phase. Include basis for estimate.)
- Estimated annual value: $_______________
- Primary value driver: ☐ Time savings ☐ Throughput increase ☐ Quality improvement ☐ Other: _______
- Confidence level: ☐ High ☐ Medium ☐ Low
Section 3: Scope and Timeline
Scope Boundaries:
| In Scope | Out of Scope |
|---|---|
Key Stakeholders:
| Name | Role | Relationship to Opportunity | Engagement Level Needed |
|---|---|---|---|
Proposed Timeline:
| Phase | Start Week | End Week | Key Milestones |
|---|---|---|---|
| ASSESS | |||
| CALCULATE | |||
| ORCHESTRATE | |||
| REALIZE | |||
| NURTURE | |||
| Documentation & Presentation |
Total Duration: _____ weeks
Section 4: Success Criteria
How will you know this capstone succeeded?
| Metric | Current State | Target | Measurement Method |
|---|---|---|---|
Minimum Viable Success: (What is the minimum outcome that would make this capstone acceptable? Be honest about the floor.)
Section 5: Risk Assessment
Top 3 Risks to Capstone Success:
| Risk | Likelihood (H/M/L) | Impact (H/M/L) | Mitigation Strategy |
|---|---|---|---|
| 1. | |||
| 2. | |||
| 3. |
Contingency Plan: (If this opportunity becomes unviable mid-execution, what is your backup plan?)
Section 6: Commitment
Time Commitment: (Estimate hours per week you will dedicate to capstone work)
- Phase 1-2 (ASSESS/CALCULATE): _____ hours/week
- Phase 3-4 (ORCHESTRATE/REALIZE): _____ hours/week
- Phase 5 (NURTURE): _____ hours/week
- Documentation/Presentation: _____ hours/week
Stakeholder Commitment: (Have key stakeholders agreed to participate? List any pending commitments.)
| Stakeholder | Commitment Obtained | Date | Notes |
|---|---|---|---|
| ☐ Yes ☐ Pending | |||
| ☐ Yes ☐ Pending |
Authority Confirmation: (Do you have or can you obtain authority to implement changes in this area?)
☐ I have authority to implement ☐ I have authority contingent on business case approval ☐ I need to obtain authority (explain plan below)
Approval
Learner Signature: _______________ Date: _______________
Instructor Review:
☐ Approved — Proceed with capstone execution ☐ Approved with modifications — See notes below ☐ Not approved — Revise and resubmit
Instructor Notes:
Instructor Signature: _______________ Date: _______________
Template 2: Progress Report
Submit progress reports at designated checkpoints (typically after ASSESS and after CALCULATE).
Capstone Progress Report
Learner Name: _______________
Report Date: _______________
Checkpoint: ☐ After ASSESS ☐ After CALCULATE ☐ After REALIZE ☐ Other: _______
Section 1: Current Status
Overall Status: ☐ On Track ☐ Minor Delays ☐ Significant Concerns ☐ At Risk
Phase Completion Status:
| Phase | Status | Completion % | Notes |
|---|---|---|---|
| ASSESS | ☐ Not Started ☐ In Progress ☐ Complete | ___% | |
| CALCULATE | ☐ Not Started ☐ In Progress ☐ Complete | ___% | |
| ORCHESTRATE | ☐ Not Started ☐ In Progress ☐ Complete | ___% | |
| REALIZE | ☐ Not Started ☐ In Progress ☐ Complete | ___% | |
| NURTURE | ☐ Not Started ☐ In Progress ☐ Complete | ___% |
Section 2: Accomplishments Since Last Report
Deliverables Completed: (List specific deliverables finished since last report or since project start)
Key Findings: (Summarize important discoveries, insights, or data gathered)
Stakeholder Engagement: (Who have you engaged? What was the outcome?)
Section 3: Challenges
Current Obstacles:
| Challenge | Impact | Status | Resolution Plan |
|---|---|---|---|
Scope Changes: (Has scope expanded, contracted, or shifted? If yes, explain and justify.)
Timeline Adjustments: (Are you ahead, behind, or on schedule? If behind, what's the recovery plan?)
Section 4: Next Steps
Planned Activities for Next Period:
| Activity | Target Completion | Dependencies |
|---|---|---|
Upcoming Risks: (What risks are you monitoring for the next phase?)
Section 5: Support Needed
Questions for Instructor: (What guidance or clarification would help you proceed?)
Resources Needed: (Are there resources, access, or support you need that you don't have?)
Peer Input Requested: (Would peer feedback on specific elements be helpful? Specify what.)
Section 6: Self-Assessment
Confidence Level:
| Dimension | Confidence (1-5) | Notes |
|---|---|---|
| Methodology application | ||
| Stakeholder engagement | ||
| Data quality | ||
| Timeline achievability | ||
| Value delivery |
Biggest Learning So Far: (What have you learned about the methodology or yourself?)
Biggest Concern: (What worries you most about completing this capstone successfully?)
Learner Signature: _______________ Date: _______________
Template 3: Final Submission Checklist
Complete this checklist before final submission. Every item must be checked.
Capstone Final Submission Checklist
Learner Name: _______________
Submission Date: _______________
Opportunity Title: _______________
Section 1: Deliverables Present
Module 2: ASSESS
| Deliverable | Present | Quality Reviewed |
|---|---|---|
| Friction inventory (≥5 points with evidence) | ☐ | ☐ |
| Opportunity assessment with criteria | ☐ | ☐ |
| Selection rationale document | ☐ | ☐ |
| Scope boundaries defined | ☐ | ☐ |
| Stakeholder analysis | ☐ | ☐ |
Module 3: CALCULATE
| Deliverable | Present | Quality Reviewed |
|---|---|---|
| Time lens baseline metrics | ☐ | ☐ |
| Throughput lens baseline metrics | ☐ | ☐ |
| Focus lens baseline assessment | ☐ | ☐ |
| Data collection methodology documented | ☐ | ☐ |
| ROI model with calculations | ☐ | ☐ |
| Assumptions documented with sources | ☐ | ☐ |
| Sensitivity analysis | ☐ | ☐ |
| Business case presentation | ☐ | ☐ |
Module 4: ORCHESTRATE
| Deliverable | Present | Quality Reviewed |
|---|---|---|
| Current-state workflow documented | ☐ | ☐ |
| Friction points mapped to workflow | ☐ | ☐ |
| Future-state workflow design | ☐ | ☐ |
| Collaboration pattern identified and justified | ☐ | ☐ |
| Handoff points and decision authorities | ☐ | ☐ |
| Implementation blueprint | ☐ | ☐ |
| Stakeholder communication plan | ☐ | ☐ |
Module 5: REALIZE
| Deliverable | Present | Quality Reviewed |
|---|---|---|
| Pilot scope definition | ☐ | ☐ |
| Pilot timeline and milestones | ☐ | ☐ |
| Measurement plan | ☐ | ☐ |
| Pilot execution log | ☐ | ☐ |
| Results documentation (all three lenses) | ☐ | ☐ |
| Before/after comparison | ☐ | ☐ |
| Variance analysis with explanation | ☐ | ☐ |
| Production deployment plan (if applicable) | ☐ | ☐ |
Module 6: NURTURE
| Deliverable | Present | Quality Reviewed |
|---|---|---|
| Monitoring framework with metrics | ☐ | ☐ |
| Thresholds and response triggers | ☐ | ☐ |
| Review cadence defined | ☐ | ☐ |
| RACI for key activities | ☐ | ☐ |
| Knowledge management plan | ☐ | ☐ |
| Lifecycle stage assessment | ☐ | ☐ |
| Sustainability budget/resources | ☐ | ☐ |
Capstone-Specific
| Deliverable | Present | Quality Reviewed |
|---|---|---|
| Executive summary (2-3 pages) | ☐ | ☐ |
| Presentation slides | ☐ | ☐ |
| Lessons learned document | ☐ | ☐ |
| Self-assessment completed | ☐ | ☐ |
| Peer review response (if applicable) | ☐ | ☐ |
Section 2: Documentation Quality
| Quality Criterion | Confirmed |
|---|---|
| All documents are clearly labeled and organized | ☐ |
| Navigation is clear (table of contents or index) | ☐ |
| Decisions include rationale ("why," not just "what") | ☐ |
| Data sources are cited | ☐ |
| Limitations are acknowledged | ☐ |
| Another practitioner could replicate from this documentation | ☐ |
Section 3: Results Integrity
| Integrity Check | Confirmed |
|---|---|
| Baseline measurements use consistent methodology | ☐ |
| Results measurements use same methodology as baseline | ☐ |
| Comparison is mathematically correct | ☐ |
| Variances are explained honestly | ☐ |
| Setbacks and challenges are documented | ☐ |
| No data has been fabricated or manipulated | ☐ |
Section 4: Presentation Readiness
| Presentation Element | Ready |
|---|---|
| Slides complete (10-12 slides) | ☐ |
| Slides are visually clear and professional | ☐ |
| Timing rehearsed (20-25 minutes) | ☐ |
| Q&A preparation complete | ☐ |
| Technology tested (if presenting remotely) | ☐ |
Section 5: Administrative
| Administrative Item | Complete |
|---|---|
| Stakeholder permissions obtained for including their information | ☐ |
| Confidential data anonymized if required | ☐ |
| File naming convention followed | ☐ |
| All files submitted in required format | ☐ |
Submission Confirmation
I confirm that:
☐ All deliverables are complete and present
☐ All work is my own (execution may involve others; methodology application is mine)
☐ Results are reported honestly, including setbacks and failures
☐ I have not fabricated data or misrepresented outcomes
☐ I have obtained necessary permissions for stakeholder information
Learner Signature: _______________ Date: _______________
Template 4: Example Capstone Summary
The following abbreviated example demonstrates expected quality and completeness. It illustrates the depth, rigor, and honesty expected in capstone work, though the actual submission would be more comprehensive.
Example Capstone: Clinical Documentation Improvement at Riverside Medical Group
Practitioner: Dr. Maria Santos
Organization: Riverside Medical Group (12-physician primary care practice)
Duration: 14 weeks
Executive Summary
Riverside Medical Group's clinical documentation process consumed an average of 2.3 hours daily per physician. That time reduced patient volume and contributed to physician burnout. A friction inventory identified documentation as the highest-impact improvement opportunity. The business case projected $286,000 in annual value through time recovery and throughput improvement.
The pilot implementation introduced AI-assisted documentation for three physicians over eight weeks. Actual results achieved 78% of projected value: 1.7 hours daily time savings per physician (vs. 2.0 projected), with documentation quality scores improving 23% (vs. 15% projected). Variance analysis identified training intensity as the primary factor affecting adoption speed.
The solution is now deployed to all 12 physicians with a sustainability framework including monthly quality audits, quarterly physician feedback sessions, and annual workflow review. First-year realized value is projected at $223,000.