Async agile 1.0, is distributed agile 2.0!
This blog expands on the ideas from “The Async-First Playbook”. You can either browse through the posts using the grid below, or start at the very beginning. Alternatively, use the search bar below to find content across the site.
Would you do that to your CEO?
The “CEO test” is when you ask yourself “Would I do that to my CEO?”. That can often help you spot behavioural anti-patterns you must correct, when interacting with your coworkers.
Our workplaces have a masculinity bias
The world of work has a toxic masculinity bias. In this post I share some thoughts about such biases.
Don't let your virtual workplace become toxic
Every work model has its pitfalls. It’s not as if a remote workplace can’t go south. In today’s post I want to explore some anti-patterns I’ve seen in remote-first and “hybrid” organisations that can make your workplace toxic. When you know of these possibilities ahead of time, you’ll be able to pre-empt them and put the right guardrails in place for your team.
4 bad collaboration habits we need to unlearn
To move away from the office mindset, then we’ll need to unlearn a few unhealthy habits we’ve picked up over the years. In this post, I want to share four of these habits. Benign as they may seem, they are pernicious obstacles in your path to being an async-first team or organisation. Let’s explore each of them and the problems they create. As we do so, I’ll outline a few alternatives to these behaviour
The next three biggest remote working superpowers
In the previous post, we discussed how written communication is the number one superpower when working asynchronously. In this post, I’m adding three more superpowers to the list. Think of these as a quartet of abilities that will help you and your team to supercharge your individual and collective effectiveness.
Distraction blocking
Reading and comprehension
Working independently
Build a mindset for change
If as a leader, agile coach or change evangelist keen on introducing asynchronous work practices on your team, you may be daunted by the potential obstacles you may face in the journey.
In this relatively shorter article, I’d like to share with you three ideas that may help you prime both your broader organisation and your team for the change. We’re not yet at the level of an implementation checklist and a playbook for individual practices will follow in due course, but for the time being, consider this as a framework to help align your team.
Why you may find it tough to introduce asynchronous work in your team
The first port of call for any change journey is your immediate team. If your colleagues don’t commit to change, it’s unlikely that even in a conducive organisational culture, a shift will happen.
As an evangelist, coach, consultant and change maker, anticipating push back from your team will help you deal with it as well. So in this article, I’d like to share with you some blockers you’re likely to encounter from your colleagues and towards the end of this piece, we’ll consider some high-level approaches to address these blockers.
Why you may find it tough to introduce asynchronous work in your organisation
Introducing change in large organisations is tough. Synchronous work has a 250 year old legacy and organisations are used to it for a number of reasons. As an advocate of asynchronous work, you need to be aware of the potential challenges you’ll face when you try to introduce a new way of working in any organisation.
This article outlines some of the obstacles you should expect.