View source for Turning a side project into a weekend campaign

'''Turning a side project into a weekend campaign''' means treating one weekend as a campaign with a single mission, timed rounds, checkpoints, a squad, and a scoreboard, so a side project makes real progress in two days. It is the concrete playbook that puts the ideas in [[Making productive work as engaging as games]] onto an actual calendar. It is written for people with full-time jobs and a book, album, app, or wiki waiting for attention.

== Pick one mission ==
A campaign has one mission. It is one shippable outcome that will exist in public or as a finished file by Sunday night.

Good missions are specific and visible:
* Publish one new wiki page with sources and categories.
* Release a song page with the track, lyrics, and credits.
* Submit an app update to the store with one new feature.
* Draft one complete book chapter from first line to last.

To choose, ask which option is the smallest thing that earns money, reach, or learning. Money means it can sell, show ads, or lead to paid work. Reach means new people can find it. Learning means you will finish the weekend knowing a skill you lacked on Friday. If a mission scores on none of these, pick another. If it feels too big to finish in two days, cut it in half and keep the half that ships.

== Friday night briefing ==
The briefing takes 15 minutes on Friday evening. It turns a vague plan into a set of decisions, so Saturday morning starts with action instead of debate.

# '''Write the mission.''' One sentence, on paper or in a note: "By Sunday at 6 PM, the song page for my new track is live."
# '''List three checkpoints.''' Break the mission into three milestones you can verify. For a wiki page: outline done, full draft done, page published.
# '''Prep your tools.''' Open the editor, log in to the sites you need, download reference files, and clear the desk.
# '''Set the scoreboard.''' Create a simple log file or sheet with the mission at the top and empty lines for each round.

Writing down when and where you will start each round is a form of implementation intention, a planning method that research has linked to better follow-through on goals. The briefing is where those plans get made.

== The campaign map ==
The map is the weekend schedule. Each round lasts 45 minutes, followed by a break. This is a version of timeboxing, where each task gets a fixed slot of time rather than an open-ended one. Adjust start times to fit your life, but keep the shape.

{| class="wikitable"
! Day !! Time !! Round !! Focus !! Checkpoint
|-
| Saturday || 9:00 to 9:45 || Round 1 || Warm-up: gather notes and sources ||
|-
| Saturday || 10:00 to 10:45 || Round 2 || Outline or structure the work || Checkpoint 1: outline done
|-
| Saturday || 11:00 to 11:45 || Round 3 || Build the first section ||
|-
| Saturday || 12:00 to 1:00 || Break || Lunch and a walk ||
|-
| Saturday || 1:00 to 1:45 || Round 4 || Boss fight: the hardest task ||
|-
| Saturday || 2:00 to 2:45 || Round 5 || Continue the build ||
|-
| Saturday || 3:00 to 3:45 || Round 6 || Finish the rough version || Checkpoint 2: full draft done
|-
| Sunday || 10:00 to 10:45 || Round 7 || Review and fix the weakest part ||
|-
| Sunday || 11:00 to 11:45 || Round 8 || Polish, links, and details ||
|-
| Sunday || 1:00 to 1:45 || Round 9 || Extraction: publish, submit, or export || Checkpoint 3: shipped
|-
| Sunday || 2:00 to 2:10 || Debrief || Review and pick the next mission ||
|}

The '''boss fight''' round goes after a warm-up and before fatigue sets in. It is where you face the task you most want to avoid: the tricky chorus, the bug, the chapter climax, the section that needs real research. The '''extraction''' round exists only to ship. No new features, no rewrites. Get the thing out.

Breaks between rounds can be 10 to 15 minutes. The Pomodoro Technique uses shorter rounds of 25 minutes; if 45 feels long, use that rhythm instead.

== Squad and comms ==
Solo campaigns work, but a squad makes it harder to drift. Your squad can be:
* '''A friend''' running their own campaign on the same weekend.
* '''An accountability partner''' who expects a message at each checkpoint.
* '''An AI assistant''' that drafts outlines, checks facts, reviews code, or proposes edits while you stay in charge.

Keep comms short. A check-in is one or two lines: "Checkpoint 1 cleared. Starting the boss fight." Send one at each checkpoint and one at extraction.

== Scoreboard ==
Track shipped items, not hours. The scoreboard records what each round produced, so you can see progress at a glance and spot rounds that drifted.

A plain text log is enough:
<pre>
MISSION: Publish the wiki page "Home studio basics" by Sun 6 PM

SAT R1  sources gathered (6 links)
SAT R2  outline done             [CHECKPOINT 1]
SAT R3  intro and section 1 written
SAT R4  boss fight: gear table finished
SAT R5  sections 2 and 3 written
SAT R6  full draft done          [CHECKPOINT 2]
SUN R7  fixed weak section, cut 200 words
SUN R8  links and categories added
SUN R9  page published           [CHECKPOINT 3: SHIPPED]
</pre>

Each line names a result. If a round ends with nothing to write, note that honestly, then shrink the target for the next round.

== Rewards and loot ==
Rewards work best when they are planned in advance and tied to checkpoints. Decide on Friday what each checkpoint unlocks:
* '''Checkpoint 1:''' a favorite coffee or snack.
* '''Checkpoint 2:''' a gaming session on Saturday evening, guilt free, because the draft is done.
* '''Checkpoint 3:''' a longer evening of play, a meal out, or a new game you have been waiting to try.

Gaming here is earned loot, not a temptation to fight. The point is order: checkpoint first, loot second. That way play feels like a win instead of an escape.

== When things go wrong ==
Every campaign hits trouble. A family event takes Saturday morning, a tool breaks, or the boss fight turns out to be twice as hard as expected. Respawn rules keep the campaign alive:
* '''Shrink the mission.''' If a full chapter will not fit, ship a complete scene. If the app feature stalls, ship the bug fix. A smaller shipped mission beats a large abandoned one.
* '''Skip, do not stop.''' Lost a round? Move to the next one on the map. Do not try to win back missed time by working through breaks.
* '''Never abandon the scoreboard.''' Even a bad weekend gets logged. The record of what happened is what makes the next campaign better.
* '''Respawn at the last checkpoint.''' If work gets messy, return to the last thing that was clearly done and rebuild from there.

== Sunday debrief ==
After extraction, spend 10 minutes on a debrief. Look at the scoreboard and answer three questions:
# What shipped?
# Which round worked best, and why?
# What slowed things down?

Then pick the next mission and write it at the top of a fresh log. Ending with the next mission already chosen makes the following Friday briefing faster, and it turns single weekends into a series of campaigns that add up to a finished book, a full album, a live app, or a growing wiki.

== See also ==
* [[Making productive work as engaging as games|Making productive work as engaging as games]]
* [[Turning a wiki into income|Turning a wiki into income]]
* [[How to run a personal wiki|How to run a personal wiki]]
* [[Randori Front|Randori Front]]
* [[Page ideas|Page ideas]]

== External links ==
* [https://en.wikipedia.org/wiki/Timeboxing Timeboxing] on Wikipedia
* [https://en.wikipedia.org/wiki/Implementation_intention Implementation intention] on Wikipedia
* [https://en.wikipedia.org/wiki/Pomodoro_Technique Pomodoro Technique] on Wikipedia

[[Category:Productivity]]
[[Category:Side projects]]
[[Category:Motivation]]
[[Category:How-to]]
[[Category:Ideas]]