The Making of Prince of Persia: Journals 1985–1993
Source: https://press.stripe.com/the-making-of-prince-of-persia ↗
The unedited journals of a young programmer creating a game that defined a genre, covering the years from Mechner's time at Yale through the completion and release of Prince of Persia.
Because these are actual journal entries — not a retrospective memoir — the book captures what building something original actually feels like day by day: the doubt, the wasted months, the technical dead ends, the tension between commercial pressure and artistic ambition, and the long stretches where nothing seems to work.
Mechner was simultaneously trying to become a screenwriter and a game designer, and the journals document the creative process without the false clarity that hindsight imposes.
For product builders, this is a primary document about the emotional and practical reality of sustained creative work — far more honest than any success narrative.
The Stripe Press edition includes Mechner's original sketches and rotoscoping studies, making it also a visual record of craft in the pre-digital-tools era.
Central argument
Mechner makes no explicit argument — the journals resist thesis — but the cumulative record demonstrates that original creative work is structurally characterized by extended periods of non-progress, divided attention, and unresolved doubt rather than the focused momentum that success narratives retroactively impose. The journals show a creator who was simultaneously pursuing screenwriting, uncertain whether the game was worth finishing, and frequently convinced he was wasting his time; Prince of Persia emerged despite this, not after it was resolved. The implicit finding is that the conditions conventionally treated as dysfunction — distraction, ambiguity, creative fragmentation — may be constitutive of genuinely original work rather than obstacles to it.
Critique
Because the journals were written by a solo creator working in a pre-team, pre-process era of game development, the book has limited direct applicability to the organizational and collaborative dynamics that define most digital product work today. Mechner's creative struggle is fundamentally individual — there are no stakeholders to align, no roadmaps to defend, no cross-functional tensions — which means the reader must do substantial interpretive work to translate the experience into contexts involving distributed teams, competing priorities, and institutional accountability. The book risks being absorbed as romantic mythology about lone creative genius precisely because the structural conditions it documents no longer exist for most product builders.
Why it matters for product
For a CPO, the journals offer a corrective to the pressure to interpret slow or ambiguous phases of product development as signals of team failure or strategic misalignment — Mechner's record shows that the most consequential creative periods looked, from the inside, indistinguishable from stagnation. This matters concretely when managing discovery work or 0-to-1 initiatives where output is invisible for long stretches: the journals provide a historically grounded argument for protecting time that doesn't yet show results, and for resisting the organizational instinct to intervene, reframe, or pivot whenever momentum isn't legible.