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.
AI and the scarcity loop
The unpredictable nature of generative AI can often feel as addictive as gambling. Addictive services often get enshittified, and can also be candidates for a classic bait-and-switch.
The trouble with AI overconfidence
As the circular funding economy of AI becomes more transparent, innovation slows and costs increase, it may help us all to temper our AI enthusiasm. There are many indications that the current state of generative AI is neither essential nor as transformative as the frontier AI companies will have us believe. If anything we could make the case that generative AI is a net negative for most stakeholders.
AI bipolarity
I’m “AI bipolar” - an enthusiast and a sceptic. Here are some of the reasons I blow hot and cold with AI.
The four most common agile fig leaves
When teams and managers forget about the values and sentiments driving the agile movement, practices become convenient fig leaves to cover up the “inanities of corporate life.” I've observed four such fig leaves most often.
The wrong kind of async
Not all asynchronous collaboration is productive. There are four ways I see teams get “async” wrong.
The dark side of remote work
All’s not well in remote work paradise. For many employees a remote work arrangement is a Faustian bargain. They have to endure the dark side of remote work.
Three work patterns that don't work for remote teams
Copy-pasting office-centric practices rarely works for remote and distributed teams. Three such practices suck, when you attempt them remotely.
I screwed up
Writing the book about “async-first” collaboration doesn’t mean that I’m immune to the status quo. I screwed up on my own rules recently, by taking a “sync-first” approach instead. And boy, did that hurt!
A tale of externalised costs
Many decisions execs take for their employees, ignore externalised costs. Mike Hopkins of Amazon claims their RTO policy has “no data” to back it. Lyft CEO, David Risher can only advocate for snacks in the office, while batting for RTO. Meanwhile, employees and other stakeholders pay for such decisions through costs to their health, productivity and happiness.
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.
Don't let group chat become a toxic time sink
Group chat can be both a helpful tool and a distraction in the workplace. While suitable for quick exchanges and simple information sharing, it falls short for more important discussions and tasks.
Busy people must collaborate differently
Well intentioned, busy people want to be collaborative. But they often end up as bottlenecks. I argue that busy people must change their model of collaboration.
7 deadly sins of knowledge management - part 2
We continue exploring the seven deadly sins of knowledge management in this week’s post. I explained three of them to you last week. Here are four more.
7 deadly sins of knowledge management - part 1
In a massively distributed world of work, effective knowledge management is a superpower for your people. On this site, we’re already discussed many things you must do, to foster knowledge sharing. This post is the first, in a two part series about things you shouldn’t do.
Shapeless days are not a badge of honour
Unpredictable days are shapeless days. This represents the classic maker-manager paradox. Makers need contiguous blocks of time to achieve meaningful outcomes. A calendar driven schedule is amongst the worst blows to a maker’s productivity. We can’t be proud of this way of working.
Offices in the cloud are just a bad idea
I notice that some teams, organisations and products are attempting to recreate an office in the cloud. This is a counterproductive trend. In this post I explain why being async-first is a better idea.