I can’t snowshoe.
It stays too warm.
Cougars in the county.
I’d like to see one.
I can’t snowshoe.
I can’t snowshoe.
It stays too warm.
Cougars in the county.
I’d like to see one.
If you wanted to ensure it lasted for 150 years – you’d choose paper.
As amazing as our current electronic technologies are – despite their strengths – terribly, terribly ephemeral. The code the worked yesterday isn’t support today. The processors of – five years ago, ten years ago – are brought to their knees by the computational complexity and presumed processor capabilities of today’s software. The runtime environments required by the digital creations I manifest as a University student not only do not exist – computers of today don’t even recognize the file types.
Perhaps it’s good that my chances of becoming a world-renowned graphic designer are quite slim. For if they were higher, and exhibits celebrating my early digital work were to be held, recovering that early work would be a significant undertaking. Even today. Unlike like my drawings and pastels – for those seem to be holding up just fine. I looked at them just the other day. The same day I went through the box in my office containing 25 years worth of my sketchbooks. All the paper – just as I remembered it. All the sketches just as they were the last time I looked at them.
I didn’t need to convert them into a different file format or upgrade the software before I opened each sketchbook and revisited each page. I simply opened it. I simply turned the page. No need to for anything more. The paper persists.
One story at a time, I’m writing down the stories of my life.
In a book.
A high-quality, hardcover book.
One story at a time, handwritten on paper in the book.
A book I want to exist for a century and a half, if not longer. The book will go into the box with all the other family stories and photos – all of which are on paper. Stories and photos that – while they may not be on their original paper – are on paper.
Sure, I could type out these stories into this site just as I’m writing this. I enjoy writing here. But there’s no chance this site will be around in more than a century. I even have a hard time envisioning it living another quarter century. Even if it does, that will mean countless technology migrations, not just server migrations, but also application layer and database migrations. All of these changes requiring regression tests – however humble.
Somewhere out on the internet there’s a story describing the problem of archiving electronic art. In it, the author describes the process. The process of picking the ideal computer for perpetually running the archived software, completely isolated from the rest of the internet. They described the need to prevent any of the bits of software from ever updating, from the intended application, all middleware, to the operating system, everything. All of which will ensure that this singularly valuable bit of software can continue to provide value for generations to come.
Unless those generations have something other than electrical service expected by the computer’s power supply.
Then – poof. It’s gone.
Last month, I brewed a batch beer. This particular recipe was originally used by a British brewery circa 1868. It was included in a book collecting a number of British and German beer recipes from 1850-1950. Theses recipes were extracted from the actual brewers logs of the time. Brewers logs that were written on paper in books and shared in-house to ensure a consistent product from batch to batch.
Am I using the same ingredients the Tetley Brewery did 147 years ago? Highly doubtful. Today’s grains, hops, and yeast are far more optimized for brewing than they were a century ago. But, since I have the beer’s characteristics; alcohol, bitterness, color, clarity, along with specified grain, hops, and yeast, I can get very close to recreating this beer. As can anyone else.
I don’t necessarily need their equipment or their process for creating fire. That’s all changed. I need the identifying, distinguishing characteristics. The same distinguishing characteristics that were originally written down 150 years ago on paper to help the next brewer on the shift.
It’s been above
freezing here all week
all the snow
from deer season
when I started here my wife
gave me a white gold chronograph
from her jewelry store in the mall
like all successful salesmen here wear
it weighed my left hand down,
silver and crystal reflections
constantly tugging at my attentions
I left it
for this softer, flatter one, yes, yes
weeks ago the batteries stopped at 9:43
but my ex-wife still runs the jewelry store.
Verschlimmbesserung: An improvement that makes something worse.
Doch: An expression for indicating an outcome occurred that was counter to the supplied evidence. Loosely translates to, “although I thought otherwise.” Even more delightfully – it can be and is used sarcastically.
beneath my rudderless patio umbrella
the recently divorced mother of two
by carpools, elevators, and skinny jeans
packed with stage actors
longing to buy her rosé.
When I ask my clients where they found the biggest benefit in my How to Use a Calendar program, they often reply:
“Scheduling for 30, 60, or 90 minutes.”
It’s tempting to block off a massive chunk of time for a big project. Whether that massive chunk of time is a an afternoon, a day, or a series of days – doing so subtly encourages procrastination in two ways;
Overcoming both of these requires peeling apart the project into smaller, more discreet, incremental tasks. Then estimating the time to accomplish each of those specific tasks. Finally, scheduling those tasks with their corresponding estimated duration on your calendar.
This has three subtle benefits:
I encourage my clients to use the following estimation framework I talk about The Power of When:
Why 30, 60, and 90 minutes?
Now, what if you reach the outcome before the estimated time is up?
If you’re interested, I wrote this post in two 60 minute sessions with an hour lunch in between.
Neal Conan: “You had solar panels (on your sailboat) for electricity.”
Matt Rutherford: “I did, but they broke.”
Neal: “They broke?”
Matt: “One by one.”
Neal: “I think you had a Kindle for reading books.”
Matt: “I did. It broke in a storm.”
I like Matt’s story for all that it tells as about our expectations and presumed requirements for a huge project we’ve never done before.
When I started out professionally the teams I worked on created deliverables; mockups, storyboards, sitemaps, taxonomy listings, content maps, wireframes, process flows, clickable prototypes, specification documents, usability testing, amazing looking proposals, Photoshop, timesheets. When I struck out on my own I assumed all of these things were required, so I packed them all with me.
Project after project I saw how each of these tools could bring as much confusion, delay, and tedious re-work as they could clarity. I saw how easy it was to iterate, debate, and perfect them, while losing sight of the project’s purpose and its promised business value. One by one, I stopped promising any specific design planning deliverable – other than a wireframe and a functioning web app. Then I dropped the wireframes. I eliminated all of this design planning documentation in favor of engaged conversations directly with the buyer that culminated in pen-on-paper sketches of how the key functionality should work followed by an estimate on when it’d be available to click-through.
Everything else? So much jetsam.
It’s not that I stopped doing the thinking encapsulated in those deliverables, the thinking became hyper-focused, hyper-prioritized on the core function of the project. If the core function couldn’t actually work nothing else will save it, not the color palette, not the logo, or which order the navigation labels are in. Hell, not even the project management methodology choice will save a project where the unique value proposition is neither.
The tools we actually need to be successful on a regular basis are so basic as to be taken for granted:
– trust in & respect for each other’s abilities
– clear, efficient, constructive communication
– absolute clarity in goals
– complete flexibility in execution
– a comfort with continual iteration
In this day and age, the rest can learned, negotiated, or rolled into the project as needed – whether it’s a project management philosophy, a unique software application, or a greater understanding of the subject matter. Presuming the four tools listed above are present, prior experience in the expected deliverables, vocabulary, or value chain of a specific domain is not only unnecessary but actually be counter-productive. Counter-productive to delivering the compelling innovation the creative team was assembled for.
Throughout its history, Apple – regularly cited as one of the most innovative and creative organizations – regularly dropped components presumed required for all computers; 3.25″ floppy drives, ethernet ports, optical drives, the ability to run arbitrary code.
At the time Google started getting becoming popular, having ads and headlines and other ‘portlets’ surrounding the search box was a presumed requirement for search engines.
Uber, Lyft, AirBnB dropped the presumed requirement that drivers/hosts needed to be licensed by the government.
Telsa, recently surpassed GM in market value, doesn’t have dealerships – a presumed requirement for an automotive brand by many states.
Yes, every one of these organizations is controversial for any number of reasons – but the very first one, the one deep down in their DNA is their bold dismissal of a presumed requirement around their core product.
So, yes I was disheartened when a Director at major employer confessed to me, “We don’t kill projects here.” For it meant a significant part of the organization was not yet boldly willing to separate the presumed requirements from the actual requirements far enough to spot the energizing, clarifying, innovation hidden in-between.
One of your presumed requirements is keeping you from growth. Do you know which one?