31–40 of 44 posts
Lots of comments on 1,000+ people teams. 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?
At this point though, I think Notion may present a better solution going forward.
Lots of comments on 1,000+ people teams. 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?
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.
I work at Automattic, and p2 is (in my mind) _the_ thing that makes our remote-only culture work. We don't really use email that much or other forms of async chat. When synchronous chat (like Slack) gets to be too in-depth, our motto is "p2 or it didn't happen." p2 has the widest visibility in the company -- anyone can search for a p2 post, or cross-post to other teams and divisions. Since many teams are spread acros…
We use discourse for this. Any type of forum-like product is very effective as a complement to email and instant messages for the reasons you describe. For effective remote I think it's indispensable to have: Instant messaging, email, forum, wiki. Looks like p2 might also serve as a sort of "company directory" thing, which we also use another product for, but I don't get much as value out of that.
Lots of comments on 1,000+ people teams. 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.
This is what i believe goes against the open principles evangelized by WordPress.
There is a live demo here https://p2customers.p2.blog/ 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?
My P2 posts are quite often 1000 chars+, I sometimes even write footnotes. (I work for Automattic)
Earlier quoted context omitted.
The previous version was a theme and is still available - https://wordpress.org/themes/p2/ This version is also a theme and will be released for self hosting in future too.
Wait so there was the old P2 and now there is the new P2 but at one point there was O2 which was supposed to be the next version of P2 https://geto2.com/ ?
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.
I used to work at WordPress.com (Automattic) after they acquired our startup Simplenote. P2 was great. 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…
Topics. Sub forums. View unread, link to posts, quoting, attachments. Voting. Reply by email. So many great things came from forums.
I work at Automattic, and p2 is (in my mind) _the_ thing that makes our remote-only culture work. We don't really use email that much or other forms of async chat. When synchronous chat (like Slack) gets to be too in-depth, our motto is "p2 or it didn't happen." p2 has the widest visibility in the company -- anyone can search for a p2 post, or cross-post to other teams and divisions. Since many teams are spread acros…
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.