Appendix M: Capstone Project Rubrics and Evaluation Criteria
Introduction
Rubrics serve two purposes that are easy to confuse. The first is evaluation: rubrics give evaluators a consistent framework for assessing work. The second — and more important for learning — is communication: rubrics tell students exactly what excellent work looks like before they produce it, which dramatically increases the probability that they will produce it.
These rubrics are designed to be read before you begin your capstone project, not after you submit it. If you read a rubric after the fact, it becomes a verdict. If you read it before, it becomes a blueprint. Use it as a blueprint.
This appendix provides full evaluation frameworks for all three capstone projects:
- Capstone 1: Launch Plan — Design a Creator Business from Zero
- Capstone 2: Monetization Audit
- Capstone 3: Scale Strategy
Each rubric is accompanied by a scoring guide, notes on common mistakes, and guidance for borderline cases. Following the individual rubrics, you will find a Peer Review Guide (for peer review processes) and Instructor Notes (for classroom and course adaptation).
These rubrics can be used in three modes:
Self-assessment: Before submitting your capstone, rate yourself honestly on each rubric category. Identify where you are at a 2 when you could reach a 3 or 4, and revise accordingly. Self-assessment before submission has been shown to significantly improve final project quality.
Peer review: Structured peer review using these rubrics gives the reviewer as much learning value as the creator of the work being reviewed. Use the Peer Review Guide in the final section for protocol.
Instructor evaluation: These rubrics provide the full framework for formal course grading when used in an academic setting. See Instructor Notes for adaptation guidance.
General Evaluation Philosophy
What These Capstones Are Designed to Test
These capstones do not test your ability to remember information. The textbook's 41 chapters and their associated quizzes cover that. Capstones test your ability to apply concepts to real or realistic situations — to take frameworks and tools and use them to make actual decisions, design actual systems, and produce actual plans.
This distinction matters for how you approach the work. A capstone answer that accurately summarizes what the ACOS framework is will score lower than one that actually applies it to a specific platform choice with genuine reasoning. A capstone that correctly identifies that creators face equity challenges will score lower than one that names a specific structural barrier, explains its mechanism, and proposes a concrete response.
The capstones reward specificity, research, and action-orientation.
The Three Dimensions of Quality
Specificity is the first test of quality. Vague answers are almost always weaker than specific ones, not because specificity is a stylistic preference but because vague answers reveal that the student has not actually worked the problem. "I would use a multi-platform strategy" is vague. "I would use YouTube as my primary distribution platform and Instagram Reels for discovery, based on the following reasoning about where my target audience spends time and my own production capacity..." is specific. The second answer demonstrates thinking. The first merely references it.
Research is the second dimension. Capstones that consist entirely of the student's opinions and intuitions are weaker than those grounded in evidence — market research, audience data, competitor analysis, financial modeling, or documented case studies. You are not required to conduct primary research for these capstones, but you are expected to engage with available evidence rather than substituting assertion for analysis.
Action-orientation is the third dimension. A plan that cannot be executed is not a plan — it is a wish. Capstone projects are evaluated in part on whether the plans they describe are implementable by a real person with the resources and constraints the student has described. Ambitious but unachievable plans score lower than modest but executable ones. This does not mean you should aim low — it means you should be honest about what you can actually do and design a plan accordingly.
The Equity Integration Requirement
Every capstone project requires demonstrated engagement with equity — with the structural barriers that affect creators from marginalized communities, the representation gaps in the creator economy, and the design choices that either replicate or resist those barriers. This requirement is not a box to check. It is an analytical dimension that applies to every aspect of creator business design.
Equity integration at the lowest level is tokenistic: "I will make sure to be inclusive in my content." Equity integration at the highest level is structural: "The following specific barriers affect creators from my target community and/or affect my target audience; here is how my business design specifically addresses them; here is how my revenue model avoids or reduces dependence on systems that discriminate; here is what I am still uncertain about and why."
The difference between tokenistic and structural equity engagement is the difference between noting that a problem exists and taking responsibility for engaging with it seriously in your own work.
Capstone 1 Rubric: Launch Plan — Design a Creator Business from Zero
Overview
Capstone 1 asks you to design a complete creator business launch plan for yourself (or for a clearly specified hypothetical creator persona). The plan covers niche and audience definition, platform strategy, content system, and revenue model design. It is evaluated in five categories.
Rubric Table
| Category | 4 — Excellent | 3 — Proficient | 2 — Developing | 1 — Beginning |
|---|---|---|---|---|
| Niche and Audience Specificity | Niche is narrowly and precisely defined, with market validation data drawn from keyword research, competitor analysis, or audience surveys. Audience persona is richly detailed — demographics, psychographics, specific pain points, content consumption habits. Clear differentiation from at least three named competitors, with specific explanation of what the proposed creator offers that those competitors do not. | Niche is clearly defined with some supporting evidence; it is specific enough to be actionable. Audience persona is reasonably detailed with demographics and basic psychographic information. Differentiation from competitors is identified and briefly supported but not rigorously analyzed. | Niche is broader than optimal or defined without supporting evidence — it could describe many creators. Audience persona exists but lacks specificity; generic characteristics rather than a portrait of a real person. Differentiation from competitors is mentioned but described in generic terms that could apply to any creator in the space. | Niche is vague or essentially undefined ("I will create content about finance/fitness/food"). No meaningful audience persona. No competitive analysis of the existing landscape. No differentiation strategy. |
| Platform Strategy Coherence | Platform selection is rigorously justified using the ACOS (Audience, Content, Objectives, Skills) framework or equivalent reasoning process. Hub-and-spoke content distribution plan is fully detailed: primary platform specified with content format plan, secondary distribution channels identified with specific repurposing strategy. 90-day content calendar is complete, varied across formats, and realistic given stated production capacity. | Platform selection is justified with clear reasoning, though the supporting analysis may not be comprehensive. Content distribution plan covers primary and secondary channels. 90-day calendar is mostly complete with occasional gaps or underspecified elements. | Platform is selected but the reasoning is underdeveloped — the choice appears intuitive rather than analytical. Content plan covers the primary platform but secondary distribution is vague or absent. Calendar covers some weeks but has significant gaps or unrealistic elements. | Platform is named but not justified. No content distribution system evident — just a list of things to post. Calendar is absent, skeletal, or entirely aspirational with no consideration of production constraints. |
| Revenue Model Design | Three or more distinct revenue streams are proposed, with realistic revenue projections for each, grounded in market data or documented comparables. Clear sequencing logic: which revenue stream to pursue first and why, how each stream is unlocked by the one before it. Digital product idea (course, membership, template, etc.) is highly specific — transformation promised, format described, price justified, target audience for the product named and distinguished from the broader audience. | Revenue model includes at least two revenue streams with basic projections. Sequencing logic is present, if not deeply analyzed. Product idea is identified and the transformation is reasonably clear, though price justification may be underdeveloped. | Single revenue stream is proposed, or multiple streams with no projections or sequencing. Product idea is vague — topic is named but format, price, and specific transformation are not addressed. | No coherent revenue model. Assumes revenue from advertising or "sponsorships" without addressing how these are earned or what they would require in terms of audience size and engagement. No product idea. |
| Equity Integration | Two or more specific structural barriers are identified for the proposed creator's community (if applicable) AND/OR for the intended audience — with clear explanation of the mechanisms through which these barriers operate. Concrete, actionable responses are proposed for each barrier identified: specific design choices, partnerships, platform decisions, or pricing strategies that directly address those barriers. Demonstrates familiarity with the relevant literature or documented examples. | Some structural barriers are identified for creator and/or audience. Proposed responses exist and are relevant, but are described in general rather than specific terms (e.g., "I will be accessible" rather than "I will offer a payment plan and a reduced-price community tier for people with financial constraints"). | An equity section is present but operates at the surface level — acknowledges that inequality exists without engaging with the specific mechanisms relevant to the niche and audience. No concrete response proposed. | Equity section is entirely absent, or present in a way that is purely tokenistic — a sentence or two at the end that does not engage with the substance of the requirement. |
| Feasibility and Actionability | Every element of the plan is executable given the creator's explicitly stated resources (time, money, skills, equipment). Timeline from Day 1 to first revenue is realistic. Success metrics for the first 90 days and first year are specific and measurable (not "grow my audience" but "reach 500 email subscribers by Day 90"). The plan includes contingency for at least one likely obstacle. | Plan is mostly executable. Minor elements may be unrealistic given stated constraints but do not undermine the overall plan. Success metrics are present, if not fully specific. | Significant elements of the plan are not actionable given the stated resources — the plan implicitly assumes tools, time, capital, or skills the creator does not have. Timeline is vague. Success metrics are aspirational rather than measurable. | Plan is aspirational throughout — it describes outcomes without a credible path to achieving them. No consideration of actual resource constraints. No timeline. No measurable success metrics. |
Scoring Guide
| Score Range | Interpretation | Recommended Action |
|---|---|---|
| 18–20 | Pass with Distinction | Work demonstrates comprehensive mastery of creator business design. Suitable for portfolio use. |
| 14–17 | Pass | Work demonstrates solid command of core concepts with areas for development identified. |
| 10–13 | Revise and Resubmit | Work shows foundational understanding but significant gaps in application. Specific revision guidance from evaluator required. |
| Below 10 | Needs Significant Revision | Work does not yet demonstrate sufficient application of course concepts. Consider additional study before resubmission. |
Common Mistakes in Capstone 1
Mistake 1: Defining the niche as a topic rather than a position. "Personal finance" is a topic. "Personal finance for first-generation college graduates navigating student debt and early wealth building" is a niche. The difference is that a niche implies a specific audience with specific needs and a specific type of creator who can credibly serve them.
Mistake 2: Building a platform strategy without acknowledging production constraints. Many students design beautiful multi-platform strategies that would require 40+ hours of content production per week. Always specify how much time you can realistically dedicate to content creation, then design a strategy that fits within that constraint.
Mistake 3: Pricing the first product too low. Many students default to $27 or $47 for their first digital product. The textbook's analysis of pricing psychology and perceived value is directly relevant here. Low prices are not generous — they are a signal about the value of the product. Justify your price with reasoning.
Mistake 4: Treating equity integration as a separate section rather than as an integrated dimension. Equity thinking is most powerful when it shows up in the niche definition, the platform choice, the revenue model design, and the product pricing — not just in a standalone paragraph at the end.
Capstone 2 Rubric: Monetization Audit
Overview
Capstone 2 asks you to conduct a comprehensive monetization audit of an existing creator business — either your own (Option A) or a publicly documented creator case (Option B). The audit assesses current revenue streams, diagnoses gaps and vulnerabilities, and proposes a redesigned revenue stack. Python analysis using the Monte Carlo simulation framework from Chapter 20 is optional but eligible for evaluation as a fifth category.
Rubric Table
| Category | 4 — Excellent | 3 — Proficient | 2 — Developing | 1 — Beginning |
|---|---|---|---|---|
| Audit Completeness | All revenue streams are documented with accurate or well-researched estimates; each stream includes estimated monthly revenue, revenue concentration percentage, and margin assessment. Revenue concentration is calculated (percentage of total revenue from largest stream) and correctly interpreted as a risk factor. The single biggest monetization vulnerability is clearly identified with specific reasoning. | Most revenue streams are documented with estimates; some gaps exist but they are acknowledged. Revenue concentration is calculated. Primary vulnerability is identified, if not fully analyzed. | Audit is partial — one or more significant revenue streams are missing or substantially misrepresented. Revenue concentration is mentioned but not calculated. Vulnerability identification is vague. | Audit is incomplete or superficial — only one or two revenue streams addressed, or revenue figures are entirely absent. No vulnerability analysis. |
| Metrics Analysis Quality | Current metrics are correctly identified and distinguished from optimal metrics for the creator's stage and strategy. Funnel analysis is specific: traffic sources quantified, conversion rates at each stage estimated and benchmarked against documented norms, email list-to-purchase conversion analyzed. Bottlenecks are correctly identified — the specific point in the funnel where audience is lost at the highest rate — with evidence for the diagnosis. | Metrics analysis is present and mostly accurate. Some gaps in funnel analysis — one or two conversion points not addressed. Bottlenecks identified with some specificity. | Partial metrics analysis — some metrics discussed but without a coherent funnel framework. The relationship between different metrics (subscriber count, email open rate, conversion rate) is not fully analyzed. | Minimal metrics engagement — the audit lists some numbers without analytical framework. No funnel analysis. |
| Redesign Quality | Revenue stack redesign is both creative and feasible — it proposes meaningful changes to the current revenue mix that are justified by the audit findings. Revenue projections for the redesigned stack are realistic and grounded in documented comparables or modeling. The improvement in revenue diversification (reduction in concentration risk) is explicitly calculated and meaningful. New revenue streams are specifically described — not just "add a course" but course topic, target price, estimated audience conversion rate, and projected launch revenue. | Redesign is present with basic projections. The connection between audit findings and redesign decisions is visible. Some new streams are specifically described. Diversification improvement is addressed if not fully quantified. | Partial redesign — some changes proposed but the logic connecting audit findings to redesign choices is unclear. Projections are absent or unrealistic. Diversification improvement is not calculated. | No meaningful redesign. The student acknowledges problems identified in the audit without proposing substantive changes, or proposes changes without justification or specificity. |
| Python Analysis (Optional — scored if attempted) | Python analysis using the Monte Carlo framework is correctly implemented — model parameters are chosen thoughtfully and justified; simulation runs the correct number of iterations; output is correctly interpreted. Plain-language summary of what the Monte Carlo output means for the creator's actual business decision-making is accurate and useful. Results are correctly integrated into the redesign recommendations. | Python analysis is attempted and mostly correct. Minor errors in implementation or interpretation that do not substantially change the conclusions. Integration with redesign is present. | Python analysis is attempted with significant errors in implementation (wrong parameters, misinterpreted output) that affect the conclusions. Interpretation is partially correct. | Python analysis not attempted, or attempted in a way that produces clearly erroneous results that are accepted without critical examination. |
| Equity Dimension | A specific structural barrier that affects the creator's monetization is correctly identified — not a general observation about inequality but a specific mechanism (e.g., advertiser rate discrimination, platform moderation disparities, audience demographic effects on brand deal rates). A revenue strategy that specifically reduces dependence on that discriminatory system is proposed and is concrete and executable (e.g., "shift from AdSense to direct memberships, which bypasses advertiser CPM discrimination"). | Equity dimension is identified and a proposed strategy is present but the strategy is described in general rather than specific terms. The connection between the identified barrier and the proposed revenue strategy is present but not fully developed. | Equity dimension is present in the audit — a barrier is acknowledged — but it does not meaningfully influence the redesign recommendations. | Equity dimension is entirely absent from the audit, or present in a single generic sentence that does not engage with the specific situation being analyzed. |
Scoring Guide
| Score Range | Interpretation | Recommended Action |
|---|---|---|
| 18–20 (or 22–24 with Python) | Pass with Distinction | Demonstrates sophisticated analytical capability. Strong portfolio piece. |
| 14–17 (or 17–21 with Python) | Pass | Solid analytical work with some areas for deepening. |
| 10–13 (or 12–16 with Python) | Revise and Resubmit | Audit framework is present but application is incomplete. Specific revision guidance required. |
| Below 10 | Needs Significant Revision | Audit does not yet demonstrate sufficient command of monetization analysis frameworks. |
Common Mistakes in Capstone 2
Mistake 1: Auditing income without auditing concentration. Many students list revenue streams and estimate monthly figures without calculating what percentage of total revenue each stream represents. Concentration risk — having 70%+ of revenue from a single platform or stream — is the central vulnerability most creator businesses face. Calculate the percentages.
Mistake 2: Conflating follower count with monetizable audience. The relationship between a creator's total follower count and their email list, membership count, or course enrollment is almost never 1:1. The funnel analysis requires you to trace the conversion from platform followers to email subscribers to paying customers. This funnel is where the real diagnostic information lives.
Mistake 3: Proposing redesigns without connecting them to audit findings. A good redesign is motivated by specific vulnerabilities the audit reveals. "Add a membership" is not a redesign — it is a suggestion. "Add a membership to diversify away from AdSense revenue, which currently represents 84% of total revenue and is subject to CPM fluctuations that caused a 40% revenue drop in Q3" is a redesign grounded in evidence.
Mistake 4: Treating the Python analysis as an add-on rather than an input. The Monte Carlo simulation is most useful when its outputs genuinely inform the redesign — when the risk range it reveals changes which recommendation the student makes. If the Python analysis is accurate but doesn't affect any recommendation in the redesign, it is an exercise in calculation, not an exercise in decision-making.
Capstone 3 Rubric: Scale Strategy
Overview
Capstone 3 asks you to design a comprehensive three-year scale strategy for a creator business — either your own (Option A) or a documented case (Option B). The strategy covers vision, Year 1 operational plan, Years 2–3 strategic plan, a 36-month financial model, organizational charts for each stage, and an equity audit of the full strategy. This is the most comprehensive capstone and is evaluated in six categories.
Rubric Table
| Category | 4 — Excellent | 3 — Proficient | 2 — Developing | 1 — Beginning |
|---|---|---|---|---|
| Vision Clarity and Ambition | Three-year vision is specific, distinctive, and compelling — it describes a particular kind of creator business with enough detail that it could not apply to any other creator in the space. The legal and operational form of the business (sole proprietor, LLC, S-Corp, team size, etc.) is clearly articulated and its selection is justified. Personal motivation for building this specific kind of business at this particular scale is explained with honesty and specificity, connecting the creator's values to their strategic choices. | Vision is clear and the business form is identified. Personal motivation is present. The vision is somewhat generic but is specific enough to provide directional guidance for the plan. | Vision is vague or aspirational without operational specificity — describes outcomes ("become a major creator in the personal finance space") without describing what the business would actually look like or how it would operate. | No clear vision articulated. Plan proceeds without a guiding destination. Business form not addressed. |
| Year 1 Operational Rigor | Revenue targets are specific and broken down by month, not just stated annually; targets reflect seasonal patterns where relevant and are grounded in baseline performance. Team and contractor plan is specific: names of roles (not just "I will hire someone for social media"), expected hours, estimated costs, and the reasoning for hire-vs.-contract decisions for each role. Legal and financial infrastructure plan (LLC formation, business banking, accounting system, insurance) is concrete with estimated costs and timeline. | Year 1 plan is mostly specific. Monthly revenue targets present, if not always individually justified. Team plan identifies roles with some reasoning. Legal/financial infrastructure addressed. Some elements underspecified but the overall plan is coherent. | Year 1 plan exists but lacks specificity in one or more major areas. Revenue targets are annual rather than monthly. Team needs are acknowledged without specific planning. | No coherent Year 1 operational plan — the three-year strategy begins in Year 2 or 3 without establishing a foundation. |
| Years 2–3 Strategic Coherence | Years 2 and 3 plans build demonstrably and logically from Year 1 outcomes — each year's strategy is conditional on the previous year's achievements, with explicit connections drawn. The chosen scaling move (team growth, product expansion, licensing, acquisition of audience, etc.) is rigorously justified by the Year 1 trajectory rather than assumed. Burnout prevention plan is specific: identified risk factors, specific structural protections (content buffer, staff coverage, sabbatical schedule), and criteria for knowing when the plan needs adjustment. | Multi-year plan is present and shows logical progression. Scaling move is identified and justified, if not exhaustively. Burnout prevention is addressed. Some logical gaps in the year-to-year progression. | Plan covers multiple years but progression is not clearly logical — Year 2 might be achievable from Year 1, or might not be, without adequate analysis. Burnout prevention is mentioned but not specifically designed. | Only Year 1 is addressed in any detail. Years 2 and 3 are aspirational or absent. |
| Financial Model Quality | 36-month financial model is realistic and internally consistent — revenue growth rates are justified by stage (faster early growth from a small base, decelerating as the business matures), expense forecast is specific and includes the often-omitted items (self-employment tax, health insurance, equipment depreciation, contractor costs). Key financial milestones are calculated and presented clearly: month of first profit, month of financial runway target achieved, month at which a specific hire becomes feasible. | Financial model covers all 36 months with most revenue and expense categories addressed. Growth assumptions are broadly realistic. Some minor unrealistic assumptions (e.g., omitted self-employment tax, understated contractor costs) that do not fundamentally undermine the model. Key milestones are addressed. | Partial financial model — covers some months or some revenue/expense categories but has significant gaps. Growth assumptions may be unrealistic (hockey-stick projections without justification, or flat projections that ignore demonstrated traction). | No financial model, or a model consisting only of annual top-line revenue projections without expense forecasting or milestone identification. |
| Org Chart and Roles | Three distinct org charts are presented — showing team structure at Year 1 end, Year 2 end, and Year 3 end — with clear visual representation of reporting relationships and role boundaries. Hire-vs.-contractor decisions are explicitly justified for each role with reasoning that engages with the tradeoffs (cost, control, flexibility, legal obligations). Specific role descriptions for each planned position or contractor include the core responsibilities, expected time commitment, and evaluation criteria. | All three org charts are present and show meaningful evolution across the three years. Role justifications are present for most positions. Role descriptions may be somewhat generic. | Org charts are present but static — they do not evolve meaningfully across the three-year period, suggesting insufficient thinking about how the team grows in response to revenue and operational needs. Role descriptions are minimal. | Org charts are absent, or only one is provided. No role descriptions. No reasoning for staffing decisions. |
| Equity Audit | All five recurring equity themes from the textbook are explicitly audited against the scale strategy: (1) platform moderation disparities, (2) advertiser rate discrimination, (3) representation gaps in creator support programs and funding, (4) parasocial dynamics shaped by creator identity, and (5) audience demographic access barriers. For each theme, the audit identifies whether the scale strategy has a vulnerability and what the strategy does (or should do) to address it. Equity commitments are specific and embedded in the business model — they show up in revenue design, hiring, product pricing, and platform choices — not only in a separate "diversity" section. | At least four of the five recurring themes are addressed. Equity commitments are present and partially embedded in business model decisions, though the integration may be more thorough in some areas than others. | The equity audit addresses two or three themes with varying depth. The connection between equity analysis and actual business model choices is present in at least one area. | Equity audit is absent, or consists of a brief acknowledgment that equity matters without engagement with the specific themes and their application to the strategy being designed. |
Scoring Guide
| Score Range | Interpretation | Recommended Action |
|---|---|---|
| 22–24 | Pass with Distinction | Demonstrates exceptional strategic thinking and business design capability. |
| 17–21 | Pass | Solid strategic plan with clear command of scale strategy frameworks. |
| 12–16 | Revise and Resubmit | Strategic plan has foundational strengths but significant gaps in one or more categories. |
| Below 12 | Needs Significant Revision | Plan does not yet demonstrate sufficient integration of scale strategy frameworks. |
Common Mistakes in Capstone 3
Mistake 1: Treating the three-year plan as three separate one-year plans. The most important feature of a coherent multi-year plan is that each year's strategy is conditional on the previous year. Year 2 should only be possible if Year 1 succeeds — and if Year 1 does not fully succeed, the plan should address what happens instead.
Mistake 2: Building a financial model without expense forecasting. Many students model revenue without modeling expenses, which produces projections that show infinite profitability. Self-employment tax (15.3% on net earnings), health insurance ($400–$700/month without employer contribution), and software subscriptions alone can add $20,000+ to annual business costs. Model expenses with the same rigor as revenue.
Mistake 3: Designing an org chart without addressing who manages whom. A list of job titles is not an org chart. An org chart shows reporting relationships, communication flows, and decision authorities. Who reviews the video editor's work? Who approves brand deal contracts? Who manages the community manager? These questions have real operational consequences.
Mistake 4: Producing an equity audit that exists only in the "equity section." The equity requirement is met when equity thinking shows up throughout the strategy — in the decision not to depend on AdSense, in the tiered pricing structure that makes courses accessible at different income levels, in the hiring decisions that build a team whose composition matches the community it serves. A separate equity audit section is the floor, not the ceiling.
Mistake 5: Burnout planning that amounts to "I will take breaks." Burnout prevention requires structural design: specific content buffer targets (you will maintain X weeks of content in advance), specific coverage plans (person Y will monitor community if you are unavailable), and specific criteria for activating recovery protocols. "I will be mindful about my work-life balance" is not a plan.
Peer Review Guide
What Peer Review Is For
Peer review serves two parties equally. The student receiving feedback gets a perspective on their work that is outside their own frame of reference — often catching things they are too close to see. The student giving feedback, in the process of evaluating someone else's work against the rubric, consolidates their own understanding of what excellent work looks like. Research on peer review consistently shows that reviewers learn as much from the process as reviewees.
Peer review is not grading. You are not determining whether your peer's work passes or fails — that is the evaluator's role. Your role is to make the work better. Approach it with that purpose, and your feedback will be more useful.
The Two Stars and a Wish Model
For each capstone, structure your feedback around two specific strengths and one specific improvement opportunity:
Two stars: Identify two specific things the submission does well. "Your equity section" is not specific. "Your equity section correctly identifies the CPM discrimination mechanism and proposes a concrete pivot to direct membership as a response — this is exactly the kind of structural analysis the rubric asks for" is specific. The more specific your praise, the more useful it is, because it tells the author exactly what to protect in their revision.
A wish: Identify one specific improvement opportunity. "I wish the financial model were more detailed" is not specific. "I wish the financial model included expense forecasting — specifically, the contractor costs in Year 2 appear to be understated. Looking at current market rates for podcast editors (approximately $75–$150/hour), the three episodes per month at your planned production scale would likely cost $1,800–$3,600/month, not the $500/month you've projected" is specific. A specific wish gives the author something they can act on immediately.
What to Look for in Each Capstone Type
Reviewing Capstone 1 (Launch Plan): Focus first on the niche definition and the revenue model, as these are the areas where most Capstone 1 weaknesses cluster. Is the niche genuinely specific? Could you name three creators who are direct competitors to the proposed niche? If not, it is probably too broad. Does the revenue model show a clear path from free content to the first paid product, and is that path realistic?
Reviewing Capstone 2 (Monetization Audit): Focus on the connection between the audit findings and the redesign recommendations. Does each recommendation in the redesign trace back to a specific finding in the audit? Are the revenue projections for the redesigned stack grounded in anything, or are they aspirational numbers? Is the equity dimension embedded in the redesign or merely acknowledged?
Reviewing Capstone 3 (Scale Strategy): Focus on internal consistency. Does Year 2 follow plausibly from Year 1? Does the financial model align with the staffing plan? (If the plan adds three contractors in Year 2 but the financial model doesn't reflect their costs, something is wrong in one or both places.) Is the equity audit substantive and integrated throughout, or is it a pro forma section?
How to Give Specific, Actionable Feedback
The test of actionable feedback is simple: could the author sit down immediately after reading your review and know exactly what to revise? If the answer is no, your feedback is not yet specific enough.
Actionable feedback: - References specific sections or sentences in the submission - Proposes a specific alternative or direction ("instead of X, consider Y") - Explains the reasoning behind the suggestion ("because the rubric asks for Z, and your current approach does Q instead") - Is honest without being unkind — the goal is to improve the work, not to demonstrate the reviewer's expertise
Feedback to avoid: - Vague praise ("great job overall!") - Vague critique ("the equity section could be stronger") - Suggestions that reflect personal preference rather than rubric criteria ("I would have chosen a different platform") - Feedback on style or voice when the rubric evaluates substance
The Equity Review
Every peer review should include specific attention to the equity integration in the submission — not just checking whether an equity section exists, but assessing whether the equity thinking is substantive and integrated.
Ask yourself these questions as a reviewer: - Are specific structural barriers named, or does the submission only acknowledge that inequality exists? - Do the equity commitments actually appear in the business model decisions (revenue, platform, pricing, team), or only in a separate section? - Does the equity analysis reflect familiarity with the documented reality of creator economy inequity, or is it primarily abstract? - If the submission proposes to serve a community, does it account for the specific barriers that community faces in accessing content and paying for products?
If the equity integration is tokenistic, say so — kindly, specifically, and with a concrete suggestion for how it could be strengthened.
Instructor Notes (For Classroom Use)
Adapting These Rubrics for Course Grading
These rubrics were designed for formative and summative assessment in courses taught at the undergraduate and graduate levels. Several adaptation decisions are worth noting.
The rubrics use a 4-point scale rather than a percentage system. This is intentional: percentage grading of creative and strategic work tends to produce false precision (the difference between a 78 and an 82 on a launch plan is not meaningful) and obscures the evaluative distinctions that actually matter. If your institution requires percentage grading, the simplest mapping is: 4 = 95–100%, 3 = 80–94%, 2 = 65–79%, 1 = 50–64%. Failing grades (below 50%) are appropriate for submissions that score below a 1 on multiple categories.
The Python analysis category in Capstone 2 is marked as optional. In courses where Python is a prerequisite or co-requisite, you may choose to make it required and adjust the scoring accordingly — a total of 24 points available rather than 20, with the same 80% pass threshold implying 19 points required for a standard pass.
Capstone 3's equity audit requires familiarity with the five recurring equity themes from the textbook. Ensure that students have access to the relevant chapters (Chapter 28 and the equity-adjacent content in Chapters 4, 9, 17, and 21 are most directly relevant) before Capstone 3 is assigned. If you are teaching a modified version of this curriculum, identify the five equity themes that are most relevant to your context and substitute them explicitly in the rubric.
Scaffolding Capstone Projects Across the Semester
These capstones are designed to be cumulative. Capstone 1 produces a launch plan that Capstone 2 may audit, and Capstone 2 produces a revenue stack that Capstone 3 may scale. For maximum learning value, assign Capstone 1 no earlier than the end of Part II (Chapters 6–10) and ideally after Chapter 11. Assign Capstone 2 after Chapter 20. Assign Capstone 3 after Chapter 32. Allowing students to develop and iterate across the three capstones rather than treating them as independent assessments produces significantly richer final work.
Consider incorporating structured peer review into each capstone's timeline: submissions reviewed by one peer before the instructor evaluates gives students a revision opportunity and trains peer review skills. Allocate at least one week between peer review submission and final submission.
Common Student Mistakes and Pre-Submission Interventions
The following mistakes appear most frequently and are most amenable to pre-submission intervention:
Capstone 1: Niche is too broad. Address this in class by having students articulate their niche to a partner, who then has to name three YouTubers/creators in that niche immediately. If the partner can name three in ten seconds, the niche is too broad.
Capstone 2: Equity dimension is absent or tokenistic. Address this by explicitly reviewing the equity section in a brief workshop before submission deadline — ask students to read their equity paragraphs aloud and self-assess against the rubric language for the 4 rating.
Capstone 3: Financial model underestimates expenses. Address this by providing a starting expense checklist: self-employment taxes, health insurance, software (email service provider, course platform, project management tool, video editing software), contractor costs, and professional services (accountant, occasional attorney) should appear in every model.
Accommodating Students Without Existing Creator Presence
Option B (the documented case study approach) exists specifically to accommodate students who are not current creators. However, the quality of Option B submissions depends heavily on the case being well-documented enough to support genuine analysis. Recommend that students choose cases with at least two years of documented history and some publicly available financial information (creator interviews, press coverage, or public revenue disclosures). The three running case study characters from the textbook (Maya, Meridian Collective, Marcus) are explicitly approved as Option B cases for Capstone 1 only. For Capstones 2 and 3, more granular financial data is required than the textbook case studies provide, so documented real-world cases are preferable.
Students who are not current creators and who choose Option B for all three capstones sometimes produce work that is analytically strong but thin on genuine application. One mitigation: require Option B students to include a final section (not evaluated by the rubric) in which they reflect on how the case study insights apply to a creator business they could envision building for themselves. This maintains the applied dimension even when working with documented cases.
These rubrics are designed to evolve with the creator economy. If significant structural changes in platform economics, equity considerations, or monetization models make elements of these rubrics obsolete, instructors should update them accordingly and communicate changes to students before assignment.