What goes wrong when you ignore that output templates reduce startup friction?

The most common reason fails: The most common failure is over-engineering templates — building elaborate multi-page structures with detailed instructions for every section, creating a template so rigid that filling it out feels like compliance paperwork rather than accelerated creation. The second failure is hoarding templates you never use: collecting dozens of formats from the internet without adapting them to your actual output patterns, then ignoring all of them because none fits your work.

The fix: Identify the three output types you produce most frequently — emails, memos, status reports, code reviews, project plans, whatever recurs at least weekly. For each one, create a template by extracting the common structure from your last three good examples of that output. Write the template as section headings, placeholder prompts, and any boilerplate that appears every time. Save the three templates where you can access them instantly. Use each template at least twice in the next week, then revise based on what you added or removed during actual use.

The underlying principle is straightforward: Templates for common output types let you start producing immediately.