Tag: ship

Keep calm and ship

There’s a very natural cycle when we ship a new project.

In the lead up, we experience hope. Hope is a beautiful thing as we’re in the land of what might be. It is beautiful and lasts until we start doing the work.

Next, there’s doubt. Could I really deliver on what I hoped? The reality doesn’t seem to be close to what I imagined. Is this going to go anywhere?

Once the work is done, we experience fear. Is this any good? Should I just pack up and leave? It is this stage that gets most projects. In response to that fear, we try making all sorts of last minute edits and changes. We forget why we wanted to do this and try and settle for something “people” will like. Or, we just stop and walk away.

Once we get past the fear, we ship. Ah! It feels great. We are elated.

For ten seconds.

Then, as we review what we shipped, we realize it isn’t the perfect product we’d envisioned. Why didn’t I catch that obvious flaw? Ugh.

Doubt and anxiety set in again. Are they going to hate it? Is someone going to write that horrible negative email?

A few hours pass. We still haven’t heard anything. Is this a confirmation of our worst fears? Should we be ashamed of what we shipped?

I’ve shipped many a project over these years. And, yet, I’ve always experienced this cycle of emotions. It is fresh in my mind as I shipped the first edition of the “Notes by Ada” project yesterday. I realized after I shipped that MailChimp’s formatting hadn’t worked as well on mobile. Bummer.

Whenever I experience this, I remember the following truths.

First, I have been ashamed of the first version of every project I have shipped so far. I always look back and ask – “What was I thinking?”

Second, we learn some incredibly valuable lessons when we ship. The best way to respond to them is to improve our creation process. And, you don’t really have a great process until you ship that first product, fall and learn. This attempt might not work, and that’s okay.

Finally, the questions to ask aren’t – “Was I good or perfect?”. They are – “Was I engaged? Was I paying attention?” As long as the answer to that was yes, we were doing the best we could. When we know better, we’ll do better.

Until then, keep calm and ship.

The ladder of control – The 200 words project

Here’s this week’s 200 word idea thanks to 99u.com.

David Marquet, Captain of the USS Santa Fe, followed a leadership principle – push authority to as low a level as possible. Under normal practice, officers would “request permission to” perform operations such as submerge the ship. The captain would approve and the officer would carry out the task.

David insisted his officers move up the ladder of control (below), stop asking permission, and instead state “Captain, I intend to submerge the ship” to which he would respond, “very well.” Initially, he had a lot of questions for the officers about whether it was safe, whether the preconditions were met, whether the team was ready, and whether it was the right thing to do. With time, he asked fewer and fewer questions as the officers learned to provide that necessary information at the same time they stated their intent.

The immediate and obvious benefit was that with this small shift in language, just a few words really, the officers became the driving force behind the submarine’s operations.

Perhaps we ought to consider moving our teams up the ladder of control as well..

Ladder of control

Source and thanks to: http://www.EBSketchin.com

‘Moving people from “request permission” to “I intend to…” raised them one rung on the ladder of control, from passive followers doing what they were told at the bottom to proactive engaged leaders, crafting the future, at the top. ‘ | David Marquet