Sharing knowledge and collaborating on docs: the Unow product team's processes
Unow is building a space for professional online courses that the team also happen to create in-house. The team of now 35+ employees is distributed across Paris and Lyon. We talked with Christelle, PM at Unow, to talk about how the product and tech teams integrated Slite into their workflows. We discuss:
The importance of writing things down
The need for a better collaborative docs space for the product team
Their most successful Slite use cases
Writing things down: fixed knowledge vs. collaborative documents
Everyone can and should create and share their knowledge at Unow. When Christelle joined the Product team in January, they already had places where they were writing things down: an internal wiki for "fixed knowledge" and Google Docs for "flow and collaborative docs".
The biggest issue they encountered was that flow in Google Docs were extremely difficult to handle as a team: they were losing trace of the docs and had a hard time finding the docs unless they got their hands on the link.
The issue with that is that their product specs in Drive were important sources of truths of their ongoing project's status. A doc that everyone should and would refer to, yet a hassle to access.
“Slite channels are public by default, everyone is informed when a new doc is created and can benefit from it” —Christelle Mozzati, Product Manager at Unow
Setting up shop in Slite
So when they found Slite, as avid Slack users, the first reflex was to merge their flow docs into Slite. It made sense because they mirrored their channel structure in Slite with their existing one in Slack. "The same way we use Slack to talk about specific things, Slite is a place where we can work on our specs and our overall organization."
They organize their Slite channels in teams (ie. Marketing, Sales, Product...) or projects (a specific feature, for example) in the same way they've always done in Slack. It made the overall on boarding on Slite of the Product and Tech teams seamless and obvious. Most of all, as Slite becomes the only place they write up their product specs, they've created a template and it's generally easier for everyone to access and pitch in.
"Slite allows us to go one step further on our two most important team values: team first and showing care. Since channels are public by default, everyone's informed when a new doc is created and can benefit from it", Christelle told us.
Their use of Slite goes beyond product specs: they've also put a lot of their tech process docs and general onboarding documents in Slite to begin to centralize their "fixed knowledge" and "flow docs" in one place. For example, they've started to use Slite to onboard new team members and tech processes can be found in Slite.
“For our product team, Slite is our collaborative signle source of truth for our specs, processes and meeting notes” —Christelle Mozzati, Product Manager at Unow
What’s a Rich Text element?
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
Static and dynamic content editing
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
How to customize formatting for each rich text
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Laure Albouy is Slite's first marketing hire and in charge of Product Marketing. Her role? Making sure our users get the most out of Slite -- including guides, product announcements, market research and more. Laure lives in Paris and is a pasta afficionada.
No items found.
Put some humanity back into your remote life. Our learnings, straight to your inbox.
All set! Next piece will land straight in your inbox.
Oops! Something went wrong while submitting the form.
No fluff, no spam, no corporate filler. Just a friendly letter, twice a month.
How Zenchef brought knowledge sharing at the heart of their collaboration
When an industry goes "Boom!"
How a CMO built an internal knowledge base to keep up with the roaring blockchain industry.
Mothership's recipe to a successful remote team: processes and excellent tools