Desk Adoption
Rollout and tool sprawl
Follows adoption, internal usage rules and the work of reducing overlap between collaboration platforms.
Team Software Guide
Team Software Guide covers chat, documents, meetings and knowledge tools, and how Australian teams cut overlap across them.
Not yet published. What we cover, and who covers it, is set out below.
What we cover
Team Software Guide is for Australian organisations trying to make collaboration tools work without adding more of them. It will cover chat and messaging, shared documents, meetings, wikis and permissions, with a steady eye on costs and overlap.
Written for Workplace technology managers and team leads in Australian hybrid organisations.
- 01Chat & Messaging
- 02Shared Documents
- 03Meetings
- 04Knowledge & Wikis
- 05Roles & Access
- 06Tool Overload
The desks
Each desk is part of the editorial team with its own beat, not an individual. The byline names the desk, and the structured data identifies it as an organisation.
Desk Collaboration
Chat, documents and meetings
Covers the day-to-day tools Australian teams use to talk, write and meet.
Desk Knowledge
Wikis and shared drives
Looks at how teams store, find and retire information across wikis and shared drives.
How we work
Written for the people who decide
Choosing and running the collaboration tools Australian teams rely on. Articles are written for people with a concrete decision in front of them, not for those trying to sell one.
Numbers name their source
Every figure says where it comes from and when it dates from. Where the industry disagrees, that is stated, rather than quietly taking a side.
Nothing tracks you here
No cookies, no analytics, no third-party scripts. If that ever changes, the privacy policy changes the same day.
Where should we start?
The order is not set yet. If there is a question you have had to answer the hard way yourself, send it to the editors. It is the most useful thing you can send a publication that has not yet begun.