How writing more allows you to have fewer, more effective meetings

According to research by Professor Steven Rogelberg 50% of meetings are seen as engaging, of course this suggests that 50% are not!

From my own experience I would have to agree that many meetings are not very useful. There are too many organisations having meetings that would be better as an email or a wiki document.

Read on to learn more about how to choose your communication medium and ways to improve your writing!

A nice companion to this article is this talk by Prof Rogelberg on The Surprising Science of Meetings here:

There are good meetings…

First off, not all meetings are a waste of time. Regularly getting together in person is great for teams and for working through problems. Useful meetings are ones where everyone present needs to provide input. Or sometimes it’s just great to get everyone in the same room to build relationships and be social.

Tasks like whiteboarding problems with peers in person generally leads to better solutions. Running things like project kick-offs in person is a wickedly effective method to start a piece of work with an engaged team.

There are some critical steps required to run a productive in-person meeting:

  • Send out an agenda. make sure there is a specific problem to be addressed. Actively limit the scope of the meeting.
  • Limit mandatory invitations to the right people, make invitations optional for other people.
  • Actively facilitate - make sure no one is left out and that no one dominates.
  • Ensure the agenda gets resolved.
  • Take notes. Send out a summary - private to attendees if applicable, otherwise share widely for feedback and communication. This is vital! - If potential attendees know that they will get a summary, they can choose not to attend but still get all they need from the meeting.

And wasteful meetings…

There are some common types of communications in organisations where the default mechanism is create a meeting but you might be just as effective by sending a written communication:

  • Status Updates
  • Information Sharing
  • Decision Making **

There are some exceptions of course - “townhalls” and such are nice to show presence of leaders. But in general if your communication is one way information passing then you should consider just emailing it instead.

** Decision making is in this list because in order to make a good decision everyone needs context. You can have a short meeting to decide something, but everyone should have already been sent all the required context and given time to digest it.

A decision making meeting where everyone is seeing the information for the first time is a waste of time. You’ll get a poor decision and you’ll have to re-visit the topic again. Or worse, you’ll get a decision that is not supported by the team and you’ll have to re-visit the topic again.

Often there is one decision maker anyway. Just commit, decide and then communicate the decision with the reasoning.

Writing to replace information sharing meetings

To handle these information sharing scenarios you should instead write a document (or email) and ask for feedback.

Maybe afterwards you can organise a meeting to discuss feedback but start with a well researched and written document. Even the meetings you run in person are far more effective if you write appropriate material before and after.

  • Writing encourages you to think through the problem before involving others.
  • Reading a written communication is asynchronous, allowing your consumers time to digest your message and do any exploration and investigations themselves.
  • Writing, sharing and asking for input as a response or comment can make costly meetings obsolete and opens the discussion up to a much wider audience.
  • Written communications provide a knowledge-base and record of decisions for the entire organisation.
  • You’re not monopolising time

You compliment writing with relevant meetings afterwards. They will re-enforce your message. You’ll be surprised how little you need to do these follow-ups.

Systems and checklists for writing

I use the following steps, systems and checklists to write effectively.

Start at the end - identify your desired outcome

You need to start with writing down the specific outcome you want. Start at the end. What is the pain for the organisation that you’re trying to relieve?

Write down who your audience is and target the contents to them by identifying how the change or information will benefit them.

Remember this writing is not going to be about what you want, but instead how it will benefit your audience.

Think about what they are optimizing for and how you can help that. You should try to target one audience at a time. For example this document…

Desired Outcome Audience Benefits to them
More peers using the written form instead of ad-hoc meetings Leads of creatives Less time in meetings, increased audience, better decisions

If you’re struggling to frame the content as benefits to the audience, you might be shouting something no one wants to hear. Reconsider sending the content.

Keep great research notes

Researching is very specific to your content but I personally need a storage system. I’ve tried microsoft one note, evernote, notion and trello in the past

Now I use Obsidian for all my notes. It’s just simple, fast and it works.

The actual writing

The writing is going to be very different for different organisations, topics and audiences.

I’ve taken some amazing lessons from the book On Writing Well by William Zinsser.

For technical writing you should try to

  • Start with a summary that is easy to digest.
  • Present a single piece of interesting information.
  • After presenting the audience with one piece of new information think about what question they will have.
  • Answer that question in your following paragraph and provide another nugget.
  • Repeat.

Here are some other structures/systems for how to approach content.

AIDA - Attention, interest, desire, action or agreement

Start by getting the readers attention. Then build their interest - what’s in it for them if they continue to participate?

Speak to their desires and finish by specifying the action they need to take next.

