You need to sign in or sign up before continuing.
Reflection — An Honest Take 8 min

Honest Take — Before You Begin

Honest Take — Module 12: The Solo PM — Time, Roadmap, and the Portfolio Cadence #

All PM literature assumes a team: the PM is one role among several, and the pushback that catches errors comes from peers. You have no peers in the room. Every role is the same person, and the pushback has to come from structure — which is what this module builds, because without structure the engineer-founder operates as the engineer most weeks, the founder occasionally, and the PM almost never. Engineering work is the most legible and the most immediately rewarding thing on your desk, and time drifts toward legible work without resistance. This module is the resistance, and it will be emotionally harder than its content suggests, because the input is everything the prior eleven modules surfaced and the work is sitting with the trade-offs instead of deferring them again.

Start with the time tracking, because it is the cheapest diagnostic with the highest yield. Track two weeks of working hours and categorize them, and here is my prediction of the shape: roughly 70% engineering (the day job plus your own products' code), 10% PM (customer emails, pricing thoughts, roadmap drift), 5% sales or less — you will notice the 5% and feel the cost — 10% founder/admin, 5% other. The 10/5 PM/sales split is the bottleneck the entire curriculum has been pushing against, and the structural fix is reallocating 5-10 points from engineering toward PM and sales. The reallocation is uncomfortable for a precise reason: engineering work feels productive in a way PM work doesn't, and sales work feels foreign in a way PM work doesn't. The discomfort is not a malfunction. It is what the fix feels like from inside.

The founder-as-bottleneck pattern deserves its own paragraph because it is the most reliable failure mode in solo operations and the most resistant to self-diagnosis. Every decision routes through you; you cannot make them all in real time; some get made too fast and the rest get deferred indefinitely; velocity is bounded not by talent or capital but by your available cognitive hours. The corrective is not "hire faster." The toolset, in the order an engineer should consider it: reduce demand (kill products, refuse work — M4 and M13), automate repeated decisions (pricing rules instead of per-customer negotiation, support templates, cached policies), decompose and delegate one bounded function to a contractor — and only then parallelize via hiring. Engineer-founders jump to hiring because it's the most obvious move and skip the first two because they feel like retreat. They are not retreat; they are the cheap moves, and parallelizing a poorly understood bottleneck multiplies the mess. Write the hiring framework anyway — conditions under which a first hire pays for itself in six months, bounded role, onboarding hours you actually have — and expect the framework to land on "not yet." Naming the conditions in advance is what prevents an instinct-hire when growth pressure spikes.

The two earlier drafts of this module had different centers of gravity, and the merge is the sentence both were reaching for: a roadmap is only as real as the time budget behind it. One draft built the 90-day roadmap with the explicit no-list — every line of which is an admission ("not shipping X this quarter," "not adding a teams tier"), individually small and collectively the substance — and predicted that your implicit commitments would total three to four times your actual capacity. Calculate the real hours: day job, family, recovery, and what remains is maybe 8-14 hours a week of true product capacity, against a mental commitment of 30-45. The gap is the diagnosis. The other draft built the time-blocked week and the quarterly portfolio review, on Leroy's attention-residue evidence: frequent role-switching erodes single-task depth by 20-40%, and PM work — holding the user, the strategy, and the constraint simultaneously — sits at the expensive end.

Merged: the week structure makes the hours real, the roadmap spends them honestly, the quarterly review keeps M4's triage from decaying, and the killed products appear on the no-list by name so reviving them is formally blocked.

Two stances to write down rather than drift through. First, the calm company: deliberately non-VC, deliberately small, deliberately solo for as long as the work permits — the deliberate-monolith stance applied to the company. It is a real strategy, it has been correct for real businesses, and it is much easier to defend in writing than to maintain under growth-narrative peer pressure, which is exactly why you write it down. The alternative — scale eventually, deliberately — is also valid; the failure mode is not choosing either. Second, if a day job or contract income currently stabilizes the whole operation: the stability is real and it also masks the urgency of your own products' revenue. Name the cutover threshold — the revenue level at which you'd drop or reduce the external work — in writing, now, while it's abstract, because the version of you who decides under pressure when revenue is close decides worse.

Conclusion #

Module 12 is the structural fix that makes everything before it sustainable. The time tracking exposes the bottleneck, the four correctives get considered in the cheap-first order, the no-list makes the roadmap honest, and the quarterly review is the cadence that keeps kill decisions killed. The calm-company question and the cutover threshold get written down while they're calm. Structure is the pushback you don't have colleagues for.

Predictions #

  • The two-week time tracking will show 60-75% engineering, 5-15% PM, 0-5% sales. The sales number will sting more than the engineering number.
  • The hours-available calculation will produce 8-14 real weekly hours against a mental commitment of 30-45. The gap is the module's main yield.
  • The no-list will run 2-3x longer than the yes-list, and at least one line of it will feel disproportionately heavy to write. The weight is sunk cost protesting; let it pass.
  • Your first time-blocked week will break within days — a deadline or an emergency will smash the structure. The second iteration, redesigned around where it broke, is the realistic one.
  • The hiring framework will conclude "not yet," and within six months a busy stretch will tempt you to violate it. The written conditions are what you re-read instead.
  • Within 60 days of writing the roadmap, an opportunity not on it will appear. The discipline is to explicitly trade something off the yes-list or say no — not to silently absorb it.
  • The 90-day cycle will end with one major outcome shipped, one minor, and 1-2 items honestly deferred. That ratio is the success state, not 100% delivery.