Worst Writing Advice Ever

Mine was to write every day.

I blame Hemingway.

At first glance, writing every day makes sense.

You get more words in, hit your targets faster, and move on to the next task.

It feels productive.

You’re getting somewhere.

Somewhere…

But is it any good?

Scientific American reports that, ‘Research on naps, meditation, nature walks and the habits of exceptional artists and athletes reveals how mental breaks increase productivity, replenish attention, solidify memories and encourage creativity.’

Here’s another way of looking at it.

Let’s say you’re thinking about a problem.

You’ve went over all the angles.

It doesn’t matter how hard you try, the answer just doesn’t come.

Then you go for a run, have a shower, or just tidy the house… and the answer pops up.

What’s happening here?

I think it’s to do with the process of digesting an idea.

I think it works a bit like this.

You have a problem.

You talk to yourself about it. Lots of inner chatting.

You let it digest.

Then wait….

wait….

and….

The answer floats to the surface.

It’s the ‘process of digestion’ that gives you the insight.

You can’t force it.

That’s why you often have the answer in the morning when you first wake up.

Somehow, you’ve been digesting it all night.

It’s the same with writing.

If you write non-stop, it stops you from getting the perspective you need to critique your work.

The word count might be impressive, but that’s about it.

Of course, what works for one person doesn’t always work for another.

PSDo you write every day? If not, how often?

Thousands of templates to jump start your project

Acceptance Test Plan

Contingency Plan

Software Development Templates

Acquisition Plan

Conversion Plan

Software Requirements Specification

Action Plan

Cost Benefit Analysis

Software Testing

API Documentation

Database Design

Standard Operating Procedures (SOP)

Audience Analysis

Datasheet

Statement of Work

Availability Plan

Deployment Plan

System Administration Guide

Bill of Materials

Design Document

System Boundary

Business Case

Disaster Recovery Plan

System Design Document

Business Continuity

Disposition Plan

System Specifications

Business Plan

Documentation Plan

Technical Writing Templates

Business Process

Employee Handbook

Test Plan

Business Requirements

Error Message Guide

Training Plan

Business Rules

Expression of Interest

Transition Plan

Capacity Plan

Fact Sheet

Troubleshooting Guide

Case Study

Feasibility Study

Use Case

Change Management Plan

Functional Requirements

User Guide

Communication Plan

Grant Proposal

Verification and Validation Plan

Concept of Operations

Implementation Plan

White Papers

Concept Proposal

Installation Plan

Work Instructions

Configuration Management Plan

Interface Control Document

Software Development Templates

Acceptance Test Plan

Maintenance Plan

Software Requirements Specification

Acquisition Plan

Market Research

Software Testing

Action Plan

Marketing Plan

Standard Operating Procedures (SOP)

API Documentation

Needs Statement

Statement of Work

Audience Analysis

Operations Guide

System Administration Guide

Availability Plan

Policy Manual

System Boundary

Bill of Materials

Project Plan

System Design Document

Business Case

Proposal Manager Templates

System Specifications

Business Continuity

Proposal Template

Technical Writing Templates

Business Plan

Quality Assurance Plan

Test Plan

Business Process

Release Notes

Training Plan

Business Requirements

Request for Proposal

Transition Plan

Business Rules

Risk Management Plan

Troubleshooting Guide

Capacity Plan

Scope of Work

Use Case

Case Study

Security Plan

User Guide

Change Management Plan

Service Level Agreement (SLA)

Verification and Validation Plan

Communication Plan

Setup Guide

White Papers

Concept of Operations

Social Media Policy

Work Instructions

Concept Proposal

Contingency Plan

 

Configuration Management Plan

Conversion Plan