Company culture is also important to making it work, in my mind. p2 is viewed as the source of truth for many conversations (including meeting notes and summaries of slack conversations), which is part of how it works. Additionally, anyone across the company is empowered to post on any p2 to start conversations, ask questions, or kickstart lengthy, technical discussions.
In response to another commenter, Automattic has been using p2 as its main form of async internal communication for years before it even hit 1k employees, so it's not the kind of thing which requires a ton of people to work. Once a few hundred people using it as the main form of async conversation, there is certainly more content than any one person can consume. :)
We have Stack Enterprise, which is permanent and searchable but admits only straightforward Q&A, no discussion.
We have Google Groups, but many employees expect them to be for announcements only, and will reply angrily to threads that are attracting long discussions. They don’t “get” mailing list culture, don’t configure their GMail filters appropriately, and feel that this is the sender’s problem.
Async decision making, such as it is, happens in Google Docs comment threads on proposals. Our auditors actually require us to click the resolve button on those threads once the proposal is accepted, so the discussion is hard to find if you come across the document later.
Now I'm at one of the big tech companies that is suddenly all-remote. I miss P2. It gives you a place where ideas can "stick" much better than with async chat, email, or wikis. At the top-level (per-team or per-project) P2s feel like much more than just another wiki aggregation page. You actually want to visit them to catch up on the latest.
The per-post threaded conversations promote more thoughtful, ongoing discussion. These naturally fade over time as new posts are made, a bit like HN or reddit. Generally this is a useful, organic default, and complements (rather than replaces) async chat.
It can be overwhelming once you're interested in tracking many P2s. But you can address this with discipline, culture, and more tools.
I don't get it. Looks like a regular news wall with endless scrolling and comments expanded.
Except anybody can post an announcement on top? and the previous ones disappear under the constant flow?
tl;dr: nah, doesn't need thousands of people to be useful.
Obligatory "Mean Girls" ;) https://www.youtube.com/watch?v=Pubd-spHN-0
My P2 posts are quite often 1000 chars+, I sometimes even write footnotes.
(I work for Automattic)
Reading P2 tends to happen in between tasks, like email, but it's a little harder to keep track of what you did and didn't read, or be aware of an important comment that got by you.
It fixes a lot of things for async work that email falls short of, but probably still needs a few more tweaks to make it slightly more manageable given its nature.
Yea - I see it as weird too. The only reason I'm still an advocate for WordPress are the self-host-ability/full customization aspects. Otherwise, you're just another Medium that's going to take my data and use it against me.
Honestly, I wouldn't touch this until Automattic publishes the code. To a old-timer who's been leveraging WP for well over a decade: ew.
This version is also a theme and will be released for self hosting in future too.
First there was actually the Prologue theme, then P2 was the second version (~2010?). Then O2 because “communication is oxygen for an organization”. Now back to P2 because that is the name that has stuck and everyone uses.
We (Automattic) use it as both a noun and a verb at this point. P2 or it didn’t happen.
Topics. Sub forums. View unread, link to posts, quoting, attachments. Voting. Reply by email. So many great things came from forums.
What about sub 100?
We are fully distributed. Lots of Slack and Zoom. Trying to create a central source of truth in Notion but that feels very static.
Any smaller teams using this?
I've spend years trying to solve the problem - how do you get the average person writing more at work? What I've come up with resembles a company "journal", but helps you automate any routine communication or update (daily standup, weekly update, retros, etc).
Would love any/all feedback on the idea, here's the website (https://www.friday.app/). You can use it as an individual, team, or with the entire org.
Some people have many answers, but other people have many questions. So I think encouraging people to ask more (even stupid) questions might be a way to get the discussion going.
Its pages can be typical wiki-docs but also things like internal news posts or discussions, and is organized into subsites for different teams/projects.
At this point though, I think Notion may present a better solution going forward.
Can anybody contrast both ? Zulip would bring the best of slack and p2 right?
This is what i believe goes against the open principles evangelized by WordPress.
I don’t think the world needs more things like this.
Give me something open source that I can hack on, or run on my own machine, ideally in a modern language.
This feels like too little, too late, in a world already cluttered by shiny, hosted tools that offer you zero privacy from the hosting provider (which you can’t change).
A company that does things like this can’t really be said to have a commitment to free software. Free software is like veganism or respect for the rule of law in society: it’s not something you do sometimes, when you feel like it. Either you believe in software freedom, or you do not.
You should not be writing source code that you expect your customers to use but not be able to read and modify.