Incorporate personal heuristics into the playbook

We should find a way to incorporate more of a personal touch into the playbook, either via quotes or anecdotes. E.g. from @jasmussen

> In software development, committing code (rather than talking about what code to write) is a great way to progress out of a mire. Often times it's faster to build and test two proposed but conflicting directions than it is to discuss which one is right.

>It is with design as it is with life: plan for the long term, but don't let that stop you from making little day to day improvements.

>Automate. Almost no task is too small to automate, you'll be surprised how much time it'll save you in the long term.

>Automation in design is not about taking the human touch out of a design, it's about extending the reach and potential of every designer out there; about giving them tools to explore hundreds or thousands of potential designs, and then through human intuition guide the process and pick the right result.

>A classic example from a past life was a designer giving a website mockup to a developer, they made it in Illustrator and the canvas was A4 landscape. They clearly had no idea what it meant to design for the web.

And from @johnmaeda:

> Rare are the folks who can live on the land or sea

Start by reviewing the playbook and the existing personal heuristics material, including the quoted anecdotes from @jasmussen and @johnmaeda. Define where personal quotes or anecdotes belong and what consistent format they should use. Done means the playbook has an agreed, integrated approach for this content rather than an open-ended collection of examples.

Written by the indexing model from the issue text.