Included
- Original skits, hook wording, character/relationship framing and setup/payoff timing.
- Comparable creative pairs, such as DAD versus another framing of a closely related premise, with repeated observations.
← Research programCB02 · Comedy format research
Comedy Formats & Audience Retention
Compare skit openings and relationship cues to understand what holds attention without mistaking one viral result for a repeatable format.
BhavCzar Skits · @BhavCzarSkits
Business objective
What this study needs to answer.
Identify comedy structures that retain viewers and can be produced repeatedly at a recorded, sustainable cost.
- Does an explicit relationship cue make a comparable setup easier to understand?
- Which setup-to-payoff structures retain viewers across repeated, similar skits?
Hypotheses · untested
Starting ideas, not conclusions.
- A clear relationship cue such as DAD may improve early understanding and retention compared with a less explicit version of a similar premise.
- A shorter setup may help early retention but may weaken the payoff; both need to be observed.
Method and scope
Compare carefully. Record the exceptions.
Pre-register a pair ID and the intended difference before publication. Match premise family, format, duration band, performer and production style where practical; alternate release order across repeated pairs. Log other changes and do not present audience exposure as randomized. Review early retention alongside the later payoff, not just the opening.
Outside the scope
- Comparing unrelated jokes and declaring that one word caused the difference.
- Treating a repost of the same skit on another platform as an independent creative replication.
Measures, denominators and observation windows
- Opening retention
- Platform-reported share remaining at a predeclared timestamp / the platform’s eligible starting cohort, at 24 hours and 7 days. Use a suitable timestamp for short clips; mark unavailable when the report is not provided.
- Average percentage viewed
- Platform-reported average view duration / video duration × 100, where those definitions align; 24-hour and 7-day snapshots, within duration bands. Replays can affect this value.
- Shares per 1,000 views
- Reported shares / reported views × 1,000 at 7 days, on the same platform and format.
- Production efficiency
- 7-day watch minutes / total production hours; report median per format and number of distinct assets.
Platform measures use matched 24-hour and seven-day snapshots where available. Report format, duration, snapshot age and missing fields. Zero denominators are undefined; inaccessible metrics are unavailable.
Baseline, costs and decision criteria
Baseline collection plan
Collect historical skit metrics if access and comparable posts exist; otherwise use week one. Record platform-specific view and retention definitions. Choose the opening timestamp and duration bands before comparing pairs; preserve failures as well as successes.
Time, costs and revenue
Track writing, rehearsals, recording, retakes, editing and publishing minutes, props/locations, collaborators and paid distribution. Keep estimates of owner labor separate from cash expenses and actual platform revenue.
Decisions after baseline
Use week-one variability and production time to set a meaningful retention improvement before later comparisons. Continue a cue or format only if its direction repeats across comparable pairs without losing the payoff or increasing cost beyond the agreed capacity. One exceptional post is a follow-up lead, not proof.
Data access, confounders and limitations
Premise quality, performer energy, sound/trends, returning viewers, upload order, duration, repetition fatigue, packaging and unequal distribution.
Use owner-accessible native reports and private operating records where available. No API credentials, monetization or complete tracking are assumed. Comparisons are observational unless a stronger design is actually established; crossposts are not independent evidence. Public reporting excludes private customer details.
Planned activity
Targets stay separate from actual output.
User-planned launch in the week beginning October 26, 2026: at least one video every day on BhavCzar Skits. Planned target only.
Initial four-week pilot
October 26–November 22, 2026, with weekly reviews on November 2, 9, 16 and 23. Final seven-day content snapshots mature November 29; order and inquiry windows may close later.
Provisional 90-day horizon through January 23, 2027. Actual launch and baseline collection remain unconfirmed.
Planned outputs
Useful evidence. Documented decisions.
- Skit-pair register and timing notes.
- Retention-curve comparisons with sample counts and creative limitations.
- Repeatable-format shortlist with production-time ranges, not promised outcomes.
Next milestone
Create the pair register and choose the first comparable premise family and opening timestamp; capture baseline exports before launch.
The shared protocol defines source records, consistent windows, private-data boundaries and weekly continue/change/pause reviews.
Read the shared protocol →Results · not collected
No findings to report yet.
This page is a project scope, not a completed case study. Future results will be added only with dated evidence, denominators, observation windows and limitations.