Skip toΒ content

Collaborating in Notion: Frontend-quality rituals and projects πŸ‘©πŸ½β€πŸŽ“πŸ› πŸŒˆ

7 mins

View Comments and Reply

Transcript

Show Transcript

Hey Amanda Matri. I started a document like I promised I would, for the Intuitive pillar or whatever we end up calling this pillar that is like most customer centered.

Some of the rituals and projects that we want to take gone. So definitely treat this as ah, a collaborative document.

I really want us all to feel like we are kind of spearheading this initiative together. So I took a stab at just defining the typical model around who's going to be driving this work, approving this work, contributing to this work, and who are we informing?

So take a look at that and let me know if you have any edits. And then also just some context for I imagine we'll start sharing this with folks beyond the front end community.

So just like, what is the front end community? How does the front end community operate? Will be shepherding efforts related to the following high quality front end pillars, like secure, reliable, performant, and intuitive.

And then what is this intuitive pillar? I'm just defining that. And then also in the context section, just linking to this living document we have around these pillars, and specifically the principles for the intuitive pillar that we'll be focusing on.

So hopefully that all makes sense. And then the bulk of this document and where I would love the most help with is basically this idea around like okay, so what kinds of rituals and projects should this pillar take on?

So I basically wrote out like with the intuitive pillar principles in mind, the following are recurring rituals and one off projects that we will schedule and facilitate to improve front end quality for customers.

So I'm just saying here also that Amanda Matri and myself will host sessions and will recruit folks who present and participate.

So I definitely don't see this as, ah, us being on stage every single session. We are more the host, facilitating and helping invited guests and attendees.

So with that in mind, and hopefully this makes sense, and again, if any of this doesn't make sense, just dive in and make changes or leave comments and I'm happy to make those changes as well.

So with that in mind, I put one idea for a ritual down that Christina brought up and that I really think could be a compelling one, which is this idea of a polished party.

And I defined the timing as ah quarterly. So maybe it's quarterly and maybe it's one to two. I'm actually leaning towards 2 hours, or we do it more frequently and it's just an hour.

But sometimes I find that 1 hour sessions that are interactive they go quite fast. But on the flip side, maybe a two hour session just feels like a drag.

So we'll just have to think about that. But the idea here is that this is a recurring variety of sessions that includes snacks for all.

We'll figure out the logistics there, but I do think so many folks at Bloom are being asked to participate. So I think we should make these fun so we somehow get snacks delivered super efficiently.

Maybe there's prizes. And I was thinking the polished party could actually be not just like one kind of ritual, but it's actually like a couple of different topics.

So maybe one Polish Party is all about an academy as a topic. So it's like, academy is basically like attendees learn from invited internal and external presenters.

Or maybe the topic is actually a Fix it fest where attendees all participate in a bug bash or a debt cleanup or maybe lens updates or anything else we can come up with that's interactive and take it on as like, individual attendees.

And then I have this other idea called delight squads. I think we'll have to think more about this, but attendees participate in teams to tackle Delight related projects that are defined ahead of time.

So maybe we define a couple of projects and when all the attendees come, we basically team them up and they have an hour to 2 hours to do something that contributes towards Delight.

These are just ideas, I'm just thinking out loud. But the basic idea is to really make these feel dynamic and exciting.

Polish Party doesn't just mean one thing, it means maybe one time we're doing a training, one time we're doing fixes and another time we're focusing on Delight.

Let me know if you have any other ideas for different types of sessions or tweaks to these sessions. We can certainly talk about the logistics and details after we kind of make progress on just general definition.

But yeah, I hope that all makes sense. And then also just, I think an open question and we can figure this out as we plan logistics is like what should we do async versus sync?

I am honestly leaning towards most of this being done in sync just because we're already asking folks to take time out of their day to contribute.

So I worry about the amount of Asynch participation we'll get especially based on some of the just early progress with front end community.

I think we're all realizing we're really busy and it's hard to contribute async plus sync. And then the only other thing I've done is I've created this little table within Polish Party where we could also just start to list out some of the potential versions of these that we want to schedule.

So maybe Amanda, you have an idea for a Fix It fest or a training or a Delight Squad session that we can just put down, describe and put a date against and then we can start scheduling these out.

I should also include a description field. There we go. So, if you have some ideas for central Polish parties that we could do just start filling them in.

And then also, again, feel free to tweak any of the concepts here, or if you just want to comment, that's helpful.

And then I also left blank templates if you have other ideas for so this is just one idea of a ritual.

It's a very rich one. So we could really just start with this idea and really run with it. But we could also come up with other rituals we want to maybe schedule in the spirit of this initiative.

Or, like, one off projects. So I just left these in case you have ideas there. Like, maybe you have something in mind that would be great to take on as a one off project.

Just, like, write that out. When should we maybe do it, and what is the description? And if you don't know when, we can always figure that out later.

But I hope this all makes sense. I'm definitely figuring this out as I go, but I'm excited to figure this out together.

And then maybe once you both have had time to contribute we can share it more broadly. I'll also share this with Christina, since she's been helping as well.

Transcript

More than 21 million people across 200,000 companies choose Loom

My teammates and I love using Loom! It has saved us hundreds of hours by creating informative video tutorials instead of long emails or 1-on-1 trainings with customers.
Erica Goodell

Erica GoodellCustomer Success, Pearson

Loom creates an ongoing visual and audible experience across our business and enables our employees to feel part of a unified culture and company.
Tyson Quick

Tyson QuickCEO, Postclick

My new daily email habit. Begin writing an email. Get to the second paragraph and think 'what a time suck.' Record a Loom instead. Feel like 😎.
Kieran Flanagan

Kieran FlanaganVP of Marketing, HubSpot

Loom amplifies my communication with the team like nothing else has. It's a communication tool that should be in every executive's toolbox.
David Okuinev

David OkuinevCo-CEO, Typeform

My teammates and I love using Loom! It has saved us hundreds of hours by creating informative video tutorials instead of long emails or 1-on-1 trainings with customers.
Erica Goodell

Erica GoodellCustomer Success, Pearson

Loom creates an ongoing visual and audible experience across our business and enables our employees to feel part of a unified culture and company.
Tyson Quick

Tyson QuickCEO, Postclick