Try to elicit the audiences’ emotions, but never be manipulative.

Borden Approach

Your audience will go through states as they consume your content. When you start they wont care much about what you’re saying. Again you need to catch their attention, fill in the details and finally specify the call to action.

  • Ho-hum: introduction, the audience is bored, get their attention
  • Why bring that up? - build a bridge to get the audience to understand why it relates directly to them
  • For instance: give the audience specific concrete facts and stories to get them thinking
  • So what?: The call to action. what do you want them to do?

Past, present, future

For this type of writing follow this pattern.

“There was a time when, but today things have changed, as we look into the future…”

Writing to convince leaders

  1. Start with the conclusion.
  2. What’s the problem you’re solving and why does it matter?
  3. What are we currently doing about this problem?
  4. What are our competitors or industry leaders doing?
  5. What’s your solution?
  6. What’s the cost?
  7. What’s the cost of inaction?
  8. The action items

(I got this list from somewhere but I didn’t note where I took it from at the time for attribution. Sorry to the author)

Review your message before publishing

Now that your piece is complete give your writing some time to settle. Do not write last minute because you want to review before publishing.

  • Do at least 2 passes to simplify the writing.
  • Get a peer review.
  • Review your publishing checklist
  • Confirm this actually provides value and needs to be sent.
  • Send 🚀

I use this checklist when reviewing my writing

  • Content: Do I absolutely have to send this?
  • Content: Is there an obvious audience?
  • Content: Does it focus on what the audience needs to hear?
  • Content: Do you address all the points you wanted to?
  • Content: Is it as short as possible?
  • Content: Is it factually correct?
  • Content: Are you engaging the readers emotions?
  • Structure: No long paragraphs?
  • Structure: Uses simple words?
  • Structure: Uses precise verbs over adverbs?
  • Structure: How does it read out lout?
  • Outcome: Will the audience need any further support
  • Outcome: Is it clear how and what the audience needs to do next?


Writing more will reduce the number of meetings you have to facilitate and attend.

Writing is not better than meetings where collaboration is key. I love a good whiteboard session or project kick-off with all stakeholders in the same room!

Writing well is difficult and takes practice. Use systems to help!

Some suggestions to start writing today:

  • Create records of your current meetings to show their value - being a note taker will make you more engaged in meetings
  • Create a clear vision for your team to show them where the backlog of work will take them
Darragh ORiordan

Hi! I'm Darragh ORiordan.

I live and work in Sydney, Australia building and supporting happy teams that create high quality software for the web.

I also make tools for busy developers! Do you have a new M1 Mac to setup? Have you ever spent a week getting your dev environment just right?

My Universal DevShell tooling will save you 30+ hours of configuring your Windows or Mac dev environment with all the best, modern shell and dev tools.

Get DevShell here: ✨

Read more articles like this one...

List of article summaries


Flexible work is here to stay but you should choose an emphasis

Note: This was written in August 2022 and I assume things will change quickly. It will be interesting to look back in a couple of years to see how much of this article is still relevant!

Most tech organisations were forced to change to remote during lockdown but haven’t explicitly changed their office attendance policy.


Hiring engineers in a candidate-driven marketplace

I’m writing this at the start of 2022 and it’s never been tougher to hire engineers. There is a very strong candidate market in software engineering at the moment.

There are roughly 1 million open software engineering roles in the USA and somewhere around 200,000 candidates. The rest of the world is having similar issues hiring engineers. Most people seem to think it will be this way for quite some time. There just aren’t enough engineers as software becomes more important to every industry.

When I started my career getting hired was skewed in favour of the hiring organisation. A candidate had to have a degree and there was no remote work so your choices for where to work were limited.

Now, in 2022 candidates with a couple of years of experience are in high demand and practises for hiring have changed significantly. You can work anywhere across a few time zones and university degrees thankfully aren’t necessary any more.

I’m mostly on the other side of interviews these days, so my are tips for other folks trying to hire engineers during these tricky times!


How engineers can help deliver software effectively

Delivery managers and team leads have the responsibility to deliver a software system via an engineering team.

Your customer wants every feature to work perfectly and they want it delivered yesterday. Your team wants to learn and grow.

It’s a tough role managing all the stakeholders and creators in a project.

Engineers can help drive great delivery by empathising with and supporting the delivery manager or leads in a project team.


Engineering systems for consistency and impact

Your most impactful engineering is done before you write any code.

It’s important to have some systems around how you approach problems to make sure you’re consistent every time.

These are some of the techniques I use to make sure I’m covering as many angles as possible when doing my pre-coding engineering.