When to show your work?

Holding onto work too long leads to stagnation, like part of a river branch flowing into a dead end swamp.

A good outcome for showing work is either some fundamental flaw is exposed or tweaks suggested to optimize it. Either way time (the only non-renewable resource) is preserved. Through a quick personal survey I've observed that my outcomes tend to be good the majority of the time when I show my work quickly. That number jumps north of 90% with one round of feedback. The first turn of the wheel must happen quickly. There's two parts: first the inspirational impulse and follow through with action or feedback. One without the other results in a flat output: discipline without inspiration is stale, and inspiration without action leads to rot. It's the latter part I want to focus on here.

Why don’t we always show our work to others quickly (or at all)? In a word, fear. I personally still need to get over the hump of self-doubt and insecurity most times, typically because I don't think it meets my personal quality bar. It’s intimidating to show your work and bear your soul. Especially if you lack confidence or are new to a domain. But it's important to caveat that it's early and that you're biased to speed, like putting the outline of a picture on the paper without filling in the shading and textures.

Strangely, I found it easier to share work related to my own mortality than about work projects. I had really no issue showing my work, admitting ignorance or putting up a scaffold to generate conversation with smart people. That’s essentially what I did with chemolog.com. Why?

Shouldn’t something as personal as battling cancer and wrestling with ideas about mortality be harder than sharing ideas about work? I know I reveal some bias here but I actually found it easier. The reasons were that I knew I was going through something (a) hard/the stakes couldn't have been higher, (b) unique yet relevant to others (c) where I needed to wrestle with hard questions. I knew that if I was curious about my own treatment and the stakes were high enough that I would be speaking from a deeply authentic place. I think that's the difference. I was willing to expose my ignorance, having carried the baton to a certain point and ask for guidance.

Sometimes when shepherding a project through it's hard to get that level of deep authenticity. One heuristic to know if you're being deeply authentic is if you will ask for help and risk exposing an underbelly of uncertainty. Are you ok with that? Sometimes at work when you own the project that's a hard hurdle, for fear of coming off as incompetent. But asking the question shows confidence and competence. If you really OWN it then you should have no issue revealing non-knowing about something. Ask: do I want the answer more than the optics of looking good?

How do you know when to share? Finding this balance point has been the difference between success and failure. Here's a good formula:

  1. Gather initial inputs from experts
  2. Write a perspective/POV/post
  3. Share it early for stakeholder feedback (say 70%-80% confidence, not more). I like to frame it as a request for comments (RFC)
  4. Finalize a decision

If you don't do this one real alternative (from personal experience, not fun) is to feel as if you’re driving the car with everyone’s hand on the steering wheel. It's a great way to get nowhere.

I’d estimate that for every 10 pieces of work, perhaps 2 aren't good enough for initial inputs. The tradeoff is between sharing something too early versus risking never sharing it. This is the type of thing that with enough calibrations you can improve.

One trick that's worked for me is shifting the work and the focus away from ones-self (ego, personal hangups) and onto THE WORK. In the end people care about the success of the project and how it'll reflect on them. So focus on that aspect and get past yourself. Consider a team as a mesh of gears. The trick is to be the fast wheel so you can pull the others to your speed. This is important if you’re fast to start with (which I am).

Find the flow, jam it out in a few hours. But getting into that zone can be a challenge - especially in COVID times with children at home. I often think about a person like Michael Jordan who could turn it on EVERY SINGLE TIME. That’s consistency of a champion. In the world of building technology it’s also important to be a champion. We are all playing at the level of a professional athlete - it’s just a different arena. The standards should be similar.

So how do we get into the zone? For me, music helps. So does doing some form of fire breathing ahead of time (inspired by Wim Hoff: 30 hard breaths/3 sec in then 3 sec out). Then Coffee. These are just mechanics. The key ingredient that is necessary - but not sufficient - is self-confidence. This has always been my rate limiting factor in the times that things aren’t going well.

So there's another reason to share quickly and frequently. Work shared too slowly, or not followed through to completion will lead to erosion of personal confidence. It amounts to a withdrawal from our own personal trust credit. I used to dismiss this as an infinitely replenish-able resource. It is not. We must build our own confidence in ourselves in the crucible of real-world feedback. That's not to say we need some confidence going in but that's not sufficient. We need to know that we can handle ourselves by establishing comfort with ever-increasingly stressful situations.