Templates for recurring work

{{whyLabel}}: You cannot automate what you haven't identified; a data-driven inventory prevents building templates for tasks that don't actually recur often.

{{howLabel}}:

• Review your calendar, sent emails, and task manager for the past two weeks.
• List every task that appeared more than twice.
• Note the approximate time spent on each occurrence.

{{doneWhenLabel}}: A list of at least 5-10 recurring tasks with frequency and duration data.

{{whyLabel}}: High-frequency, low-complexity tasks (e.g., status updates) are the best candidates for immediate templating.

{{howLabel}}:

• Use a 2x2 matrix: Frequency (High/Low) vs. Complexity (High/Low).
• Prioritize 'High Frequency / Low Complexity' for quick wins.
• Flag 'High Frequency / High Complexity' for modular system building.

{{doneWhenLabel}}: A prioritized list of tasks ready for the design phase.

{{whyLabel}}: Templates often fail because they miss small, critical sub-steps; mapping the current 'as-is' state prevents this.

{{howLabel}}:

• Pick your most frequent task (e.g., 'Onboarding a new client').
• Write down every single click, email, and document creation step involved.
• Identify where you currently 'copy-paste' or 're-think' the process.

{{doneWhenLabel}}: A step-by-step flowchart or bulleted list of a single complete workflow.

{{whyLabel}}: Fragmented templates (some in email, some in folders) lead to system abandonment.

{{howLabel}}:

• Choose a tool that supports both text and file attachments.
• Recommended: A Markdown-based note-taking app (for longevity) or a Cloud-based Document system.
• Ensure the tool has a robust search function and 'duplicate' feature.

{{doneWhenLabel}}: A dedicated 'Master Template' folder or workspace is created.

{{whyLabel}}: Consistent naming ensures templates are sorted logically and are searchable in 2025's digital environments.

{{howLabel}}:

• Use the ISO 8601 date format: YYYY-MM-DD.
• Use prefixes for categories (e.g., COM_ for Communication, PRJ_ for Project).
• Avoid spaces; use underscores (_) or hyphens (-) for cross-platform compatibility.
• Example: 'TPL_COM_Client-Onboarding_v01'.

{{doneWhenLabel}}: A written naming guide is stored in your repository.

{{whyLabel}}: An index acts as a 'Table of Contents,' reducing the cognitive load of finding the right starting point.

{{howLabel}}:

• Create a single document named '00_START_HERE'.
• Link to every sub-template you are about to create.
• Add a one-sentence description for when to use each template.

{{doneWhenLabel}}: A functional index document with placeholders for future templates.

{{whyLabel}}: 80% of professional communication is repetitive; snippets save hours of typing.

{{howLabel}}:

• Write templates for: Meeting requests, Follow-ups, and Project handovers.
• Use clear placeholders like [CLIENT_NAME] or [DATE] in bold/brackets.
• Keep them modular: Create 'Opening', 'Body', and 'Closing' blocks that can be mixed.

{{doneWhenLabel}}: At least 3 reusable communication templates are in the repository.

{{whyLabel}}: Checklists prevent 'decision fatigue' and ensure no critical setup step is missed.

{{howLabel}}:

• Based on your workflow analysis, list every setup task (e.g., 'Create folder', 'Invite team').
• Group tasks into 'Pre-Launch', 'Launch Day', and 'Post-Launch'.
• Include links to the specific tools or documents needed for each step.

{{doneWhenLabel}}: A master checklist that can be duplicated for every new project.

{{whyLabel}}: Formatting reports or invoices from scratch is a major time-sink.

{{howLabel}}:

• Create 'Shell' documents for recurring reports (e.g., Weekly Status).
• Lock the styles (Fonts, Headers, Margins) so you only ever edit the content.
• Include a 'Version History' table at the top of each document.

{{doneWhenLabel}}: A set of 2-3 'Shell' documents ready for data entry.

{{whyLabel}}: Theoretical systems often break in practice; a pilot phase identifies these 'bugs' early.

{{howLabel}}:

• Commit to using your templates for every recurring task for one work week.
• Do not edit the templates during the task; just use them as they are.
• Keep a 'Friction Log' next to you to note whenever a template feels 'clunky'.

{{doneWhenLabel}}: Completion of one work week using the new system.

{{whyLabel}}: Refinement based on real usage is what turns a 'tip' into a 'system'.

{{howLabel}}:

• Review your Friction Log from the pilot week.
• Identify templates that were too rigid or had missing placeholders.
• Look for 'orphan' tasks that still required manual work and need a template.

{{doneWhenLabel}}: A list of specific adjustments needed for your templates.

{{whyLabel}}: Iteration ensures the system remains useful rather than becoming a burden.

{{howLabel}}:

• Update the templates based on the Friction Audit.
• Simplify any steps that felt redundant.
• Update the version number in the file names (e.g., v01 to v02).

{{doneWhenLabel}}: All templates updated to their second, refined version.

{{whyLabel}}: Workflows change over time; outdated templates cause more errors than they prevent.

{{howLabel}}:

• Set a recurring calendar invite for the first Friday of every month.
• Review the Master Index and delete any templates not used in the last 90 days.
• Check if any links or software commands in the templates have changed.

{{doneWhenLabel}}: A recurring 30-minute calendar event is active.

{{whyLabel}}: Documentation allows you to delegate tasks in the future and ensures consistency if you take a break.

{{howLabel}}:

• Create a simple 1-page guide explaining the naming convention and where to find templates.
• Explain the 'Duplicate, don't Edit' rule to prevent overwriting masters.
• Store this guide in the '00_START_HERE' document.

{{doneWhenLabel}}: A completed 'System Manual' document.