This Meeting Didn’t Need To Be An Email

(This column is posted at www.StevenSavage.com, Steve’s Tumblr, and Pillowfort.  Find out more at my newsletter, and all my social media at my linktr.ee)

There’s a joke we’ve all heard – and probably repeated – “this meeting could have been an email.” It’s popular because it’s true, we’ve all had the meeting that could have been an email, and let’s be honest we’ve probably held those meetings. We’re all part of the problem.

But I’d like to argue that this joke wrong in some cases. That meeting didn’t need to be an email. That meeting didn’t need to exist in any form – email, chat, and so on – and that’s the real issue.

Am I going to analyze a joke about having too many meetings? Yes I am. If you don’t like it, send me an email.

So let’s take a look at this joke. We wasted a bunch of time getting people into a room, virtual or otherwise, to discuss things or share data. Some of us probably didn’t need to be there, certainly some of us didn’t want to be there. The end results probably could have been done in an email, not necessarily even a chain, just one.

The joke isn’t quite as funny when you analyze it, is it?

But here’s the thing. The meeting in question – or the email in question – is held because something had to be settled or something had to be done, or something had to be cleared up. Be it a meeting or email, something had to be done because something else didn’t.

So the real question is what was needed to avoid the meeting or the email that could have replaced it.

Was there some document that didn’t exist so people had to discuss it? Was there a signoff that could have been automated but is instead 5 people in meeting knowing 3 of them didn’t need to be there? Did people just not talk in the past and now you’re sitting in an actual room for hours because you could have done something earlier?

That meeting didn’t need to be an email. It needed to be a process. It needed to be an accurate help document. It needed to be a form in your software. It needed to be something that didn’t waste people’s time. It needed to not happen.

Now I am going to defend meetings as I schedule them as part of my job. But a good meeting is held when needed and should prevent even more time-consuming things from happening. A good meeting prevents other meetings.

But we shouldn’t just replace meetings with email. We have to make as many unnecessary.

Steven Savage

Can You Imagine Starting?

(This column is posted at www.StevenSavage.com, Steve’s Tumblr, and Pillowfort.  Find out more at my newsletter, and all my social media at my linktr.ee)

I was going to do a post on media forms and what we can learn about today’s media from the Dada art movement, but Serdar had to go and get all brilliant and discuss how people can’t and shouldn’t wait for the right conditions to start something. It deserves it’s own blogpost, so me discussing art movements has to wait.

Serdar points out how people wait for the right conditions and how you can always find advice, from Doris Lessing to Buddhism that the time is never right, never perfect. The problem of course is helping people understand it’s time to get off their butts and do it. If you’ve ever tried to get someone – or yourself – “going” you know what I mean.

Now I work with Agile methodologies, as anyone who’s known me for five minutes is aware. Agile is about breaking work down, doing it in order of importance, and very importantly getting going. Just start and take feedback later – in fact doing something means you at least get feedback so you can do better (or even just quit). Agile isn’t “move fast, break things” it’s “move fast, make things.”

Thus as you can imagine I have to help people “get started” and “just get going.” Which should be easy as I have a lot of experience, a lot of certifications, and a very irritatingly effective attitude of “just do it.” Should be easy with a person like me, right?

Of course you know the answer is that it’s not, which irritates me at an irrational level. Sometime I “buddy up” with “just give it a try.” Sometimes I “Agile harder.” Sometimes I end up a therapist. But Serdar’s post made me realize in some cases what people lack is the ability to imagine starting. It’s easy to look at a big project or some ambitious idea and be so overwhelmed you can’t imagine starting – and in some cases it’s easier to imagine failing.

It’s easy to imagine not starting. I’ve realized as I mull offer Serdar’s writings that people like me are trained imagining how to start, other people have that imagination of how to start and we have to help others develop that capacity.

Of course easier said than done, and each person or group is an individual case. Maybe we have to inspire. Maybe we have to (in some cases literally) draw a picture. Maybe we encourage a prototype. Maybe we just “give it a shot.” But we need people to be able to see starting despite “imperfect” conditions.

Which means when we’re trying to help someone overcome a fear of imperfect conditions, our first job might be to help them see what’s possible. But the next job is helping them develop that imagination.

Steven Savage

Five Words To Victory

(This column is posted at www.StevenSavage.com, Steve’s Tumblr, and Pillowfort.  Find out more at my newsletter, and all my social media at my linktr.ee)

Serdar’s latest book (which I assure is a doozy) is a challenging one for him to write.  It’s the kind of challenge where writing it requires trusting yourself, as he notes in this blog post.  As he explores this need for self-trust – a factor he and I have both written on – he said something tangential that is very important in facing challenges:

“That said, every single time I’ve started to work on a project on a sentence-by-sentence basis, as opposed to all the plotting and planning I’ve made ahead of time, the sentence-by-sentence work is what brought everything together.”

These words reminded me of a rule I’ve heard again and again – when facing a challenge, break down your work enough that you find something you can do in five minutes then do it.  That lets you get going, take a step towards your goal – and possibly figure what to do for the next five minutes.  String together enough five minutes and you’re done.

At the start of a project things look insurmountable.  You doubt you can do it, but five minutes is all you need to realize maybe you can.

You can do this as writing as well when you’re not sure you can do a particular work.  You don’t have to write for five minutes on a project you’re not sure of – try five words.  Then five sentences, even if you have to do it five words at a time.  Then maybe five paragraphs.  Then, well, see how far you can go.

You don’t have to use what you’ve written.  You’ll almost certainly change it, edit it, or even throw it the hell out.  But at least you’ve got something to explore what you want to make and figure out how to do it.

But you have to start with those five words.

Most success is due to momentum.  You don’t really know what you have to do to complete a book or any other writing project.  You just have a start, a finish, and maybe a vague roadmap if that.  Even if you have a detailed plan it is going to change as you write and make discoveries about your work. 

So you might as well start with something small, like five words.

Steven Savage